Reconciliation means comparing records and explaining differences where evidence allows. It should not mean editing the records until they agree. If a wallet history and a separate account screen appear inconsistent, the inconsistency itself is useful information to preserve.
Build a small comparison
Record the source of each entry, its original wording, amount, currency, timestamp, and masked reference. Include a column for uncertainties. An empty reference field or an unknown time zone belongs in that column rather than being filled with a guess.
Look for duplicate entries, similar amounts on different dates, or notifications that may describe the same event twice. These are possible explanations to test, not conclusions. A visually similar amount does not establish a match, particularly where more than one transaction is under discussion.
Protect the chain of context
Retain original exports or screenshots separately from personal annotations. If you make a spreadsheet, note which source supports each row. This makes it possible to revisit an interpretation when a later statement appears. Otherwise an early assumption can become embedded as if it were original evidence.
For readers considering Philippine online-payment claims claims, reconciliation does not verify a platform’s payment capabilities or the availability of GCash or Maya. It is a general record keeping practice. A successful comparison may resolve an apparent mismatch, or it may leave a documented unanswered question. Both outcomes are more defensible than declaring success or failure from a single screen whose meaning has not been established.
Use a matching hierarchy
Start with an explicit link supplied by the issuing provider, if one exists. Next compare the relevant reference, transaction type, amount and timestamp together. A match on amount alone is weak: two PHP 500 entries on the same afternoon can represent different events. Do not merge them simply to make the totals agree. Mark a possible link as tentative until something identifies it more securely.
For an illustrative reconciliation, list a PHP 500 debit, an unrelated PHP 100 purchase, and a later PHP 500 credit as three separate rows. The ending balance might equal the starting balance minus PHP 100, but that arithmetic does not prove the credit reversed the debit. It only shows a net change compatible with that explanation. A provider’s linked reference would add evidence of the relationship. Keep both the balance calculation and the event matching visible, because one checks arithmetic while the other checks what the movements actually mean.
Official reference
For wallet-specific questions, start from the GCash Help Center or Maya support. These links do not verify a gambling-service relationship.