Xero can accept organisation settings, account lists, conversion balances, open receivables and payables, bank accounts, statement lines, contacts, and historical transactions through several routes. That flexibility is useful, but it creates a sequencing problem: two individually reasonable imports can represent the same accounting event twice. A controlled implementation therefore starts with an evidence boundary that identifies what remains authoritative in the legacy system and what Xero will own from the conversion date forward.
The most important date is not the day users receive access. Xero defines the conversion date as the date of the opening account balances and normally the start of live use. A business moving from another system should balance the old books through the day before that date, export the final trial balance and subsidiary schedules, and retain the closing bank statements. Pre-conversion invoices and bills may still need to exist in Xero so that the receivable and payable control balances have real open items behind them.
This implementation sequence is designed for a CPA or financial team that must explain the result later. It distinguishes system accounts from ordinary accounts, bank conversion balances from new-account opening transactions, imported statement lines from Xero account transactions, and a visually clean dashboard from an accepted first close. The deliverable is not merely a configured organisation; it is a traceable starting ledger with named owners, exceptions, and rollback evidence.
Key decisions at a glance
- Set Xero's conversion date only after the prior system is balanced through the preceding day and the team has frozen a signed source package.
- Treat chart import and conversion-balance import as one controlled design because a balance-bearing chart file can overwrite balances already entered in Xero.
- Support Accounts Receivable and Accounts Payable conversion balances with the actual unpaid invoices, bills, credits, overpayments, and prepayments that compose them.
- Prevent duplicate bank history by defining one boundary across imported statements, imported transactions, opening or conversion balances, and the bank feed start.
Freeze the Organisation, Conversion Date, and Source Boundary
Begin with an organisation decision record covering legal identity, base currency, financial year end, tax basis and rates, reporting method, invoice settings, and the intended Xero subscription. The accountant should resolve any jurisdiction-specific treatment before data entry begins. Record the Xero subscriber, implementation owner, source-system owner, and acceptance approver separately so a subscription or access change cannot silently redefine the accounting design.
Select the conversion date after the legacy ledger is balanced, not because it is a convenient training date. Xero's current guidance describes the conversion date as the date of the opening balances and says it is the day after the date through which the previous system was balanced. Export a final trial balance dated the preceding day, aged receivables and payables, tax and payroll schedules where applicable, fixed-asset and loan schedules, inventory evidence, and closing statements for every bank and card account. Hash or otherwise version the source package so later extracts cannot be mistaken for the approved close.
Decide explicitly how much history belongs in Xero. A conversion-balance approach brings a reliable opening position and open items; a detailed-history approach adds transactional comparison but requires more mapping, validation, and reconciliation. Do not let users continue posting in both systems after the boundary. If late legacy entries are unavoidable, capture them in a controlled exception register, decide which system records the correction, and refresh all dependent balances together rather than patching a single account in isolation.
- Approve the legal organisation, base currency, financial year, tax configuration, reporting basis, subscription, and subscriber before importing data.
- Fix the conversion date and document the final legacy posting cutoff, including who can authorise a late source-system entry.
- Export the prior-day trial balance plus subsidiary ledgers, bank statements, tax schedules, loans, fixed assets, inventory, and outstanding-item evidence.
- Classify each dataset as conversion balance, open item, detailed history, reference-only archive, or intentionally excluded material.
- Define rollback, exception ownership, reconciliation tolerances, and acceptance signatures before the first production import.
Design the Chart and Conversion Balances as One System
Choose between Xero's default chart and a mapped import based on reporting needs, not nostalgia for the legacy codes. Xero expects unique account codes and names, uses tracking rather than legacy subaccounts in many designs, and reserves system accounts for functions such as Accounts Receivable and Accounts Payable. Locked or system accounts cannot be treated like ordinary imported rows. Map source accounts to valid Xero types and tax rates, identify consolidations and splits, and rehearse the file in a non-production organisation or controlled test cycle.
A chart import can have wider effects than its filename suggests. Current Xero guidance says accounts omitted from an update file may be archived or deleted, locked accounts may resist code changes, and a file containing balances imports those amounts as conversion balances and overwrites existing conversion balances. Changing an account code and name together can create a new account instead of updating the intended one. Preserve the exported pre-import chart, review the Import Summary, and stop when the counts of new, updated, system, excluded, archived, or errored accounts differ from the approved mapping.
Balance proof must respect Xero's accounting model. Conversion balances come from the prior-day trial balance, while a pre-existing bank account's conversion balance should come from the closing bank statement because the ledger balance may include unpresented items. Accounts Receivable and Accounts Payable need the unpaid invoices, bills, credit notes, overpayments, and prepayments that make up those control totals. If a conversion file is out of balance, a historical adjustment can conceal the mapping problem; treat that adjustment as an exception to clear, not a convenient completion technique.
- Map every source code to a Xero account type, tax rate, report purpose, status, and owner; flag system and locked accounts before import.
- Keep unchanged existing accounts in the chart file when the chosen import route would otherwise archive accounts omitted from the file.
- Leave the Balance column blank unless the approved operation is specifically intended to replace Xero conversion balances.
- Tie receivable and payable controls to entered or imported open documents, and isolate temporary holding accounts with a dated clearance plan.
- Run an imported-account summary and trial balance after each staged file; never approve a historical adjustment without explaining its source.
Stage Bank Accounts, Statement History, and Feed Start Dates
Create each Xero bank or credit-card account from an approved inventory containing masked identifiers, currency, ownership, statement cadence, and the source account code. For accounts that existed before the organisation's conversion date, enter a bank conversion balance from the closing statement on the preceding day. For an account opened after conversion, Xero uses an opening transaction such as a transfer or receive-money entry, followed by reconciliation. Those are different accounting cases and should not be mixed.
Draw one timeline for every account. Mark the last statement line represented in the converted history, the first statement line Xero should receive, the feed activation date, any manually imported gap, and any account transactions created by a conversion tool. Xero's Conversion Toolbox can import bank transactions as spend or receive money transactions and can optionally mark them reconciled, which creates statement lines. A later feed or statement import covering the same dates can therefore duplicate the banking layer even when the general ledger appears plausible.
Connect feeds using the authorised account owner and keep real banking credentials outside the implementation record. Imported statement lines belong on the bank side of Xero reconciliation; invoices, bills, transfers, payments, and spend or receive money entries belong on the accounting side. During the pilot, match existing items first, create only genuinely missing transactions, test transfers across both accounts, and hold ambiguous deposits, fees, processor settlements, and owner activity for evidence. A bank rule should be treated as a suggestion generator that a reviewer accepts, edits, or declines.
- Document the masked bank account, currency, prior-day statement balance, conversion treatment, feed owner, and reviewer for every account.
- Choose a single non-overlapping history path for each date range: converted account transactions, imported statement lines, or live feed data.
- Reconcile a controlled sample containing an invoice payment, bill payment, transfer, fee, deposit, and genuinely new cash transaction.
- Compare the Xero Statement Balance, Balance in Xero, source statement, and outstanding items instead of relying on the dashboard alone.
- Pause production when duplicate statement lines, unexplained user-created lines, missing feed dates, or account-number mapping uncertainty appears.
Prove the First Close Before Releasing the Organisation
The first-close test should reproduce the approved opening position and one complete operating cycle. Run the trial balance at conversion, balance sheet, profit and loss, aged receivables, aged payables, account transactions for sensitive ledgers, and the bank reconciliation report pack. Trace a sample from each subsidiary source through the Xero transaction and financial statement. Confirm that open invoices and bills equal their control accounts, retained earnings and equity are intentional, tax and multicurrency treatments are reviewed, and every temporary holding balance has an owner.
Bank acceptance is evidence-driven. The Bank Reconciliation Summary distinguishes Balance in Xero, outstanding payments and receipts, unreconciled statement lines, calculated statement balance, imported statement balance, and a user-entered statement ending balance. A zero-looking difference on one screen is not enough if a future-dated match, deleted line, duplicate import, or manual mark-as-reconciled entry changes a different report. Preserve the report pack, statement extract, reconciliation details, and exception disposition at the same cut-off date.
Release normal processing only after owners sign the configuration, mapping, source totals, open-item proof, bank reconciliations, role assignments, and unresolved-risk list. Then set appropriate Xero lock dates through an advisor-authorised process. Locking protects the accepted period but does not replace monitoring: schedule checks for feed continuity, new connected apps, chart changes, historical adjustments, unreconciled lines, and balance drift. A controlled implementation ends with repeatable close procedures and support ownership, not with the import confirmation message.
- Match the Xero conversion-date trial balance to the signed legacy trial balance account by account and document every mapped difference.
- Reconcile aged receivables and payables to their system control accounts and verify that each open item is collectible, payable, or deliberately disputed.
- Run the bank reconciliation report pack at a fixed date and retain the Summary, Bank Statement, Statement Exceptions, and supporting statements.
- Clear or formally approve historical adjustments, conversion holding accounts, duplicate lines, feed gaps, tax exceptions, and unexplained equity.
- Obtain implementation, accounting, security, and business-owner acceptance before setting lock dates and retiring source-system posting access.
Vendor documentation and ALLMSP resources
- Xero Central: Start using Xero
- Xero Central: Setting your conversion date
- Xero Central: Import a chart of accounts
- Xero Central: Import a chart of accounts using the Conversion Toolbox
- Xero Central: Enter conversion balances
- Xero Central: The accounting behind Xero conversion balances
- Xero Central: Enter opening bank account balances
- Xero Central: Import bank transactions using the Conversion Toolbox
- Xero Central: Bank reconciliation in Xero
- ALLMSP: Xero software support category
- ALLMSP: Software support
- ALLMSP: Cloud computing and migrations
- ALLMSP: Managed IT
- ALLMSP: CPA and financial firms
Frequently Asked Questions
What should be fixed before a Xero conversion starts?
Approve the organisation settings, subscription, subscriber, base currency, financial year, tax configuration, conversion date, source-system cutoff, history scope, account mapping, and acceptance owners. Export the prior-day trial balance and supporting schedules before importing anything. That package becomes the evidence baseline for every conversion balance and exception.
How should the Xero conversion date be selected?
Use the date of the organisation's opening conversion balances, normally the first day Xero owns live accounting. Balance the prior system through the preceding day and run the trial balance to that cutoff. Avoid choosing a training or feed-connection date that does not correspond to a completed accounting boundary.
Can a Xero chart-of-accounts import change existing accounts?
Yes. Xero can update existing accounts, archive or delete omitted accounts depending on the import route, reject invalid rows, preserve restrictions on locked accounts, or create a new account when identifying fields change. Review the Import Summary and a post-import chart export against the approved source-to-target mapping before continuing.
Does importing a chart of accounts also import conversion balances?
It can. If the chart file includes a mapped balance column, Xero treats those values as conversion balances and can overwrite balances already present in the organisation. Leave the column blank unless that replacement is intentional, then re-run the trial balance and open-item proof immediately after the import.
How are Accounts Receivable and Accounts Payable conversion balances supported in Xero?
Enter or import the unpaid invoices, bills, credit notes, overpayments, and prepayments that compose the control totals. Their outstanding values must agree with the receivable and payable conversion balances. Temporary holding accounts need a documented clearance sequence; they should not survive the accepted conversion without an explicit reason.
Should a bank conversion balance come from the trial balance or bank statement?
For a pre-existing bank account, Xero's guidance points to the closing bank statement for the day before conversion, because a trial-balance amount can include unpresented checks or deposits not yet reflected by the bank. Reconcile those outstanding differences rather than forcing the statement balance to equal the ledger.
How do duplicate bank records arise during a Xero implementation?
Overlap is the usual cause. A conversion tool may create account transactions and statement lines, a manual statement file may cover the same dates, and a new feed may download them again. Document the last converted line and first feed line for each account, then inspect the Statement Exceptions report.
What should a Xero implementation pilot reconcile?
Use representative invoice and bill payments, a transfer, a fee, a deposit, a new cash transaction, an outstanding item, and at least one ambiguous line sent for review. The pilot should prove matching, creation, bank-rule review, statement and ledger balances, error handling, evidence retention, and owner sign-off.
When should lock dates be set after a Xero conversion?
Set them after the conversion trial balance, open-item controls, bank report pack, and exceptions are approved. Xero requires an advisor role to set or change lock dates. Preserve the accepted reports first, record the chosen scope, and define a controlled process for any later historical correction.
When should an accountant lead a Xero implementation decision?
Escalate decisions involving conversion date, tax treatment, system accounts, receivable or payable controls, retained earnings, multicurrency, historical adjustments, opening bank balances, lock dates, or a prior-period correction. These choices affect the ledger and financial statements, so software convenience alone is not an adequate basis.
