Operating Models in Corporate Finance

An operating model in corporate finance defines how the work of the finance function is distributed: which entities execute, where decision rights sit, what is performed inside the group and what is contracted to external providers, and which infrastructure carries the processing. Between corporate structure above and transaction execution below, the same set of legal entities under the same finance mandate can run as a single centralized operation or as a federation of local teams supported by outsourced processing — and that difference determines who can release a payment and where an unmatched settlement gets resolved.

Across organizations, most of the variation resolves to two axes — how far decision rights and execution are concentrated, and how much of the execution is sourced from outside the group. Each axis is treated in a dedicated applied reference, Centralized vs Decentralized Treasury Models and In-House vs External Financial Operations. The space between the poles of those axes is occupied by named structures through which large organizations configure finance work in practice: shared service centers, treasury centers and in-house banks, payment factories, netting and re-invoicing centers.

What an Operating Model Defines

An operating model assigns finance work to performing units and fixes the terms under which they perform it. For each recurring category of work — payment execution, liquidity management, reconciliation, financial reporting, and compliance operations — the model fixes the performing unit first. It then ties that unit to a location, a legal entity, an authority basis, and the systems on which processing runs. Taken together these assignments form a placement map of the finance function, in which every activity resolves to a performing unit, and each unit to a location, an authority basis, and a platform.

What separates the model from organizational structure is the difference between ownership and performance. The entity chart and reporting lines establish who legally owns obligations and who is accountable for results; the operating model establishes where the work is actually done and under whose operational authority. In multi-entity groups the two routinely diverge. A subsidiary remains the legal obligor on its payables while a shared service center in another jurisdiction prepares and releases the payments under authority delegated from the subsidiary’s own approval chain. The divergence is the mechanism by which groups concentrate execution without restructuring legal entities, and every point of divergence creates an accountability interface that governance has to cover explicitly.

One level below sits process design. A payment process passes through the same states — initiation, approval, release, confirmation, reconciliation — whoever performs them; the operating model decides which unit holds each step and on which system it runs. The same process design can therefore operate under sharply different models, from approval retained in the subsidiary with release in a central payment factory to the full chain held by one local team. Transformations that redesign processes while leaving the model untouched, or move the model while assuming processes carry over, fail at the handoffs — steps that previously sat inside one team now cross units, time zones, and systems the process design never specified.

With governance frameworks the relationship runs in both directions. Delegated authority limits, segregation-of-duties requirements, and control obligations are defined in governance instruments; where those controls physically sit — which unit performs the second approval, which system enforces the limit — follows from the operating model. A change in the model therefore forces a governance remap. When payment release moves from local entities into a central factory, authority matrices, control ownership, and monitoring scope have to move with it, or the documented control structure goes stale against the actual flow of work.

In practice the boundary between these layers matters because each moves through a different mechanism. Entity charts change through legal restructuring, process designs through re-engineering, governance frameworks through policy revision and approval. The operating model changes through redistribution of work, authority, and system access across units. That pace — slower than rewriting a policy, faster than restructuring entities — makes the model the lever most finance transformation programs actually pull.

Dimensions of Variation

Four axes account for most of the structural variation across corporate finance operating models: how far decision rights and execution are concentrated, where execution is sourced, where the work is placed physically and legally, and which functions the model covers at what degree of standardization. The axes move independently — a group can concentrate execution while sourcing it externally, or standardize a process while leaving it locally executed — and a model is a position on all four at once.

Centralization of Decision Rights and Execution

The concentration axis runs from full local autonomy, where each entity manages its own cash, banking, and payments, to full central concentration, where a single unit decides and executes for the group. Decision rights and execution travel along it separately. A group can centralize policy — counterparty limits, banking strategy, hedging mandates — while every transaction is still executed locally; it can equally concentrate execution into one processing unit while approval authority stays with the entities whose obligations are being settled. Most real configurations are mixed: central policy with local execution, central payment processing alongside local collections, full concentration for funding decisions next to distributed transactional work.

Where a group sits on this axis determines what it can see and how fast it can act. Concentration produces group-level cash visibility, fewer banking relationships, and the ability to move liquidity across entities within one decision cycle; it also concentrates operational dependency, since a central unit becomes a single point of failure for every entity it serves. Distribution keeps execution close to local business and local regulators at the cost of fragmented visibility and duplicated capability. The applied comparison — pooling structures, intercompany funding mechanics, mandate design, the failure modes of each pole — is the subject of Centralized vs Decentralized Treasury Models.

Sourcing of Execution

Along the sourcing axis, configurations range from fully in-house operations through business process outsourcing of transactional work — invoice processing, reconciliation matching, payment preparation — to arrangements where the infrastructure itself is external and the company operates on a provider’s platform. Accountability does not travel with the work. Regulatory obligations, fiduciary duties, and liability for failed execution remain with the company regardless of who performs the processing — which is why sourcing decisions are control decisions as much as cost decisions.

What sources well is rule-based work with definable inputs and outputs — matching, data entry, standardized reporting — because it can be specified in a contract and measured against service levels. Authority-bearing steps resist sourcing. Payment approval, release authority, and exception judgment usually stay inside the group unless compensating controls make external execution auditable. Crossing the boundary also changes the control instrument, from direct supervision of staff to contract terms, service-level monitoring, and periodic audit of the provider. The full decision space — provider categories, contract structures, retained-organization design — sits with In-House vs External Financial Operations.

Location and Entity Placement

Where concentration and sourcing decide who performs the work, placement decides where the performing unit sits — physically and legally, and the two placements are separate decisions. Physical location sets labor market, cost base, and time-zone coverage. A center serving entities across regions either works extended shifts or accepts that some markets’ cutoffs fall outside its operating day. Legal placement determines which entity employs the staff, holds the system contracts, and acts as service provider to the rest of the group — a branch, an existing subsidiary, or a dedicated service entity.

Jurisdictional consequences attach to placement in a way they do not attach to the other axes. Intercompany services trigger transfer pricing obligations, so a service entity charging affiliates needs a defensible cost-allocation model. Activity performed on behalf of other entities can fall inside a regulatory perimeter: payment execution for group companies intersects payment services regulation in several jurisdictions, and whether an intra-group exemption applies depends on where the executing entity is incorporated and what exactly it performs. Data residency rules constrain where processing for certain entities may physically run. None of these constraints selects the model on its own; each removes placements that would otherwise be available.

Functional Scope and Standardization

Which activities the model deliberately covers — and which remain local arrangements by omission — is the scope component of the fourth axis. Transactional finance — payables, payment execution, receivables processing, reconciliation — enters scope first in most groups. Judgment-heavy functions such as tax structuring or deal finance typically stay outside any shared construct and follow the entity chart. The practical effect of scope is boundary definition. An activity outside scope has no defined performing unit beyond its local owner, which is tolerable for judgment work and a control gap for transactional work.

How uniform the covered processes are across units — standardization — moves independently of concentration. A group can run one process template executed locally on a common platform, or consolidate work into a center that still operates a separate variant per entity, consolidating location without consolidating process. The degree of standardization caps what the other axes can deliver. A center running dozens of local variants reproduces the fragmentation it was built to remove, at added coordination cost, and external sourcing is contractible only to the extent that the process can be specified once. Consolidation and sourcing both wait on the same event — the point at which one process template can be written down and enforced across entities. A group’s operating model is its position on all four axes at once, whatever its organization chart names it.

Structural Archetypes

Within the configuration space the four axes define, practice has settled into a small set of named constructs that occupy recurring positions. Each archetype packages a position on concentration, sourcing, placement, and scope into an institutional form with its own service agreements, account structures, and system footprint. Large groups typically operate several at once, and the boundaries between them blur where one construct absorbs another’s function.

Shared Service Centers and Global Business Services

A shared service center consolidates transactional execution from multiple group entities into one internal unit operating under intercompany service agreements — payables processing, billing and collections support, reconciliation, and record-to-report work in its typical scope. On the axes, the SSC concentrates execution while decision rights remain wherever governance places them, sources the work in-house as a captive unit, takes its physical placement from labor cost and time-zone coverage, and rests its economics on standardization. The center earns its consolidation by processing one process template at volume, and every local variant it preserves erodes the case for its existence.

Extended across functions, the construct becomes global business services. Finance operations sit alongside procurement, HR services, IT, and master data management under a single management layer, with global process owners holding design authority for each process end-to-end across regions. That ownership layer is the structural addition: an SSC executes processes designed elsewhere, while a GBS organization holds the authority to redesign them. Sourcing within GBS is commonly hybrid — captive centers and external providers under one orchestration — and the captive center is in practice the unit through which the sourcing axis gets traversed, since work that has been consolidated, specified, and measured inside an SSC is work in a contractible state.

Treasury Centers and the In-House Bank

A treasury center concentrates the treasury function itself — liquidity management, funding and intercompany lending, FX execution, ownership of banking relationships — for a region or for the group. Decision rights and execution both move here, which places the construct at the far end of the concentration axis for treasury work; regional variants under a global lead exist where time-zone coverage demands them. Placement is the jurisdiction-sensitive choice of the archetype set. Treasury centers have historically clustered in locations selected for tax treaty networks, regulatory treatment of intercompany finance, and access to banking and treasury talent — Singapore, Dublin, Amsterdam, and Luxembourg are the canonical examples.

On top of a treasury center, the in-house bank layers a change in account structure. Group entities hold internal accounts with the IHB entity, displacing a share of their external bank accounts; intercompany funding, internal FX, and internal settlement post to those accounts as ledger movements, while external banking concentrates in the IHB itself. External account counts and transaction volumes fall, and in exchange the group assumes intercompany position management. Every internal account balance is an intercompany exposure, carrying interest terms, documentation requirements, and withholding tax implications. The distinction between the two constructs is the layer they operate on — a treasury center concentrates the work, an in-house bank restructures the account topology beneath it.

Payment Factories and On-Behalf-Of Structures

Group payments converge on a single processing point in a payment factory. Entities submit instructions; the factory validates and formats them, applies controls, and releases them through consolidated bank connectivity. Execution concentrates; approval authority frequently stays with the originating entities, making the factory a standing example of the split between decision rights and execution described on the concentration axis. Standardization is its entry condition — one format library and one connectivity layer are what the construct consists of.

Beneath the routing layer, settlement runs in one of two modes. In-name-of processing executes each payment from the originating entity’s own account, with the factory acting as gateway. On-behalf-of processing goes further. Under POBO, the factory’s entity — typically the in-house bank — pays from its own account on behalf of the subsidiary and records an intercompany position; COBO mirrors the structure for collections, with incoming flows attributed to entities through virtual account hierarchies. On-behalf-of structures collapse external accounts further and shift the reconciliation burden onto the intercompany layer, where attribution of flows replaces per-entity bank statement matching. They also carry the regulatory weight of the archetype set. Executing payments for other legal entities is precisely the activity that intersects payment services regulation, so the placement of the executing entity decides which regime applies and whether an intra-group exemption is available.

Netting and Re-Invoicing Centers

On a fixed cycle, a netting center offsets intercompany payables and receivables across participating entities and settles net positions only — each participant moves one net amount per cycle against the center. Gross intercompany settlement volume and FX conversion counts drop accordingly. The price is operating discipline: a fixed netting calendar, a dispute cut-off, and enforced participation by the entities inside the cycle. On the axes the construct is narrow — single-purpose scope, high standardization, concentrated execution.

Into the intercompany trade chain, a re-invoicing center inserts itself as counterparty. It takes title to trade flows and re-invoices each side in its local currency, concentrating the group’s transactional FX exposure in one entity. Where netting offsets obligations that already exist, re-invoicing restructures the obligations themselves — who owes whom, and in which currency.

Predating the in-house bank, both constructs are progressively absorbed by it — continuous internal settlement across IHB accounts performs the netting function without a periodic cycle, and IHB internal FX takes over the currency concentration role. Standalone centers persist where no IHB exists, or where participants outside the IHB perimeter — joint ventures, minority-held entities, entities in restricted jurisdictions — require a construct they can join without holding internal accounts.

How Configurations Combine

A complete operating model is a portfolio of positions set function by function rather than a single stance: treasury can sit fully concentrated in a treasury center while payables run through a shared service center and tax follows the entity chart untouched. The archetypes are the implementation vehicles for those positions, and each occupies a characteristic location on the four axes:

Archetype	Concentration	Sourcing	Placement	Scope and standardization
Shared service center	Execution concentrated; decision rights unchanged	Captive in-house	Labor cost, time-zone coverage	Transactional finance; standardization as economic basis
Global business services	Execution plus process design authority	Hybrid: captive and external under one orchestration	Multi-hub by region	Cross-functional; global process ownership
Treasury center	Decision rights and execution together	In-house	Jurisdiction-driven: tax treaties, regulatory treatment, talent	Treasury function
In-house bank	Maximum: account topology centralized	In-house	Jurisdiction-driven; regulatory perimeter sensitive	Intercompany finance and internal settlement
Payment factory	Execution concentrated; approval frequently local	In-house or provider platform	Connectivity and cutoff coverage	Payments; format standardization as entry condition
Netting / re-invoicing center	Execution concentrated, single-purpose	In-house	Jurisdiction-driven: FX controls, withholding	Intercompany settlement and FX

In operation, the archetypes interlock. A shared service center prepares the payables that a payment factory releases. On-behalf-of settlement in that factory works only when an in-house bank carries the intercompany positions it generates, and the in-house bank in turn presupposes treasury-center governance over intercompany finance. Global business services holds the process-ownership layer that keeps the whole chain standardized.

Where the interlock is missing, the combination fails along predictable lines. A payment factory commissioned ahead of format standardization processes exceptions at scale instead of payments. Without an in-house bank behind it, on-behalf-of settlement scatters intercompany positions across entities, with no unit managing the resulting exposures. Consolidating a center before its processes converge yields one location running many variants — consolidation without the visibility or cost outcome that justified it.

Few groups design the full configuration at once. The recurrent build sequence runs from process standardization to shared service consolidation, then payment factory connectivity, treasury concentration, the in-house bank, and finally on-behalf-of settlement — each stage producing the precondition the next stage consumes. Groups enter the sequence at different points and stop at different depths; the ordering constraint, not the endpoint, is what repeats across organizations.

The sequence also runs in reverse. Acquisitions bolt non-standardized entities onto a perimeter built for converged processes; divestments carve served entities out of centers sized for them; regulatory shifts in data residency or the payment services perimeter remove placements the configuration depended on. Each event lands somewhere specific — a center sized for a perimeter that no longer exists, a placement a new regime no longer permits — and the configuration moves again along the same axes.

Determinants of the Operating Model

The configuration a group runs is less a design choice than an intersection of constraints. Determinants rarely select a model outright; each prices some positions out or bars them entirely, leaving a space within which the design decision is actually made. Reading a configuration therefore starts with reading its determinant profile.

The perimeter is drawn by entity topology. Wholly-owned subsidiaries can be absorbed into shared constructs by internal mandate; joint ventures and minority-held entities resist absorption, because fiduciary duties to outside shareholders and contractual consent rights keep them on arm’s-length arrangements — visible to group treasury, outside on-behalf-of structures and the in-house bank. Jurisdictional spread works the same way through accumulation. A second country doubles the regulatory regimes, tax positions, and placement constraints the configuration must satisfy at once; a tenth country means ten of each. Acquisition cadence matters separately from size — a perimeter that changes every year favors loosely coupled constructs an acquired entity can join quickly, while deep integration pays back only where the perimeter holds still long enough to amortize it.

Whether concentration is available at all follows from the group’s management model. A financial holding that runs entities as a portfolio — separately financed, separately banked, kept disposal-ready — has no basis for an in-house bank, since internal accounts and intercompany positions are precisely what a clean disposal cannot carry. An integrated operator extracting synergies across entities faces the opposite pressure, because fragmented execution forfeits the integration the group exists to capture. The operating model cannot be more concentrated than the management model above it.

Below a certain transaction volume, each archetype costs more than the fragmentation it removes — the fixed apparatus of intercompany service agreements, transfer pricing documentation, a netting calendar, format libraries, and internal account administration is recovered only at volume. Homogeneity gates standardization, since one process template presupposes comparable flows; a conglomerate whose divisions bill, collect, and settle in structurally different ways converges on a shared template slowly or never, whatever its aggregate volume.

In jurisdictions with currency controls — China, India, and Brazil are the standing examples — onshore accounts and local documentation keep execution in-country, with each transaction approved individually, so entities there participate in group visibility while staying outside on-behalf-of settlement. Withholding tax on intercompany interest prices the positions an in-house bank creates, jurisdiction pair by jurisdiction pair. Data residency rules and the payment services perimeter, raised under placement, accumulate on top. Each regime subtracts placements and structures from the feasible set, and the group’s regulatory footprint — the sum of those subtractions — is what removes positions that would otherwise be economic.

Systems landscape decides sequencing more often than strategy does. A group operating a dozen ERP instances cannot standardize processes by decree — the templates live in the systems, and consolidation of process is gated by consolidation or interfacing of platforms. Connectivity determines whether a payment factory is a routing project or a multi-year rebuild. The absence of a treasury management system caps cash visibility regardless of how concentrated the mandate is on paper. Where the build sequence stalls, the binding constraint is more often the system landscape than the organizational design.

Determinant profiles differ even between direct competitors — a different entity history, regulatory footprint, or ERP estate — which is why configurations transplant poorly. A model copied from a peer arrives without the determinant profile that made it economic, and the gap surfaces as exception queues and local workarounds rebuilding what the copied design removed.

The Operating Model in the Corporate Finance System

Downstream of the configuration, the operating model fixes the institutional form of every function it distributes. The treasury function shows the dependency at full scale. Its mandate — liquidity, funding, FX, banking relationships — is constant across groups, while its shape under one model is a single desk inside corporate finance, under another a treasury center with an in-house bank and regional satellites, under a third a coordination layer across local finance teams that each keep execution. The mandate defines what treasury does; the operating model decides what treasury is in a given group — headcount, location, system footprint, and the boundary between what it executes and what it oversees.

Authority structures inherit the same map. Delegated authority instruments name the units that hold each approval step, so a redistribution of work forces a redistribution of authority. When payment release moves into a factory, the authority matrix must grant the factory’s release rights and bound them, and segregation of duties changes its enforcement mechanism — duties separated within one local team become duties separated across units and time zones, verifiable only through system access design. Control placement, monitoring scope, and audit perimeters all trace the model’s work distribution, and each lag between a model change and its governance remap is an interval in which documented controls describe a flow of work that no longer exists.

The third dependency takes physical form in infrastructure. Account topology, bank connectivity, and the system landscape implement the model’s choices. An in-house bank exists as an internal account ledger and the administration around it, a payment factory as a format library and consolidated channels, a shared service center as common platform access across the entities it serves. Multi-entity infrastructure and the operating model constrain each other in both directions — the model dictates what the infrastructure must support, while the installed landscape gates which model movements are executable at all.

Upstream, the chain closes where it began. The operating model is bounded by the management model and entity topology above it, and bounds the functions, authority structures, and infrastructure below it — which is why two groups with identical entity charts and identical policies can run materially different finance operations. The difference is visible in artifacts. An authority matrix records where release rights actually sit. The bank account count shows how far external banking has centralized, and intercompany service agreements — with the transfer pricing files behind them — name which entity performs whose work. Read as a set, those records are the operating model.