Payment Reconciliation

A practical example

Example: month-end, a finance analyst matches a processor's settlement file against the order system.

Two refunds appear in the processor file but not in the order system, and one fee is higher than the contracted rate, so both are flagged for investigation.

What to evaluate before investing

• Can the tool ingest settlement and fee files from each processor you use, in their native formats?
• Does matching handle real-world noise, such as partial refunds, multi-currency orders, and timing differences between capture and settlement?
• Are unmatched items routed to a review queue with status tracking until each is resolved?

Limitations and tradeoffs

Reconciliation detects and explains discrepancies after the fact; it cannot recover lost funds on its own, and unresolved items still require manual follow-up.