Payment Gateway Reconciliation: Why Does the mada Transfer Differ From Total Sales?
📅 19/11/2026
Payment gateway reconciliation is the process of matching sales and electronic collections with payment provider reports and bank transfers, while identifying fees, refunds and outstanding amounts. If the POS shows card sales of SAR 10,000 but a smaller amount reaches the bank, this does not necessarily indicate a cash shortage. There may be fees, payments not yet due for settlement or refunds. A cloud accounting system helps organize these differences when each transaction is linked to its correct reference and account.
This guide is intended for stores, restaurants and businesses that accept mada, card and electronic gateway payments in Saudi Arabia. It differs from general bank reconciliation because it focuses on the collection cycle between the POS or online store and the payment provider before the funds reach the bank. All fees and transfer dates in the examples are hypothetical; review the merchant agreement and actual provider reports.
Payment Gateway Reconciliation: Why Are Gross Card Sales Different From the Net Transfer?
There are three distinct amounts: the invoice amount, the payment transaction amount and the bank settlement amount. They may be equal in a simple transaction, but they differ when payment is split between cash and card, fees are deducted, part of the amount is refunded or settlement is delayed. Do not use the sales report alone to establish collection, or the bank statement alone to establish revenue.
Suppose a restaurant invoice totals SAR 230 and the customer pays 100 in cash and 130 by card. The sales report shows 230, while the card payment report shows only 130. If the accountant compares the entire invoice with the card payment report, an apparent difference of SAR 100 will arise. Therefore, the payment method and amount must be recorded for each portion of the invoice. Review point-of-sale solutions to determine how payment methods are presented in reports.
| Source | What does it establish? | What does it not establish on its own? |
|---|---|---|
| Invoice | Supply value and VAT | Receipt of the amount in the bank |
| Terminal or gateway report | Payment transaction status | Bank batch settlement |
| Provider statement | Fees and settlements | Accounting revenue reconciliation |
| Bank statement | Amount actually transferred | Details of each invoice |
Setting Up a Clearing Account for mada Payment Reconciliation
A payment provider receivables account or a clearing account for each provider can be used to record amounts collected by the provider on behalf of the business, then clear them upon transfer and settlement. Do not record the amount in the bank account before it actually arrives, and do not mix mada receivables with online store gateway receivables if their settlement reports differ.
In an example of a sale of SAR 1,150 including 15% VAT, assume that the supply has occurred and the payment is successful. Debit payment provider receivables 1,150, credit sales 1,000 and credit output VAT 150. Upon transfer, if the provider deducts a fee of SAR 20 and deductible VAT of SAR 3 supported by a valid document, debit bank 1,127, debit fee expense 20, debit input VAT 3 and credit receivables 1,150.
Do not assume that every payment fee is subject to VAT or that its VAT is deductible. Review the nature of the service, the documents and the VAT Implementing Regulations. If the provider deducts fees from a later batch instead of the same batch, record them in the appropriate period and according to the correct accrual. The guide to accounting system components can help when designing the accounts.
Book a demo to review payment method reports.
How Do You Reconcile Combined Settlement Batches?
A bank or provider may combine transactions from several terminals or branches into a single transfer. Request the detailed settlement report and identify the batch ID, its date, the transactions included, fees, refunds and adjustments. Then match each transaction to its reference number in the POS or online store. Do not allocate the transfer equally among branches if their sales differ.
| Item | Hypothetical amount in SAR |
|---|---|
| Total eligible payment transactions | 10,000 |
| Refunds | 500 |
| Fees before VAT | 100 |
| Assumed VAT on fees | 15 |
| Expected net transfer | 9,385 |
If SAR 9,385 reaches the bank, the settlement matches at the total level, but you must verify that the refund relates to the correct transactions and that the fees are documented. Two incorrect transactions may offset each other while the total remains correct. Review bank reconciliation for the final stage of matching the bank statement, and do not replace detailed reconciliation with a single aggregate entry for differences.
Differences Between the Sale Date and the Transfer Date
A payment may take place on Thursday evening, while the provider transfers the amount on a later business day according to the contract. If the transaction occurs on the last day of the month, revenue may appear in one month and the transfer in the next. Do not change the sale date to the transfer date merely to simplify reconciliation. Recognize the event according to the recognition rules and leave the receivable in the clearing account until settlement.
Example: card sales of SAR 5,750 on December 31 are settled in January. If the sale occurred in December, sales before VAT are 5,000 and VAT is 750, with the receivable appearing at year-end according to the contract. In January, the receivable is cleared upon transfer and recognition of fees. Revenue is not recorded again. Review monthly accounting close to determine how to review clearing accounts at period-end.
Handling Declined and Pending Transactions
Not every transaction appearing on the payment terminal screen is successful. Authorization may begin and then be declined, the connection may time out, or the customer may be charged while the final result does not appear in the system. Do not immediately collect the amount again without checking its status with the provider, as the customer could be charged twice. Make the supervisor responsible for uncertain cases.
If the invoice has been issued but payment fails, review whether the goods were delivered or the sale canceled, and whether the document needs correction or a customer receivable should be recognized. Do not automatically delete an issued invoice. If payment succeeds later, link it to the original document instead of creating a new sale. Retain the transaction reference, attempt time and provider result.
Test the sales cycle with multiple payment methods before approving POS procedures.
Handling Refunds and Payment Disputes
A refund is a separate transaction from the original sale and may be deducted from a later settlement. If the business refunds SAR 115 to a customer for an item subject to the standard VAT rate, and the return meets the correction requirements, the effect may be a reduction of revenue by 100 and VAT by 15, with recognition of a liability or a reduction in provider receivables depending on the circumstances. The refund must be linked to the relevant note and original document in accordance with the rules, rather than treated as a bank fee.
A payment dispute, on the other hand, may lead to an amount being temporarily held or deducted until the dispute is resolved. Do not assume that every dispute means the sale is canceled for accounting purposes. Verify the reason for the dispute, the business’s entitlement, the documents and the supply status. It may be necessary to recognize a disputed balance or a loss under the applicable framework after assessing the evidence. Retain proof of delivery and provider correspondence without sharing unnecessary sensitive data.
Connecting Payment Terminals to POS Systems: What Should You Test?
If the system supports integration with specific payment terminals, this may reduce manual amount entry and enable the transaction result to be linked to the invoice. However, partial payments, connection failures, transaction cancellations, refunds and repeated attempts must be tested. Do not assume that every terminal or bank is supported. Ask about the model, provider and required settings.
In a restaurant example, the POS sends an amount of SAR 345 to the terminal. If the transaction succeeds, the payment reference should be returned and the invoice should display the correct status. If the response fails after the amount has been charged, the supervisor should be able to query the transaction before trying again. Ask to see the integration log and verify that the terminal does not accept a different amount without a clear procedure. Review the sales system and the accounting and point-of-sale service to define the scope of testing.
View the plans and ask about supported payment terminals.
Reconciling Branches, Terminals and Shifts
When a business has several branches, each terminal may have a different merchant or terminal ID. Maintain a mapping that links the ID to the branch, shift and settlement account. If a terminal is moved from one branch to another, update the mapping from the date of transfer and do not change historical data without a reason. An allocation error may make one branch appear more profitable than another even when the total is correct.
Suppose the first branch has card sales of SAR 6,000 and the second has 4,000, and the settlement fees relate to transactions from both branches. Use actual fee details for each transaction if available, or a reasonable documented allocation policy if the fees are shared. Do not allocate all fees to the branch whose account received the transfer. Review multi-branch accounting management and measuring branch profitability to determine the effect of allocation on reports.
A Daily Discrepancy Report and Monitoring Indicators
Create a report showing the opening balance of provider receivables, collected sales, refunds, fees, transfers and closing balance. You should be able to explain the closing balance with a list of unsettled transactions or documented adjustments. If a transaction remains outstanding beyond its expected date, move it to the follow-up list.
| Indicator | Meaning | Action |
|---|---|---|
| Unsettled amounts | Receivables not yet received in the bank | Review due date |
| Transactions without a reference | Data linkage failure | Identify invoice and source |
| Fee discrepancy | Unmatched deduction | Review contract and document |
| Pending refund | Unresolved amount | Follow up on provider status |
| Unallocated batch | Transfer without details | Request settlement report |
Do not use the discrepancy percentage alone to judge quality. A difference of 0.1% may be small in percentage terms but may relate to a significant duplicate transaction. Record the cause, the responsible person and the resolution date. The internal control guide helps define permissions for modifying settlements.
Book a session to review settlement scenarios with the system team.
Practical Cases and Advanced Reviews
Designing a Unified Reconciliation Register Before Importing Provider Statements
A business may use more than one payment gateway, each with a different reporting format. Create a unified template that includes the provider name, merchant or terminal ID, transaction ID, payment time, currency, amount, transaction type, settlement ID and transfer date. Do not rely on the order of rows in the file, because the provider may change it when a new report is downloaded. The original ID must remain available even after the data has been converted to an internal format.
If the file contains a row for the sale and a separate row for fees, do not combine them before identifying the type of each row. There may be a row for a previous adjustment, a refund or a hold. When importing, retain a copy of the source and the date it was received, then record the number of accepted, rejected and duplicate rows. If the file is imported again, the system or procedure should recognize previously recorded transactions rather than add new entries. Review the accounting workflow when defining the point at which entries are posted from the reconciliation register to the accounts.
Matching by Reference Rather Than Amount Alone
There may be ten transactions of SAR 115 on the same day. Matching the first transaction with the same amount does not prove that it is the correct transaction. Use the payment reference, terminal ID, time and order ID, bearing in mind that some references may differ between the terminal, provider and bank. Create a map of the identifiers that can be used at each stage.
In a store example, two invoices of SAR 230 appear at the same time, one paid by card and the other in cash. If the accountant searches only for 230, the transfer may be linked to the cash invoice. Verify the payment method and reference. If a payment covers more than one invoice, retain an allocation relationship showing the amount assigned to each document. Do not change the invoice number to force a successful match.
Opening and Closing Balances of the Payment Provider Account
Suppose the payment gateway receivables account starts the month with a balance of SAR 12,000. During the month, transactions collected on behalf of the business total 90,000, refunds 4,000, documented total fees 2,000 and transfers 88,000. The closing balance is SAR 8,000, assuming no other movements. This balance must match the list of unsettled transactions or documented adjustments.
| Account movement | Amount in SAR |
|---|---|
| Opening balance for the month | 12,000 |
| New transactions | 90,000 |
| Refunds | −4,000 |
| Fees | −2,000 |
| Transfers | −88,000 |
| Closing balance | 8,000 |
If the provider report shows a different balance, review the periods covered by the report. A transfer may be recorded in the provider statement a day before it appears in the bank. A refund may be confirmed in the system but not yet deducted from the settlement. Separate timing differences from errors and retain a report showing the date of each movement.
Payment Gateway Fees: Fixed and Variable Charges and Subsequent Settlements
The provider agreement may include a fixed fee per transaction, a percentage of the amount, monthly fees or fees for additional services. Do not assume that the difference between total transactions and the transfer represents a single fixed percentage. If the report shows fees at the transaction level, use them in reconciliation. If the deduction is aggregated, request the document explaining how it was calculated.
Hypothetical example: sales of SAR 50,000, transaction fees of SAR 600, monthly fees of SAR 150 and a prior fee adjustment of SAR 50. Total deductions before any assumed VAT are SAR 800. Do not allocate the full 800 to current transactions if the adjustment relates to a previous period or the monthly fees are shared. Identify the nature and date of each item and the appropriate cost center, and review tax documents when recognizing input VAT.
How Do You Resolve a Difference Between the POS Report and the Provider Report?
Start by identifying the direction of the difference. If the POS shows 100 card transactions while the provider shows 98, identify the two unmatched transactions. One may be a failed transaction that the employee recorded as successful, and the other may be a cash transaction classified incorrectly. If the provider shows more transactions, there may be a successful payment not linked to an invoice, a duplicate collection or a transaction from a terminal not assigned to the branch.
Do not record a cash discrepancy against the employee before verifying its cause. The problem may be in the integration or the payment method settings. Ask the supervisor to review the log, transaction receipt and provider status, then determine the accounting and operational action. If an excess amount has been collected from the customer, process the refund according to the appropriate procedures and do not use an entry that conceals the customer’s entitlement.
Matching Online Store Payments With Orders
In an online store, the order amount may change after payment due to cancellation of an item, a shipping adjustment or a discount. Link each change to the order ID and transaction reference. Do not rely on the current order total alone if it has changed after collection. Retain the original amount, the adjustments and their timing so that you can explain the provider report.
If a customer pays SAR 575 and then receives a refund of SAR 115, the original transaction may appear in one day’s report and the refund in another day’s report. If you compare the net order amount of 460 with the original collection of 575 without accounting for the refund, a difference of 115 will appear. The reconciliation register must show that the difference relates to a refund rather than a missing amount. Review the integration of sales, inventory and accounts to determine how adjustments are transferred from the store.
An Escalation Plan for Disputed Amounts
Define when a transaction should move from the ordinary follow-up list to escalation. This depends on the contractual settlement date, transaction status and amount involved. You may need to provide the payment reference, proof of delivery, invoice and correspondence to the provider. Do not share sensitive card information or login credentials. Maintain a record showing the date the case was opened, responses and the final decision.
If the amount is held, distinguish a temporary hold from a final loss. Review the business’s entitlement to the amount and evidence of collection under the accounting framework. When the dispute is resolved, record the outcome according to the documents and close the case only after reconciling the account. Do not leave the disputed balance in a general account without follow-up; small amounts may accumulate and become material over time.
A Sample Electronic Payment Shift Closing Procedure
At the end of the shift, the employee reviews the totals for each payment method in the POS, the supervisor reconciles the terminal or gateway report, and the accountant records cases requiring follow-up. The bank does not need to have transferred all amounts on the same day. What matters is that successful transactions match the documents and that uncertain cases are documented. The following day, settlements that have arrived are reviewed according to their due dates.
| Step | Responsible person | Evidence of completion |
|---|---|---|
| Shift closing | Cashier | Payment method report |
| Transaction reconciliation | Supervisor | List of references and statuses |
| Settlement import | Accountant | Provider statement and batch number |
| Bank reconciliation | Accountant | Bank transaction and fees |
| Approval of discrepancies | Reviewer | Documented cause and action |
This checklist can be used to train a new employee without granting permission to modify accounts. If the system provides automated reports, test them on a shift that includes a mixed payment, a refund and a failed transaction. In this way, reconciliation becomes part of daily work rather than a task deferred until month-end.
Reviewing Settlements Involving More Than One Currency
If the business allows transactions in different currencies, identify the sale currency, settlement currency, conversion rate and fees according to the contract and accounting framework. The amount transferred in Saudi riyals may differ from the recorded accounting amount because of exchange rate changes rather than a collection shortfall. Do not use an assumed rate to reconcile every transaction. Retain the transaction amount in its original currency, its value in riyals, the source of the rate and the transfer date. If separate currency conversion fees apply, distinguish them from exchange differences and payment fees. Review financial reports to determine how these items are presented under the applicable accounting policy.
Ready to Try the System?
Start your free trial or speak with the sales team to help choose the right solution.
Frequently Asked Questions
Why Did the Bank Receive Less Than the Card Sales Total?
The reason may be fees, refunds, settlement timing or held amounts. Review the provider report before recording the difference.
Should I Record the Net Transfer as Revenue?
No, if the sale has already been recorded. The transfer clears the receivable, and fees are recognized according to their supporting documents.
Is Every Difference Between Sales and the Bank a Loss?
No. It may represent a receivable not yet due for transfer or a documented difference.
How Do I Handle Mixed Payments?
Record each portion according to its payment method and link it to the same invoice, then reconcile each method with its source.
Does Terminal Integration Eliminate the Need for Reconciliation?
No. It reduces some errors but does not eliminate fees, refunds, delays or connection issues.
When Should I Follow Up on a Transaction That Has Not Arrived?
After reviewing the contractual settlement date and transaction status, escalate according to the provider’s procedures.
Conclusion
Payment gateway reconciliation begins with the invoice and payment reference, continues through the provider report and clearing account, and ends with the bank statement. Use the guide to cloud accounting software to understand how to manage operations in one place, and request a trial of payment reports before making a decision.
Start evaluating the right system for your sales and payments.
Manage Your Business with Greater Flexibility
Try Digital Business for free. Start issuing electronic invoices designed to meet ZATCA requirements in minutes.


