Payment terms that follow the contract
A contract carries its own payment term, dated like its other terms. Every invoice takes its due date from a clear order of levels and shows which level decided.
The problem
The client's default is 30 days, but the new framework agreement says 15, and one project was agreed at 45. When the term lives only on the client, someone has to remember to change the due date on every invoice, and when the contract changes mid-year, older invoices must not change with it.
How Doktally solves it
- A payment term on the contract, versioned like its rate and limits: a change applies from a date and the history is kept.
- One clear order decides the term of each invoice:
- the term picked on the invoice by hand;
- the project's term, when the invoice bills that project;
- the term of the client's contract in force on the invoice's day, in that day's version;
- the client's term;
- the organization's default.
- The source is shown: the invoice says which level decided its due date, so nobody has to guess.
- Drafts keep a hand-picked term when they are rebuilt; issued invoices never change.

The result
Due dates match what was signed, invoice after invoice, and a renegotiated contract changes only the invoices from its date on.
Technologies
Contracts, Payment terms, Java
- Published: 2026-11-19
- Project: Doktally — Invoicing, time billing and VAT for small businesses
- Case study