Skip to content
EncryptTechBD
Home Industries Our Work Blog Pricing About Contact Discuss Your Project
বাংলা (BN)
Payments & Reconciliation 6 min read

Daily payment settlement reconciliation problems and fixes

A symptom-first guide to missing payouts, duplicate entries, fee gaps and cut-off mismatches, with fixes, prevention and an escalation path.

E
EncryptTechBD · 0 comments
Stack of US dollar bills on a table
Photo: Shopify / StockSnap

At the end of the day the settlement report says one number, the order system says another, and finance has an hour before the bank cut-off. The instinct is to blame the gateway. More often the mismatch is a definition, a timing boundary or a missing identifier that was never agreed at the start.

This guide is organised by symptom. For each problem it gives the likely causes, the fix and the control that prevents a repeat. It assumes a business in Bangladesh receiving settlements from cards, mobile financial services and bank transfers, often through more than one provider. It does not assume a particular vendor or a fully automated system.

Agree the reconciliation model first

Before touching the spreadsheet, write down the fields that every source must provide: order ID, payment or gateway transaction ID, provider payout ID, bank reference, gross amount, fee amount, refund amount, settlement date and status. If one source cannot provide a field, record the substitute and the person responsible for the manual bridge.

Define three totals: gross sales, fees and net settlement. A reconciliation that compares only net settlement to order value will always show a gap, because the provider has already deducted a fee. Define the cut-off time and timezone too. A payment captured at 23:50 may settle in the next batch, and that is not an error.

Symptom: the settlement total does not match sales

Likely causes: provider fees deducted, refunds netted against the batch, chargebacks, tips, taxes, rounding or a currency conversion. Fix: build a gross-to-net bridge for each payout and reconcile each component separately. Link every refund to its original payment instead of treating it as a new deduction. Prevention: store fee and refund fields at the transaction level, and review the bridge daily rather than at month-end.

Symptom: a payout is missing or late

Likely causes: the payout fell after the cut-off, the provider placed a hold, a merchant account is under review, a bank holiday shifted the value date, a batch failed or the money went to a different merchant account. Fix: check the provider's payout dashboard and batch status before calling the bank. Collect the payout ID, expected value date and affected transaction IDs, then escalate through the provider's support channel. Prevention: keep an expected-payout register with value dates and alert when a payout is one business day late.

Symptom: the same payment appears twice

Likely causes: a retried request created a second charge, a webhook was delivered more than once, a settlement file was imported twice, or a staff member entered the same receipt manually. Fix: deduplicate on the provider transaction ID, not on amount and date. Reverse the duplicate with an audit note; do not delete the row. Prevention: enforce an idempotency key on payment creation, store the provider's unique ID with a database constraint and check a file checksum before import.

Symptom: amounts match but the dates do not

Likely causes: authorisation and capture happen on different days, the provider settles on the next business day, the report uses UTC while the business uses local time, or a weekend batch rolls into Monday. Fix: match on the settlement date and keep unmatched items in an open-items queue with an ageing column. Prevention: record the expected settlement date at capture and define a cut-off calendar that includes weekends and bank holidays.

Symptom: refunds and partial refunds break the match

Likely causes: several partial refunds against one order, a refund that failed after the order system marked it complete, a fee retained on the refund, or a store credit issued instead of a cash refund. Fix: give refunds their own state machine and link each refund ID to the original payment. Reconcile the net refund, not the requested amount. Prevention: a refund register with requester, approver, provider status and settlement date.

Symptom: fees, taxes and charges are unclear

Likely causes: the contract lists a headline rate but the statement includes gateway, payout, currency or platform fees; VAT treatment differs; or the effective rate changes with volume. Fix: keep the contracted fee schedule beside the reconciliation file and calculate the effective fee per payout. Ask the provider to explain any line that does not map to the contract. Prevention: review effective fees monthly and raise a query when the variance exceeds a threshold you set in advance.

Symptom: mobile financial services and bank references do not match

Likely causes: the provider statement contains a truncated reference, the order ID was not sent at checkout, the customer paid from a different number, or the provider uses its own transaction ID. Fix: build a mapping table between provider IDs, bank references and order IDs, and route unresolvable items to a manual queue with a named owner. Prevention: require an order reference at collection, use provider APIs or official exports where available, and avoid relying on customer-entered text as the only key.

The diagnostic sequence

  1. Confirm the reporting period, cut-off and timezone for every source.
  2. Reconcile transaction counts before amounts; a missing row is easier to spot than a value gap.
  3. Match on the strongest shared identifier, then fall back to a documented secondary key.
  4. Separate gross sales, fees, refunds and chargebacks into distinct lines.
  5. Put every unmatched item into an open-items queue with an owner and an age.
  6. Check the next settlement batch before concluding that money is missing.
  7. Escalate with a payout ID and a transaction list, not a screenshot of a total.

The daily close routine

A ten-step close is enough for most small finance teams: import provider statements, import bank movements, import the order ledger, run the three-way match, review exceptions, clear or assign each item, post the reconciled totals, file the evidence, notify the owner and lock the day. The routine should take the same path every day so that a substitute can run it without asking questions.

Set thresholds for what counts as an exception. A small rounding difference and a missing payout are not the same risk. Define who can write off an amount, who can adjust a ledger entry and who must approve both. Keep the evidence in one folder per day: provider statement, bank statement, match report and exception notes.

Escalation triggers

  • A payout is missing beyond its expected value date.
  • The same transaction appears in two payouts.
  • A refund is marked complete but not settled.
  • Fees exceed the contracted schedule by more than your agreed tolerance.
  • A provider changes a statement format or an API response without notice.
  • Any adjustment above the approver's limit.

Settlement control sits within Commerce Systems, alongside order management and payment integration. The pricing page explains how a reconciliation build is separated from ongoing support. For the budget side, read the cost guide for daily payment settlement reconciliation.

Sources

Services that deliver this

Want this implemented properly?

Pricing →

Every engagement starts with a written scope. If a requirement is outside it, we quote it separately before starting.

Responses (0)

No comments yet. Add the first one below.

Leave a response

Your email address will not be published. Required fields are marked *.

Keep reading

More field notes