In this article
- Key takeaway
- Overdue is not always the same as collectible
- Segment the ledger before configuring reminder levels
- The collection sequence that avoids preventable errors
- Illustrative case: the disputed part-payment
- Illustrative case: an invoice remains open after payment
- Configure Odoo controls around collection quality
- What managers should measure
- Remember the IFRS 9 judgement
- A practical receivables review checklist
- Frequently Asked Questions
- Can Odoo send automated invoice reminders?
- Should every overdue balance receive the same message?
- Why reconcile before reminding?
- Is receivables ageing sufficient for IFRS 9 provisions?
- How SERPA can help
Author’s role: SERPA — Odoo Finance and Receivables Automation Team
Key takeaway
Reconcile receipts before sending reminders, separate disputed balances from routine collections and assign accountable owners to exceptions and next actions.
How Zimbabwean finance teams can automate routine collections without damaging customer relationships or misstating outstanding balances.
A customer invoice becomes overdue and an automated follow-up is about to go out. The customer has already paid part of the amount, but the bank receipt was not matched. Another part is under a genuine delivery dispute. A reminder for the full balance may look efficient in the software and still be wrong for the relationship.
Accounts receivable automation is strongest when repeatable actions are automatic and exceptions receive accountable human review. The aim is not to send more messages; it is to collect legitimate balances using evidence that finance, sales and the customer can understand.
Overdue is not always the same as collectible
Odoo 19 supports invoice follow-ups based on overdue days, with channels including email, SMS, WhatsApp, post and manually scheduled actions, depending on configuration and available services. It can assign a responsible user, schedule reminders and record contact history in the customer chatter. But it does not decide whether a disputed delivery is valid or whether an unidentified receipt belongs to the invoice in question.
Odoo’s own documentation advises reconciling bank transactions before starting follow-ups, precisely because an invoice can remain open while a customer payment has already reached the bank. This ordering should be a design requirement, not a courtesy check after a complaint.
Segment the ledger before configuring reminder levels
| Account condition | Recommended action | Human review needed |
|---|---|---|
| Undisputed overdue invoice | Use a defined automatic reminder after reconciliation | Check approved timing and communication tone |
| Payment received, not matched | Pause reminder and investigate unapplied cash | Match only when reference and evidence agree |
| Partial payment | Assign a collector and next-action date | Confirm the remaining agreed balance |
| Delivery or price dispute | Hold disputed portion and create a review task | Finance and sales validate contract and delivery evidence |
| Strategic account / broken promise | Use named relationship owner and manual contact | Balance recovery with contract and relationship risk |
The collection sequence that avoids preventable errors
-
Reconcile incoming bank transactions and payment channels to the customer ledger.
-
Review unmatched cash, short payments, credit notes and customer claims.
-
Identify the undisputed balance and hold items requiring evidence review.
-
Assign the next action to a collector, with a due date and documented owner.
-
Record the outcome in Odoo and resume follow-up only where the amount and customer status are defensible.
This order reduces false chases and makes escalations more credible. Customer statements or screenshots can help locate a receipt, but should not replace bank evidence and proper reconciliation.
Illustrative case: the disputed part-payment
A Zimbabwean distributor issues an invoice to a key account. The customer reports both a short delivery and a payment already made. Instead of escalating the full balance, the collector checks the purchase order, dispatch note, proof of delivery, bank transaction and relevant contract terms. Finance reconciles the cleared cash; sales determines whether the disputed quantity calls for a credit note or adjustment. The team then resumes collections for the amount not in dispute.
The value is accurate customer communication and a clear audit trail, not a hypothetical cash-saving claim. The business can pursue what is due without asserting that a genuine query has already been resolved.
Illustrative case: an invoice remains open after payment
A retailer receives funds through its usual bank channel with an incomplete reference. Odoo cannot confidently match the receipt, so the invoice remains outstanding. The finance team places the item on an unapplied-cash list and investigates using invoice details, payer identity and bank information. It does not clear the account against a guess or issue an accusatory reminder during review.
Once the payment is correctly matched, the ledger and the customer communication should tell the same story. A daily review of unapplied cash is often more valuable than increasing the frequency of reminder messages.
Configure Odoo controls around collection quality
Set follow-up levels by overdue days and customer segment. Require defined approval for escalation templates, restrictions on accounts with unresolved disputes, responsible-user ownership and a review date for exceptions. Check whether the relevant message channel is available and properly enabled in the installed Odoo environment; WhatsApp, SMS and mailed letters can require additional setup or messaging credits.
Where the business offers payment plans or promise-to-pay arrangements, record the agreed terms, next action and reviewer. A verbal promise with no due date or owner should not be treated as collected cash.
What managers should measure
| Measure | Operational meaning | Management use |
|---|---|---|
| Unapplied cash: value and age | Funds received but not allocated confidently | Prioritise matching before customer reminders |
| Collection effectiveness / DSO | Collection performance and working-capital pressure | Monitor trends alongside other controls |
| Dispute count and resolution time | Billing, service or delivery issues affecting collection | Escalate recurring root causes |
| Promise-to-pay kept rate | Follow-through on agreed commitments | Focus human contact on unreliable accounts |
| Cash auto-match accuracy | Quality of automation, not merely volume | Review matching rules and exceptions |
| Receivables ageing | Exposure by overdue period | Target overdue but undisputed amounts |
Days sales outstanding (DSO) is useful, but cannot explain a rising dispute backlog or payments that have not been allocated. Review a small set of complementary measures with stable definitions and drill down to the underlying transactions.
Remember the IFRS 9 judgement
The aged receivable report helps management identify overdue balances, but the accounting estimate of expected credit losses requires more than ageing alone. Where IFRS 9 applies, historical collection or loss experience should be assessed alongside current conditions and reasonable, supportable forward-looking information. The finance team must exercise judgement over significant disputed or doubtful accounts.
A practical receivables review checklist
-
Bank feeds and other receipts reconciled before the follow-up run.
-
Unapplied cash and partial payments reviewed daily or at an appropriate transaction frequency.
-
Disputed invoices marked, assigned and excluded from routine escalation as configured.
-
Reminder channels, thresholds and message tone approved by finance management.
-
Each sensitive account has a named collector, next action and documented commitment.
-
Ageing, collection outcomes and customer complaints reviewed together.
Frequently Asked Questions
Can Odoo send automated invoice reminders?
Yes. Odoo 19 follow-up levels support automatic or manual actions and several channels, depending on installed services and configuration.
Should every overdue balance receive the same message?
No. Undisputed invoices can follow a standard sequence; part-payments, disputes and strategic accounts need judgement and named responsibility.
Why reconcile before reminding?
An invoice may remain outstanding in the software while a corresponding payment has already reached the bank. Reconciling first prevents incorrect reminders.
Is receivables ageing sufficient for IFRS 9 provisions?
No. Ageing informs the assessment, but expected credit losses also require appropriate historical, current and forward-looking information.
How SERPA can help
SERPA configures Odoo receivables workflows, bank reconciliation, follow-up policies and exception reporting to reflect actual payment channels and customer relationships. Request a consultation to review your accounts receivable controls and collections workflow.