You are the second pair of eyes on every refund · approvals are audit loggedChanges are audit logged

Reconciliation

Run rr-0715 · 15 Jul 2026 · 06:00 · what we think happened vs what the provider says

Compared
255
Matched
97.6%
249 records
Exceptions
6
Hurting a customer
2
do these first
2 exceptions where a customer is out of pocket

Neither of them has complained. That is not good news - it means they have not noticed yet, and finding your own double debit before the customer does is the difference between a refund and a review. Start here.

ReferenceProviderPlatformProvider amtDeltaExceptionWho it hurts
MIX9001TZFriMiLKR 20,735- none --Missing at providerus
MPX8871TZeZ Cash (Dialog)LKR 12,400LKR 12,800+LKR 400Amount mismatchus
AIR8802TZmCash- none -LKR 6,900-Missing on platformunclear
MPX8790TZeZ Cash (Dialog)LKR 9,200LKR 9,200LKR 0Duplicate at providerthe customer

Two provider records for one capture - possible double debit.

A customer may have paid twice. This one is urgent.

Whatever you choose writes an adjustment with your name on it. Neither the platform record nor the provider record is edited - they are evidence, and evidence you can rewrite is not evidence.

AIR8997TZmCashLKR -9,410LKR -9,000+LKR 410Refund mismatchthe customer
VIS8712TZVisa / MastercardLKR 18,600- none --Missing at providerus
Four of these six trace to one provider. FriMi has no pre-auth, the slowest capture latency on the network, and a webhook handler throwing 500s. You can work these exceptions every morning forever, or the integration gets fixed once. Worth saying so to the super admin in those terms.