When sales agrees different percentages and dates with a customer, the practical question is how those payments appear on one invoice so finance knows what is due and when. At ToDoOps we rely on the official Odoo 19 documentation from Odoo 1 for the application behavior, and on the public overview of IFRS 15 from the IFRS Foundation 2 for the difference between a due date and revenue recognition.
Why one invoice with a due-date schedule?
Odoo’s documentation describes payment terms as covering due dates, early payment discounts and other conditions, and an installment plan as paying one invoice in parts, with amounts and dates the seller defines in advance 1. It also notes that issuing several invoices for one order is neither a payment term nor an installment plan; it is an invoicing policy.
This guide covers the first case: one invoice with several due dates. Separate advance invoices deducted from a final invoice, and chasing overdue debts, are different topics.
Hypothetical example: a SAR 10,000 invoice
The following example is hypothetical, for explanation only, and is not a customer case. An invoice issued on 21 November 2026 carries an agreed face amount of SAR 10,000. We do not discuss any tax calculation here.
| Installment | Share | Amount (SAR) | Due date | Rule |
|---|---|---|---|---|
| First | 30% | 3,000 | 21 Nov 2026 | Invoice date |
| Second | 40% | 4,000 | 21 Dec 2026 | 30 days after |
| Third | 30% | 3,000 | 20 Jan 2027 | 60 days after |
| Total | 100% | 10,000 |
If an actual payment of SAR 3,000 is registered and reconciled against the first installment, SAR 7,000 remains on the same invoice. No new invoice is created, and the schedule does not mean collection happens automatically. Test that the payment is allocated to the intended installment before approving the setup.
If you agree two equal installments instead, each becomes SAR 5,000. Keep the invoice total unchanged and document the schedule agreed with the customer.
Configuring terms in the Odoo application
According to the documentation 1, you create the term under Accounting ‣ Configuration ‣ Payment Terms, then New. The steps:
- Enter a clear name, such as “30/40/30 on 0/30/60 days”.
- In the Due Terms section, add three lines: 30% with After at 0 days, 40% after 30 days, and 30% after 60 days. Choose the days-after-invoice-date option rather than the end-of-month option, since this example does not depend on month end. Check the option label on your own version’s screen.
- Enter 21 November 2026 on the Example line to see the resulting payments and dates before saving.
- Tick Show installment dates if you want the installment breakdown on the invoice report, and enter the displayed text in the Preview column.
Lines are computed in the order of their due dates. Our recommendation is to keep the percentages summing to 100% at all times. The early discount option sits on the same screen, but we do not recommend enabling it before a localization and accountant review in Saudi Arabia.
The end-of-month case
The Days end of the month on option adds a buffer so an invoice registered at the end of a month does not fall due on the first day of the next. Odoo adds the After days to the invoice date, moves to the end of the resulting month, then adds the number set for the following month 1. In the documentation’s example, the setting is five days, then day 1.
- Invoice dated 5 March: 10 March, then 31 March, then 1 April.
- Invoice dated 28 March: 2 April, then 30 April, then 1 May.
To fall due a number of days before month end, the documentation points to a negative value in After.
Journal entries and reconciliation
An invoice with multi-line terms generates one journal item per due date, rather than a single item at the final balance date 1. In our example the receivable shows three items, SAR 3,000, 4,000 and 3,000, each with its own date. That is what makes reconciliation, installment follow-up and the aged receivable report more precise.
A due date alone does not decide when revenue is recognized. The IFRS 15 overview describes revenue as reflecting the transfer of promised goods or services, recognized as obligations are satisfied 2. So the schedule serves collection and reconciliation, and any accounting or tax treatment stays with your accountant.
Scope and what does not change
The term can be set on a contact (the Sales & Purchase tab) so it becomes the default on that contact’s new orders and invoices. It can also be set on a quotation or sales order so the resulting invoices inherit it, or directly on the invoice 1.
Changing a customer record does not prove that previously posted invoices were rewritten. We do not promise automatic migration of existing records; open invoices are reviewed case by case.
We suggest the project scope list the required terms, the customers covered, the print documents, sample data and the testing team. For sizing, start with the calculators. Related pages: Finance applications, Sales applications and wholesale solutions. For a general look at the Sales and Inventory interface, the demo is available; it does not show advanced features or accountant settings.
Acceptance tests
We suggest running these on a test environment before sign-off:
- Preview: the Example line dated 21 November 2026 gives 3,000, 4,000 and 3,000 with the dates in the table.
- Partial payment: registering SAR 3,000 and reconciling it to the first installment leaves SAR 7,000 on the same invoice.
- Credit note: record a test credit note, check its effect on installments and balance, and document it.
- Rounding: use an amount that does not split evenly and confirm the installments sum to the invoice.
- Leap year and month end: try valid month-end dates, including 29 February 2028.
- Document language: check printing in Arabic and English, the Preview text and installment dates.
- Overdue installment only: the first is overdue and the others are not yet due; review the aged receivable report.
- Contact override: a customer whose default term differs from the sales order’s; confirm which one reaches the invoice.
Frequently asked questions
Do three installments mean three invoices?
No. It is one invoice with three due dates. Several invoices for one order are an invoicing policy, according to the documentation 1.
Does an installment date decide when revenue is recognized?
No. A due date alone does not decide that, per the overview 2, and the accounting decision belongs to your accountant.
Does changing a customer’s terms change their old invoices?
We do not assume so. The change concerns defaults on new documents, and posted invoices are reviewed separately.
Conclusion
One invoice with a clear due-date schedule gives sales and finance visible installments, easier reconciliation and a sharper view of receivables. It rests on correctly configured lines, a known boundary for what a change affects, and written acceptance tests. If you have a schedule such as 30/40/30, share the number of terms, customers and documents through the contact page so we can discuss a defined scope, and start sizing with the calculators. More is on the home page.
Source notes
- [1] Odoo, official Odoo 19 documentation, the payment terms and installment plans page. We used it for the definitions of terms and installments, setup fields, the end-of-month option, application on contacts and documents, and journal items by due date.
- [2] IFRS Foundation, public overview of IFRS 15. We used it only for the idea that a due date does not decide revenue recognition. It is not the full standard.
The SAR 10,000 example is hypothetical, and the operating recommendations are proposed checks for your scope.
