Prove every fee you're billed
Recivr aggregates your Visa and Mastercard invoices, normalises every billing line, and matches it against the fees it calculated for the same period — so the manual reconciliation cycle becomes a review queue.
- The full composition of your fee base, by fee and by scheme
- Exceptions with a probable cause and a trace to the rule and rate
- The fee schedule you are actually billed on, not the one you assume
Invoice billing lines
| Fee | Billed | Calculated | Δ |
|---|---|---|---|
Clearing · intra non-EEA 2LY0011C | €4,612.08 | €4,612.08 | — |
Acquirer non-EEA CNP 3B1102147 | €4,042.33 | €4,042.33 | — |
Settlement processing 3F3305021Tier boundary applied at ICA level, not BID | €2,884.10 | €2,741.62 | +€142.48 |
EMV 3DS authentication 3H4095056 | €1,896.30 | €1,896.30 | — |
Recurring acquirer fee TACR021Rate change effective 12 Aug, billed from 1 Aug | €612.55 | €598.20 | +€14.35 |
Lines matched
94.2%
1,284 of 1,363
In review
79 lines
each with a cause
Value in query
€1,864
0.42% of invoice
Composition
Find out what you are actually paying for
A consolidated invoice tells you the total. Recivr tells you the shape: which fees dominate the bill, what each one costs per transaction, what share of spend it represents, and how that has moved since the last cycle.
- Ranked by share of spend, so the material fees come first
- Volume, total, rate and cost per transaction on every line
- Movement against the previous cycle, on rate rather than total
Invoice composition
52 unique fees
- Clearing2LY0011C12.5%
- Acquirer non-EEA CNP3B110214710.9%
- Recurring acquirer feeTACR0217.4%
- Non-EEA settlement3F33050217.2%
- EMV 3DS authentication3H40950565.1%
Five fees account for well over a third of the bill. Optimising the other forty-seven is a rounding error by comparison.
Exceptions
A review queue, not a spreadsheet hunt
When a billed line and a calculated line disagree, the useful question is why. Each exception arrives with the rule and rate Recivr expected, what the scheme actually billed, the transactions in scope, and a probable cause.
- Tier boundaries applied at the wrong level
- Rate changes billed from the wrong effective date
- Fees charged on volume that should not have attracted them
Exception detail
Settlement processing · 3F3305021
Billed €2,884.10 · calculated €2,741.62 · Δ +€142.48
- Probable cause
- Tier boundary applied at ICA level, not BID
- Rule expected
- Tier 2 · 0.0130% above 2.4M txns
- Scheme billed
- Tier 1 · 0.0137%
- Transactions in scope
- 211,480
Anyone on the team can now answer “why this fee” without reopening the clearing files.
What it does
From consolidated PDF to an answerable question
Ingest and normalise
Invoices and billing files from both schemes, parsed into a common line-level model.
Match
Each billing line matched against the fees Recivr calculated for the same scope and period.
Explain
Differences tagged with a probable cause and traced to the rule, rate and transactions.
Schedule
The fee schedule and billing cycle you are actually on, made explicit.
Attribute
Portfolio-level charges pushed back down to the merchants whose volume drove them.
Optimise
The fees worth negotiating, ranked by what a basis point of movement is worth.
FAQ
Invoice reconciliation questions
What does invoice reconciliation actually match?
Every billing line on your Visa and Mastercard invoices is parsed, normalised and matched against the fees Recivr calculated for the same period. You see the composition of the invoice by fee, by scheme and by billing cycle, and where the calculated position differs from the billed one.
What happens to lines that do not match?
They become a review queue rather than a spreadsheet hunt. Each exception carries a probable cause, the rule and rate Recivr expected, what the scheme billed, and the transactions in scope — so the question moves from finding the difference to deciding what to do about it.
Can it show which fees are worth optimising?
Yes. Invoices are broken down by fee identifier with volume, total, rate and share of spend, so the fees that dominate your cost base are visible immediately — as is the fee schedule you are actually being billed on, which is not always the one you think you agreed.
How far back can we reconcile?
As far back as you have invoices and transaction data to load. Historical periods are reconciled on the same engine and rule versions that were in effect at the time, so a restated period reflects the rules as they stood, not as they stand today.
The rest of the platform
One engine, several surfaces.
Every product below runs off the same priced transaction events.
Real-time cost engine
Interchange and every scheme fee calculated in under 50 ms, at authorization, capture, refund and chargeback.
Pricing management
Set how each merchant is priced by region, card type, amount and currency, and see the margin on every transaction.
Merchant analytics
Scheme cost in basis points by merchant, MCC, card product and region, so under-priced merchants stand out.
Interchange reconciliation
The schemes' own clearing reports reconciled against your transactions, with a daily deviation in basis points.
Rule change monitoring
Visa and Mastercard releases and bulletins mapped in with effective dates, so you see what each change costs before it is billed.
Bring us last month's invoice
We will parse it, match it against calculated fees, and show you the exceptions with a cause attached to each one.