--- title: "Two invoices share a number: check the legal entity before chasing" canonical: https://www.billabex.com/en/blog/duplicate-invoice-numbers-legal-entities/ lang: en alternate: https://www.billabex.com/fr/blog/factures-meme-numero-entites.md updated: 2026-10-01 index: https://www.billabex.com/llms.txt --- # Two invoices share a number: check the legal entity before chasing “Invoice 2026-0042 has already been paid.” The reply sounds decisive until your team finds two documents carrying that reference. One was issued by one company in the group and the other by a second company. The customer uses the same accounts payable team for both, while your collections spreadsheet displays only a short invoice number. An exact match in that column cannot establish which debt the customer means. Before sending another request, reconstruct the document's identity. Its number matters alongside the issuer, recipient, date, amount, currency and original invoice. The objective is to distinguish two separate receivables, a copy of the same document and a genuine numbering error. Each situation requires a different correction, even when the initial symptom looks identical in a consolidated account view. ## Read both original documents first Open the invoices actually sent to the customer. Compare the issuer's legal name and identification, the complete reference and the issue date. Then check the invoiced customer, amount and underlying supply. An export may have removed a prefix or truncated a reference; two identical cells do not prove that the original documents really carry identical numbers. France's Service Public guidance lists a unique invoice number based on a continuous chronological sequence, together with the seller's and buyer's identities, among the required information. Examine these details together. An invoice number is not a universal identifier shared by every supplier. [Service Public, mandatory invoice information, verified 11 August 2026](https://entreprendre.service-public.gouv.fr/vosdroits/F31808). Also establish whether you are comparing an original invoice and a copy, a corrected document or two separate sales. An attachment returned by the customer does not become a new receivable because its filename has changed. Conversely, two companies may have issued distinct documents that your report has incorrectly grouped under a reference stripped of its useful context. ## Distinguish a legal entity from an establishment In France, Insee defines the **SIREN as a nine-digit identifier assigned to a legal unit**. It states that the number is not reused after that unit ceases to exist. This identification is more reliable for distinguishing issuing companies than a shared logo or an abbreviated trading name. [Insee, SIREN definition](https://www.insee.fr/fr/metadonnees/definition/c2047). The **fourteen-digit SIRET identifies an establishment**. It incorporates the legal unit's SIREN and an internal establishment number. Two establishments belonging to the same company should therefore not automatically be treated as separate legal persons. [Insee, SIRET definition](https://www.insee.fr/fr/metadonnees/definition/c1841). That distinction prevents a false resolution: “The addresses differ, so both invoices can remain as they are.” If the legal issuer is the same and two different transactions carry the same reference in a numbering context that does not permit it, the accounting team needs to investigate. Adding the customer's name to a spreadsheet cannot make an incorrectly numbered invoice compliant with the applicable requirements. For an issuer outside France, use the relevant official identifiers for its country and inspect the contractual documents. The absence of a French SIREN is not itself an inconsistency. The method is to establish the entity's identity, then read the full invoice reference in the appropriate billing context. A multinational group label does not answer either question by itself. ## The right total can conceal two wrong account balances Consider a simulated example with no real company data. Issuing company A invoices €4,800 and issuing company B invoices €7,200 to the same customer. Each uses reference 2026-0042 within its own numbering system. The customer pays €4,800 for A's invoice, but the consolidated tracker allocates the payment to B because it searches only for the invoice number. | Position | A's invoice | B's invoice | Total outstanding | | -------------------- | ----------: | ----------: | ----------------: | | Before payment | €4,800 | €7,200 | €12,000 | | Correct allocation | €0 | €7,200 | €7,200 | | Incorrect allocation | €4,800 | €2,400 | €7,200 | The total outstanding is the same in the last two rows: **€7,200**. A check limited to the aggregate amount detects nothing. Nevertheless, A could chase a settled invoice while B requests only €2,400 against an entirely unpaid invoice. The missing context shifts €4,800 from one case to the other without changing the amount displayed across both companies in the report. The customer's “already paid” reply must therefore be linked to the correct document before the team concludes that the customer is mistaken. Apply the method for [tracing unallocated cash](https://www.billabex.com/en/blog/payment-received-invoice-still-open-tracing-unallocated-cash/) with the issuing entity included in the investigation. The credited bank account and remittance information help reconstruct the payment's path, alongside the evidence supporting its invoice allocation. ## Make the identity clear in the conversation After identifying the two cases, avoid sending another message that preserves the ambiguity. State the issuer's legal name, full invoice reference, issue date and relevant amount. When the same contact handles several companies, present the documents in a short table separating the entities instead of combining their amounts in a sentence that is difficult to interpret or forward. For example: “We have located the €4,800 payment allocated to invoice 2026-0042 issued by A. Our request concerns invoice 2026-0042 issued by B for €7,200. Could you confirm that this second document has been identified in your payment process?” This is a simulated message to adapt after checking the underlying facts, rather than a statement about an actual customer account. Where the customer has made [one payment covering several invoices](https://www.billabex.com/en/blog/one-payment-multiple-invoices/), request a breakdown that preserves issuer identity too. A list containing only invoice numbers can reproduce the same problem. The clarification should enable another colleague to continue the case without repeating the investigation or guessing which company the customer had in mind when describing a payment. ## Correct the allocation without renumbering for convenience If the mistake originates in the collections tracker, correct the link while preserving the document's legal reference. If it originates in the accounting records, have the authorised person assess the correction within the relevant system. If the invoices themselves contain an anomaly, the accounting team should determine the appropriate documentary treatment. Quietly changing a PDF is not a sound collections fix. Odoo 18's documentation illustrates why renumbering deserves separate treatment: it describes specific access rights, recorded changes and restrictions for inconsistencies such as duplicates or incompatible dates. The presence of a renumbering function in a software product does not establish that using it is justified in your circumstances. [Odoo 18, invoice sequences](https://raw.githubusercontent.com/odoo/documentation/18.0/content/applications/finance/accounting/customer_invoices/sequence.rst). The year can help interpret a reference and locate the correct context. It should not be used to remove a prefix, conceal a collision or arbitrarily authorise repetition of a number. Preserve the complete reference communicated to the customer even if an internal screen also provides a shorter working identifier. Both people discussing the invoice need a dependable way to identify the same document. ## Close the issue when each individual case is consistent Before restarting reminders, check the balance of each invoice, the replies linked to it and the messages already sent. An accounting correction may require an explanation to the customer if an excessive request has gone out. The [collections audit trail](https://www.billabex.com/en/blog/collections-audit-trail-automation/) helps reconstruct that conversation, while the corrected allocation remains the evidence for the amount now due. The outcome should be specific: each invoice retains its identity, every payment has a justified allocation and the contact understands which entity is requesting which amount. The [Billabex customer view](https://www.billabex.com/en/product/customer-view-360/) helps teams examine invoice and conversation context. During a demonstration, use a reference appearing under two issuers to check how your organisation would keep both cases distinct and follow up the appropriate receivable. ## Sources - [Service Public, mandatory invoice information, 11 August 2026](https://entreprendre.service-public.gouv.fr/vosdroits/F31808). - [Insee, SIREN, 21 October 2025](https://www.insee.fr/fr/metadonnees/definition/c2047). - [Insee, SIRET, 4 December 2019](https://www.insee.fr/fr/metadonnees/definition/c1841). - [Odoo 18, invoice sequence documentation](https://raw.githubusercontent.com/odoo/documentation/18.0/content/applications/finance/accounting/customer_invoices/sequence.rst).