Down Payments in a Business App: An Advance Invoice Is Not an Instalment Plan

Before adding a deposit button to an order app, ask your accountant what the business actually needs: an advance invoiced separately, or one invoice paid in instalments. The customer may pay in stages in either case, but the document relationships are different. Your software should implement the approved process, not choose it from a convenient button label.

This article concerns software requirements. It does not determine when tax is due, which document is legally required or how a refundable security deposit should be accounted for. Those decisions need the appropriate professional review.

Identify the document the first payment belongs to

The Odoo 19 downpayment guide explicitly distinguishes downpayment invoices from payment terms or instalment plans. In its documented model, a single invoice requiring several payments uses payment terms with an instalment plan instead.

Use that distinction when briefing your developer. Is the first customer request a separate advance invoice, an amount due against an existing invoice or something else approved by your accountant? Show the related order and document clearly. Avoid displaying the same advance as both a separate additional charge and a payment already reducing another invoice without a defined relationship.

If the business means a security deposit that may be returned, say so immediately. Do not assume a sales downpayment workflow is suitable simply because both are called “deposit”.

Define the amount and its approved basis

Odoo documents percentage and fixed-amount downpayment options. Your app still needs a rule for the basis: which order version and which included amounts does the requested advance refer to? Have the accountant define tax treatment and the developer demonstrate the calculation using approved test cases.

An order change should not silently rewrite an advance invoice already issued. Decide who reviews the changed position and which permitted follow-up document or adjustment is needed. Preserve the earlier basis so staff can explain it.

Keep the invoice request separate from evidence of payment. A prepared advance document does not prove funds arrived. Also specify whether the business may start work before payment confirmation; this is a reviewed business rule, not something to infer from a document being posted.

Show how the advance reaches the final invoice

Require a demonstration of the whole cycle, not merely creation of the initial request. Staff need to see the advance document, its actual payment status and how it is accounted for in the final billing position. The customer should not be asked to pay the same amount twice because two screens use unrelated totals.

A full advance is an important test case. Odoo documents that a 100% downpayment still requires another invoice to complete the sales order. Do not infer “no final document needed” from a zero remaining payment alone.

There are configuration limits to check as well. The same guide warns of deduction complications with delivered-quantity invoicing when the delivered value is below the advance, and discusses negative-total and credit-note handling. Do not turn the simple demonstration into a promise that every partial-delivery case nets automatically. Have your implementer and accountant review the actual configuration and show the approved outcome.

Accept the financial trail with test records

Use a fixed advance, a percentage advance and a full advance in a test environment. Follow each from preparation through the confirmed payment evidence to final invoicing. Add an order change and a partial delivery that does not yet support the expected deduction.

Check what the customer sees, what staff can reconcile and which exception still needs review. Do not erase an advance record merely to make the outstanding total look tidy. Capture the expected document relationships in your acceptance criteria when planning the order app. A working deposit feature needs an explained final position, not just a successful first collection.