Software and switching

Converting a register without losing history

Load prior depreciation as filed, run the new system beside the old for a period, and reconcile to the last return. Nothing is recomputed silently.

Figure 1. Illustrative screen with sample data: the field map for a Sage Fixed Assets file, validated before anything is written.

Published 10 February 2026; last checked 20 September 2026. Applies to: Conversions from any fixed-asset system or spreadsheet. Authority: The company's conversion method since 1990; AU-C section 500. Written by Fixed Assets Desk Inc., Sachse, Texas. General description of federal rules; not tax advice for a particular taxpayer.

A register conversion is safe when the last closed year is run in the new system and reconciled, account by account and book by book, to the figures the old system filed, with every difference explained and decided before go-live. Prior depreciation is loaded as filed, never recomputed.

The fear is losing history; the cure is a parallel run.

People stay on software they dislike because the register holds thirty years of decisions, prior depreciation as filed, elections, disposals, and a conversion that recomputes any of it silently produces a schedule that does not match the return. The method that removes the fear is old and plain: load every asset with its prior depreciation in every book exactly as filed, run the last closed year in the new register, set the result against the old system's filed figures account by account, and explain every difference before going live. Nothing is trusted because the software says so; it is trusted because the reconciliation ties.

Figure 2. Illustrative report preview with sample data.

The five steps.

  1. Export and file. The asset export with all books, the last filed depreciation schedule and Form 4562, and the disposals report for the last closed year. The file is confirmed and the conversion quoted within one business day.
  2. Map and load. Fields are mapped by table (method, life, convention, class) and the unusual combinations are flagged; prior accumulated depreciation is loaded by book as filed, not recomputed.
  3. Run the last closed year in parallel. The new register computes the year the old system already filed.
  4. Reconcile by account and by book. Cost, accumulated depreciation and current-year expense, old against new, with a cause for every difference: rounding rules, a convention setting, a disposal recorded in one system only, an error carried in the old return.
  5. Decide and document. For each difference you choose to match the return or to correct going forward; the reconciliation with the decisions is the file the auditor sees. Then go live, with the same account manager.
By account, last closed yearOld system, as filedNew register, parallel runDifferenceCause and resolution
1520 Buildings and improvements, cost2,940,000.002,940,000.000.00
1520 accumulated depreciation1,327,100.001,327,100.000.00Prior depreciation loaded as filed
1540 Machinery and equipment, cost1,981,500.001,981,500.000.00
1540 accumulated depreciation1,210,912.401,210,914.10(1.70)Old system rounded each asset to the dollar; documented, old figure kept as filed
1550 Vehicles, depreciation expense117,780.00117,780.000.00
1560 Computer equipment, depreciation expense137,426.67136,380.001,046.67Old system had a laptop batch on half-year; the mid-quarter test applied; corrected going forward with the preparer's agreement
Figure 3. A page of the reconciliation report from a parallel run, sample data. Every difference has a cause and a decision.

What the differences usually are.

Rounding: two systems rarely round the same way, and the cents are found and kept as filed. Conventions: a batch placed on half-year in a mid-quarter year. Prior periods: an override made to match a return and never documented. Disposals: recorded in the ledger and not the register. And, sometimes, an error in a filed return; we show it rather than reproduce it, and the taxpayer and the preparer decide. The switching pages list what each source system exports and what carries over, field by field; the spreadsheet article lists what a workbook usually carries in.

What to record on the asset.

  • Prior accumulated depreciation by book, as filed, as the opening balance, with the source document.
  • Every override made to match a filed figure, with the reason and the date.
  • The reconciliation report, the causes and the decisions, kept with the first year's file.
  • The conversion date, which is the first period the new register owns.
  • The old system's final export, archived, for the auditor who asks in three years.

In Fixed Asset Desk: conversion is done by our staff in five to seven business days and the reconciliation report is part of every conversion; the quote is on the file, once.

Sources: The company's conversion method, in use since 1990; AICPA AU-C section 500 on audit evidence for opening balances. Checked 20 September 2026.

The questions asked about this, answered.

Why not recompute history from cost and dates?

Because the return was filed on the old figures, with their rounding, conventions and overrides. Recomputing produces a schedule that does not match the return; loading as filed does.

What if the parallel run finds an error in the old return?

We show it. You and the preparer decide whether to match the return or correct going forward, and the decision is documented in the reconciliation.

How long does it take?

Five to seven business days from the export to the parallel run for most registers; three to seven for spreadsheets; longer for multi-state registers with many state books.

What do we keep afterwards?

The reconciliation with its decisions, the old system's final export, and the conversion date, which is the first period the new register owns.

Try it on your own register.

Fourteen days, the full product, no card. Load your assets, run a schedule, compare it with what you filed.

Start the 14-day trialRequest a demo

Hosted by us in a dedicated environment for your organisation, or on your own server. One database per customer; your data is exportable in full at any time.

Priced by asset records. Every plan is the full product. Your data is exportable in full, at any time, at no charge. Plans from $1,000 a year.