Most payment provider invoices are not built to be read. They are summary statements generated by the provider's billing system, shaped by the provider's internal accounting, and designed to be paid rather than checked. Reading one properly means knowing what each line is, where the provider has room to be wrong, and which charges you are entitled to push back on. This guide walks through the whole document, line type by line type.
- A PSP invoice is a summary, not an itemization. It usually shows aggregates, rarely shows the contract logic behind each charge, and is structured to be approved at a glance.
- The main line types are processing fees, FX, volume tiers, settlement and payout fees, periodic and minimum fees, reversal and failed-transaction fees, pass-through fees, and credits or rebates.
- Ambiguity concentrates in three places: the FX line, where the margin hides inside the rate; the tier logic, where the wrong band quietly gets applied; and the credits, where money owed to you is simply left off.
- Every line deserves three questions: is the rate right, is it applied to the right basis, and should it be on this invoice at all?
- You cannot fully verify an aggregate invoice by eye. Real verification means reconstructing the expected charge for each transaction from the contract and comparing it back.
Short answer
To read a PSP invoice, start by identifying what the document actually is: an aggregate summary rather than a per-transaction record. Then work through it by line type. For processing fees, check the rate and the tier. For FX, find out whether the rate you received sits inside your contracted spread over the mid-market reference, because the margin is usually hidden in the rate rather than shown as a fee. For settlement and payout fees, check who was supposed to bear them. For periodic and minimum fees, check the timing and whether a ramp period applies. For every line, ask whether the rate is correct, whether it was applied to the right basis, and whether it belongs on the invoice at all. The charges most worth challenging are FX markup, misapplied tiers, and missing rebates.
Every line on a PSP invoice, at a glance
The whole invoice in one view: each line type, what it covers, where the error tends to hide, and the fastest way to sanity-check it. Each line type gets its own section below.
| Line item | What it covers | Where the error hides | How to sanity-check it |
|---|---|---|---|
| Processing fees | The core per-transaction charge, fixed and percentage | A rate or tier that does not match the contract | Match the billed rate to the contracted rate for that transaction type, corridor, and volume band |
| FX conversion | Converting one currency to another | Margin baked into the rate, with no reference shown | Reconstruct the mid-market rate at conversion and confirm the spread is within your contracted basis points |
| Volume tiers | Pricing that steps down as volume rises | A higher-priced band applied, or volume not aggregated | Confirm your aggregate volume qualified for the band that was billed |
| Settlement and payout fees | Paying funds out, including intermediary deductions | Charges netted at settlement that the contract excludes | Check who was meant to bear the fee and whether it was excluded from netting |
| Periodic and minimum fees | Recurring platform fees and monthly minimums | Timing: charges billed outside the contractual window | Check the charge date against any ramp or waiver period |
| Reversal and failed-transaction fees | Returned, reversed, refunded, or failed transactions | Fees applied where the contract waives or reduces them | Confirm the fee should apply at all, and check for duplicates |
| Pass-through and scheme fees | Third-party network, scheme, and regulatory costs | Margin added on top of the true third-party cost | Tie each charge back to the underlying third-party rate |
| Credits and rebates | Money owed back to you | The line that is simply missing | Confirm every rebate or credit your contract entitles you to appears |
First, work out what you are actually looking at
Before reading any line, establish two things about the document.
Is it an invoice or a settlement statement? An invoice bills you for fees after the fact. A settlement statement shows fees already deducted from money that flowed through. The distinction matters because settlement-side deductions are money that is already gone, which makes them harder to recover and easier to overlook. Many providers split charges across both, so a fee missing from the invoice may have been taken at settlement instead.
Is it itemized or aggregated? Most PSP invoices show totals by fee type or by period rather than a row per transaction. An aggregate is convenient and unverifiable: a single "FX fees: $48,200" line cannot be checked without the underlying transactions behind it. If your provider offers a transaction-level export, that file, rather than the invoice, is the document you actually need to verify anything.
Once you know what the document is, read it line type by line type.
Processing fees
What it is: the core charge for moving a transaction, billed as a fixed fee per transaction, a percentage of value in basis points, or both. This is usually the largest line.
Where ambiguity lives: in the rate and the tier. Your contract sets a specific rate for a specific transaction type, corridor, and volume band, and the invoice may apply a different one. A few basis points of deviation is invisible per transaction and material across a quarter. This is the most common discrepancy of all.
What to challenge: any rate that does not match the contracted rate for that transaction's actual properties. Confirm the fixed and percentage components separately, since providers sometimes bill both where the contract specifies one.
FX conversion
What it is: the cost of converting one currency to another. It is the most opaque line on the invoice, because the margin is usually baked into the exchange rate rather than shown as a separate fee.
Where ambiguity lives: inside the rate itself. Your contract typically specifies a spread, measured in basis points, over a mid-market or interbank reference rate. The invoice shows a single blended rate and no reference point. Whether you were charged within your contracted spread can only be answered by reconstructing the reference rate at the moment of conversion and comparing it to the rate you received.
What to challenge: any conversion where the implied spread exceeds your contracted basis points. This is where the largest silent losses sit, because FX spreads commonly add far more to cross-border cost than the visible transaction fee, and almost no one checks them. The difference between an FX spread and an FX markup is worth understanding in its own right before you negotiate this line.
Volume tiers
What it is: pricing that steps down as volume rises, so transactions above a threshold are charged at a lower rate.
Where ambiguity lives: in which band was applied and how volume was counted. Tiers depend on aggregating volume correctly, often across multiple entities or corridors, and the provider's billing system may default to a higher-priced band when that aggregation is incomplete on their side. The fee type is right; the tier is wrong.
What to challenge: any period where your aggregate volume should have qualified for a better band than the one billed, and any case where volume across your entities was not combined as the contract allows.
Settlement and payout fees
What it is: charges for paying funds out, including payout-method fees, local rail versus SWIFT differences, and intermediary or correspondent bank deductions.
Where ambiguity lives: in who was supposed to bear the fee and whether it was netted from settlement. Contracts often specify which party absorbs intermediary costs and which transaction types are excluded from netting. Charges deducted at settlement that the contract reserves for invoice-side billing, or netted off payouts the contract excludes, are easy to miss because they never appear as a clean invoice line.
What to challenge: any settlement deduction applied to a transaction type the contract excludes, and any intermediary fee the contract assigns to the provider rather than to you.
Periodic and minimum fees
What it is: recurring charges that are not tied to a single transaction, such as a monthly platform or account fee, and minimum monthly fees that top up your bill when transactional charges fall below a floor.
Where ambiguity lives: in timing. A monthly minimum applied before a contractual ramp period ends, a platform fee billed for a period the contract excludes, or a minimum true-up calculated on the wrong base are all clause violations rather than arithmetic errors, and they only surface if you check the charge date against the contract terms.
What to challenge: any periodic fee billed outside its contractual window, and any minimum top-up applied during a ramp or waiver period.
Reversal, chargeback, and failed-transaction fees
What it is: charges associated with returned, reversed, refunded, or failed transactions.
Where ambiguity lives: in whether the fee should have applied at all. Providers sometimes charge full processing fees on transactions that never completed, or apply reversal fees the contract waives below a threshold.
What to challenge: fees on failed or returned transactions where the contract specifies a reduced fee or none, and any duplicate charge where the same transaction appears to have been billed twice.
Pass-through and scheme fees
What it is: third-party costs the provider passes on to you, such as network, scheme, or regulatory fees.
Where ambiguity lives: in whether the pass-through was marked up. A genuine pass-through should match the third-party cost exactly. Some providers add margin to it and present the total as a single pass-through line.
What to challenge: any pass-through fee you cannot tie back to the underlying third-party rate, especially where the contract states these are billed at cost.
Credits and rebates
What it is: money owed back to you, including volume rebates, performance discounts, and corridor-specific reductions.
Where ambiguity lives: in the line that is not there. This is the only category where the error is an omission. A rebate your contract entitles you to is simply left off the invoice, and because nothing is shown, nothing prompts you to question it.
What to challenge: any rebate, discount, or credit your contract specifies that does not appear. This requires knowing your own entitlements well enough to notice their absence, which is exactly why omitted credits are among the most reliably missed items on any invoice.
The three questions to ask of every line
You do not need to memorize the categories. You need three questions, applied to every charge on the document.
Is the rate right? Does the rate billed match the rate your contract sets for this exact transaction type, corridor, and volume band?
Is the basis right? Was that rate applied to the correct amount, the correct count, or, for FX, the correct reference rate?
Should it be here at all? Is the charge inside its contractual window, of a type the contract permits, free of duplication, and is anything the contract owes you actually present?
Almost every PSP invoice error answers one of those three questions wrong.
What you cannot do by eye
Reading this closely makes you a sharper reviewer of an invoice. On an aggregate summary, that is still not the same as verifying it. The questions above all resolve to one underlying task: reconstructing what each transaction should have cost under the contract and comparing it to what was actually charged. On a handful of transactions you can do that by hand. On real volume you cannot, which is why catching these errors reliably means pricing every transaction against the contract automatically rather than reading a summary closely. That automated approach is known as fintech infrastructure verification, and it is the difference between suspecting a charge is wrong and being able to prove it.
A quick checklist
Before approving a PSP invoice, confirm:
- You have the transaction-level data behind the aggregates, rather than just the totals.
- Processing rates match the contracted rate for each transaction's type, corridor, and tier.
- The implied FX spread sits within your contracted basis points over the mid-market reference rate.
- Volume was aggregated correctly and the right tier was applied.
- Settlement deductions only cover charges the contract permits to be netted.
- Periodic and minimum fees fall inside their contractual windows.
- Failed, reversed, and refunded transactions were charged correctly or not at all.
- Pass-through fees match the underlying third-party cost with no added margin.
- Every rebate, discount, and credit your contract entitles you to actually appears.
The bottom line
A PSP invoice is a summary written to be approved, not audited. Reading it well means treating every line as a claim to be tested against the contract: the right rate, on the right basis, legitimately on the document, with nothing owed to you left off. The lines worth your attention first are FX, where the margin hides in the rate, tiers, where the wrong band slips in, and credits, where the error is an absence. Reading closely catches some of it. Verifying every transaction against the contract catches the rest.
Frequently asked questions
How do I read a PSP invoice?
Start by identifying whether the document is an invoice or a settlement statement, and whether it is itemized or aggregated. Then work through it by line type: processing fees, FX, tiers, settlement and payout fees, periodic and minimum fees, reversal fees, pass-through fees, and credits. For each line, ask whether the rate is correct, whether it was applied to the right basis, and whether it belongs on the invoice at all.
What are the main line items on a PSP invoice?
The common ones are per-transaction processing fees, FX conversion charges, volume-tier pricing, settlement and payout fees, periodic fees such as platform and minimum monthly fees, reversal and failed-transaction fees, third-party pass-through and scheme fees, and credits or rebates owed back to you.
Which PSP invoice charges are most often wrong?
FX markup, where the margin is hidden inside a blended rate; misapplied volume tiers, where a higher-priced band is billed than your volume qualified for; and missing rebates or credits, where money owed to you is simply omitted. Rate deviations on processing fees are the single most frequent error.
Why is the FX line on a PSP invoice so hard to check?
Because the FX margin is usually built into the exchange rate rather than shown as a separate fee. The invoice displays one blended rate with no reference point, so confirming whether you were charged within your contracted spread requires reconstructing the mid-market reference rate at the moment of conversion.
What should I challenge on a PSP invoice?
Any rate that does not match your contract, any FX spread wider than your contracted basis points, any tier that does not reflect your actual volume, any settlement deduction or pass-through the contract does not permit, any fee billed outside its contractual window, and any rebate or credit that should appear but does not.
Can I verify a PSP invoice manually?
At small volume, yes. At real transaction volume, no, because verification means reconstructing the expected cost of every transaction from the contract and comparing it back, which is a per-transaction task. Reading an aggregate invoice closely helps you spot candidates to challenge, but full verification requires pricing each transaction against the contract automatically.
