Switching on online payments takes days, but matching payments to invoices can cost the finance team hours every week: batched payouts from the gateway, deducted fees, refunds and instalment payments. That's where an Odoo integration earns its keep.
Common gateways in Saudi Arabia
- Payment gateways: Moyasar, HyperPay, Tap and PayTabs, which typically support mada, credit cards and Apple Pay.
- Buy now, pay later: Tabby and Tamara, where the customer pays in instalments and you receive the amount from the provider.
- Payment links and remotely paid invoices, for B2B companies that send a pay link with the invoice.
What the integration does
- Records the payment in Odoo the moment it succeeds, linked to the sales order or invoice.
- Separates gateway fees and their VAT into their own account.
- Records the batched payout from the gateway and matches it to the payments it covers.
- Handles full and partial refunds and reflects them on the invoice.
- Prevents a payment being recorded twice if the notification arrives more than once.
A clearing account per gateway
The clearest accounting practice is a clearing account per gateway in Odoo: payments go in when they succeed, the payout comes out when it reaches the bank, and the remaining balance is what hasn't been paid out yet. When the balance doesn't return to zero, you know immediately there's a difference to follow up.
Checklist
- A clearing account for each gateway and each instalment provider.
- An account for gateway fees and the VAT on them.
- A bank statement matching rule that recognises each gateway's payouts.
- Test a successful payment, a failed one and a partial refund before go-live.
- A weekly report of pending amounts in each clearing account.
At MUNSAQ we connect the gateway and build the reconciliation rules in accounting together, because connecting payments without reconciliation only moves the problem from the store to the finance team.
