--- title: "We will pay next week: making payment promises trackable" canonical: https://www.billabex.com/en/blog/verifiable-payment-promises/ lang: en alternate: https://www.billabex.com/fr/blog/promesse-paiement-verifiable.md updated: 2026-09-13 index: https://www.billabex.com/llms.txt --- # We will pay next week: making payment promises trackable “We will pay next week.” That reply often ends a reminder conversation without giving the team enough information to know what to check. Does the customer mean initiating a transfer, obtaining internal approval or having the money arrive? Does the commitment cover every open invoice or just one? Without clarification, the promise can remain green in a tracking sheet while nothing has changed in the bank account. A usable payment promise identifies an observable event, an amount and a date. It also identifies who will follow up if the expected event does not happen. That discipline lets a business respect the customer's stated intention while maintaining ownership of the case. The approach below is intended for customer accounts in France and Europe, where payment methods and local calendars need to be understood. ## Clarify the expected action with one useful question Your first reply does not need to become a questionnaire. Confirm the essential point: “Thank you. Could you confirm the planned transfer initiation date and the amount covered?” If several invoices remain open, list their references or attach a short statement. Give the customer an easy opportunity to correct your interpretation. One person may say “payment on Friday” because that is when they will submit the invoice for approval. Another may mean a transfer that is already authorised. Ask what still needs to happen and who owns that step, especially if an earlier commitment has slipped. The aim is to locate the dependency without requiring the customer to describe their entire organisation. If the reply reveals a [missing purchase order](https://www.billabex.com/en/blog/missing-purchase-order-blocked-invoice/), the case has returned to a documentation task. The promise is conditional: someone must still supply evidence or secure approval. Recording a firm payment date from that response would hide the action needed to make payment possible. ## Record the promise separately from the invoice due date Keep the original invoice due date, the date promised by the customer and your next review date in separate fields. They answer different questions. The first describes the receivable being tracked, the second records information from a conversation, and the third schedules your own work. If your company agrees a contractual amendment, route and document that decision through its established approval process. Accounting products also make relevant distinctions. Dynamics 365 Finance documentation describes one tab for open transactions marked as promised for payment and another for posted payments that have not been settled against an invoice. In this particular software example, a promise is a tracking state distinct from a payment. That observation does not establish how every other product works. [Source: Microsoft Learn](https://learn.microsoft.com/en-us/dynamics365/finance/accounts-receivable/collectionsworkspace). The operational record can be compact: invoice references, amount and currency, stated date, expected event, customer contact, any condition and internal owner. Include a link to the original message. Another colleague should be able to recover what the customer actually said, especially if an automated summary has turned tentative wording into an apparently definite commitment. ## Schedule the check around the actual payment method An announced transfer and visible cash do not necessarily occur at the same time. Banque de France explains that a standard SEPA transfer has a maximum execution period of one business day after the sending bank receives the instruction; a paper instruction can take two business days. The clock does not start when the customer writes their email. [Source: Banque de France](https://www.banque-france.fr/fr/a-votre-service/particuliers/mieux-connaitre-moyens-paiement/virement-sepa). Set the review using the transfer method, actual initiation date and freshness of your banking information. An accounting import from yesterday is not enough to establish that today's promise has been broken. An instant transfer, a standard SEPA transfer and a payment outside SEPA should not all be assessed using the same timing assumption. Make the calendar explicit as well. In bilingual correspondence, write “18 September 2026” or “18 septembre 2026”, rather than an ambiguous numeric date. When the team and customer operate in different countries, clarify the relevant banking day if necessary. A little precision prevents a conversation about “Friday” becoming an argument over when checking should have started. ## A worked example of a partial commitment Imagine three invoices for €1,200, €1,800 and €2,400, totalling €5,400. The customer announces a payment of €3,000 next week. These figures are entirely hypothetical. The team should clarify which invoices the amount covers: it may exactly settle the first two, or represent a payment on account intended for a different allocation. Suppose the customer confirms a €3,000 transfer to settle the €1,200 and €1,800 invoices. After receipt and reconciliation, those invoices are paid and the €2,400 invoice remains open. That specific promise has been fulfilled by 100%, although only €3,000/€5,400, approximately 55.6%, of the original portfolio has been collected. If only €2,700 arrives, fulfilment is 90% by value and €300 remains unexplained within the promise's scope. The total outstanding account balance is still €2,700, calculated as €5,400 minus €2,700. Do not confuse the shortfall against the promise with all invoices still due. This distinction prevents the account being described as fully settled or a substantial payment being treated as if nothing had happened. ## Decide what to do after the stated date First check the funds and their allocation. A [payment received but not reconciled](https://www.billabex.com/en/blog/payment-received-invoice-still-open-tracing-unallocated-cash/) can make a fulfilled commitment look missed. Look for an amount correction or an [unallocated credit note](https://www.billabex.com/en/blog/unallocated-credit-note-balance-check/) before sending a message claiming that no payment has been made. If nothing explains the difference, restate the specific facts: the announced amount, the date and the position you can currently see. Ask whether the transfer was initiated or whether an obstacle remains. The answer may justify another review date, a request for supporting evidence or closer human involvement. It should not simply erase the earlier commitment from the record. For French obligations, Civil Code article 1353 allocates the burden of proof between the party seeking performance and the party claiming to have discharged the obligation. Preserving evidence supports that distinction. An internal “promised” label does not, on its own, establish that the debt has been paid. [Source: Légifrance](https://www.legifrance.gouv.fr/codes/article_lc/LEGIARTI000032042341). ## Preserve rescheduling history so it can inform decisions When the date changes, add an event instead of overwriting the previous entry. Record the explanation, who approved the revised follow-up and when the next check will happen. Two delays caused by the same missing document call for a different response from two unexplained delays. The history should help the team choose an action, rather than produce a vague judgement about the customer. Keep matured promises in your analysis even when a new promise is obtained. Otherwise, fulfilment appears to improve because missed commitments disappear from the denominator. Also decide whether you are measuring the promised initiation date or the agreed receipt date, then apply that convention consistently. Neither measure can be interpreted properly if its meaning changes between accounts. When assessing [debt collection software](https://www.billabex.com/en/debt-collection-software/), test a case containing a conditional promise, a partial payment and a rescheduled date. Your team should be able to recover the original scope, check actual movements and resume the conversation accurately. Good tracking becomes visible when the promise turns into payment, or when a remaining discrepancy calls for a clear decision. ## Sources - [Microsoft Learn: Collections coordinator workspace](https://learn.microsoft.com/en-us/dynamics365/finance/accounts-receivable/collectionsworkspace). - [Banque de France: SEPA transfers and execution periods](https://www.banque-france.fr/fr/a-votre-service/particuliers/mieux-connaitre-moyens-paiement/virement-sepa). - [Légifrance: Civil Code article 1353](https://www.legifrance.gouv.fr/codes/article_lc/LEGIARTI000032042341).