--- title: "The payer is not your customer: mapping entities without merging debts" canonical: https://www.billabex.com/en/blog/payer-versus-customer-entity-mapping/ lang: en alternate: https://www.billabex.com/fr/blog/payeur-different-client-entites.md updated: 2026-10-02 index: https://www.billabex.com/llms.txt --- # The payer is not your customer: mapping entities without merging debts Your invoice is addressed to a subsidiary, but the incoming transfer names its holding company. The accounts payable contact replies from a shared group address and asks you to send all future reminders there. That arrangement may be entirely ordinary. It becomes problematic when your records gradually replace the contractual customer with the payer's name, until nobody can explain which company remains responsible for an unpaid invoice. Keep three roles distinct: the entity owing the amount, the team organising settlement and the entity actually making the payment. One organisation may perform several roles. Their appearance in the same mailbox or bank transfer does not, by itself, make them interchangeable for legal or accounting purposes. The distinctions below use French law; arrangements involving other European countries require the relevant contractual and legal context. ## A third-party payment is not automatically an anomaly Article 1342-1 of the French Civil Code allows payment by someone who is not obliged to make it, subject to a legitimate refusal by the creditor. The ordering party's name can therefore differ from the debtor's without that difference alone making the payment inconsistent. [Civil Code, article 1342-1](https://www.legifrance.gouv.fr/codes/article_lc/LEGIARTI000032035237). That possibility does not remove the need to understand the transaction. Ask which invoices it covers, for which company and with what allocation. A group treasury entity may make one consolidated transfer while a shared service centre only prepares the payment file. The contact's email address describes part of the working process; it does not necessarily establish which entity owns the bank account being used. Avoid overreaching in either direction. An established third-party payment arrangement is not proof of fraud. A familiar group name does not prove that any receipt can be allocated to whichever subsidiary is convenient. The first decision is to establish the connection between the observed payment and the open invoices, preserving the original transfer information while the team checks its purpose. ## Use the contract to identify the debtor Retrieve the purchase order, contract or acceptance of the supply, then compare the entity that entered the transaction with the entity named on the invoice. If those documents conflict, resolve the inconsistency before moving the debt in your records. A trading name shared across the group cannot replace the legal identity of the specific company involved in the transaction. Article 1199 of the French Civil Code establishes that contractual obligations arise between the parties, subject to the exceptions provided by the legislation. Participation in a payment does not, on its own, establish responsibility for all the customer's contractual obligations. Separate undertakings may exist and need to be identified and assessed. [Civil Code, article 1199](https://www.legifrance.gouv.fr/codes/article_lc/LEGIARTI000032041378). This check is particularly useful when several subsidiaries use similar references. The method for [distinguishing invoices with the same number](https://www.billabex.com/en/blog/duplicate-invoice-numbers-legal-entities/) establishes document identity. The additional step here is to record who pays for whom, without turning the name visible on the bank statement into a replacement contractual customer simply because that name is easy to recognise. ## Build a short map of responsibilities A useful record can contain just a few clearly explained roles: contractual debtor, invoice identity, approval contact, payment contact, usual payer and evidence of that payer's role. Add the verification date and the contact who can confirm a change. The objective is to support the next action without implicit assumptions, rather than reproduce the group's entire organisational chart in your receivables system. For the administrative process, the customer may confirm that a central team receives invoices for a subsidiary and prepares its payments. Where a mandate or another document defines representation, retain its reference and scope. Do not expect the collections team to classify an ambiguous legal undertaking from a job title or an email signature without reviewing the relevant documents and obtaining appropriate support. Distinguish the ability to receive a copy, approve an invoice and agree a payment extension. Different people may hold those responsibilities. A contact who is excellent at tracing bank transfers may not be authorised to change the agreed payment terms. Make that boundary visible so that a helpful administrative conversation does not silently become a presumed agreement to new commercial conditions. ## One group transfer still needs allocations by company Consider a wholly fictitious example. Subsidiary A owes €9,000 and subsidiary B owes €6,000, producing €15,000 of open receivables. Holding company H transfers €10,000. A confirmed breakdown allocates €7,000 to A and €3,000 to B. After reconciliation, the remaining balances are therefore **€2,000 for A and €3,000 for B**. If the tracker merely creates an “H” account with a €10,000 receipt, both invoices may remain open for €15,000 while an unallocated credit appears elsewhere. Conversely, if the team combines everything under H and requests the remaining €5,000 from the holding company as its own debt, the record loses the distinction between the two actual debtors in the simulated arrangement. The €5,000 total remains useful for understanding the group's portfolio. It does not justify merging the receivables. The correct representation preserves two balances, one incoming payment and the supporting allocation. The amounts must reconcile: the initial €15,000, less the €10,000 received, leaves €5,000 distributed according to the confirmed breakdown. No additional receipt is created by correcting the account labels. This extends the approach to [one transfer covering several invoices](https://www.billabex.com/en/blog/one-payment-multiple-invoices/). If the allocation is missing or disputed, keep that uncertainty visible and obtain clarification. Selecting the subsidiary with the oldest invoices purely to make the report look tidier is not evidence for an allocation. It can conceal the actual unresolved balance and misdirect the following conversation. ## A central team's promise must specify which debts it covers In the example, the central team subsequently says, “We will pay on Friday.” That statement does not establish whether it means A's €2,000, B's €3,000 or the full €5,000 remaining. Ask for the amount, invoices, companies and expected date. Record who supplied the information and the confirmed role in which that person was speaking for the relevant payment process. If the contact explicitly promises payment of A's €2,000, B's follow-up remains separate. A promise does not settle an invoice before the receipt is received and reconciled. The method for [making payment promises verifiable](https://www.billabex.com/en/blog/verifiable-payment-promises/) therefore needs one additional piece of precision here: the identity of the debtor whose invoices are covered by that commitment. Address the operational request to the appropriate authorised contact while naming the company whose invoice remains open. You can ask a payment centre to confirm processing without claiming that it entered into the underlying debt itself. This gives the central team a practical request it can handle while preserving the responsibilities supported by the documents held on the customer account. ## Treat a proposed debt takeover as a separate decision “The holding company is taking over all debts from now on” goes beyond a contact update. Article 1327 of the French Civil Code requires creditor agreement and a written record for an assignment of debt. Article 1327-2 separately addresses release of the original debtor, requiring the creditor's express consent within that framework. [Civil Code, assignment of debt](https://www.legifrance.gouv.fr/codes/id/LEGISCTA000032034723). Have such a request assessed before changing the debtor or treating the original entity as released. Depending on the documents, it may describe payment on behalf of another company, a particular undertaking or a separate legal transaction. This article does not resolve every group structure, insolvency situation or cross-border arrangement; classification requires examination of the actual documents and the applicable law. The [Billabex customer view](https://www.billabex.com/en/product/customer-view-360/) helps place invoices and exchanges in context. For your organisation, test a third-party payment covering two subsidiaries and check that every remaining commitment can still be explained. Effective follow-up makes cooperation with the payer easier while preserving the identity of the receivables your business is working to collect from its customers. ## Sources - [French Civil Code, article 1342-1](https://www.legifrance.gouv.fr/codes/article_lc/LEGIARTI000032035237), payment by a person not obliged to pay. - [French Civil Code, article 1199](https://www.legifrance.gouv.fr/codes/article_lc/LEGIARTI000032041378), contractual obligations between parties. - [French Civil Code, articles 1327 to 1328-1](https://www.legifrance.gouv.fr/codes/id/LEGISCTA000032034723), assignment of debt and release of the original debtor.