Reconciliation and Reporting
Close merchant books with daily and period reconciliation workflows and clear mismatch diagnosis paths.
#Purpose
Defines how merchants reconcile transaction, settlement, payout, refund, and dispute data into period-close outputs.
#
- Access to transaction exports, settlement reports, payout reports, and internal ledger extracts.
- Documented tolerance policy for acceptable variances and escalation thresholds.
- Named close owner and backup approver for each reporting period.
#
- Run daily close by exporting net transaction and settlement datasets for the same cutoff window.
- Match records by canonical IDs and verify gross, fee, net, and currency totals.
- Investigate mismatches by category: missing event, delayed settlement, duplicate record, or state drift.
- Document variance resolution and rerun checks until unresolved variance is within policy.
- Complete period-close package with sign-off, exception notes, and retained evidence links.
#Expected outcomes and confirmations
- Daily and period totals reconcile across merchant and platform records.
- Unresolved variances are tracked with owner and target resolution timestamp.
- Close package is reproducible for internal review and audit.
#Common failure states
- Dataset cutoff windows are inconsistent, causing false variance.
- Missing webhook ingestion creates incomplete internal ledger states.
- Manual adjustments are made without documented justification.
#
- Re-run exports with aligned cutoff windows and compare record counts first.
- Trace mismatched IDs through event history to identify source-of-truth divergence.
- Escalate material unresolved variance with reconciliation workbook and affected IDs.
#Risk and compliance notes
- Never close period books while material unexplained variance remains.
- Store reconciliation artifacts with tamper-evident retention controls.
- Apply segregation of duties between preparer and approver where possible.