Integrating Two Treasury Functions: 8 Best Practices for Consolidating Cash Management and Banking Relationships After a Merger

Few areas of post-merger integration carry as much quiet consequence as treasury. It rarely commands the headline attention that brand consolidation or workforce restructuring attracts, yet treasury integration touches every artery of a combined organization’s financial life: how cash moves, where it rests, who can access it, and how risk is managed across borders and currencies. Get it right and you unlock liquidity synergies, reduce banking costs, and give leadership a consolidated view of the combined entity’s financial position within weeks of close. Get it wrong—or neglect it entirely—and you may spend the next eighteen months reconciling phantom balances, paying duplicate bank fees, and watching two finance teams operate in parallel with no shared visibility.

For seasoned M&A professionals, treasury integration sits in a peculiar middle zone. It is neither as operationally complex as full ERP consolidation nor as straightforward as merging a travel policy. It demands technical fluency in cash management, banking infrastructure, and payment systems, but it also requires the diplomatic skill to manage bank relationships that may stretch back decades. It is, in short, one of those integration workstreams that rewards rigorous planning and punishes improvisation.

This article examines the core dimensions of treasury integration in a post-merger context, explains why the timing and sequencing matter, and presents eight best practices for consolidating cash management and banking relationships. Along the way, it addresses the practical question every deal team eventually asks: do we need to integrate treasury on Day 1, or can it wait?

The answer, like most things in M&A, is “it depends”—but the variables that determine the answer are knowable, and the frameworks for managing them are well established.

The Role of Treasury in a Modern Organization

Before examining how to merge two treasury functions, it helps to ground the discussion in what treasury actually does. In mid-size and large organizations, the treasury function typically manages a broad set of responsibilities that span operational finance, risk management, and strategic capital planning.

Cash and liquidity management sits at the core. Treasury ensures the organization has sufficient cash in the right accounts, in the right currencies, at the right times to meet obligations. This includes daily cash positioning, short-term forecasting, and managing intercompany funding flows. In multinational organizations, this responsibility extends to cross-border pooling structures, notional or physical, that concentrate liquidity and minimize idle balances.

Banking relationship management is the second pillar. Treasury selects, negotiates with, and oversees the organization’s banking partners. This covers everything from the number and type of bank accounts to the fee structures, service-level agreements, and connectivity protocols (SWIFT, host-to-host, API-based) that link the company’s systems to its banks.

Payments and collections represent the transactional engine. Treasury designs and governs how the organization sends and receives money—wire transfers, ACH, direct debits, checks (still, remarkably), and increasingly real-time payment rails. Payment factory models and shared service centers often fall under treasury’s oversight.

Debt and capital markets activity covers borrowing, investment of surplus cash, and management of the organization’s capital structure. Treasury teams manage revolving credit facilities, commercial paper programs, term loans, and relationships with credit rating agencies.

Financial risk management rounds out the portfolio. Treasury typically owns the hedging programs for foreign exchange, interest rate, and in some sectors commodity price risk. This involves policy design, counterparty management, and execution of derivative instruments.

When two organizations merge, each of these functions must be examined, compared, and ultimately unified—or deliberately kept separate with clear governance. The scope of that effort depends on the relative size and complexity of the two entities, the degree of geographic overlap, and the strategic intent behind the deal.

Day 1, Day 30, or Day 180: When Should Treasury Integration Begin?

One of the most common misconceptions in post-merger planning is that treasury integration is a Day 1 imperative across all dimensions. In practice, the reality is more nuanced.

Certain treasury activities are required on or before Day 1. These include establishing legal authority over the acquired entity’s bank accounts (signatory changes, board resolutions), ensuring the acquiring company can fund the target’s payroll and critical vendor payments, and confirming that intercompany loan agreements are in place to move cash between legacy entities. Regulatory requirements—particularly in financial services or in jurisdictions with strict foreign exchange controls—may add further Day 1 obligations. If the deal involves a change-of-control clause in the target’s credit facilities, treasury must also manage the refinancing or waiver process before close.

Beyond these non-negotiables, most elements of treasury integration are recommended within the first 90 to 180 days but are not operationally required on Day 1. Rationalizing bank accounts, migrating to a single treasury management system (TMS), consolidating cash pools, and renegotiating banking agreements all benefit from deliberate planning rather than rushed execution. Attempting to merge two complex banking structures overnight introduces operational risk that experienced treasury professionals rightly avoid.

Some elements may even remain optional or deferred for a year or longer, particularly when the acquirer intends to operate the target as a semi-autonomous business unit or when regulatory constraints (such as ring-fencing requirements in banking) prevent full consolidation. In cross-border deals involving countries with capital controls—think Brazil, China, India, or South Africa—full cash management integration may require regulatory approvals that extend well beyond the first year.

The guiding principle is straightforward: secure control and visibility on Day 1, pursue consolidation in a phased and risk-managed sequence over the following months, and accept that full optimization may take a year or more.

The Benefits of Integration—and the Case for Keeping Functions Separate

The financial and operational benefits of consolidating two treasury functions are well documented and can be substantial.

Improved liquidity visibility is typically the most immediate gain. A single, consolidated view of global cash positions enables better investment of surplus funds and more efficient internal funding, reducing reliance on external borrowing. For organizations with significant cash balances, even modest improvements in yield on consolidated positions can translate to meaningful annual savings.

Reduced banking costs follow naturally from account rationalization. Most acquired companies carry more bank accounts than they need, often accumulated through their own prior acquisitions. Consolidating accounts reduces maintenance fees, simplifies bank fee analysis, and strengthens the organization’s negotiating position with fewer, more strategically important banking partners.

Operational efficiency improves as duplicate systems, processes, and controls are eliminated. Running two treasury management systems, two payment platforms, and two sets of bank connectivity infrastructure is expensive and introduces reconciliation complexity that nobody enjoys.

Enhanced risk management results from unified hedging programs, consolidated counterparty exposure monitoring, and standardized policies. Two separate treasury teams may hedge the same currency pair in opposite directions—an expensive form of internal inefficiency that integration eliminates.

Stronger governance and controls emerge when a single policy framework, a single approval matrix, and a single set of SOX or equivalent controls govern the combined entity’s treasury operations. This reduces audit findings and strengthens the organization’s overall control environment.

Despite these benefits, there are legitimate reasons to maintain separate treasury functions, at least temporarily. If the acquired entity operates in a highly regulated industry with distinct capital or liquidity requirements, forced consolidation may create more compliance risk than it eliminates. If the deal thesis depends on preserving the target’s operational autonomy—common in private equity platform strategies or conglomerate models—treasury independence may support that objective. And if the two entities operate in entirely different geographies with minimal currency or banking overlap, the integration effort may yield limited synergies relative to its cost and disruption.

The decision should be driven by a clear-eyed assessment of synergy potential, integration cost, operational risk, and strategic intent—not by a reflexive assumption that consolidation is always superior.

Key Terms and Current Trends Shaping Treasury Integration

Several developments in the treasury landscape are reshaping how integration teams approach post-merger consolidation. Understanding these trends is essential context for the best practices that follow.

Treasury Management Systems (TMS) are the central technology platforms treasury teams use to manage cash positioning, forecasting, payments, debt, and risk. Leading platforms include Kyriba, ION (formerly Wallstreet Suite and IT2), FIS, and SAP’s treasury module. Integration decisions often hinge on which TMS the combined entity will adopt and how quickly migration can be completed.

SWIFT connectivity and bank communication protocols govern how treasury systems talk to banks. The trend toward API-based connectivity and SWIFT’s gpi (global payments innovation) standard is creating more real-time, data-rich connections that can accelerate post-merger bank onboarding. However, migrating bank connectivity remains one of the most time-consuming elements of treasury integration, particularly when the target relies on proprietary bank portals rather than standardized messaging.

Cash pooling structures—both physical (where balances are physically concentrated into a header account) and notional (where balances are offset for interest purposes without physical movement)—are central to multinational liquidity management. Integrating two pooling structures requires careful analysis of legal entity hierarchies, intercompany agreements, tax implications, and banking partner capabilities.

Real-time payments and instant liquidity are becoming standard in many markets, altering the economics of cash concentration and the frequency of cash positioning. Integration teams must now consider whether the combined entity’s banking infrastructure supports real-time rails and whether treasury processes can absorb the speed.

Bank relationship rationalization is a perennial post-merger priority, but the current environment adds complexity. Banks are increasingly selective about the clients they serve and the products they offer, driven by their own capital and compliance costs. Choosing which banking relationships to retain, expand, or exit requires understanding not just price but strategic value, geographic coverage, and product capability.

ESG and sustainable finance considerations are beginning to influence treasury decisions, including green bond issuance, sustainability-linked revolving credit facilities, and ESG-related reporting. When integrating two treasury functions, alignment on sustainable finance commitments and frameworks deserves early attention.

With this foundation in place, we can turn to the practical frameworks for executing treasury integration effectively.

8 Best Practices for Consolidating Cash Management and Banking Relationships

1. Conduct a Comprehensive Treasury Discovery Before Close

Effective treasury integration starts well before Day 1. During due diligence or, at minimum, during the pre-close planning phase, the integration team should build a complete inventory of the target’s treasury landscape. This inventory should cover bank accounts (by entity, country, currency, and purpose), banking partners, cash pooling structures, TMS and payment platforms, intercompany loan agreements, hedging programs, credit facilities, and guarantees.

This discovery effort often reveals surprises. Companies that have grown through their own acquisitions may carry dozens or even hundreds of dormant bank accounts, legacy banking relationships with no clear owner, and hedging positions that were never rationalized. The earlier these are identified, the more effectively the integration team can plan the consolidation sequence and estimate the effort required.

The discovery should also map the target’s treasury policies and controls, including signatory authorities, payment approval limits, and segregation of duties. Gaps between the acquirer’s and target’s control environments must be identified early, as they often represent both a risk and a quick-win opportunity for standardization.

2. Establish a Clear Treasury Integration Governance Model

Treasury integration involves legal, tax, IT, operations, and compliance stakeholders in addition to treasury itself. Without a clear governance model, decisions stall, workstreams conflict, and critical dependencies are missed.

Best practice is to appoint a dedicated treasury integration lead—ideally someone with deep treasury operational experience and credibility with both legacy organizations—who reports into the overall integration management office (IMO). This lead should manage a cross-functional working group with defined decision rights, escalation paths, and reporting cadences.

The governance model should also establish clear ownership of bank relationship decisions. In many integrations, both legacy treasury teams have strong opinions about which banks to retain, often influenced by long-standing personal relationships. A structured evaluation framework (see Practice 5) depersonalizes these decisions and anchors them in strategic criteria.

3. Prioritize Day 1 Readiness Over Day 1 Perfection

As discussed earlier, the Day 1 treasury checklist should focus on control, compliance, and continuity rather than optimization. The integration team should ensure the following are in place at close: legal authority over the target’s bank accounts, the ability to fund the target’s critical payment obligations, compliance with change-of-control provisions in credit agreements, visibility into the target’s daily cash positions (even if initially manual), and a clear intercompany funding mechanism.

Pursuing full account rationalization, TMS migration, or cash pool restructuring on Day 1 introduces unnecessary operational risk. Payroll failures, missed vendor payments, and disrupted customer collections are integration wounds that are difficult to heal. A phased approach that secures the essentials on Day 1 and sequences optimization over the following months protects the combined entity’s operational stability while preserving the momentum toward full integration.

4. Map the Combined Banking Landscape Before Making Cuts

One of the most common pitfalls in treasury integration is premature bank rationalization. The instinct to reduce the number of banking partners is sound—fewer banks generally mean lower costs, simpler administration, and stronger relationships—but executing cuts without a comprehensive map of the combined banking landscape creates risk.

The integration team should build a matrix that maps every banking relationship across both legacy entities by geography, product, and volume. This matrix should capture transactional banking (payments, collections, accounts), liquidity management (cash pooling, money market investments), trade finance, foreign exchange, credit facilities, and ancillary services such as merchant acquiring or escrow.

Only with this complete picture can the team make informed decisions about which relationships to retain, consolidate, or exit. In some cases, a banking partner that appears redundant based on account count may provide critical product capabilities in a specific geography or serve as the sole provider of a regulatory-required service.

5. Evaluate Banking Partners Using a Structured Scorecard

Deciding which banking relationships to keep and which to wind down is one of the most consequential decisions in treasury integration. A structured scorecard approach ensures these decisions are transparent, defensible, and aligned to the combined entity’s strategic priorities.

Effective scorecards typically evaluate banking partners across several dimensions: geographic coverage and alignment with the combined entity’s footprint, product breadth and depth, pricing competitiveness, technology and connectivity capabilities, credit appetite and willingness to support the combined entity’s borrowing needs, service quality and responsiveness, and strategic relationship value (including the bank’s sector expertise and willingness to invest in the relationship).

Weighting these dimensions according to the combined entity’s priorities—and scoring each bank against them—produces a rational basis for the rationalization plan. This approach also provides a defensible narrative for banks that are being exited, which matters because maintaining goodwill with departing banks preserves optionality for future needs.

6. Consolidate Cash Pools and Liquidity Structures Methodically

Cash pool integration is one of the most technically complex elements of treasury consolidation, and it deserves its own workstream with dedicated resources.

The first step is to decide on the target-state liquidity architecture for the combined entity. This involves determining whether to use physical or notional pooling (or both), selecting the pooling currencies and header account locations, and choosing the banking partner or partners that will host the structure. Tax considerations are paramount here, as intercompany cash movements create transfer pricing implications, and the location of header accounts can affect withholding tax obligations on intercompany interest.

The second step is to design the migration path from the current-state structures to the target state. This migration must account for legal entity hierarchies, local regulatory constraints (some jurisdictions prohibit or restrict cross-border pooling), bank account opening and closing timelines, and system connectivity requirements. In complex multinational integrations, this migration may proceed region by region over six to twelve months.

The third step is to ensure that intercompany agreements, board resolutions, and regulatory filings support the new structure. Treasury teams sometimes design elegant pooling architectures only to discover that the legal documentation lags months behind, creating compliance exposure.

7. Align Treasury Technology Early, Even if Migration Takes Time

The question of which TMS will serve the combined entity should be answered as early as possible, even if the actual migration takes months or longer. Early alignment on the target-state technology architecture allows the integration team to design processes, configure bank connectivity, and train users in parallel with other workstreams.

In practice, most acquirers adopt one of three approaches: retain the acquirer’s TMS and migrate the target onto it, retain the target’s TMS if it is demonstrably superior, or select a new platform that better fits the combined entity’s needs. The third option is the most disruptive and is typically reserved for situations where neither legacy platform is fit for purpose.

Regardless of the approach, the integration team should avoid the temptation to customize the chosen platform extensively during migration. Post-merger TMS implementations that attempt to replicate every legacy process and report on Day 1 often become multi-year projects that drain resources and delay the realization of integration benefits. A standardized configuration that covers core requirements, with enhancements phased over subsequent quarters, delivers value faster and with less risk.

8. Communicate Proactively with Banks, Regulators, and Internal Stakeholders

Treasury integration is fundamentally a relationship management exercise as much as it is a technical one. Banks, regulators, and internal stakeholders all have legitimate interests in how the consolidated treasury function will operate, and all respond better to proactive communication than to surprises.

Banking partners should be informed early about the integration plan, including the timeline for account rationalization, the combined entity’s expectations for service and pricing, and the strategic role each bank will play going forward. Banks that understand their position in the post-merger landscape can allocate resources accordingly and are more likely to provide the support the integration team needs during the transition.

Regulators in jurisdictions with capital controls, banking license requirements, or foreign exchange restrictions may require formal notifications or approvals before treasury structures can be changed. Engaging with these regulators early—ideally during the pre-close planning phase—prevents delays that can hold up the entire integration timeline.

Internal stakeholders, including business unit finance teams, shared service centers, and the broader integration management office, need clear communication about how treasury changes will affect their daily operations. Payment process changes, new bank account details for intercompany settlements, and revised approval authorities all require advance notice and, in many cases, training.

Common Pitfalls in Treasury Integration

Even well-planned treasury integrations encounter predictable obstacles. Awareness of these pitfalls allows integration teams to build mitigation strategies into their plans from the outset.

Underestimating account closure timelines is among the most frequent frustrations. Closing a bank account in some jurisdictions can take three to six months, particularly when regulatory approvals, tax clearances, or outstanding payment instruments are involved. Integration plans that assume rapid account closure often fall behind schedule.

Ignoring tax and transfer pricing implications of cash pooling and intercompany funding arrangements can create significant financial exposure. Treasury integration decisions that make operational sense may create adverse tax outcomes if not reviewed by tax counsel.

Overlooking the human dimension is a subtler but equally damaging pitfall. Treasury teams at the acquired company often include deeply experienced professionals with institutional knowledge that cannot be replaced by a system migration. Retaining key talent through the integration period—and making clear their role in the combined organization—is essential for continuity.

Treating treasury integration as an IT project rather than a business transformation effort leads to technology-centric plans that neglect process design, policy alignment, and organizational change management. The TMS migration is a means to an end, not the end itself.

Failing to capture and report synergies undermines the business case for integration. Treasury synergies—reduced bank fees, lower borrowing costs, improved investment returns, and headcount efficiencies—should be tracked and reported to leadership with the same rigor applied to revenue and cost synergies in other workstreams.

Conclusion

Integrating two treasury functions after a merger is neither a trivial administrative exercise nor an insurmountable technical challenge. It is a complex, multi-dimensional workstream that rewards early planning, structured decision-making, and disciplined execution. The eight best practices outlined here—comprehensive discovery, clear governance, phased Day 1 readiness, complete banking landscape mapping, structured partner evaluation, methodical cash pool consolidation, early technology alignment, and proactive communication—provide a framework that scales across deal sizes, industries, and geographies.

The organizations that execute treasury integration well tend to share a common trait: they treat treasury not as a back-office function to be merged after the more visible integration workstreams are underway, but as a strategic enabler of the combined entity’s financial performance from Day 1. They recognize that cash is the lifeblood of any business, and that the infrastructure governing its movement deserves the same rigor and executive attention as commercial integration or operational restructuring.

The payoff for getting this right is tangible: lower costs, better visibility, stronger controls, and a unified financial infrastructure that supports the combined organization’s growth objectives. The cost of getting it wrong is equally tangible, measured in missed synergies, operational disruptions, and the slow erosion of confidence that comes when leadership cannot answer the simple question, “How much cash do we have, and where is it?”

As treasury technology evolves, real-time payment networks expand, and regulatory environments grow more complex, the bar for post-merger treasury integration will only rise. What lesson from your own experience with treasury integration—successful or otherwise—would you add to this framework?