Skip to content
Bodek Ledger

Part payments and split payments

One payment across several invoices, or several payments against one. Each is its own auditable row.

Updated · 2 min read

On this page

Real money does not arrive in the shape of your invoices. Ledger is built for that rather than against it.

Several payments against one invoice

A $15,000 invoice paid $2,000 now and $13,000 in March is two payment records, both applied to the same invoice.

The invoice shows Part paid, with $2,000 received and $13,000 outstanding, and both payments listed as rows you can click through to. Nothing was overwritten and the first payment is still a separate, dated, attributable fact.

One payment across several invoices

A customer sends $8,000 covering three invoices. Record the one payment of $8,000, then open it and apply amounts against each invoice.

Fill oldest first does the obvious allocation for you — oldest invoice first until the money runs out — which is what most people want and what most contracts say.

Money you cannot place yet

Record the payment and apply none of it. It sits as unapplied, which is the honest description: the money is real, where it belongs is not yet known.

Unapplied money shows on the contact's record and on the customer statement, so it does not get forgotten, and it is a real credit — the customer's balance already reflects it.

Overpayments

If somebody pays more than they owe, record what actually arrived. The excess stays unapplied as a credit on their account and can be applied to the next invoice or refunded.

Ledger will not let you apply more to a document than it owes, which is what stops a credit quietly vanishing into a rounding difference.

Changing your mind

Un-apply detaches an applied amount. The payment stays recorded and becomes free again. The invoice goes back to what it was owed before.

Nothing is deleted and nothing needs a correcting entry, because applying is a link rather than a posting.

What is guaranteed

amount_paid and balance on every document are derived from the applications, recomputed whenever anything changes, and never written directly by any code path. That is why a part payment cannot leave a wrong balance behind — there is no stored number to go stale.

Settings → Check the books re-derives all of them and reports any disagreement. It should always find none.

Still stuck? Contact support and we'll get back to you as soon as possible.