Cross-border sales teams often celebrate the commercial group they have won. Finance must collect from a specific legal entity.
That difference sounds administrative until the names begin to drift. A regional parent signs a master agreement. A local subsidiary places the order. Another group company receives the service. The invoice goes to a shared finance center, and the team assumes the best-known brand will pay.
When payment is late, each participant can point to a different part of the transaction. The issue is no longer simply whether the customer is willing to pay. It is whether the creditor can show who bought what, who received it and who owes the money.
This is entity drift. It grows quietly as a customer relationship expands across countries, products and departments.
Why Growth Makes Entity Drift More Likely
International sales reward speed and flexibility. Open-account terms can help a supplier compete, but they also mean delivery happens before payment. The US Department of Commerce notes that international open-account terms commonly run for 30, 60 or 90 days and create meaningful non-payment exposure for the exporter.
During that gap, organisations change. A customer may centralise procurement, move accounts payable to a shared service centre or ask a different subsidiary to receive future invoices. Sales teams may treat those changes as routine because the commercial group remains the same.
Legal entities are not interchangeable simply because they share a logo or owner. Finance therefore needs a control that follows the transaction rather than the brand.
Build a Five-Point Entity Map
Before the first invoice, create a one-page map with five roles.
1. Contracting entity: Record the full legal name and registered details of the company that accepted the agreement. Preserve the signed contract, accepted proposal or purchase order.
2. Ordering entity: Identify the company named on the purchase order and the person authorised to place it. If the order comes from a different group company, resolve that difference before delivery.
3. Receiving entity: Record which company and location received the goods or services. Keep delivery confirmation, project acceptance or system records showing completion.
4. Invoiced entity: Confirm the exact company name, billing address, tax details, purchase-order reference and submission channel required by accounts payable.
5. Paying entity: Ask which company or treasury centre will send the funds and what reference will appear. A payment from another group entity may be operationally normal, but it should not be assumed in advance.
The map is not a substitute for legal review. It is a way to expose inconsistencies while the customer still wants the transaction to proceed.
Make Changes Explicit, Not Conversational
Entity drift often begins with a reasonable email: “Please invoice our Dubai company from next month” or “All payments now go through the group office.”
Do not treat that message as a complete instruction. Ask four follow-up questions:
· What is the full legal name and address of the new entity?
· Does the change affect the existing contract or only future orders?
· Who is authorised to confirm the change?
· From which invoice or delivery date does it apply?
Then document the answer in the customer record and the relevant transaction. Commercial teams should not have to interpret a finance note months later.
Preserve the Digital Trail
Digital records make cross-border trade faster, but the business still needs a coherent trail. The UAE recognises electronic and digital invoices and is moving toward structured electronic invoicing. Its electronic-transactions framework also gives importance to the integrity and retrievability of electronic documents.
The practical lesson is broader than compliance. Keep original files, complete approval emails and system records. Do not rely only on screenshots, exported chat fragments or a new summary created after the dispute begins.
Each record should answer one of three questions: who acted, what they approved and when they did it.
Add a Pre-Invoice Exception Check
Automation should process clean transactions quickly. It should also stop mismatched ones before they reach the customer.
Create an exception when:
· the contract and purchase order name different entities;
· delivery is requested for a company not recorded on the order;
· billing details change after delivery;
· the customer asks for an invoice to be reissued to another entity; or
· the payer says it is acting for a different group company.
Assign one owner to resolve the exception. Sales can confirm the commercial history, finance can verify billing requirements and legal counsel can advise when the contractual position is unclear.
The goal is not to slow every sale. It is to stop the few transactions most likely to become difficult receivables.
Use The Map When Payment Is Late
If an invoice becomes overdue, start with the entity map before sending another generic reminder.
Ask the customer to confirm that the invoiced entity accepted the obligation, that the invoice is approved and that no amount is disputed. If another entity is expected to pay, ask for a dated confirmation that identifies its role without casually releasing the original obligor.
Separate a genuine invoice-routing problem from a dispute about liability. The first may be fixed with a document or corrected submission. The second requires a deliberate decision based on the contract, evidence and relevant professional advice.
Entity drift is a governance problem before it becomes a collections problem. The businesses that control it do not depend on perfect customer behaviour. They make every cross-border sale answer the same basic question: exactly which company owes us, and can we prove why?
For a UAE receivable that has moved from an entity-routing issue into a recovery decision, Debitura’s UAE debt collection network is a relevant next step to evaluate alongside the records.
Article received via email
