Merchant Settlement Reconciliation for Card Payments
Retail and hospitality businesses running card transactions through in-store terminals or POS systems face a specific reconciliation challenge: the point-of-sale system records the sale at the moment it happens, but the actual settlement from the card processor comes through in a batch, net of interchange fees, sometimes a day or two later, and sometimes with individual transactions declined or reversed after the fact. Store-level or location-level staff rarely have the tools to check this, so head office finance ends up trying to match POS reports against merchant statements across many locations manually, and a location with a genuine settlement shortfall can go unnoticed for weeks.
STARTING PRICE
From €299
Standard tier · Multi-step workflow with AI extraction/decisioning and 2-3 integrations.
Get a quote →Saves roughly 4-6 hrs/week for a multi-location retail or hospitality finance team.
How the automation works
We connect your POS or terminal sales data with your merchant processor's settlement reporting and match every transaction across both, batch by batch and location by location, decomposing each settlement into its component sales and interchange fees rather than treating the net deposit as one number. Interchange fees are validated against expected rates by card type and transaction method, since these vary meaningfully between chip, contactless and card-not-present transactions, and any location showing a persistent settlement shortfall or an unusually high fee rate is flagged for investigation automatically instead of waiting for someone at head office to notice.
Process flow
- 01
Pull POS and settlement data integration
Sales data from the point-of-sale system and settlement batch data from the merchant processor are pulled for every location automatically.
- 02
Match transaction to settlement ai
Each POS sale is matched to its corresponding line in the settlement batch, handling the normal one- to two-day lag between sale and settlement.
- 03
Validate interchange fees ai
Interchange fees are checked against expected rates by card type and transaction method (chip, contactless, card-not-present), which vary and are a common source of unnoticed overcharging.
- 04
Flag location-level anomalies ai
A location showing a persistent settlement shortfall or an unusually high effective fee rate compared to peers is flagged for investigation automatically.
- 05
Deliver reconciliation by location output
A reconciled settlement report is delivered showing matched sales, validated fees and any exceptions, broken down by location for head office review.
Inputs
- POS/terminal sales transaction data by location
- Merchant processor settlement batch data
- Interchange rate schedule by card and transaction type
- Location and terminal mapping
Outputs
- Location-level reconciled settlement report
- Interchange fee discrepancy flags
- Unmatched transaction exception list
- Settlement shortfall trend by location
Works with
Prefer a fully custom build instead of an off-the-shelf integration? We scope both options during your free consultation — most jobs like this one work fine on standard connectors, but higher-volume or non-standard systems sometimes need bespoke API work, reflected in the complex tier.
Where this goes wrong if you get it wrong
- Interchange rates genuinely differ by card network, card type (debit vs. credit vs. rewards card) and how the transaction was captured (chip, contactless, keyed manually) — validating against a single flat expected rate will produce constant false discrepancies; the check needs the full rate schedule matrix, not a simplified average.
- Chargebacks and disputed transactions reduce a later settlement batch for a sale that happened weeks earlier, and if the reconciliation doesn't explicitly track the link back to the original transaction, this shows up as an unexplained shortfall in the wrong period entirely.
- A single physical location can have transactions split across multiple terminal IDs or processing accounts (a main till plus a separate outdoor kiosk, for example) — reconciliation needs terminal-level granularity that rolls up correctly to the location, or genuine location-level shortfalls get diluted and hidden in an aggregate view.
- A location with a consistently higher decline or reversal rate than its peers is often an early signal of a terminal hardware issue, a fraud pattern, or a training gap at that location — track this as a distinct metric worth investigating, not just noise within the settlement variance.
Frequently asked questions
Why doesn't our settlement deposit match our daily POS sales report?
Settlement batches include a normal one- to two-day lag from sale to deposit and are net of interchange fees, so the raw numbers won't match day to day — this reconciliation matches them correctly accounting for both factors instead of leaving finance to guess at the gap.
Can this catch a processor overcharging on interchange fees?
Yes, fees are validated against the expected rate schedule by card type and transaction method, which is specifically where overcharges most commonly hide since the rate matrix is complex enough that manual checking rarely happens.
Does this work across multiple store locations?
Yes, it's built for multi-location reconciliation, rolling terminal-level data up to each location and flagging any location showing an anomalous pattern compared to its peers.
How does it handle chargebacks that arrive weeks after the original sale?
Chargebacks are matched back to the original transaction explicitly, so the reduction in a later settlement batch is correctly attributed to the original sale rather than appearing as an unexplained current-period shortfall.