--- title: "The decision-maker is away: preparing payment decisions before departure" canonical: https://www.billabex.com/en/blog/decision-maker-away-payment-approvals/ lang: en alternate: https://www.billabex.com/fr/blog/decideur-absent-arbitrages-paiement.md alternates: fr: https://www.billabex.com/fr/blog/decideur-absent-arbitrages-paiement.md en: https://www.billabex.com/en/blog/decision-maker-away-payment-approvals.md es: https://www.billabex.com/es/blog/decisor-ausente-preparar-decisiones-de-pago-antes-de-su-salida.md updated: 2026-11-04 index: https://www.billabex.com/llms.txt --- # The decision-maker is away: preparing payment decisions before departure The business owner is away for a few days. A colleague covers collections, but one customer requests instalments and another offers payment in exchange for a discount. The records are accessible; authority to make those decisions may not have been delegated. Waiting for the owner's return can stall the work. Letting every substitute improvise can create commitments the company never intended. Useful preparation therefore concerns specific decisions: who may agree to what, for which customers, during which period and with what evidence? This article proposes an operating method for a French SME negotiating customer payments. It is not a universal legal delegation template, and it concerns receivables decisions rather than authority to transfer money to suppliers. The legal references below are French, not a statement of rules across every European jurisdiction. ## Separate account access from authority to commit Being able to read a conversation does not automatically authorise somebody to change an agreement. Sending from a shared mailbox does not confer every power held by the business owner either. Before the absence, distinguish operational tasks from decisions: providing a document, confirming a balance, suggesting a date, accepting instalments, granting a discount and abandoning a claim are different actions. Article 1998 of the French Civil Code links the principal's commitments to the authority given to the agent and addresses express or implied ratification of acts beyond that authority. The precise position still depends on the circumstances and the representation rules applicable to the business. [Source: French Civil Code, Article 1998](https://www.legifrance.gouv.fr/codes/section_lc/LEGITEXT000006070721/LEGISCTA000006136406/). Do not conclude that an internal limit always makes a commitment ineffective against the company. Article 1156 also addresses a third party's legitimate belief in the representative's authority and subsequent ratification. Ambiguous signatures or conduct may therefore require legal examination, rather than a reminder of internal policy alone. [Source: French Civil Code, Article 1156](https://www.legifrance.gouv.fr/codes/article_lc/LEGIARTI000032041104/2026-05-07). ## Write authority the substitute can actually apply An instruction to handle urgent matters does not resolve an instalment request. For each authorised decision, specify the customer scope, amount limit, permitted duration, required evidence and exclusions. Explain whether an amount limit concerns the account's total balance, the principal being rescheduled or the value of a financial concession. Those measures produce different decisions on the same request. Accepting instalments on ten thousand euros is not granting a ten-thousand-euro discount. A concession can affect cash timing without reducing principal. The substitute must understand which measure consumes the delegated allowance and when the consumption is recorded. Otherwise, a clear-looking ceiling can be applied differently by two people using the same records. Distinguish preparation from acceptance as well. A colleague may collect documents and prepare an internal proposal without being authorised to confirm an agreement externally. Customer wording should reflect that status. Saying that a request has been submitted for a decision describes a process; saying that the company accepts expresses a materially different commitment. ## Worked example: an individual limit is insufficient Consider a fictional business. During the absence, a manager may accept instalments covering at most **€10,000 per account**, without a discount, within a cumulative allowance of **€20,000 of rescheduled principal**. The allowance is consumed when an arrangement is accepted. Receipts during the absence do not replenish it. Every limit here is an explicit assumption for the example. Three customers successively request arrangements covering **€6,000, €7,000 and €9,000**. Each request fits the individual ceiling. However, the first two consume **€13,000**, leaving **€7,000**. The third would bring the cumulative total to **€22,000**, exceeding the allowance by **€2,000**. It therefore requires the escalation route established before the absence. Artificially splitting that third request into two confirmations does not solve the issue: nine thousand euros of principal would still be rescheduled. A genuinely different proposal must be assessed on its actual terms, with customer agreement and the necessary authority. Keep the complete account visible so separate colleagues cannot unknowingly consume the same remaining capacity. This calculation is not a cash forecast. The **€13,000 covered by accepted arrangements** remains receivable until the corresponding payments arrive. Delegation enables a decision; it does not turn a promise into money. The earlier discussion of [exceptions requiring human review](https://www.billabex.com/en/blog/ai-collections-agent-human-exceptions/) helps identify cases that should remain outside the delegated allowance altogether. ## Prepare the accounts likely to need attention Before departure, identify promises falling due, expected responses and requests already awaiting a decision. Each handover record should contain an updated balance, recent correspondence, missing evidence and the intended next action. A list of customer names forces the substitute to reconstruct the investigation, even if the information technically exists somewhere in the organisation. Include decisions already approved but not yet communicated. Without that distinction, the substitute may reopen a negotiation that has already been settled internally. Where an amount is uncertain, state what must be checked before confirmation. The handling of a [delayed accounting synchronisation](https://www.billabex.com/en/blog/delayed-accounting-sync-pause-reminders/) still applies when delegated authority exists; permission to decide does not repair stale information. Test the handover using a fictional account before the owner leaves. The substitute should locate the documents, explain how the allowance is calculated and identify the approver for an exception. If completing the exercise requires calling the owner to interpret the rule, the handover is not yet specific enough for independent use. ## Arrange a route for requests outside the scope Name another authorised decision-maker, an appropriate channel and the information needed for review. If nobody can decide, the substitute acknowledges the request, explains the next step and records a follow-up date. They should not promise a favourable outcome merely to keep the conversation moving. Identify genuine urgencies before departure and involve appropriate advisers where legal consequences matter. Pausing an automated reminder is not, by itself, a change to the contractual payment deadline. It may be an internal measure while the request is examined. The account history should distinguish that operational pause from extra time actually agreed with the customer. Treating the two as interchangeable makes later interpretation of the payment arrangement unnecessarily difficult. Also prepare for the substitute becoming unexpectedly unavailable, using the same attention to account continuity as after an [email outage](https://www.billabex.com/en/blog/email-outage-resuming-reminders/). An inaccessible personal inbox or a locally stored spreadsheet can create another bottleneck. Authorised colleagues need access to the work, and each open request needs a named owner. Access should support continuity without granting everyone unrelated information or broader decision rights. ## Close temporary authority and remove temporary access System permissions should follow the assignment. France's CNIL recommends reviewing permissions **at least annually** and explicitly warns against forgetting temporary access granted for cover. That minimum review frequency is not a reason to retain unnecessary permissions until the next annual review. [Source: CNIL, 13 March 2024](https://www.cnil.fr/fr/securite-gerer-les-habilitations). When the owner returns, reconcile accepted arrangements, pending requests, exceptions and actual receipts. Check the consumed allowance against recorded decisions, rather than silently recalculating it under a different rule. Agreements made during the absence still need follow-up after the temporary decision period has ended. The end of the cover arrangement should not orphan those commitments. Remove temporary access and retain evidence according to the applicable rules. The aim is not to create a permanent copy of the owner's authority. When assessing [debt collection software](https://www.billabex.com/en/debt-collection-software/), test whether the account, responsible person and required decision remain understandable to the authorised substitute. Reliable cover depends on prepared, reviewable decisions rather than an improvised exchange of somebody else's password. ## Sources - French Civil Code: [Article 1998, obligations of the principal](https://www.legifrance.gouv.fr/codes/section_lc/LEGITEXT000006070721/LEGISCTA000006136406/). - French Civil Code: [Article 1156, representation](https://www.legifrance.gouv.fr/codes/article_lc/LEGIARTI000032041104/2026-05-07). - CNIL, 13 March 2024: [managing access permissions](https://www.cnil.fr/fr/securite-gerer-les-habilitations).