Article map
Corporate transactions expose the limits of treasury visibility quickly. An acquired business may use unfamiliar banks, local portals, manual payment controls and account structures that are not documented centrally. A carve-out may depend on the seller’s cash pool, ERP, bank connectivity and signatories until transition services end. Rapid organic growth can create similar fragmentation as new entities and accounts are opened faster than governance expands.
Treasury’s immediate objective is not to force the target operating model on day one. It is to establish sufficient control to know where cash is, who can move it, which obligations are imminent and which dependencies could fail. Integration then proceeds in layers: stabilise, connect, reconcile, redesign and optimise.
This article provides a practical TMS playbook for maintaining decision-ready cash visibility while ownership, systems and banking relationships are changing.
1. Separate day-one control from target-state optimisation
The transaction plan should distinguish what must be known or controlled before legal close, what can operate temporarily under transition arrangements and what belongs in the future treasury model. Mixing these horizons creates unrealistic delivery plans and distracts from critical risk.
The operating boundary should define:
- day-one bank-account, balance, authority and critical-payment visibility
- transition-service dependencies for ERP, bank statements, payments, pooling and reporting
- legal-entity, currency and jurisdiction perimeter that changes at close
- target decisions on bank panels, pools, payment factories and internal funding
- exit dates, costs and operational risks for each temporary arrangement
A TMS integration register should track each requirement by horizon. This allows management to see whether day-one readiness is secure even when the full integration programme will continue for months.
2. Create the acquired or separated treasury inventory
The first information challenge is completeness. Data room lists may be outdated, and local teams may not know which accounts are linked to automated sweeps, guarantees, merchant acquiring, tax, payroll or customer instructions. Treasury should validate the inventory against bank evidence and system behaviour.
The governed data record should capture:
- bank accounts, signatories, digital users, balances and statement channels
- loans, facilities, guarantees, deposits, investments and derivative positions
- cash pools, sweeps, intercompany arrangements and restricted balances
- critical payment calendars, direct debits, collections and settlement accounts
- ERP ledgers, interfaces, file routes, credentials and transition-service owners
Unknowns should be recorded explicitly. An integration dashboard that shows ninety per cent confirmed coverage is more useful than a confident-looking list whose completeness has never been tested.
3. Establish a controlled opening position on day one
Treasury needs an opening cash position that can be reproduced and approved. Where automated connectivity is not yet available, controlled uploads or bank confirmations may be necessary, but the source, timestamp and reviewer must remain visible.
The end-to-end workflow should make visible:
- confirm account ownership and legal-close cut-off
- capture balances, pending payments and expected current-day flows
- identify cash subject to seller pools, blocked-account or transition arrangements
- reconcile the opening position to bank evidence and available ledger records
- approve the position and escalate stale, missing or unexplained accounts
Manual collection can be acceptable temporarily. Uncontrolled collection is not. The TMS should time-limit manual sources and track the plan to replace them with durable connectivity.
4. Secure authority and payment continuity
Changes in ownership create a high-risk period for bank access and payment authority. Former employees may retain entitlements, new signatories may not yet be active, and urgent payments may be routed through exceptional processes. Treasury should treat access and payment continuity as linked workstreams.
The control architecture should address:
- pre-close and post-close signatory and digital-access matrix
- verified emergency payment route with independent approval
- revocation of seller, former-employee and obsolete service-provider access
- dual control over changes to beneficiary and account instructions
- daily monitoring of rejected, delayed or unusual payments during the transition
A carve-out should not rely on informal access to the seller’s bank portal or credentials. Temporary services need documented authority, secure channels, end dates and contingency arrangements.
5. Use progressive connectivity rather than waiting for perfection
The integration architecture should support several data states at once. Strategic banks may connect through APIs or host-to-host, smaller accounts may use statements or secure uploads, and transition data may arrive from the seller. The TMS should normalise these sources into one governed view.
The TMS configuration should support:
- source-labelled ingestion for bank, seller, ERP and manual transition data
- canonical entity, account, currency and transaction mapping
- visible freshness, completeness and confidence indicators
- temporary mapping rules with owner and expiry date
- migration path to target bank and ERP connectivity
This approach allows treasury to make decisions before every interface is complete while preventing temporary workarounds from becoming invisible permanent architecture.
6. Measure integration risk and control convergence
Traditional project metrics such as tasks completed do not show whether treasury can operate safely. Management needs measures of account coverage, source freshness, payment readiness, transition dependency and control convergence.
Management reporting should measure:
- percentage of accounts and cash value visible within required time
- critical payment routes tested and signatories active
- open transition-service dependencies and days to exit
- accounts with confirmed ledger mapping and reconciliation
- manual data sources, temporary controls and overdue remediation
Progress should be weighted by materiality. Connecting ten small accounts does not offset a missing operating account that funds payroll or debt service.
7. Move through stabilise, connect, redesign and optimise
A practical integration sequence protects the business while creating a path to the target model. Each phase should have exit criteria rather than a vague expectation that maturity will improve over time.
The implementation plan should sequence:
- stabilise ownership, authority, critical payments and opening visibility
- connect material banks and ERPs while controlling temporary sources
- reconcile accounts, instruments and intercompany positions
- redesign account estate, pools, banking panel and payment operating model
- optimise cash concentration, forecasting, funding and reporting after control is stable
The programme should maintain a decision log for target-state choices. This prevents local exceptions, bank preferences or transition urgency from silently defining long-term architecture.
Management questions before approval
Before management approves cash visibility M&A treasury, the discussion should test the boundary described by separate day-one control from target-state optimisation, the reliability of bank accounts, signatories, digital users, balances and statement channels, and whether pre-close and post-close signatory and digital-access matrix remains effective when an exception occurs. It should also ask how percentage of accounts and cash value visible within required time will reveal whether the decision delivered its intended treasury result.
- Are day-one, transition and target-state requirements separated?
- Has the account and instrument inventory been validated against bank evidence?
- Is the legal-close opening position reproducible and approved?
- Are signatory and digital-access changes complete?
- Is an emergency payment route tested?
- Are temporary data sources labelled, controlled and time-limited?
The TMS record should connect those answers to establish a controlled opening position on day one and to the action 'stabilise ownership, authority, critical payments and opening visibility'. Where judgement changes the normal route for cash visibility M&A treasury, the evidence, approver, effective date and next review should remain visible beside source-labelled ingestion for bank, seller, ERP and manual transition data.
Evidence a controlled TMS should retain
The operating record for cash visibility through mergers, carve-outs and rapid growth should show how bank accounts, signatories, digital users, balances and statement channels became an approved action under secure authority and payment continuity. It should retain source identity, calculation or transformation, workflow status, exception treatment and approval, together with the downstream result represented by source-labelled ingestion for bank, seller, ERP and manual transition data.
- pre-close and post-close signatory and digital-access matrix
- verified emergency payment route with independent approval
- revocation of seller, former-employee and obsolete service-provider access
- source-labelled ingestion for bank, seller, ERP and manual transition data
- canonical entity, account, currency and transaction mapping
- visible freshness, completeness and confidence indicators
Version history for bank accounts, signatories, digital users, balances and statement channels should preserve the information used when the decision was taken, even if later correction changes the current view. Comparing that history with percentage of accounts and cash value visible within required time and the practical outcome in 'a carve-out with forty-five days to replace seller connectivity' allows management to evaluate process discipline and decision quality without hindsight rewriting.
Practical illustration: a carve-out with forty-five days to replace seller connectivity
A business being separated from a conglomerate uses the seller’s ERP and bank connectivity under a forty-five-day transition service. It has fourteen bank accounts across six countries, but only nine appear in the data-room inventory. Treasury validates statements and discovers three collection accounts and two guarantee-related accounts that local finance had treated as operational details.
For day one, balances are ingested through controlled seller files and independently confirmed for material accounts. New signatories and an emergency payment route are tested before close. During the next four weeks, the TMS connects strategic banks, maps the new ERP chart and retires temporary sources account by account.
The carve-out exits the transition service with complete cash coverage and no payment interruption because the plan prioritised control and evidence before optimisation.
Implementation checklist
A treasury team preparing to operationalise this topic should be able to answer yes to the following questions:
- Are day-one, transition and target-state requirements separated?
- Has the account and instrument inventory been validated against bank evidence?
- Is the legal-close opening position reproducible and approved?
- Are signatory and digital-access changes complete?
- Is an emergency payment route tested?
- Are temporary data sources labelled, controlled and time-limited?
- Can management see missing and stale account coverage?
- Are transition dependencies tied to exit dates?
- Are ledger mappings and reconciliations progressing by materiality?
- Is the target operating model protected from temporary workarounds?
Common design failures
Transaction pressure encourages shortcuts that can become structural weaknesses if they are not made visible and retired.
- waiting for target connectivity before creating any consolidated position
- trusting data-room inventories without bank validation
- treating signatory change as an administrative task separate from payment continuity
- sharing credentials or relying on informal seller access
- allowing temporary manual files to continue without owner or expiry
- optimising pools and accounts before ownership and reconciliation are stable
The strongest integration programmes are realistic about temporary controls but uncompromising about their ownership, evidence and retirement.
Closing perspective
Mergers, carve-outs and rapid growth make treasury fragmentation visible. The response should not be a rushed attempt to standardise everything immediately, but a controlled sequence that secures authority, opening cash, payment continuity, data coverage and reconciliation.
A TMS can hold that sequence together by making sources, gaps, dependencies, temporary controls and target-state decisions visible. It gives treasury a stable operating record while the organisation around it changes.
Frequently asked questions
What should treasury prioritise on acquisition day one?
Treasury should prioritise complete material-account visibility, authority over bank access, critical payment continuity, known liquidity obligations, restricted-cash identification and a reproducible opening position.
Can manual bank data be used during a carve-out?
Yes, where automation is not yet available, but the source should be secure, timestamped, independently reviewed, reconciled and subject to a clear replacement date.
How does a TMS help post-merger integration?
A TMS can consolidate heterogeneous bank data, track integration dependencies, control temporary processes, manage access and account lifecycle, reconcile positions and support the move to a common treasury model.