Advance offset

Two events sit at opposite ends of a contract: the money moves at the start, the invoice is raised on delivery. In between, the two records live separate lives, and in Turkiye they usually live in separate accounts as well, because local practice tracks advances received and advances paid outside the trade account. The counterparty may have booked the same cash straight against the trade account instead. Nobody has made a mistake, yet the two balances no longer agree, and the gap is exactly the advance. The offset is the entry that ends that split: the prepayment is applied to the invoice it belongs to, and only the genuinely unpaid remainder stays open. The longer the offset waits, the fewer people remember which order the money was for, so this is a linking job to be done as movements arrive, not a period-end clean-up.

The figure worth quoting is net exposure: gross balance minus advances that have not yet been applied. Staged delivery is where this turns mechanical. If a contract is delivered in four lots and the advance is a fifth of the contract value, each invoice should absorb a fifth of its own amount from the advance account, which shrinks with every offset. Lots are rarely equal, so in practice one invoice swallows the whole advance and another absorbs none, and the leftover rolls forward until it looks like a balance nobody can explain. Deposits and performance guarantees deserve separate treatment here: they are held to be returned rather than applied to an invoice, so carrying them alongside advances makes an account look prepaid when it is not. iFinances keeps advance movements in the same table as invoices and payments, flags an unapplied advance with its own written reason, and reports net exposure separately. The offset entry itself is made in your own system by you.

Three misreadings follow the term around. The first is confusing an offset with netting: an offset links money already paid inside one commercial relationship to its own invoice, while netting settles mutual receivables and payables across two different accounts and needs both parties to agree to it. The second is treating an unapplied advance as unpaid debt. The cash moved months ago and only the link between two records is missing, but the practical cost is a collections team chasing a receivable that does not exist and a customer relationship strained over nothing. The third surfaces at audit: until the advance is applied, neither the receivable nor the payable balance reflects the real position, which is why the advance account is asked for as its own aged list at period end.