Introduction: Why Reconciliation and Settlement Matter
For any business that accepts payments, two processes determine daily financial health: settlement (the transfer of transaction funds) and reconciliation (the accounting matching process). In Morocco, where electronic transaction volume exceeded 18 billion dirhams in 2025 according to Bank Al-Maghrib, these processes have become a major operational concern.
A merchant selling online, in-store, and through field agents can generate hundreds of transactions daily across multiple channels. Without a reliable reconciliation process, it is impossible to know whether every dirham has been received, what fees have been deducted, and where discrepancies lie. The consequences are direct: undetected financial losses, accounting errors, and considerable time spent on manual matching.
This guide explains in detail how settlement and reconciliation work in Morocco, the challenges specific to the Moroccan market, and the solutions available to automate these processes. Whether you are a fintech, an e-commerce business, or a company with physical points of sale, you will find here the elements needed to master your settlement chain.
Settlement Explained: From Authorization to Funds Transfer
Settlement is often confused with payment authorization. In reality, these are two distinct steps in the same process. Understanding this distinction is fundamental to managing cash flow effectively.
Authorization is the first step. When a customer presents their card (physically or online), the issuing bank verifies that the account has sufficient funds and reserves the amount. At this stage, no money transfer takes place. The merchant simply receives confirmation that the payment will be honored.
Capture comes next. The merchant confirms that the transaction should be executed. For online payments, capture is generally automatic. In certain cases (hotels, car rentals), capture can be deferred by several days. It is at capture that the transaction is submitted for settlement.
Settlement is the actual transfer of funds. The issuing bank debits the customer's account, transfers the funds through the interbank network (CMI in Morocco), and the acquiring bank credits the merchant's account, minus processing fees. This transfer does not happen transaction by transaction but in batches.
This three-step process explains why there is always a delay between when a customer pays and when the merchant receives funds in their account. This delay, called the settlement cycle, varies by payment channel and provider. To learn more about how payment gateways work in Morocco, see our dedicated guide.
The Settlement Cycle in Morocco
In Morocco, the settlement cycle is structured around the Centre Monetique Interbancaire (CMI), which acts as the central switch between banks.
The standard CMI cycle operates on D+1. Transactions captured during a day (until midnight) are grouped into a batch. The next business day, CMI performs clearing: it calculates the net amounts owed between issuing and acquiring banks, then orders the transfers. The merchant receives funds in their account on D+1, net of commissions.
Batch processing means that individual transactions are aggregated. A merchant who completed 200 transactions during the day will receive a single transfer corresponding to the net total of those transactions. This approach simplifies banking flows but complicates reconciliation, as each individual transaction must be linked to the overall amount received.
Delays vary by channel:
- Card payments via CMI: D+1 (standard)
- Maroc Pay (QR code): D+0 to D+1 depending on the provider
- Domestic bank transfers: D+0 to D+1
- International SWIFT transfers: D+2 to D+5
- Cash on delivery (collected by agent): variable, often D+2 to D+7
For multi-channel businesses, this diversity of timelines creates significant complexity. The same product sold online and in-store will generate two different settlement flows, with distinct delays and fees. Our payment gateway comparison details the settlement conditions of each provider.
Reconciliation Explained: Matching Transactions to Received Funds
Reconciliation is the process that verifies whether funds received in your bank account exactly match the transactions recorded in your system. It is the control mechanism that ensures no transaction is lost, no amount is incorrect, and that applied fees are accurate.
Why reconciliation is critical:
Without rigorous reconciliation, a business can lose money without knowing it. An undetected chargeback, an incomplete settlement batch, abnormally high fees: these discrepancies accumulate silently. For a business processing 10,000 transactions per month, a 0.1% discrepancy already represents a significant annual loss.
Manual vs. automated reconciliation:
The traditional method involves downloading the bank statement, exporting transactions from the POS system or payment gateway, then comparing the two in a spreadsheet. This process, often done in Excel, is time-consuming, error-prone, and does not allow real-time discrepancy detection.
Automated reconciliation uses APIs and connectors to extract data from all sources (payment gateway, bank account, ERP) and perform matching automatically. Discrepancies are flagged immediately, enabling rapid resolution.
Types of Reconciliation
Depending on the granularity and objective, three levels of reconciliation exist.
Transaction-level reconciliation. Each individual transaction is compared with its settlement status. This verifies that every authorized payment has been captured, then settled. This level of detail is necessary to detect missing transactions or incorrect amounts. It is the most precise level but also the most demanding in terms of data.
Batch-level reconciliation. Transactions are compared by settlement batch. This verifies that the total amount of a batch matches the sum of individual transactions, minus fees. This level is sufficient for most businesses and allows detection of amount discrepancies between what the gateway reports and what the bank credits.
Bank statement reconciliation. Amounts credited to the bank account are matched against expected settlement batches. This level is the most common in accounting. It ensures that all settlement batches have been received and that accounting balances are correct. This is typically where the accounting team intervenes.
A robust reconciliation process ideally combines all three levels to provide a complete view, from individual transactions to bank balances.
Common Discrepancies and Their Causes
Even with a well-established settlement process, discrepancies appear regularly. Identifying their causes is the first step to resolving them.
Chargebacks (disputes). A customer disputes a transaction with their bank. The amount is debited from the merchant's account, sometimes several weeks after the initial transaction. Chargebacks disrupt reconciliation because they appear as unexpected debits on the bank statement. In Morocco, chargebacks on local cards remain relatively rare but are increasing with e-commerce growth.
Partial refunds. A partial refund creates a negative transaction that does not match the initial transaction amount. If the reconciliation system is not configured to handle partial refunds, the discrepancy will never be resolved automatically.
Fees and commissions. The settled amount is always less than the transaction amount because gateway, acquirer, and scheme (Visa/Mastercard) fees are deducted. If the commission rate varies (for example, by card type), calculating expected fees becomes more complex. To understand the fees associated with payment solutions in Morocco in detail, see our comparison.
Currency conversion. For foreign currency transactions, the exchange rate applied at settlement may differ from the rate displayed at the time of transaction. This gap, called the exchange spread, is a frequent source of discrepancies.
Pending or failed transactions. A transaction authorized but not captured, or captured but not settled, creates a temporary discrepancy. These cases generally resolve themselves but must be tracked.
The Multi-Channel Challenge: Reconciling Multiple Settlement Streams
Moroccan businesses increasingly operate across multiple channels simultaneously: online store, physical points of sale (POS terminals), field agents, and sometimes marketplaces. Each channel generates its own settlement flow with its own timelines, formats, and counterparts.
Concrete example: a Moroccan retail chain receives card payments in-store (settled by CMI via the acquiring bank on D+1), online payments (settled by the e-commerce gateway on D+1), Maroc Pay payments (settled on D+0 by the provider), and cash collected by agents (deposited on D+3 on average). To reconcile the whole picture, the accounting team must handle four different data sources, with distinct formats and references.
This fragmentation is the main obstacle to efficient reconciliation. Businesses that grow in volume without centralizing their settlement data quickly become overwhelmed. Manual matching between these sources is not only time-consuming but also error-prone.
The solution lies in centralizing settlement flows into a single system capable of aggregating data from all sources and performing matching automatically.
Automation: APIs, Webhooks, and Dashboards
Reconciliation automation rests on three technical pillars.
Settlement APIs allow programmatic extraction of transaction and settlement data from the payment gateway. Instead of manually downloading CSV files, your system queries the API to obtain the day's transactions, their settlement status, and net amounts. To learn more about payment API integration in Morocco, see our technical guide.
Webhooks notify your system in real time when a settlement event occurs. Rather than periodically polling the API, you receive an instant notification when a batch is settled, when a chargeback is received, or when a refund is processed. This reactive approach keeps reconciliation continuously up to date.
Reporting dashboards provide a consolidated view of settlement and reconciliation status. A good dashboard displays transactions pending settlement, settled batches, detected discrepancies, and trends over time. It allows accounting and finance teams to monitor the situation without manipulating files.
ERP integration closes the loop. Reconciled settlement data is automatically injected into the accounting system (Sage, SAP, or any other ERP used in Morocco). Accounting entries are generated automatically: debit to the bank account, credit to the sales account, and booking of transaction fees. This automation eliminates manual data entry and reduces error risk.
Accounting Integration: From Settlement to Journal Entries
Reconciliation only has value if it correctly feeds accounting. Here is how to structure the flow between settlement and journal entries.
Accounting for a typical transaction:
When a 1,000 MAD sale is made by card, the gateway charges 2% in fees (20 MAD). The merchant receives 980 MAD. The corresponding journal entry is: debit bank account 980 MAD, debit bank fees account 20 MAD, credit sales account 1,000 MAD.
The timing challenge: the sale is recorded on D+0, but funds arrive on D+1. A transit account (often called "pending collections") must be used to record the receivable between the time of sale and the actual receipt of funds.
Batch matching: each settlement batch corresponds to a bank transfer. Matching involves verifying that the transfer amount exactly corresponds to the net total of the batch. Discrepancies must be investigated and accounted for (unexpected fees, chargebacks, adjustments).
Periodic reporting: at month-end, a reconciliation report is produced. It summarizes transaction volume, settled amounts, total fees, chargebacks, and unresolved discrepancies. This report is an essential element of internal control and compliance with Bank Al-Maghrib requirements.
For businesses managing high volumes, automating this chain (from settlement to journal entries) delivers considerable productivity gains. It frees the accounting team from repetitive data entry and allows them to focus on analysis and control.
How ChariBaaS Simplifies Reconciliation and Settlement
ChariBaaS was designed to solve precisely the challenges described in this guide. The platform centralizes all payment and settlement flows into a single interface, regardless of the collection channel.
Unified multi-channel settlement. Whether payments come from bank cards (via CMI), Maroc Pay, bank transfers, or cash collected by agents, ChariBaaS aggregates all flows into a single dashboard. Each transaction is tracked from authorization to settlement, with detailed fees breakdown. Visit our dedicated accounting and settlement service page for more details.
Automatic reconciliation. The ChariBaaS reconciliation engine automatically matches transactions with settlement batches and bank movements. Discrepancies are detected and flagged in real time. Chargebacks, refunds, and adjustments are automatically integrated into the reconciliation process.
Reporting API. The ChariBaaS API exposes dedicated endpoints for settlement and reconciliation. You can extract settlement data by period, channel, status, and inject it into your ERP or BI tool. Webhooks notify your system in real time for each settlement event.
Payment and transfer management. ChariBaaS is not limited to reconciliation. The platform also manages payments and bank transfers, allowing you to centralize the entire financial chain in a single tool.
Dashboards and reports. Periodic reconciliation reports are generated automatically. They include transaction details, settlement batches, fees, detected discrepancies, and corrective actions. These reports are exportable and compatible with formats required by auditors and regulators.
For businesses that want to eliminate manual Excel reconciliation and gain visibility over their financial flows, ChariBaaS offers a turnkey solution. Contact us for a personalized demonstration.
FAQ
What is bank settlement?
Settlement is the actual transfer of funds between the parties of a transaction. After a card payment is authorized, settlement transfers money from the customer's account to the merchant's account, typically on D+1 (next business day) in Morocco.
What is payment reconciliation?
Reconciliation is the process of matching transactions recorded in your system with funds actually received in your bank account. It verifies that each transaction has been correctly settled and identifies discrepancies.
How to automate reconciliation in Morocco?
Through a platform like ChariBaaS that provides: a unified dashboard with all transactions, automatic settlement reports, APIs to extract data, and automatic matching with bank statements. This eliminates manual reconciliation in Excel.
What is the settlement delay in Morocco?
The standard delay is D+1 (next business day) for card payments via CMI. Some providers offer D+0 (same day) for Maroc Pay payments. SWIFT bank transfers can take 2-5 business days.
Frequently Asked Questions
- What is bank settlement?
- Settlement is the actual transfer of funds between the parties of a transaction. After a card payment is authorized, settlement transfers money from the customer's account to the merchant's account, typically on D+1 (next business day) in Morocco.
- What is payment reconciliation?
- Reconciliation is the process of matching transactions recorded in your system with funds actually received in your bank account. It verifies that each transaction has been correctly settled and identifies discrepancies.
- How to automate reconciliation in Morocco?
- Through a platform like ChariBaaS that provides: a unified dashboard with all transactions, automatic settlement reports, APIs to extract data, and automatic matching with bank statements. This eliminates manual reconciliation in Excel.
- What is the settlement delay in Morocco?
- The standard delay is D+1 (next business day) for card payments via CMI. Some providers offer D+0 (same day) for Maroc Pay payments. SWIFT bank transfers can take 2-5 business days.