Read this before you start testing. It explains what the app is for and what "working correctly" looks like.
When a parent needs to prove in court how much they spend on their child — tuition, medicine, groceries, school supplies — they need receipts. Not just a list, but a paper trail that a judge and a lawyer can verify. Proof builds that paper trail automatically.
A parent — usually a mother — who is either in the middle of, or preparing for, a legal case involving child support or custody. She may have years of expenses that she needs to document going back 1–3 years. Proof helps her turn that backlog into a court-ready record.
Three ways:
① Bank and GCash emails — The app connects to Gmail and reads her BPI transfer notifications, GCash payment confirmations, and shopping receipts from Shopee, Grab, etc. These become transaction records automatically.
② Physical receipts — She (or a helper like you) takes a photo of a paper receipt. The app reads it using AI and matches it to the bank record for the same purchase.
③ Manual entry — For cash purchases with no trail, she types it in herself.
A court-ready document — a clean, printable record of all expenses with dates, amounts, store names, and the source of each entry (bank email, receipt photo, or manual). Her lawyer submits this to the court. Every entry links back to a real email or receipt that can be independently checked.
This is not a budgeting app where rounding errors don't matter. If the app reads ₱350 as ₱3,500 on a receipt and it ends up in the legal document, that's a problem in court. Opposing lawyers will look for errors. Your job as a tester is to catch those errors before a real document gets filed.
Use the "Bulk upload receipts" button. The app will try to read the receipt automatically using AI (OCR).
It should extract: the store name, the date, and the total amount. These three things are the minimum.
If there's a bank email or GCash record for the same purchase, the app should link them together automatically.
You'll see a review screen. If the amount or store name is wrong, you can fix it. If it looks right, you confirm.
The purchase now shows a receipt attached status, and it's part of the legal record.
— The store name matches the receipt (e.g. "Puregold Molino", not just "Puregold" or a blank)
— The amount matches exactly (down to the centavo)
— The date is correct (watch for MM/DD vs DD/MM confusion)
— After confirming, the purchase shows receipt attached
— A photo of the receipt is visible inside the purchase record
The receipt says ₱350.00 but the app read ₱3,500.00 — or any mismatch at all. Always cross-check the physical receipt against what the app shows before confirming.
The app shows "GCash", "Unknown", or a completely different store. The receipt should tell you the real name — if the app got it wrong, flag it.
The receipt says June 5 but the app says May 6. This is a common OCR error (day and month get swapped). Flag every date mismatch.
You confirmed the receipt but the purchase still shows pending or no receipt icon. Something failed silently — flag it.
The screen goes blank, shows an error message, or stops responding. Note exactly what you were doing right before it happened.
Especially on iOS — if the app asks for camera permission and you allowed it but the camera still doesn't open, that's a bug.
When you find something wrong, send a message with:
1. What you were doing — e.g. "I was uploading a Puregold receipt from March 2024"
2. What you expected — e.g. "Amount should be ₱487.50"
3. What actually happened — e.g. "App showed ₱4,875.00"
4. A screenshot — always include one if you can
Don't fix it yourself or skip it — log every mismatch, even small ones. Small errors in a legal document matter.
Receipt attached — done, receipt is saved ✓
Pending — receipt is expected but not yet uploaded
Lost the OR — user said the receipt is lost; a note explains why
No receipt — no receipt and no explanation (weakest record)