---
title: "Month-end supplier payment runs: working with customer cut-off dates"
canonical: https://www.billabex.com/en/blog/month-end-payment-runs-customer-cutoff/
lang: en
alternate: https://www.billabex.com/fr/blog/paiements-fournisseurs-fin-mois-cloture-client.md
updated: 2026-09-19
index: https://www.billabex.com/llms.txt
---

# Month-end supplier payment runs: working with customer cut-off dates

“The payment run has closed; your invoice will go through next month.” That reply can describe two very different situations: a document genuinely arrived too late for the announced processing window, or the customer's organisation routinely pushes payments beyond their due dates. To decide what to do next, you need to understand the stages of the cycle and establish where your invoice actually stopped.

Working with a customer's cut-off means preparing approval and obtaining confirmation early enough. It does not mean quietly replacing the due date in your account records. You can recognise an operational constraint while preserving the contractual date and any resulting delay. Those facts serve different purposes: organising the work, establishing the account position and forecasting when cash may become available to your business.

## Find out which stage has closed

“Closed” may refer to invoice entry, selection of a payment proposal, approval by a signatory or transmission of a bank file. A team may still be able to add an invoice to a proposal while being unable to amend instructions already transmitted. The first useful question concerns the stage: “Has invoice selection finished, or have the payment instructions already been executed?”

The distinction exists in software used by purchasing organisations. Microsoft explains that Dynamics 365 Finance's automated payment proposals create a journal without automatically posting it, leaving subsequent validation possible. A completed proposal is therefore not evidence that your bank has received the funds. This is a documented software example, rather than a claim about how your particular customer has configured its system. [Microsoft documentation](https://learn.microsoft.com/en-us/dynamics365/finance/accounts-payable/automate-vendor-payment-proposal).

Ask what makes an invoice eligible for selection: receipt through the right channel, purchase order matching, service approval or a due date inside the run's selection period. If a [purchase order is missing](https://www.billabex.com/en/blog/missing-purchase-order-blocked-invoice/), sending a reminder earlier will not resolve that condition. You need to identify the owner and the missing evidence, rather than simply schedule another message to the same address.

## Keep the due date separate from the customer's internal calendar

For French business transactions, the DGCCRF sets out general limits of **60 calendar days after invoice issue**, or **45 days end of month** subject to contractual conditions, alongside rules specific to certain transactions and sectors. An applicable maximum does not replace a shorter agreed term. A monthly payment run does not, merely by existing, establish a new contractual payment deadline. [DGCCRF guidance](https://www.economie.gouv.fr/dgccrf/les-fiches-pratiques/delais-de-paiement-les-regles-connaitre?language=fr).

France's Observatory of Payment Terms identifies insufficient payment runs, inadequate preparation and registration subject to imposed cut-off dates as sources of delay. Its analysis supports looking at the organisation instead of treating each missed date as an isolated accident. The publication discusses French business practices; it does not provide a prevalence estimate for these problems in your own customer portfolio. [Guide, page 15](https://www.banque-france.fr/system/files/2024-11/Guide_Bonnes_pratiques_ODP_V6.pdf).

Maintain three distinct dates: the applicable due date, the customer's next announced processing event and your own review date. Adding an operational milestone should not overwrite the first. Where a European contract is governed by another jurisdiction, check the relevant rules before importing French limits or making a legal assessment. The operational method travels across borders more readily than any particular country's statutory payment regime.

## Work backwards from the expected payment

Start with the date on which the customer expects funds to be released, then establish when invoices are selected and when approvals must be complete. The required preparation margin depends on the actual route. One available contact may resolve an issue quickly; several absent approvers may make the same request take longer. Avoid presenting a fixed number of preparation days as universally sufficient.

Gather the references accounts payable actually uses: invoice number, entity, purchase order where relevant, open amount and requested evidence. A pre-cut-off check can be concise: “Is invoice F241, due on 30 September, approved for the announced run? If not, which approval is outstanding and who can complete it?” That wording asks for information you can act on, instead of another acknowledgement that the email has arrived.

If the usual contact has left, first [rebuild the payment route](https://www.billabex.com/en/blog/accounts-payable-contact-left-payment-route/). Knowing the deadline provides little value when documents go to an inactive mailbox. Record the confirmed channel and the replacement contact's role. Otherwise your team can repeatedly prepare a correct package and still send it to someone who no longer has access or authority to move the invoice forward.

## Calculate the effect of missing a run

Consider an entirely simulated case. An **€18,000 invoice** is due on 30 September 2026. The customer announces selection on 24 September, approval of instructions on 28 September and expected receipt on 30 September. Supporting evidence is requested on 22 September but arrives only on 25 September. The customer then proposes receipt on 30 October because the invoice missed the original selection.

The announced cash delay is 30 days, from 30 September to 30 October. To illustrate its financial weight, assume available borrowing priced at a hypothetical annual rate of 8%, on a 365-day basis and excluding fees. Simple financing cost would be €18,000 × 8% × 30 / 365, or approximately **€118.36**. This is a financing simulation, not a market quotation or a calculation of statutory late-payment interest.

If the customer agrees to an additional process producing receipt on 7 October, the delay becomes seven days. Under the same assumptions, financing cost falls to approximately €27.62, a difference of €90.74. That difference becomes an actual saving only if the borrowing would really have been used and charged on that basis. With no available facility, the more serious issue may be a liquidity shortfall that the interest calculation does not capture.

## Ask for a specific decision after the cut-off

When selection has closed, ask whether an additional run or individual payment is possible for the invoice concerned. Provide its due date and approval position without asking your contact to bypass controls. If they cannot decide, identify the person who can approve an exception and when that decision will be available. A lack of response must not be recorded as acceptance of the request or confirmation of a payment date.

When the customer offers another date, establish the invoices and amounts it covers. Our method for [making payment promises trackable](https://www.billabex.com/en/blog/verifiable-payment-promises/) separates a general intention from a usable commitment. Retain the original date and the subsequent reply. Moving the expected receipt in your forecast should reflect the new information without removing an overdue invoice from the accounting record or rewriting the history of the conversation.

If the problem recurs, examine several cycles using the same questions: were documents available, was approval complete, and did the selection process permit payment by the due date? This separates shortcomings in your own preparation from the customer's structural constraints. It also creates a concrete basis for discussing the process commercially, rather than issuing a fresh set of urgent messages at the end of every month.

## Verify the result after the run

The final step is to check receipt and allocation to the correct invoice references. A completed batch status, a reassuring email or a dated promise remains different from an observed bank movement. Where the customer sends one combined amount, retain enough allocation information to identify the documents settled before closing their follow-up cases. A total that looks right does not automatically establish which invoices the customer intended to pay.

[Billabex's payment promise tracking](https://www.billabex.com/en/product/payment-promises/) helps retain announced dates and amounts in their conversation context. Your work calendar can then anticipate approval steps and check promised dates, while accounting retains evidence of the payment itself. That connection makes month-end follow-up useful: prepare the documents early, secure a clear decision and verify the actual outcome instead of treating the customer's processing calendar as an automatic explanation for every unpaid balance.

## Sources

- DGCCRF, 23 December 2025: [French business payment-term rules](https://www.economie.gouv.fr/dgccrf/les-fiches-pratiques/delais-de-paiement-les-regles-connaitre?language=fr).
- Observatory of Payment Terms, November 2024, pages 15–16: [organisation of invoice payments](https://www.banque-france.fr/system/files/2024-11/Guide_Bonnes_pratiques_ODP_V6.pdf).
- Microsoft Learn, updated 4 August 2026: [automating vendor payment proposals](https://learn.microsoft.com/en-us/dynamics365/finance/accounts-payable/automate-vendor-payment-proposal).