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

Payment reconciliation: what to set up before you automate it

Reconciliation is not a report — it is a control. Here is the minimum setup that lets you prove which orders are paid, partial or due without relying on screenshots.

E
EncryptTechBD · 0 comments
Customer paying by card at a retail counter
Photo: Unsplash

Ask five people in a growing online business how much money was collected yesterday and you will usually get five answers. That is not a discipline problem; it is a missing control.

Reconciliation means matching three things: the order, the payment and the provider record. When all three agree, the order is closed. When they do not, someone reviews it.

Do not build on SMS scraping

Reading payment SMS messages feels convenient, but it is a fragile foundation for a financial record. Messages get deleted, duplicated, delayed or forwarded. Use the official merchant API, documented exports or the provider's settlement report. If those are not available, use a controlled manual import — but do not pretend it is automation.

The minimum data per payment

  • Method (cash, bKash, Nagad, bank, card)
  • Provider reference or transaction ID
  • Amount and date
  • Which order it belongs to
  • Status: matched, unmatched, refunded

The review queue is the product

Automation will never match everything. The useful part is a queue that shows what did not match, why, and who is responsible. A reconciliation system without an exception queue is just a second spreadsheet.

Close daily, report monthly

Match payments daily while the context is fresh. Publish a monthly summary from the matched records: collected, outstanding, refunded and disputed. The numbers should be reproducible by anyone with access.

Controls worth adding early

  • Refunds require a second approval
  • Manual matches record who made them
  • Provider totals are compared to internal totals
  • Unmatched items older than 7 days are escalated

Our Commerce Systems team sets up reconciliation on official exports or authorised APIs, with a review queue rather than a promise of full automation.

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