Software due diligence for cross border deals is harder than the single country version for one reason: the estate is governed by agreements written in one place and deployed in many. A global enterprise agreement signed by a parent in the United States may not cover a subsidiary in Germany the way the deal team assumes, and a regional reseller contract in Asia may carry terms the head office has never read. When a deal crosses borders, the buyer inherits not one licensing position but several, stitched together by agreements that rarely line up cleanly.
This guide sets out how to run software due diligence for cross border deals so the buyer sees the full picture rather than the head office summary. It builds on the core software due diligence method and connects to post close license reconciliation, where the regional positions are finally consolidated. Where the target shares agreements with a parent, read it alongside mapping shared and group wide software agreements.
Why software due diligence for cross border deals is different
Three things make a cross border estate harder to read. First, entitlements and deployments sit in different jurisdictions, so a global agreement has to be tested against local headcount and local usage rather than a single number. Second, currency and regional pricing mean the same product carries different rates in different markets, and a true up priced at head office list can understate the cost in a high price region. Third, contracts are governed by different laws, so an assignment that is routine in one country can require consent or trigger termination in another.
The practical effect is that the head office contract register is never the whole story. Local entities buy software directly, sign regional reseller deals, and renew on local cycles that the centre does not track. The first job of cross border diligence is to find every place the target touches software, not just the places the head office knows about. Where the target runs a mixed estate, combine this with software due diligence for on premises estates.
Reconstruct the estate jurisdiction by jurisdiction
The reconstruction discipline that works for any estate has to be repeated per jurisdiction. Pull the general ledger and accounts payable for each operating entity, not just the consolidated accounts, because local software spend often never reaches the group software line. Pull the identity provider and admin consoles per region to see what users actually log in to. Then test the global agreements against each region: a worldwide enterprise agreement may exclude certain territories, cap usage by region, or require local order forms that were never raised. The gap between the global entitlement and the regional deployment is the exposure.
Key takeaways
- A cross border target carries several licensing positions, not one. Global agreements rarely cover every territory the way the head office assumes.
- Local entities buy software directly and renew on local cycles. Reconstruct the estate per jurisdiction, not from the consolidated register.
- Currency and regional pricing can make a true up far more expensive than a head office list price suggests. Price exposure in the right currency.
- Governing law decides whether a contract can be assigned without consent. The same transfer can be routine in one country and blocked in another.
Price the exposure in the right currency and the right law
Once the estate is reconstructed, the exposure has to be priced where it lives. A seat true up in a high price market costs more than the same true up at head office rates, and a publisher will bill in the local currency at the local list. Equally, the right to consolidate regional contracts onto a single global tenant depends on the governing law of each agreement and on data residency rules that can prevent moving workloads across borders at all. The commercial team prices the gap; the legal team, instructed by the buyer own counsel, confirms which transfers need consent. Neither number is reliable without the other.
Audit risk is also regional. The major publishers behind post deal audits, Oracle, SAP, Microsoft, IBM, and increasingly Broadcom for VMware, Salesforce, and ServiceNow, run compliance programmes that vary by territory and by the maturity of the local sales team. A target that looks compliant centrally can carry concentrated exposure in one region where deployment outran the local entitlement. As of June 2026, inherited and disputed licensing has produced nine figure publisher claims in cross border groups, with SAP reported to have pursued AB InBev for around 600 million dollars over inherited and indirect usage. Confirm current figures with primary sources.
Recommendations for buyers
- Reconstruct the estate per operating entity and per jurisdiction, never from the consolidated group register alone.
- Price every true up in the local currency at the local list, not at head office rates, so the deal model is not understated.
- Instruct counsel to confirm assignment and data transfer requirements jurisdiction by jurisdiction before fixing the deal structure.
- Build a single consolidated license position that rolls the regional findings together, ready to hand to post close reconciliation.
Run a regional renewal and audit calendar
A cross border estate renews on many cycles at once, and the buyer that loses track of them loses leverage. Build a single calendar that lists every material agreement, its renewal date, its notice period, and the entity and jurisdiction it belongs to. A renewal in a high price market that auto rolls before the integration team has decided whether to keep the tool is expensive in a way the central spend summary never shows. The same calendar should flag where a publisher audit clock is running, since the right to audit and the practical likelihood of one both vary by region and by the local sales relationship.
The calendar does two things for the buyer. It tells the deal team which decisions fall inside the first hundred days, where keep, drop, or renegotiate choices have to be made quickly and in the right currency. And it converts a scattered set of regional contracts into a schedule the integration lead can act on without rediscovering each agreement. A buyer that walks into the first major regional renewal already knowing the notice period, the local list price, and the consolidation alternative negotiates from strength rather than reacting to an automatic rollover.
Hand a single consolidated position to the deal team
The output of cross border diligence is not a stack of regional reports. It is one consolidated license position that shows the buyer the total exposure, broken down by jurisdiction, priced in the right currency, and flagged for the clauses that need consent. That single view is what the deal team prices and what the integration team inherits on day one. Built by an independent, buyer side advisor with no affiliation to any publisher or reseller, it is a number the buyer can defend in front of an investment committee and carry straight into reconciliation after close.