TSA Exit Acceleration
Get the ledger off the seller's ERP on schedule.
Fixed-fee proposal in 48 hours. Senior team on day one. The first conversation is always free.
A TSA general ledger cutover is the moment Newco's books leave the seller's ERP and land on the buyer's own ledger, with a mapped chart of accounts and opening balances that reconcile to the sub ledgers. Get it right and every future close stands on solid ground. Get it wrong and the error compounds, which is why it belongs at the center of a planned TSA financial operations exit.
The general ledger is the spine of the finance function. Every sub ledger feeds it, every report draws from it, and every audit tests it. During the TSA the seller runs Newco's general ledger inside its own ERP, producing the trial balance, the close, and the statutory reporting. The cutover is the point at which that responsibility moves to the buyer's own ledger. It is not a data copy. It is the transfer of the financial system of record, and it has to happen without losing a single balance or breaking the audit trail.
What the cutover has to achieve is deceptively simple to state. The buyer needs a chart of accounts that fits Newco, opening balances that reconcile to the sub ledgers, comparative history sufficient for reporting and audit, and a clean line in time where responsibility passes. Each of those is a discrete piece of work, and each can derail the close if it is rushed or skipped. The cutover rewards sequencing and punishes shortcuts.
Because the ledger sits downstream of accounts payable, accounts receivable, fixed assets, and payroll, the cutover cannot be planned in isolation. The opening balances it carries are only as good as the sub ledger reconciliations that feed them. Sequencing the ledger cutover after the sub ledgers are clean, rather than alongside them, is the difference between a trial balance that ties out and one that does not.
The chart of accounts is the first decision and shapes everything after it. The seller's chart was designed for the seller's business, often with a granularity and structure that no longer fits a standalone Newco. The buyer can adopt the seller's chart wholesale, which is fast but imports complexity it does not need, or design a chart fit for the new business, which is cleaner but requires a mapping from old to new. Most carve-outs land in between, simplifying where they can while preserving the detail audit and tax require.
Whatever the choice, the mapping must be explicit and tested. Every account in the seller's ledger that carries a Newco balance needs a defined destination in the new chart, and the mapping must be applied consistently to both the opening balances and the comparative history. An incomplete or inconsistent mapping produces balances that land in the wrong account, distorting the financial statements from the first close. The mapping document becomes a control artifact, reviewed and signed off, not a spreadsheet someone keeps on a laptop.
The chart of accounts also drives the reporting hierarchy, the cost center structure, and the management reporting Newco will rely on after exit. The buyer designs these together rather than bolting reporting on afterward. A chart built only to satisfy the migration, without thought for how the business will be run and measured, forces a painful redesign within the first year. The interaction with master data and the close is developed in the TSA month end close coordination.
Opening balances are where the cutover succeeds or fails. The buyer carries forward the trial balance from the seller's ledger as the starting position in the new system, and that trial balance must reconcile to every sub ledger that feeds it. Accounts payable must tie to the open payables file, accounts receivable to the aged receivables, fixed assets to the asset register, and so on. A balance that does not reconcile at the cutover date is an error that every subsequent period inherits, and tracing it later is far harder than catching it at handover.
The control is a reconciled trial balance signed off by both parties at the cutover date. The buyer should not accept opening balances on trust. It reconciles each line to its supporting sub ledger, investigates every difference, and obtains the seller's agreement that the closing position in the old system equals the opening position in the new one. This sign off is the financial equivalent of the closing balance sheet in the deal, and it deserves the same rigor.
Fixed assets deserve particular attention because the register, the accumulated depreciation, and the ledger control account must all agree. A mismatch there flows into depreciation, tax, and the balance sheet for years. The detail of moving the asset register cleanly is covered in the TSA fixed-asset register migration, and the buyer should confirm it is reconciled before the ledger cutover relies on it.
The buyer must decide how much history to migrate and how much to archive. Migrating every historical journal into the new system is expensive and rarely necessary. The usual answer is to migrate opening balances and enough comparative history to run reporting and meet immediate audit needs, while archiving the deep transactional history in an accessible read only form. The key requirement is access. The buyer must be able to retrieve historical detail for audit, tax, and dispute purposes long after the seller's system is gone, which means the archive and the retention rights are part of the cutover plan, not an afterthought.
The audit trail must survive the boundary. An auditor needs to follow a balance from the new ledger back through the cutover into the seller's records and down to source documents. The buyer preserves the mapping, the reconciliations, and the sign off as the bridge across the cutover, so the chain of evidence is unbroken. A cutover that loses the trail leaves the first audit after exit with balances it cannot substantiate, which is a problem that surfaces at the worst possible time.
The cutover date itself should fall on a clean period boundary, almost always a month end or quarter end after a completed close. Cutting over mid period splits transactions across two systems and turns the reconciliation into a forensic exercise. Aligning the cutover with a closed period gives a stable trial balance to carry forward and a clean line where responsibility passes. This sequencing is part of accelerating the wider exit, which is the focus of the TSA Exit Acceleration service.
A ledger cutover is not done when the data loads. It is done when the first independent close runs clean. The buyer should run at least one close in the new ledger while the seller's system is still available as a fallback, comparing the result against what the old system would have produced. Differences are investigated and resolved before the seller's environment is switched off. This parallel close is the proof that the chart of accounts, the opening balances, and the reporting all work together under real conditions.
The buyer also confirms the downstream reporting before declaring victory. Statutory reporting, management reporting, consolidation into the portfolio, and any covenant reporting to lenders all draw on the ledger, and each must produce the expected numbers from the new system. A cutover that satisfies the accountants but breaks the lender report is not complete. The buyer tests the full reporting chain, because the ledger exists to feed it.
When the parallel close ties out, the reporting works, and the audit trail is intact, the buyer switches off the ledger service and retains the archive and access rights agreed in the TSA. A disciplined cutover gives Newco a financial system of record it owns and trusts, on schedule. A rushed one leaves a trial balance that never quite reconciles, a problem that quietly taxes every close for years until someone finally untangles it.
It is the point at which Newco's financial records move from the seller's ERP to the buyer's own ledger, with a mapped chart of accounts and validated opening balances. Before the cutover the seller runs the books under a TSA. After it, the buyer owns the close. The cutover must preserve a clean audit trail across the boundary.
Usually a mix. The buyer migrates opening balances and enough comparative history to run reporting and meet audit needs, and archives the deep transactional history in an accessible read only form. Migrating every historical journal into a new system is expensive and rarely necessary, but the buyer must retain access for audit, tax, and dispute purposes.
Opening balances that do not reconcile to the sub ledgers and a broken audit trail. If accounts payable, receivable, fixed assets, and the trial balance do not tie out at the cutover date, every period after it inherits the error. A reconciled trial balance signed off by both parties is the control that prevents it.
At a clean period boundary, almost always a month end or quarter end after a completed close. Cutting over mid period splits transactions across two systems and complicates reconciliation. Aligning the cutover with a closed period gives a stable trial balance to carry forward as opening balances.
The sub ledger that must reconcile before the general ledger relies on it.
Read the article →How the chart of accounts and master data feed the close across the cutover.
Read the article →The reconciled payables file that becomes an opening balance in the new ledger.
Read the article →The 90-day governance, IT, finance, HR and procurement separation plan we run on live carve-outs. Get the playbook plus the bi-weekly Day One Letter — short, signal-heavy, buyer-side.
No spam. Unsubscribe in one click. · Read the overview first →
Fixed-fee proposal in 48 hours. Senior team on day one. The first conversation is always free.
Seven buyer-side moves to exit a Transition Services Agreement on time and below budget. The mark-up, the extension-fee curve, exit sequencing, and the 11-month calendar.
One tactic, one benchmark, or one pattern from a recent buyer-side engagement. Short. Signal heavy. Free.
Subscribe to The Day One Letter →