Understanding sync exceptions
Field agents collect cash where there is often no signal. Every offline collection is queued on the device and synced when connectivity returns — but if a write cannot be reconciled cleanly, it lands in the sync-exception queue instead of vanishing. Because these exceptions represent money that may have moved, they are the highest-priority alerts in the portal.
How a sync exception arises
When an agent records a payment offline, the receipt is written on the phone and queued. On reconnection the app replays those writes to the server. Most sync automatically. A sync exception is raised when a queued write cannot be applied cleanly on arrival — for example it does not reconcile against the expected loan or amount.
Why they are treated as money-authority alerts
A sync exception is not a cosmetic glitch — it means a cash collection is captured on a device but not yet confirmed on the books. Until it is resolved, there is a gap between what the borrower believes they paid and what the ledger shows. Left unresolved, that gap can cause a borrower to be wrongly chased for money they have already handed over. That is why the exception queue is surfaced as a priority: real money is in question.
The design goal is that a failed sync is recoverable, never lost. A collection that cannot sync drops into the exception queue for review — it does not silently disappear, and the borrower's receipt still exists on the device.
What to do with them
Exceptions are meant to be worked down to zero, not left to accumulate. Each one is reviewed and cleared through the resolution workflow so the field-collected payment is either correctly posted or correctly rejected — see “Resolving a sync exception.”