Key Takeaways

• The match runs across three records, not two: invoice issued, payment captured, deposit received.

• PayPal's published US rate for Standard Credit and Debit Card Payments is 2.99% plus a $0.49 fixed fee. On a $4,800 capture that's $144.01 the bank never sees.

• A refund costs more than the refunded amount. PayPal states that "the fees you originally paid to receive the payment are not returned to you".

• Stripe's default US settlement timing is T+2 business days, and one payout settles a batch of transactions, not one payment.

• Cash that arrives with no usable invoice reference sits as unapplied cash, a liability on the ledger rather than revenue.

What does a three-way match between invoice, capture, and bank deposit actually compare?

A three-way match compares three independent records of the same money, each of which can be right while disagreeing with the others. The invoice says what you asked for, the gateway says what the card gave up, and the bank says what arrived after the processor took its cut.

Two-way matching, invoice against capture, generates false alarms: it flags a fully paid invoice as short every time a processing fee lands. The bank leg turns "we're missing $414" into "we paid $414 in fees and refunds".

Why does a gateway payout never equal the invoice total?

A payout never matches an invoice because the processor deducts its fees, nets refunds and disputes into the same batch, and pays on its own settlement clock. Stripe ships a payout reconciliation report for exactly this.

Here's one batch, priced with PayPal's published US merchant rates as of August 2026.

The invoice is paid in full at $4,800.00 and the bank shows $4,385.99. That $414.01 gap contains no missing revenue. Each piece of it comes from a known mechanic:

• Processing fees. Square publishes 2.9% plus 30 cents for Online API payments and 3.3% plus 30 cents for invoice payments on its free plan, so the same $4,800 settles differently by rail.

• Refunds and chargebacks. They net against unrelated captures. Refunding $250 costs $250 plus the fee already paid on it, and a dispute pulls both the principal and PayPal's $20.00 fee.

• Currency conversion. PayPal adds 1.50% for international commercial transactions, and Stripe's published rates add 2% when conversion is required on top of a 3% international card rate.

• Batched settlement. With Stripe's T+2 US default, Monday's captures land Wednesday alongside Tuesday's refunds, matching no single invoice date.

Reconcile the batch before the invoice. I tie the settlement file to the bank line first, then its line items back to invoices, so no fee gets explained twice.

How do you clear a partial payment or a lump of unapplied cash?

You clear them by deciding, per payment, whether the shortfall is a fee, a dispute, or a real balance owed, and posting each answer differently. Unapplied cash stays a liability line for as long as it sits there.

The cases that recur, and where each one lands:

1. Short payment on a known invoice. $9,700 arrives on a $10,000 invoice. Apply what came in, leave $300 open, chase it as receivable.

2. Deduction the customer took deliberately. An agreed discount or service credit. Post a credit memo so the invoice closes at the right number instead of leaving a stub.

3. Lump sum covering several invoices. One $42,150 wire against eleven invoices. Split it by remittance advice and park any unmatched remainder.

4. Payment with no reference. ACH or wire with a truncated memo field. Hold it in suspense, match later on customer, amount, and date.

5. Overpayment. Refund it, which costs the processing fee again, or hold it as credit against the next cycle.

Two habits keep the unapplied pile small. Put a machine-readable invoice reference into every payment request, and reconcile daily, because a $600 unexplained ACH is findable this week and not in six. Monthly checks turn small mismatches into revenue leakage nobody attributes to anything.

Related terms

Terms you'll hit while tracing one payment from invoice to bank:

• Usage reconciliation checks the other half of the equation, comparing units recorded in your product against units billed.

• Credit memo closes an invoice a customer short-paid for an agreed reason.

• Merchant of record determines who carries chargeback and refund liability, which changes whose reconciliation this is.

• Involuntary churn starts as a failed payment, which shows up first as an invoice that never reconciles.

• Revenue leakage names the end state of short payments nobody chased.

• Billing vs invoicing separates calculating what's owed from issuing the document that collects it.

FAQ

Is payment reconciliation the same as bank reconciliation?

No. Bank reconciliation compares your general ledger cash balance against the bank statement. Payment reconciliation works one level down, tying individual invoices to individual captures and settlements. A company can pass bank reconciliation while carrying thousands in untraced unapplied cash.

How is payment reconciliation different from usage reconciliation?

Payment reconciliation checks the money, usage reconciliation checks the units. Usage reconciliation asks whether the invoice charged for everything the product metered. Payment reconciliation starts once the invoice is correct and asks whether the money arrived. Both fail independently.

What is remittance advice and why does it matter here?

Remittance advice is the note a payer sends listing which invoices a payment covers. It turns a $42,150 wire into eleven applied invoices instead of a suspense entry. When it arrives as a PDF or not at all, cash application drops back to manual matching on amount and date, where most unapplied cash starts.

How often should you reconcile payments?

Daily, matched to the processor's payout cadence. Each batch arrives with an itemized settlement file, so reconciling on arrival explains every fee, refund, and dispute while the transactions are recent. Monthly checks find the same discrepancies weeks later, when the contact who could explain a $300 deduction has gone.