Skip to content

Payment operations

A paid order is not yet money in the bank

Understand the journey from a customer payment to a settlement, and make reconciliation part of your normal operating rhythm.

PayPort editorial team

Three questions describe three different events

Did the customer complete payment? Is the sale available for settlement? Has the money reached the business bank account? These questions are often collapsed into one word: paid. Keeping them separate makes customer support and cash planning more reliable.

The provider's terminology and timing may vary. Read the agreed settlement rules and the report definitions for your own setup. The point is to know which event each status represents rather than assume that a checkout confirmation means a same-day bank deposit.

Follow one order all the way through

Choose a real order reference and locate its payment record, any fees or refunds, the settlement batch, and the bank deposit. If that route is difficult for one order, it will become harder as volume grows.

Keep the store reference and provider transaction identifier together. Settlement batches often cover several transactions, so the bank total will not necessarily equal an individual sale. A shared identifier lets finance trace the difference without asking customers for screenshots.

Explain the difference between gross sales and the deposit

The amount customers paid can differ from the amount deposited. Depending on the contract, reports may include processing fees, refunds, chargebacks, reserves, conversion, or other adjustments. Their presentation and timing are provider-specific.

For a simple internal exercise, imagine gross payments of 1,000 in one currency, 30 in fees, and 100 in refunds. The remaining 870 is only an illustrative subtotal, not a promised settlement. Your actual report may allocate those items to different batches or include other adjustments. The aim is to make every difference explainable.

Read timing as a cash-flow issue

Review settlement frequency, cutoff times, weekends, bank processing, and any conditions that delay release. Ask whether the timing is counted from payment, capture, or another event. A headline such as 'weekly settlement' is not enough to plan payroll or inventory purchases.

Hold enough operational flexibility for the timing in your contract. If a batch is late, your team should know what date was expected and which contact can explain the status, rather than rely on a vague estimate.

Know how an exception is reviewed

A refund or dispute can change a later settlement even when the original sale appeared complete. A reserve or hold should have an identifiable contractual basis, scope, and review process. Ask how evidence is submitted and how decisions are communicated.

Keep communications, transaction references, and the relevant agreement accessible. This is practical record keeping: the team handling a query should not have to reconstruct the relationship from old inboxes.

Investigate a mismatch without guessing

Suppose a bank deposit is lower than the total of the orders you expected to settle. Begin with the settlement batch identifier and the dates covered, not with an assumption that a payment is missing. Some transactions may belong to the next batch, while a refund of an older order may reduce the current one.

Compare the included transactions, their currencies, and each adjustment line. Then check whether the bank deposit matches the reported net amount. If the difference remains unexplained, send the provider the batch reference and the specific lines in question. A focused query is easier to investigate than a screenshot of a total alone.

Keep the unresolved amount in a reconciliation log. Record the owner, the response received, and the next review date. Once resolved, document the reason so that the same difference can be recognized next time.

Create a routine your finance team can sustain

Set a regular reconciliation rhythm appropriate to your volume. Compare order totals to payment records, match settlement batches to bank deposits, and investigate unexplained items before they accumulate. Keep unresolved differences in a shared list with an owner and next action.

A useful payment setup makes those steps legible. When a provider cannot explain how a confirmed sale reaches your bank, ask for a worked example before increasing volume. Commercial clarity is part of the payment experience, even if the customer never sees it.

Match orders, transactions, settlement batches, and bank deposits separately. An unexplained difference needs an owner, not a guess.
What to take away
Back to the blog