An overdue invoice is an accounting fact; collecting it is a sequence of customer conversations, checks and decisions. A useful collections workflow makes each commitment visible while the ledger remains the authority for balances, payments and credit notes.
Start with an accurate balance
Before contacting a customer, confirm that receipts are reconciled and the invoice is genuinely overdue. Check whether there is a credit note, billing error or existing dispute. Odoo's standard invoice follow-up already supports overdue reminders and assigned follow-up activities; do not duplicate those functions without a clear need for cross-team exception handling.
What is a promise to pay?
It is a recorded customer commitment to pay an agreed amount by an agreed date. Record the invoice reference, amount, date, contact outcome, customer contact and the colleague responsible for the next check. A conversation note is not proof that the money arrived: verify the payment against the ledger before marking the promise fulfilled.
Use a clear path from contact to resolution
- Identify the item: confirm the overdue balance and the correct customer contact in the governed finance system.
- Contact with context: use the approved channel and record the outcome without exposing unnecessary personal information.
- Classify the response: distinguish paid, promised, disputed, unable to pay, wrong contact and no response. Each needs a different next action.
- Assign the next owner: record the action, due date and evidence needed. A dispute may require sales, service or finance input rather than another reminder.
- Verify closure: reconcile payment, resolve the dispute or record the authorised decision. Do not close merely because a reminder was sent.
Handle missed promises without automatic pressure
If a promised date passes, first check for a payment in transit or a reconciliation delay. Then review the customer's history and any open dispute. A reminder or escalation should follow approved policy and be proportionate; the workflow should show who reviewed the exception and what they decided. Do not describe an automated step as a legal demand or threaten an outcome the business has not authorised.
Keep disputes in their own lane
A customer who contests the invoice needs a reason, supporting documents, a decision owner and a target review date. Record whether the issue concerns pricing, delivery, quality or allocation. The person resolving the dispute should update the relevant commercial or accounting record under existing controls. A promise-to-pay date should not conceal an unresolved dispute.
Illustrative example
A customer says an invoice includes an incorrect service charge. The collections owner records the invoice reference and the disputed line, then routes the evidence to the service owner. Finance keeps the original ledger record intact while the charge is checked. If a correction is approved, the authorised accounting process makes it. The collections owner then confirms the revised balance with the customer and records the next agreed action. This is an illustrative process, not a claim about a customer result.
Measures that help managers intervene
- Promises due this week, fulfilled only after ledger verification, and missed after reconciliation checks.
- Open disputes by age, cause and decision owner.
- Follow-ups with no next owner or date.
- Customer contacts repeated after payment or while a dispute remains unresolved.
Use these measures to improve accuracy and resolution, not to reward the highest number of messages sent.
Where Intelliflow fits
Odoo or another accounting system remains authoritative for invoices, payments, statements and standard follow-ups. Intelliflow can be configured to coordinate exception ownership, cross-team decisions and evidence where the standard follow-up path is insufficient. The exact reminders, integrations, permissions and customer messages must be tested in the target deployment and approved under the organisation's policy before use.
Frequently asked questions
Does a workflow change the amount owed?
No. A workflow tracks the work and decisions around the account; authorised accounting actions change the ledger.
Should every overdue invoice become a separate case?
Not necessarily. Standard follow-ups may be enough. A case is more useful when there is a dispute, cross-team decision, repeated missed commitment or other exception that needs visible ownership.
To review a real, governed collections path, book a working demo. Related reading: rules for follow-up.
Intelliflow Editorial Team. This is an operating-process example, not legal, credit or financial advice. Apply local policy and obtain appropriate review before customer-facing use.
Source
Odoo 18: follow-up on invoices explains native reminder and follow-up capability, including the need to reconcile bank transactions before follow-up.