The invoices look settled. The payment records show the money came in. Then, the bank deposit arrives lower than expected, and someone has to find out why.

 

The answer may be in a transaction from another day.

 

A refund from last week or a chargeback on an older sale can reduce today’s payout. The processor may also deduct fees, and a payment received after the batch cutoff may appear in a later payout.

 

Invoices show what customers owe. Payment records show what they paid. The deposit shows what reached the bank after settlement activity.

 

Keeping those amounts separate makes the difference easier to trace.

 

Follow the Payout

 

Gross customer payments  −  Fees deducted  −  Refunds  −  Chargebacks  ±  Transactions shifted between payout periods  ±  Other adjustments  =  NET DEPOSIT

 

Start with the transactions included in a payout, rather than every invoice issued that day.

 

A Tuesday invoice may still be unpaid, while a Tuesday payment might settle in a later batch. The processor’s payout detail shows which transactions were included and what was deducted.

 

Fees aren’t always taken from each payout. Some are billed separately, so use what your report shows.

 

For example, customers make $10,000 in payments on Tuesday, and all those payments are included in a payout that reaches the bank on Wednesday.

 

The processor then deducts $200 in fees, a $400 refund, and a $100 chargeback, leaving a $9,300 deposit.

 

The refund and chargeback may relate to older sales. The smaller deposit doesn’t mean Tuesday’s customers left $700 unpaid.

 

The U.S. Chamber of Commerce’s guide to credit card processing explains where to find sales, refunds, chargebacks, fees, and net deposits on a merchant statement.

 

For a timing difference, follow the transaction ID and payout date until the payment appears.

 

Check Where Each Payment Went

 

The payout explains the deposit amount. The next question is whether each payment was applied to the right invoice.

 

A $500 payment toward a $700 invoice leaves $200 due, regardless of the deposit amount. A duplicate payment or one tied to a canceled invoice also needs review.

 

These issues can exist even when the payout totals match.

 

Your team may already catch these cases through manual checks or the tools you have in place. What matters is seeing which payments match open invoices and which need attention.

 

Paycile’s invoice-to-payment reconciliation automatically matches payments to open invoices and flags exceptions such as partial payments, overpayments, underpayments, duplicates, and payments against canceled or expired invoices.

 

That helps your team see what each payment covers and what needs review. The processor’s payout detail supplies the fees, refunds, chargebacks, and timing needed to explain the deposit.

 

Make the Review Repeatable

1. Compare invoices with gross customer payments to find unpaid balances and partial payments.
2. Review the payout detail for the included transactions and any fees, refunds, chargebacks, or other adjustments.
3. Trace payments that missed a batch cutoff to the payout where they settled, then compare its net amount with the bank deposit.
4. Resolve invoice exceptions separately from payout differences.

 

For vertical software teams, showing invoice, payment, and payout status separately gives users a trail to follow. It also keeps the full amount a customer paid visible when a fee reduces the deposit.

 

When a deposit looks short, each difference needs a place to go. It may be an unpaid balance, a payout adjustment, a timing difference, or an error that still needs investigation.

 

Book a demo and walk through your invoice matching process with us.

KEY TAKEAWAY

Before following up on an invoice, trace the payout. The difference may come from a refund, chargeback, fee, or payment that settled in a later batch.

Newsletter Archive

Stay informed with operational insights for finance teams that move money at scale.