Practical guide
Credit control before shipment: designing the decision flow
Credit control before shipment checks an order against the customer’s credit limit, overdue receivables and recorded payments before goods leave the warehouse. The decision should release the order, block it or send a controlled exception for approval.
- Pre-shipment Receivables Control
- Finance & AR for Distribution Credit Control
- Aktashwater: accounts receivable broken down by product group

In detail
Finance, sales and the warehouse need a shared answer: may this order ship, and who decides when its terms are not met? A receivables report shows debt; a pre-shipment check turns it into an action: proceed, hold the order or review an exception. The status should explain the reason and next step, rather than show only a red or green indicator.
A credit limit and available credit are different amounts. First define whether the check applies to a customer, contract or agreed group. Several outlets may share one payer; a separate outlet record does not establish a separate limit. The policy defines the calculation currency, exchange-rate source and conversion date. Exposure may include invoices, accepted orders and uninvoiced shipments. Confirm the scope and whether the current order is already included to avoid counting it twice. Available credit does not override an overdue-debt rule.
A decision needs a source, update time and complete data. Distinguish a promise to pay, a confirmed receipt and allocation to the customer and documents. Money may have arrived while a particular invoice remains open: policy determines how an unallocated payment affects available credit, not a message from a sales manager. With stale data, a review status proves neither overdue debt nor permission to ship. Name the reconciliation owner and the action allowed until the review is complete.
An exception applies to a specific order version, amount and validity period. For a partial shipment, specify the approved portion and how the remainder will be checked: approval of one portion does not authorize the whole order. Record the breached rule, rationale, approver and recheck conditions. A promised payment can support the request but cannot be treated as settled debt. A one-off approval must not silently change the limit for later orders.
Two orders for the same payer may rely on the same available credit. Define when exposure updates and when the check repeats before shipment. For partial fulfillment, link the remaining order, shipment and invoice: an amount must neither be counted twice nor disappear from the calculation. A cancellation or return request does not release credit until the event required by policy is confirmed. The log retains the data snapshot, rule version and decision basis; a later payment cannot explain an earlier approval.
For a discussion, prepare an anonymised order, partial shipment, invoice and payment chain, with the credit snapshot used for the decision. Add a hold and a limited approval example. Compare the expected outcome with warehouse action: which amount is released, what remains under review and who resolves a discrepancy. First validate rules and data; assess any effect on overdue debt or approval time separately using comparable records.
How it is applied
- Choose a customer group and checkpoint. Identify the payer, limit scope, currency and owners in sales, finance and the warehouse.
- Describe the sources, update times and links between an order, partial shipment and invoice. Define which confirmed events change exposure.
- Prepare cases of overdue debt, a limit breach, an unallocated payment, an unconfirmed receipt and partial fulfillment, with the expected decision for each.
- Record approval authority, order version, released amount and exception expiry. Specify how the remainder is checked and when changed data triggers a recheck.
- Reconcile test decisions with the financial source and the warehouse action; assign an owner to each discrepancy.
Practical checklist
- The systems of record for receivables and payments are explicitly named.
- Credit-limit and overdue rules are approved by the finance owner.
- An exception cannot proceed without an accountable person and a reason.
- The warehouse receives an unambiguous status without reconciling reports by hand.
Scope and limits
Distribution credit control supports an operational decision but does not replace financial accounting or the company’s contractual policy. Financial data sources and legal grounds are defined within the implementation.
