--- title: "Small customer balances: measuring handling cost before deciding" canonical: https://www.billabex.com/en/blog/small-customer-balances-handling-cost/ lang: en alternate: https://www.billabex.com/fr/blog/petits-soldes-clients-cout-traitement.md updated: 2026-10-08 index: https://www.billabex.com/llms.txt --- # Small customer balances: measuring handling cost before deciding A four-euro balance can consume more work than the amount at stake. It can also reveal a deduction applied systematically by a customer, an incorrect setting or a payment allocated to the wrong case. Stopping reminders without knowing which situation you face risks removing the signal together with the amount. The useful decision therefore begins before “collect or abandon”. Establish what the difference represents, what the next action would cost and what the team could learn by taking it. For a business operating in France, this approach reduces unnecessary handling without treating a case removed from the collection queue as a paid receivable. ## Establish the cause before judging the size A €1,200 invoice with €1,196 allocated to it leaves four euros outstanding. That subtraction does not explain why. Part of the payment may be missing, but there could also be a credit note, a fee charged by your own bank or a rounding difference between systems. Start with information available without contacting the customer: the invoiced amount, the amount actually received, payment allocation, supporting evidence and commercial terms. Investigating an [unagreed early payment discount](https://www.billabex.com/en/blog/unagreed-early-payment-discount/) helps distinguish a numerical difference from a reduction the customer believes was authorised. Then classify the case by its established cause, leaving a temporary category for unexplained differences. “Under five euros” is a size filter, not an accounting explanation. A repeated credit note problem requires a process correction even if every incident looks immaterial when considered alone. Take a small sample of the unexplained category before introducing a blanket rule. If several cases arise from the same export field or customer instruction, resolving that common cause may remove future work. Automatically closing them would make the report tidier while leaving the underlying error in place. ## Calculate the cost of the next intervention In an entirely simulated example, sixty customers each have a confirmed four-euro balance, totalling €240. Individual handling takes six minutes per customer. The hourly rate chosen to value working capacity is €42. Each intervention therefore costs 6 / 60 × €42 = €4.20, or €252 across all sixty cases. Even full collection would consume capacity valued above the €240 being sought. That does not establish that the receivables are irrecoverable. It shows that this particular handling method is disproportionate under the assumptions used. Nor does it establish that abandoning the interventions would immediately reduce payroll by €252. The released time may be used on other cases. A cash saving requires identifying expenditure actually avoided. Calculating the [cost of a reminder across several teams](https://www.billabex.com/en/blog/payment-reminder-cost-three-teams/) helps separate working capacity, allocated cost and actual cash expenditure. Focus on costs still to be incurred. Yesterday's investigation cannot be recovered by continuing today. It may have supplied valuable information, but its past cost does not automatically justify another intervention. Ask what the next step adds and whether a less demanding step could achieve the same purpose. ## Change the method before giving up the amount Now suppose a common verification and a coordinated batch of requests take twelve minutes altogether, with no additional investigation for individual cases. The capacity cost becomes 12 / 60 × €42 = €8.40. This assumes reliable balances and appropriate messages; it does not apply to sixty different disputes. If the team uses a hypothetical collection rate of 75% by value for this decision, expected receipts are €240 × 75% = €180. The difference from the capacity cost is €171.60. This simplified calculation is neither a guaranteed forecast nor a result after tax: it excludes other costs, customer effects and the timing of receipts. | Simulated method | Capacity cost | Receipts considered | Interpretation | | ----------------------- | ------------: | -----------------------: | --------------------------------- | | Individual intervention | €252 | At most €240 | Cost exceeds the principal sought | | Common handling | €8.40 | €180 under an assumption | Worth testing for suitable cases | Common handling means shared preparation followed by communications specific to each customer. It does not mean sending one customer the other fifty-nine customers' balances. Any cost reduction must preserve the accuracy and confidentiality of the individual case. The decision can also change when new information arrives. A customer who confirms the missing four euros can pay it with an agreed later transfer, provided the allocation remains traceable. That option differs from silently assuming the balance will be covered by an unrelated future invoice. ## Look for accumulation below the individual threshold Another customer deducts three euros from each of twenty-four invoices, accumulating €72. A rule that clears every balance below four euros hides a repeated practice. The team should be able to see amounts released or still outstanding by customer over a defined period. A percentage alone creates another blind spot. A hypothetical tolerance of 0.5% means one euro on a €200 invoice but €500 on a €100,000 invoice. If you use a relative limit, add an appropriate absolute limit and state whether both conditions must hold. These are internal policy decisions, not statutory allowances. A rule could therefore require an established cause, a low amount, limited accumulation per customer and an identified approver. Keep exceptions visible, including unusual repetition, a dispute, a recent bank detail change or uncertain payment allocation. A small amount should not disable a useful control over the wider account. ## Understand what the software tolerance actually does Odoo 18 documents a reconciliation model for payments below the invoice amount, allocating the difference to the configured counterpart account. Its payment tolerance does not apply to overpayments. This illustrates why the effect of a setting matters more than its label. [Odoo reconciliation models](https://raw.githubusercontent.com/odoo/documentation/18.0/content/applications/finance/accounting/bank/reconciliation_models.rst). Request a before-and-after example showing the customer balance, resulting accounting entry, supporting evidence and reminder consequences. A threshold intended to propose a bank match does not automatically represent commercial authority to release a debt. Test the sign of the difference too. A four-euro shortfall and a four-euro overpayment are different situations. A rule using only an absolute value could hide money belonging to the customer. Agree how these cases are handled before automating the process, including who reviews amounts that remain unexplained. ## Separate management policy from legal and tax treatment The French Civil Code defines debt remission as a contract releasing the debtor from an obligation. Removing a case from a work list or changing a software status does not by itself adequately describe that decision. Specify who may approve it and how it is documented. [French Civil Code, Article 1350](https://www.legifrance.gouv.fr/codes/id/LEGISCTA000032035671). French tax guidance also states that non-payment at maturity does not establish definitive irrecoverability for VAT recovery. A small balance or an expensive investigation should therefore not automatically become a tax classification of irrecoverable debt. Treatment depends on the cause and applicable conditions. [DGFiP guidance, BOI-TVA-DED-40-10-20, paragraph 40](https://bofip.impots.gouv.fr/bofip/1100-PGP.html/identifiant=BOI-TVA-DED-40-10-20-20170405). The approach to [allocating invoice dispute decisions](https://www.billabex.com/en/blog/invoice-dispute-decision-owner/) is useful here: someone establishes the facts, an authorised person decides and accounting applies the appropriate treatment. A small team can perform these roles without losing the distinction between them. ## Keep reporting that explains the remaining differences Track cash received, corrections, debt releases and still-open balances separately, together with time spent on repeated causes. A falling case count is insufficient evidence of improvement: it can reflect better payment or a growing number of abandoned amounts. The [Billabex customer view](https://www.billabex.com/en/product/customer-view-360/) helps place the next action in the context of the account. For small differences, the objective is to bring together the facts needed for a proportionate decision. Several weeks later, your team should still be able to explain why a balance was handled that way, who approved it and what actually changed in the amount owed. ## Sources - Odoo 18, reconciliation models, underpayment section, accessed 7 September 2026. - French Civil Code, Article 1350, in force since 1 October 2016, accessed 7 September 2026. - DGFiP, BOI-TVA-DED-40-10-20 dated 5 April 2017, paragraph 40, accessed 7 September 2026.