**The M&A Transaction Lexicon**

Common Vocabulary Across the Transaction Lifecycle

Version 2.2  ·  Terminology and regulatory references current as of September 2026. Jurisdiction-specific entries are the part most likely to require periodic maintenance.  ·  Stephen Getty | stephengetty.com

Purpose

M&A transactions are run by several stakeholder communities at once: the deal and corporate-development principals who set the thesis, the governance and advisory layer that oversees the complete program, and the functional and technical teams that execute it. Each group uses slightly different terminology and may assume others use terms in the same way. This often delays a transaction when meaning and intent are lost in translation among them.

Most advisory consultancies know what they mean when terms are used within their own organization. Similarly, most M&A professionals know what they intend to communicate, but others usually hear terms and are left to infer meaning. While no single authoritative standard is mutually agreed on that governs M&A terminology, this lexicon consolidates and normalizes terms widely used by transaction advisers, corporate-development teams, integration and separation practitioners, and functional leaders. It is designed as a plain-language reference intended to be shared across the deal, governance, and execution layers, on both the buy side and the sell side. This supports a term meaning the same thing to all of them.

A semantic model of the transaction

This lexicon is organized around one idea: a transaction is a single event seen from at least two sides. The buyer's integration and the seller's separation are mirror images, and much of the vocabulary is shared. An integration management office and a separation management office play the same role; Day 1, transition services, and standalone readiness arise on both sides; RemainCo and SpinCo are the two halves of one separation. The lifecycle organizational hierarchy of program, phase, stage, sub-stage, activity group, activity, and task, the milestone roadmap, and the operating-model layers form a common frame within which every workstream, on either side of the deal, can locate its own terms.

How to use this lexicon

Entries are grouped into a general grounding section, holding the terms every stakeholder should be familiar with, followed by workstream sections for each specialist vocabulary. Within each section entries are alphabetical. Cross-references shown as "See also" are clickable and link to the referenced entry; an alphabetical index at the end links every term to its definition, so a user can immediately reference a term without knowing its section. Where usage has strong variance across sources, the entry states this rather than ignoring the variance. This is written for broad usage but assumes the US as the largest audience. Thus, language and grammar are tailored to US conventions. However, applicability tags such as [United Kingdom], [Multiple jurisdictions], or [Structure-dependent] mark terms whose relevance depends on where, or how, a deal is structured; an untagged term is treated as having general applicability.

Transaction pattern and structures

A transaction can take many forms on both sides of the deal. The table below provides a reference for the reader; each pattern is defined further in the corporate development section.

Structure of a transaction program

A program is addressed along two axes. Vertically, work breaks down from the program into phases, stages, sub-stages, activity groups, activities, and tasks. Horizontally, it is divided into workstreams that run across every phase. Milestones mark fixed points in time, and gates mark the decision checkpoints between stages. It is important to note that smaller and simpler transactions may not require the same depth of structure as larger or more complex transactions.

Frequent lifecycle milestones

The lifecycle relies on a normal roadmap of fixed events which often become shorthand for discussing phases or stages, such as treating “Day 1” to mean the same thing as “Day 1 Readiness”. This common lack of precision adds unnecessary confusion. This table treats milestones as specific points in time with two phases that are most often defined by milestones. Close is a legal event; Day 1 is an operational convention, usually coinciding with or immediately following Close. In a spin-off with no purchaser, Day 1 is the new entity's first operating day. In a separation, post-Day 1 dependency ends not at a further milestone but incrementally at the exit from each transition service.

Operating model layers

The transaction target design is described through an operating model. For purposes of this lexicon it is expressed through six commonly used layers, set out below. A condensed four-layer framing of people, process, technology, and governance is also common but less explicitly structured.

A note on terminology conventions

Two conventions are worth stating. First, Legal Day 1 and Operational Day 1 are recorded here because they are often encountered, but they are treated as firm-specific and perspective-dependent rather than as universal milestones; a seller's view of operational separation and a buyer's Day 1 are the same transaction seen from opposite sides. Second, sequential Day 2 and Day 3 labels are avoided in favor of the named phases “stabilization” and “end state”, since their meaning varies by organization.

M&A Acronyms and Abbreviations

M&A transactions use terminology drawn from transaction execution, finance, legal documentation, regulatory approval, integration, separation, technology, and operating-model disciplines. In many cases, terms are shortened to acronyms or abbreviations, which may mean nothing to those outside of a particular discipline. This section clarifies between abbreviated terminology that is portable across jurisdictions and those whose meaning or applicability depends on a particular market or jurisdictional entity.

Terms included have a recurring and material relationship to transaction structures, valuation or economics, due diligence, signing or closing, regulatory approval, separation, integration, or transaction implementation. Sector or industry specific terminology is excluded from this lexicon. Regulatory terminology and abbreviations that are principally related to the industry in which the target or buyer operates, such as banking, healthcare, energy, telecommunications, or other regulated sectors, are addressed in industry specific lexicons.

These tables are the quick reference for abbreviations used in this lexicon. The body defines the subset of terms that merit an expanded definition beyond the table, so an abbreviation may appear here without a matching entry in the sections that follow. If an abbreviation has more than one meaning within M&A transactions, each relevant meaning is listed separately and tagged by context. Meanings that are general corporate terminology, without a meaningful M&A transaction specific meaning, are not included.

General M&A Acronyms

The following abbreviations are general terms of practice understood across international M&A professionals. Their use does not depend on a particular legal jurisdiction, though individual markets, firms, and advisers may prefer different terms.

Inclusion in this table does not mean that every term applies to every transaction. The concept of a term may be represented by other abbreviations and terms in jurisdictions that are not scoped herein.

General Usage Notes

Some terminology varies between markets but is generally understood as referring to the same concept. For example, CIM and IM are both used internationally, though particular markets or geographies may use one by cultural preference. Similarly, LOI, MOU, EOI, IOI, and NBO may describe different stages or forms of preliminary transaction communication depending on the team.

The same abbreviation may also represent completely different concepts. PPA, for example, can mean either a “Purchase Price Adjustment” during transaction closing or “Purchase Price Allocation” for accounting and tax purposes after the transaction. It is always critical to understand context.

Regional and Market Specific M&A Terminology

Many transaction concepts are understood in all markets, but the terminology used to describe them may differ materially. These terms are addressed here rather than with jurisdiction specific laws and regulators because the language distinction relates primarily to geographic deal market conventions rather than legal requirements.

Market Terminology Interpretation

Being included in this table does not imply that the underlying concept behind the term exists only in the identified markets. It indicates that the specific terminology or abbreviation has a particularly strong regional association.

For example, RWI and W&I perform comparable roles in transaction risk, but the terminology differs by market. Similarly, a U.S. transaction may refer to a Stock Purchase Agreement, while other jurisdictions refer to a Share Purchase Agreement. The conceptual transaction functions are the same, but different terms evolved in the different business cultures.

Jurisdiction Specific Legal and Regulatory Acronyms

The abbreviations and short forms below refer to specific laws, regulators, regulatory regimes, legal tests, employment frameworks, tax structures, and other concepts materially dependent on jurisdiction.

These terms are not necessarily applicable just because a transaction is cross-border. Applicability depends on several contextual factors, such as the jurisdictions of the parties and operation sites, revenue or transaction value thresholds, ownership and control concerns, investor nationality, number of employees, transaction structure, competitive harm, national security considerations, and applicable laws.

Jurisdictional Interpretation

Inclusion in this table means that the legal intent, authority, test, or applicability of the term is geographically specific to the regulatory regime indicated. It should not be taken to imply that comparable requirements do not exist in other jurisdictions.

Note that multiple regulatory regimes may, and often do, apply to the same transaction. A cross-border acquisition may, for example, require separate analysis of:

• Merger control filings;
• foreign investment or national security screening;
• foreign subsidy review;
• employee information, consultation, or transfer requirements;
• privacy and data transfer obligations;
• sanctions restrictions; and
• transaction specific tax or ownership rules

Regulatory analysis should always address the full transaction scope rather than just the governing law of the principal acquisition agreement.

Scope Boundary for Industry Specific Lexicons

This common core lexicon intentionally excludes regulatory terminology that is relevant primarily due to the industry, regulated activity, or product portfolio of the buyer or target rather than to the M&A transaction itself.

Examples include banking and financial services supervisory frameworks, healthcare regulation, pharmaceutical and medical device regulation, energy regulation, telecommunications regulation, and specialized export control situations where applicability is driven by the business.

This approach permits the core M&A lexicon to remain applicable across all industries while relying on sector specific sections to capture the additional regulatory requirements that may arise when a transaction involves a regulated business.