Connecting receivables, credit limits and accounting facts

This article is for sales, finance and IT leaders who need an explainable order decision. A promise to pay, confirmed receipt, a recorded payment and settlement of a specific debt are different facts. Agree which source confirms each fact and who investigates discrepancies. The sales status should show the basis of the check rather than stand in for accounting.

Outstanding receivables and overdue debt are not the same. An open invoice may not yet be due under the agreed terms; overdue status depends on the due date and review date. Reconcile the same customer or approved group, legal entity, contract, currency and point in time. Aggregating currencies requires an agreed exchange rate and conversion date. Record separately whether taxes are included and which documents form the position.

A notification, payment instruction or screenshot does not prove that a debt has been settled. Even confirmed receipts may remain an advance or be unapplied to the relevant invoices. For partial payments, retain links to the settled portion and outstanding balance. If a receivables snapshot already includes a payment, do not subtract it again. Returns, adjustments and payment reversals affect the position only on a confirmed basis under company rules.

A simplified calculation subtracts recorded receivables and the new order from the limit. It describes the remainder only when there are no other included commitments. A real rule must specify whether other open orders and uninvoiced shipments are included, while avoiding counting the same commitment twice. A positive remaining limit alone does not authorise shipment: overdue debt, contract terms or customer status may impose other restrictions.

Retain the values, sources, snapshot times and rule version used in the decision. A payment, limit change or revised order amount may require a new check. For concurrent orders, define how previously accepted commitments are counted: two checks against the same available amount can produce an incorrect combined decision. If an exchange response is lost, establish the outcome in the receiving system before retrying; a blind retry may create a duplicate.

Record an exception against a specific order, amount, reason, authorised approver and expiry. It does not erase debt, overdue status or decision history. Disputed amounts, stale snapshots and unconfirmed payments need a clear status, owner and recheck condition. Bring an anonymised document chain and one real type of discrepancy to the process discussion. This helps define a verifiable initial scenario without promising a universal credit rule.