One contract, three countries, four debtor entities: which company actually owes you?

The contract says one thing, the invoice says another, and the money is nowhere. A software vendor signs a deal with a multinational's US subsidiary, the platform gets rolled out through a reseller in Singapore, the end customer is in France, and when the invoice goes unpaid, three entities have a reason it's not their problem.

Welcome to international software collections. The first question isn't "how do we collect?" It's "who actually owes us?"

The four-entity problem

International enterprise deals are rarely a clean two-party contract:

• The parent—the multinational whose name is on the press release
• The subsidiary—the entity that signed the agreement
• The reseller or channel partner—the company that invoiced the end customer (or should have)
• The end customer—the company actually using the software

When payment stops, each one points at another. The subsidiary says the reseller holds the relationship. The reseller says the end customer hasn't paid them. The parent says it's a local matter. And your invoice sits in the middle, aging.

How we trace the liable entity

Entity tracing is investigation work, and it follows a pattern:

1. Start with the contract, not the press release. The entity that signed is the entity that owes—unless the agreement clearly delegates payment to another party. The signed order form names the defendant, full stop.
2. Map the corporate structure. Parent, subsidiary, affiliates—which entities exist, where they're registered, and which one holds the money. In most jurisdictions, a subsidiary's debt is the subsidiary's problem—but a parent that guaranteed, co-signed, or blended the deal is fair game.
3. Follow the usage. The end customer used the software. Their operations team knows it. Even if the billing chain runs through a reseller, the end customer's usage record is your evidence that value was delivered—and that the reseller's "they didn't pay us" excuse has a counter.
4. Check the channel agreement. If the reseller was responsible for invoicing and collecting, they may have breached their own contract—which makes them the collection target, not the end customer.
5. Establish jurisdiction. Where the entity is registered, where the contract says disputes are resolved, and where the money actually sits. Negotiation beats litigation in every country; litigation is only worth it where the judgment can be enforced.

Why this is specialized work

A generalist agency treats "the customer" as one company and sends one letter. International software debt needs someone who can trace the entity, work the local jurisdiction, and negotiate in the debtor's language and business culture—all while you deal with one point of contact and one consolidated report. That's what our international desk is built for: local agents in 15+ countries, multilingual negotiators, and an in-house lawyer who's worked in jurisdictions most agencies won't touch.

The short version

When the money's missing and the org chart is complicated, don't guess which entity owes you—trace it. Contract first, structure second, usage third, channel fourth. The right entity, pursued in the right jurisdiction, with the right evidence, pays. The wrong one just makes the write-off easier to file.