Card Merchant Settlement and Fee Reconciliation Controls for UAE Businesses
Editorial responsibility: Valusage Business Advisors Editorial Practice (Editorial Practice)

Direct answer
A card merchant settlement reconciliation should connect POS or order-system sales to acquirer or gateway batches, then match gross collections, fees, refunds, chargebacks and timing differences to the bank deposit and ledger. Finance should reconcile by merchant ID, outlet, channel, currency and settlement date, retain batch evidence, investigate missing or duplicate deposits and separate genuine timing items from unresolved losses or fee errors.
Advisory decision map
From information to a controlled decision
- 01Question
- 02Evidence
- 03Options
- 04Action
Illustrative evidence trend
Decision supportCard receipts can look complete at the point of sale while cash arrives later and net of several deductions. A reliable reconciliation follows the transaction from the sales system to the merchant batch, settlement statement, bank and ledger.
Build the reconciliation population
Capture card sales, refunds, voids and tips where relevant from each POS, order platform or billing system. Identify the outlet, channel, merchant ID, terminal, currency and business date. Confirm that all expected terminals and online channels appear in the population.
Match batches before bank deposits
Compare daily sales totals with acquirer or gateway batches. Investigate missing batch closures, offline transactions, duplicate submissions and transactions that moved to another business date. Retain the batch or settlement evidence instead of relying on a dashboard total that later changes.
Rebuild the net settlement
Start from gross processed value and list fees, refunds, chargebacks, reserves, withheld amounts and other deductions separately. The calculated net should agree with the bank receipt. Use the provider contract and current statement to validate fee categories rather than posting the net difference to one general expense account.
Track timing differences by expected date
Record the expected settlement date for each batch based on the agreed cycle and non-working days. A timing item should carry the batch reference, amount, expected date and owner. Items that pass their expected date become exceptions, not permanent reconciling items.
Reconcile refunds and chargebacks
Link each refund or chargeback to the original transaction and supporting approval. Distinguish customer service actions, fraud disputes, duplicate charges and provider adjustments. Monitor repeated reasons and unusual concentrations by outlet, employee, product or channel.
Close from daily detail to the ledger
Reconcile daily batches and monthly provider statements to bank receipts, merchant receivables, fees and refund or chargeback accounts. Review manual journals and unmatched deposits separately. IAS 7 addresses cash-flow information, but the classification and accounting treatment for a specific arrangement require fact-specific review.
Merchant settlement checklist
1. Capture every outlet, terminal, channel and merchant ID. 2. Match sales and refunds to provider batches. 3. Rebuild gross value, deductions and net settlement. 4. Match net settlement to the bank receipt. 5. Age timing items by expected settlement date. 6. Link refunds and chargebacks to source evidence. 7. Reconcile provider statements to the ledger. 8. Escalate missing, duplicate and recurring exceptions.
These recommendations are editorial management-control guidance. They do not determine contractual fee entitlement, dispute rights, tax treatment or accounting classification for a specific merchant arrangement.
About the author
Haris Arif is Head of Finance and Investment. He is a finance and investment leader with experience across multi-entity businesses in technology, F&B and hospitality. He writes practical insights on financial control, management reporting, working capital, tax readiness and finance transformation for UAE founders, CFOs, investors and management teams.
Connect with Haris Arif on LinkedIn: https://www.linkedin.com/in/harisarifofficial/
Continue the decision
Services, evidence and next steps
Related control guidance
Continue with another evidence-led management review
Accounting and BookkeepingAccrual Ageing and Reversal Controls for UAE Month End Close →
Accounting and BookkeepingEmployee Advance and Staff Receivable Reconciliation Controls in the UAE →
Accounting and BookkeepingPurchase Price Variance and Supplier Cost Change Controls for UAE Businesses →
CFO, Finance and Cash FlowCash Flow Forecast Variance Analysis Controls for UAE Businesses →Professional boundary
This article is general information. It is not a filing opinion, legal advice, audit conclusion, investment recommendation or guarantee of authority acceptance or commercial outcome.
Why does the bank deposit differ from card sales?+
The provider may settle on a later date and deduct fees, refunds, chargebacks, reserves or other documented adjustments from gross processed value.
What should a merchant settlement reconciliation include?+
Include sales, refunds, batches, gross settlement, each deduction, expected settlement date, bank receipt, ledger posting and unresolved exceptions.
How should old settlement timing items be handled?+
Investigate items that pass their expected settlement date and reclassify them as exceptions with a named owner and follow-up action.
Valusage email updates
Receive related Valusage guidance
Original summaries with official sources and practical context. Confirm by email. Unsubscribe at any time.
Relevant next steps
Connect this guidance to a defined requirement
Contextual advisory review
Connect every card sale to its final bank settlement
Describe the entity, decision, deadline and evidence available. The service, enquiry and article path accompany the request. No engagement begins until scope, responsibilities, timing, exclusions and fees are agreed in writing.
Review the related service →Contextual enquiry
Connect every card sale to its final bank settlement
Tell us the outcome, deadline and current position. The selected service context is retained with your request so the right scope can be reviewed.
