Contrepoint - Three-Way Reconciliation Engine for Orders, PSP Payouts and Bank Lines

Dashboard, three-column matching workspace with match tray, exceptions queue, exception detail and match group detail. Every exception and match group in the demo opens its own page.

Order to PSP, PSP transactions to payout, payout to bank line, and direct bank to ledger for SEPA transfers and direct debits. Each suggestion names its rule and version, such as P2B-02 v5, with a confidence score.

Fee difference, missing payout, duplicate, FX difference, refund or chargeback netted, unknown bank credit, unapplied SEPA transfer, R-transaction, short payment and timing.

Across 3 legal entities, with 8 staff users, 7 sources, 9 payouts, 13 order and ledger rows, 13 PSP transactions, 10 bank lines, 14 match suggestions and 6 match groups.

Payouts Arrive Net

Each PSP pays out gross captures minus processing fees, interchange and scheme fees, refunds, chargebacks and reserve movements. Nobody could say how much the PSPs had really charged, or whether a missing payout was a timing difference or money lost.

Every Source Speaks Its Own Format

Banks deliver camt.053 and CFONB 120 statements over EBICS, Adyen sends settlement details, Stripe balance transactions and PayPal STL reports. SEPA transfer references are often missing or mistyped, so the order number cannot always be read from the bank line.

Money That Comes Back Later

SEPA direct debits can return as R-transactions with reason codes such as AM04 or MD06, and under SDD Core a payer can ask for a refund for 8 weeks, or 13 months if unauthorised. A matched collection can be reversed long after it was booked.

A Trail the Auditors Can Follow

Entries follow the Plan Comptable Général, closed periods can only be reversed in a later one, and the ERP's FEC needs the matching fields filled. Every match, write-off and posting has to show who or which rule did it, when and why.