--- title: "An invoice changes after a reminder: preserving the case history" canonical: https://www.billabex.com/en/blog/invoice-changed-after-reminder-versions/ lang: en alternate: https://www.billabex.com/fr/blog/facture-modifiee-apres-relance-versions.md updated: 2026-10-20 index: https://www.billabex.com/llms.txt --- # An invoice changes after a reminder: preserving the case history A customer answers a €6,000 reminder by attaching a credit note your colleague has just issued. The system now displays €4,800. Opening the earlier conversation still shows a request for €6,000. Should someone edit that conversation, replace its attachment or simply send the new balance? Start by separating two requirements. The current case must be accurate, while its history must still explain what was actually sent. A corrected invoice, an added receipt and a repaired import are different events. Treating them as one changed field makes the next decision harder to understand. For a French supplier serving customers in France or elsewhere in Europe, the operational question is practical: can another colleague reconstruct the request without confusing a later correction with information the team already had? ## Establish what has actually changed Before comparing amounts, classify the event. An agreed reduction after invoicing may lead to a credit note. An incorrect recipient may require an appropriate document correction. A receipt reduces the open balance without changing the invoiced price. A repaired import may only align the collections tool with a document that was already correct. French tax guidance distinguishes, among other cases, a replacement invoice cancelling the original and a credit note. It specifies references connecting the correction to the initial invoice. This is different from silently overwriting a document already supplied. [BOFiP, 19 January 2022 version, paragraphs 180–260](https://bofip.impots.gouv.fr/bofip/142-PGP.html/identifiant=BOI-TVA-DECLA-30-20-20-20-20220119). Ask for the source document and its status first. “Sales promised a credit” does not mean “the credit note has been issued and allocated.” If approval remains pending, the reminder may need a pause or human intervention. Do not describe a balance dependent on an unresolved decision as final. Also establish which invoice and legal entity the correction concerns. A similar reference from another account should not change this customer's outstanding amount merely because the files appear together. ## Separate the accounting document from the case state Odoo 18 documentation illustrates the distinction. Its Reverse option opens a draft credit note, while Reverse and Create invoice validates and reconciles the credit note before opening a draft replacement invoice. These objects and states are not interchangeable. [Odoo 18, credit notes and refunds](https://raw.githubusercontent.com/odoo/documentation/18.0/content/applications/finance/accounting/customer_invoices/credit_notes.rst). That describes Odoo, not every integration. Check what your system displays when a correction is prepared, posted, cancelled or reconciled. A “modified” label alone cannot establish whether the amount owed has changed. A case can show its current summary while retaining connections to the original invoice, the credit note and associated receipts. Readers should be able to reconstruct the sequence without searching through nearly identical copies. The method for [unallocated credit notes](https://www.billabex.com/en/blog/unallocated-credit-note-balance-check/) supports the balance calculation. Here, the central question is what was known when the reminder was sent. ## Reconstruct the dates explaining the request Consider a simulation involving one €6,000 invoice, with amounts including VAT. A reminder requests €6,000 on 12 October at 09:00. A €1,200 credit note is approved and allocated at 11:00. On 13 October, a €2,400 receipt arrives and is allocated to the invoice. The current balance is €6,000 minus €1,200 minus €2,400, or €2,400. The balance has fallen by €3,600 since the reminder, equivalent to 60% of the requested amount. However, only €2,400 is cash received. The other €1,200 comes from a commercial and accounting correction. Saying the customer “paid 60%” would therefore be wrong. Cash paid represents 40% of the original invoice, and the remaining balance also represents 40%. Now change one assumption. The credit note was approved on 11 October, but the integration retrieved it only at 11:00 on 12 October. The 09:00 reminder no longer reflects a correction made later. It used an incomplete state. The message itself is unchanged, but the cause requiring attention is different. Keep the document date, relevant approval date, arrival in the collections tool and sending time distinguishable. An accounting date alone does not establish when automation could access the information. This connects to [delayed accounting synchronisation](https://www.billabex.com/en/blog/delayed-accounting-sync-pause-reminders/), with a specific consequence: repair the process that allowed an inaccurate request to be sent. ## Preserve the sent message and add an explanation The earlier message should remain identifiable as the actual communication, including its amount and attachments. Replacing its content with the new balance would suggest the customer received something different. A linked annotation can explain subsequent developments and point to the corrected state. CNIL recommends recording changes with the actor's identifier, date, time, operation and reference to affected data, while protecting logs against overwriting. It also warns against excessive duplication of personal data and unlimited log retention. [CNIL, operation logging, 14 March 2024](https://www.cnil.fr/fr/securite-tracer-les-operations). Those principles do not justify keeping every document copy or all personal conversation content forever. Distinguish accounting documents, useful case history and security logs, with suitable access and retention arrangements. A [collections audit trail](https://www.billabex.com/en/blog/collections-audit-trail-automation/) helps define necessary evidence; it does not remove the need to establish why that evidence is retained. An explanation should also identify its source. “Balance corrected” is less useful than a reference to the approved credit and allocated receipt, especially when the next colleague must answer a customer who holds the earlier statement. ## Reassess the next action, not just the displayed balance Updating the balance does not necessarily cancel a message already prepared. In the simulation, a €4,800 reminder drafted before the receipt arrived would still overstate the amount by €2,400. Ask what happens when a correction arrives between preparation and sending. The test should examine the final text, attachments and referenced invoices. Include a legitimately cancelled correction too. If a credit note is reversed, the case should show that subsequent development and its explanation. Neither blind reuse of an older message nor disappearance of the reversal is a satisfactory outcome. Someone should decide whether the customer needs an immediate clarification. Where the reminder was inaccurate, a short message can acknowledge the discrepancy, identify the credit and receipt used, and state the verified balance. Where the change occurred afterwards in the normal course of business, a factual update may suffice. In both situations, the tone should follow established facts. Avoid describing a correction as customer non-payment. If the supplier issued the wrong amount, making the customer defend an outdated request adds friction and leaves the underlying cause unresolved. ## Test the handover to another colleague Give the case to someone who did not handle the original exchange. Can they explain why €6,000 was requested, why €2,400 remains and what action is now authorised? If they must guess whether the credit existed before sending, the history is still incomplete. Explore that continuity through [Billabex's customer view 360](https://www.billabex.com/en/product/customer-view-360/) using successive correction and receipt events. Ask which information is visible and how the next reminder is handled, without assuming immutable archiving architecture or native accounting-document versioning. The practical result should be an understandable case, an accurate current request and a faithful explanation of what the customer has already been told. ## Sources - BOFiP, BOI-TVA-DECLA-30-20-20-20, 19 January 2022 version, paragraphs 180–260. - Odoo 18, Credit notes and refunds, official documentation. - CNIL, Sécurité : tracer les opérations, 14 March 2024. Sources accessed 7 September 2026.