Does matching hold up under a financial audit?
Every action is written to an immutable log with its date and timestamp, the transaction or notification identifier, the user who performed it and the action type, whether match, match later, withdraw, discard or close out. Reasons are stored alongside the actions that require them. Logs filter by date range, identifier, status and user action, register closure logs summarize a full period, and an exportable audit file can be generated at any time.
In detail
Yes. Every matching action is written to an immutable log, so the path from raw notifications to reported totals can be reconstructed.
What each log entry records
- The date and timestamp.
- The transaction or notification identifier.
- The user who performed the action.
- The action type: match, match later, withdraw, discard or close out.
- The reason, for actions that require one.
Logs can be filtered by date range, identifier, status and user action. Register closure logs summarize a full period, and an exportable audit file can be generated at any time for an auditor or an internal control team.
Why it holds up
Auditors look for three things: that totals can be traced to source records, that exceptions were handled by authorized people, and that closed periods were not altered afterward. The log answers the first two, with a dedicated permission required for withdrawals. Close Out answers the third by locking a register once it is finalized.
Automatic matches are traceable too, because the strategy that resolved each transaction follows a documented cascade. Your merchants' finance teams can explain why two records were linked, not only that they were, which is what turns a reconciliation into evidence.