--- title: "A fifteen-minute receivables meeting: which decisions need preparation?" canonical: https://www.billabex.com/en/blog/fifteen-minute-receivables-meeting/ lang: en alternate: https://www.billabex.com/fr/blog/reunion-impayes-quinze-minutes.md updated: 2026-09-24 index: https://www.billabex.com/llms.txt --- # A fifteen-minute receivables meeting: which decisions need preparation? A receivables meeting often begins with an ageing report shared on screen. Each line prompts an explanation, a search for an email or a question directed at someone who is absent. Forty minutes later, participants know more history, but decisions remain open. To make fifteen minutes useful, prepare the choices beforehand and reserve collective time for accounts that genuinely require a decision across responsibilities. A short format will not suit every problem. A complex dispute, contractual review or significant risk may need a dedicated discussion. The objective is not to decide faster than the evidence permits. It is to identify choices ready to be made, assign missing information and prevent the entire portfolio from waiting until the next meeting before ordinary work can continue. ## Use the time limit to improve preparation The November 2020 Scrum Guide describes a **fifteen-minute** daily event intended to produce an actionable plan. That duration belongs to its specific framework; it does not establish a scientifically optimal length for a receivables meeting. Here, fifteen minutes is a proposed working format to test against your team's needs and the decisions it handles. [Scrum Guide, Daily Scrum](https://scrumguides.org/scrum-guide.html). Preparation should make the choice immediately visible. “Customer twenty days overdue” is a status, not a decision question. “Authorise a two-part payment proposal or request another option before Friday” identifies a choice. Add why it matters now: a stated commitment, documents ready for approval, an upcoming cash requirement or a customer reply that needs an answer before the next routine review. Provide a simple place to submit topics in advance. The customer file with a clear question and recommendation may be enough. Avoid creating another spreadsheet that requires someone to copy the whole ledger every week. The [division of responsibility across operations, finance and sales](https://www.billabex.com/en/blog/invoice-dispute-decision-owner/) should already show which facts are confirmed and which team is waiting for a decision before it can act. ## Separate three kinds of case before sending invitations Routine cases have a known next action that fits existing authority. They continue without a collective presentation. Incomplete cases need specific information; assign that investigation to an owner. Decision cases contain alternatives or exceed delegated authority. Those justify the decision maker's attendance, provided the information needed to assess the options is available. A meeting is a poor substitute for evidence that nobody has yet attempted to retrieve. This distinction is not based only on balance size. A small recurring credit may reveal a billing problem requiring an organisational decision. A large invoice may be following an approved payment schedule without needing another debate. Consider the decision's effect, frequency and urgency. Participants can then understand the priority instead of treating the largest number on the report as automatically the most useful topic for collective discussion. France's Observatory of Payment Terms suggests simplifying checks and reducing signatories where invoice approval routes become excessive. Applied to your internal process, that prompts a useful question: does the meeting remove a blocker or add an unnecessary approval? This is an organisational adaptation, rather than an instruction to remove a control that remains necessary for the particular transaction or business. [Guide, page 13](https://www.banque-france.fr/system/files/2024-11/Guide_Bonnes_pratiques_ODP_V6.pdf). ## Prepare choices that are genuinely actionable For each selected topic, set out the open amount, last verified fact, customer request, options and case owner's recommendation. Identify what remains uncertain. An option is not “take the necessary action”; it describes an action, an owner and its implications. A credible alternative should allow comparison, rather than presenting a decision that has already been made informally as the only possible conclusion. Consider a hypothetical customer asking to settle €15,000 through payments of €9,000 and €6,000. The meeting can authorise offering that schedule, seek an earlier date for the second payment or instruct the owner to obtain another proposal. It cannot declare that the customer has accepted the schedule before receiving a reply, or treat the first €9,000 as cash already received by the business. A second case might concern a proposed €350 credit, with its basis prepared and accounting approval still required. A third could require an operational manager to intervene on missing evidence. The different choices explain why a reminder count alone cannot organise the conversation. Each decision addresses a specific obstacle and requires a different follow-through, even when all three accounts appear under the same overdue heading. ## Invite people for their role in the decision Bain's RAPID tool distinguishes five roles: preparing a recommendation, providing input, giving required agreement, deciding and performing the action. That distinction helps avoid inviting someone solely because they appeared in an old email thread. The publication describes a management method; it does not establish a numerical improvement in collections attributable to using the framework. [Bain, The five steps to better decisions, page 5](https://media.bain.com/Images/BAIN_BRIEF_Decision_Insights_The_five_steps_to_better_decisions.pdf). In a smaller business, one person may fulfil several roles. Keep the arrangement proportionate by identifying who can decide and who will execute. If the decision maker is absent and no delegation covers the matter, do not record the other participants' consensus as authorisation. The meeting can prepare a recommendation and assign the request for approval, but the account's status must reflect that limitation honestly. People supplying a document do not always need to attend the full meeting if their information can be provided clearly beforehand. Conversely, an unresolved technical question may justify a separate discussion with them. A short meeting works better when attendance follows the choice to be made, rather than a standing requirement that every function be represented regardless of the topics actually requiring attention. ## Test the agenda against twelve simulated cases Suppose twelve accounts are under review in a fictional example. Six have an established next action, three await assigned documentary research, and three need prepared decisions. The meeting could spend two minutes on exceptions arising since preparation, nine minutes on the three choices and four minutes confirming actions. The total is 2 + 9 + 4 = 15 minutes, without reading every account aloud. That allocation does not require a decision within three minutes when the facts change. If new information undermines the options, assign verification and arrange the appropriate discussion. A valid outcome can be “decision deferred, document due tomorrow, owner identified”. That is more precise than provisional agreement that each participant interprets differently after the meeting and that no one knows whether they are authorised to implement. With four participants, fifteen minutes represents one combined person-hour. A hypothetical forty-five-minute meeting with the same participants would use three person-hours. The gross difference is two hours. If the new preparation adds twenty minutes for one person, the net difference becomes one hour and forty minutes. This illustrates potentially released capacity, not salary savings or automatic improvement in receipts. Measure actual effort consistently with the [cost of collections work across multiple teams](https://www.billabex.com/en/blog/payment-reminder-cost-three-teams/). ## Finish with a record that starts the next action For each choice, record the decision, who made it, who will execute it and the review date. Where it authorises an offer to the customer, record “proposal authorised”, then wait for the reply before registering agreement. A [trackable payment promise](https://www.billabex.com/en/blog/verifiable-payment-promises/) must remain connected to amounts and dates actually announced, rather than the terms your internal meeting hopes the customer will accept. At the next review, return only to decisions not executed or new facts that change the choice. If the same investigation keeps recurring, examine the obstruction: the wrong owner, inaccessible evidence or a decision still waiting for someone with authority. [Billabex's customer view](https://www.billabex.com/en/product/customer-view-360/) gathers conversations and invoices to prepare these discussions. The fifteen minutes become useful when everyone leaves with an executable action and an account position colleagues can understand without requiring another meeting to explain it. ## Sources - Ken Schwaber and Jeff Sutherland, Scrum Guide, November 2020: [fifteen-minute Daily Scrum](https://scrumguides.org/scrum-guide.html). - Observatory of Payment Terms, November 2024, page 13: [simplifying approval routes](https://www.banque-france.fr/system/files/2024-11/Guide_Bonnes_pratiques_ODP_V6.pdf). - Marcia W. Blenko, Michael C. Mankins and Paul Rogers, Bain, 2013, page 5: [RAPID decision roles](https://media.bain.com/Images/BAIN_BRIEF_Decision_Insights_The_five_steps_to_better_decisions.pdf).