---
title: "Wholesale credit exceptions: who approves the next delivery?"
canonical: https://www.billabex.com/en/blog/wholesale-overdue-customer-delivery-approval/
lang: en
alternate: https://www.billabex.com/fr/blog/grossiste-validation-livraison-client-retard.md
alternates:
  fr: https://www.billabex.com/fr/blog/grossiste-validation-livraison-client-retard.md
  en: https://www.billabex.com/en/blog/wholesale-overdue-customer-delivery-approval.md
  de: https://www.billabex.com/de/blog/grosshandel-lieferbestaetigung-kunde-verspaetet.md
  es: https://www.billabex.com/es/blog/mayorista-quien-valida-nueva-entrega-a-cliente-con-retraso.md
  it: https://www.billabex.com/it/blog/grossista-approvare-consegna-cliente-in-ritardo.md
  nl: https://www.billabex.com/nl/blog/groothandel-levering-goedkeuren-klant-met-achterstand.md
  pl: https://www.billabex.com/pl/blog/hurtownia-zgoda-na-dostawe-klientowi-z-zalegloscia.md
  pt: https://www.billabex.com/pt/blog/grossista-validacao-entrega-cliente-atraso.md
updated: 2026-11-16
index: https://www.billabex.com/llms.txt
---

# Wholesale credit exceptions: who approves the next delivery?

The driver is waiting, the customer is calling sales, and the warehouse sees an order blocked for overdue invoices. Each team holds part of the information. Sales understands the urgency, accounting sees the arrears, and logistics knows the goods are ready. Without a clearly assigned decision, the person under the most immediate pressure may authorise release.

That turns a credit exception into a coordination problem. A wholesaler needs a process that produces a quick but explainable decision: which delivery is approved, against what financial position, by whom and until when? It must also distinguish an internal credit policy from commitments already made to the customer. The examples and legal discussion below concern wholesale B2B operations in France.

## Identify the debtor before focusing on the warehouse

A customer may order from several stores and request delivery to several sites while one company receives all invoices. Conversely, a trading name may cover distinct legal entities. The name displayed at the loading bay therefore does not establish the account perimeter that needs review.

[GS1 France describes the GLN as a 13-digit identifier](https://www.gs1.fr/obtenir-vos-codes/gln-lidentite-numerique-votre-entreprise) for entities and locations, including warehouses and billing functions. This standard helps distinguish destinations. It is not a solvency measure, and several GLNs do not necessarily mean several separate debtors.

The decision record should connect the invoiced entity to the relevant locations and open orders. Otherwise, each warehouse may believe it respects a local limit while total exposure to the same company keeps rising. A common identity comes before the choice of threshold. Where records conflict, clarify the relationship instead of authorising delivery under whichever account currently appears available.

## Give each team a fact to confirm

Sales explains the commercial context: an unusual order, goods needed for a specific operation, the consequences of postponement and the customer’s response. It separates confirmed facts from its impression of the relationship. “Longstanding customer” provides context but does not establish that payment has occurred.

Accounting confirms open invoices, their due dates, payments actually reconciled and disputed amounts. Logistics identifies goods already dispatched, goods prepared and other orders that might leave the same day. Management or its authorised delegate decides within the defined limits. These roles can be combined in a small business, but the checks remain distinct.

The warehouse should not interpret credit terms or compare bank screenshots forwarded by telephone. It needs an executable instruction: identified order, approved maximum amount, any condition requiring verification and the decision-maker’s name. If instructions are missing or contradictory, the process specifies who can resolve them before the shipment leaves.

## Calculate exposure after the proposed operation

An approval based only on the overdue invoice often ignores what happens next. For the internal decision, combine open receivables with deliveries already committed that are not yet included in the accounting balance. Avoid counting the same goods twice where a shipment has already been invoiced.

Consider a fictional example using amounts consistently including VAT. The customer has €10,000 of open invoices, of which €8,000 is overdue. An uninvoiced delivery is worth €1,000. The proposed new dispatch is €3,500. Exposure after dispatch would therefore reach €14,500 before other movements.

Sales reports an expected €2,000 transfer. Until receipt has been verified under the chosen procedure, keep it as anticipated information. Once the payment has actually been reconciled, calculated exposure would fall to €12,500. If the fictional delegation allows up to €12,000, it would still not authorise the complete proposed dispatch.

These figures recommend no universal credit limit. They show why an announced payment does not establish that a new order falls within authority. The decision-maker can assess other arrangements within the agreement, but should do so using the actual total and visible assumptions. A smaller release, different timing or another commercial response each requires its own explicit decision.

## Write authority so the decision can be reproduced

A delegation can specify an amount limit, the types of arrears covered, exclusions and a substitute decision-maker. More importantly, it states what must return to management: a serious dispute, an unfulfilled commitment, uncertain debtor identity or exposure outside the delegated range.

“Sales may release good customers” provides no verifiable criterion. A usable decision is more precise: authorisation for the identified order, within the approved amount, after confirmation of the stated payment, valid during the defined period. Name the person responsible for checking the condition so that a second team does not assume the first has already done it.

An earlier authorisation should not be treated as indefinitely reusable. An exception for Monday’s delivery must not automatically release another order on Thursday. The owner needs to retrieve the approved operation and establish that it was executed once. Where the amount or date changes, the decision should be reassessed rather than copied without review.

## Distinguish an internal hold from a right to suspend

Credit policy is a management tool. Refusing to perform an already accepted commitment also requires assessment under the agreement and applicable law. [Article 1219 of the French Civil Code](https://www.legifrance.gouv.fr/codes/article_lc/LEGIARTI000032041509) addresses withholding performance where the other party’s non-performance is sufficiently serious. Crossing a software threshold does not automatically establish those conditions.

Distinguish a new order not yet accepted from a delivery already contractually due. If management considers suspension, it should assess the circumstances and necessary communication. Logistics should not discover that decision in front of the driver or customer. A clear commercial answer is easier to implement than an unexplained system status.

[Service Public Entreprendre explains that payment terms operate within the applicable framework and belong in commercial documentation](https://entreprendre.service-public.gouv.fr/vosdroits/F23211). Before labelling the customer overdue, verify the correct due date, especially where sector-specific provisions apply. An incorrect date can create an unjustified hold and a needless argument about a customer’s reliability.

## Close the loop after the goods leave

The authorised shipment must feed back into the record: quantity dispatched, relevant delivery note and subsequent invoice. [Matching partial deliveries to invoices](https://www.billabex.com/en/blog/wholesale-partial-deliveries-invoice-collections/) prevents a €3,500 authorisation being treated as €3,500 actually dispatched where only part of the order left the warehouse.

Sales should receive the outcome as well. It can then explain the next step without making another inconsistent promise. If further payments were agreed, a [payment schedule](https://www.billabex.com/en/blog/payment-schedule/) records their amounts and dates. A vague release message is not a substitute for that agreement, nor does it establish that every future order will receive the same treatment.

When reviewing the account, management should examine repeated exceptions and their causes. A customer released every week may reveal a poorly defined limit, incorrect billing relationships or repeatedly unfulfilled payment commitments. Those findings lead to different actions. Counting releases alone would not explain whether the policy or execution needs attention.

A [shared payment register](https://www.billabex.com/en/blog/tracking-client-payments-with-excel-download-our-free-template/) and the [Billabex agent](https://www.billabex.com/en/product/agent/) can support circulation of the relevant context. Approval to deliver remains assigned to the appropriate person and documented so that warehouse staff can execute it without becoming the final arbiters of customer credit risk.
