What should I hand over when moving from spreadsheets to accounting software?

Decide what the change is meant to solve

A business may move to accounting software because invoices are difficult to track, several people are editing spreadsheets or monthly reporting takes too long. Name the problems first. Otherwise, the migration can reproduce the same unclear categories and incomplete records inside a more complicated system.

Agree which tasks the new system will handle: customer invoicing, supplier balances, bank reconciliation, stock, payroll connections or management reports. Some tasks may remain in a separate system. Record those boundaries so that a transaction is not omitted because each person assumes another system contains it.

This article focuses on the handover of financial records. It does not recommend a particular product or promise that any software automatically meets every tax or company-record requirement. The business remains responsible for understanding and preserving its records.

Choose a cutoff date and define the historical scope

Decide the date from which the new system becomes the working record. Then specify whether you are bringing in detailed historical transactions, opening balances with outstanding items, or another reviewed approach. The correct choice depends on reporting needs, record quality and the accountant’s plan.

Make the boundary explicit. If a supplier invoice was raised before the cutoff but paid afterwards, the new system needs enough information to settle it correctly. Importing only cash movements can miss the opening amount owed. Importing both a balance and all its underlying transactions without a proper plan can duplicate it.

Keep the spreadsheet version used for the handover unchanged and clearly identified. If corrections are later necessary, retain a change record rather than silently replacing the file on which the opening balances were based.

Prepare the records behind the opening balances

Collect the final account balances and the records that support them. This includes bank reconciliations, unpaid customer and supplier schedules, loan balances, asset records and relevant tax or payroll balances. Identify the period and legal entity on every export.

A total alone is not always enough. The business may need the individual customer invoice references and due dates to allocate receipts and chase late payments. Likewise, a supplier balance should be traceable to the invoices and credits making up the amount.

Do not turn an unexplained difference into a convenient opening balance simply to finish the import. Put it on the unresolved-item list, identify its possible effect and agree who will investigate it. The new system should not give an unsupported number the appearance of certainty.

A handover pack that supports a meaningful check

Use the table as a starting point and add the records relevant to the business. A stockholding retailer and a consulting company will have different details to reconcile.

Map the categories before importing transactions

Spreadsheets often contain categories created informally by different people. One person may use “transport”, another “vehicle costs” and another the supplier’s name. Review the categories and decide how they map to the new account structure.

Keep a mapping sheet showing the old category, new account and any exception requiring review. Do not collapse items solely to reduce the number of accounts if doing so would hide information the owner needs. Equally, hundreds of supplier-named expense accounts may make the reports difficult to interpret.

Review tax codes with the appropriate adviser. Copying a label from the spreadsheet does not establish the correct tax treatment. If the historical file did not distinguish VAT treatment or private elements, identify that gap before applying automated import rules.

Test a realistic set of transactions

Illustrative example: a fictional maintenance business has an unpaid customer invoice at the cutoff, a supplier credit and a payment still clearing through the bank. The migration is checked by following those items into the new system and processing their later settlement correctly.

The opening totals might agree while individual customer allocations are wrong. A sample test can reveal that invoices lost their references, credit notes became positive invoices or dates were interpreted incorrectly. These errors can affect statements sent to customers even though a headline balance appears correct.

Include ordinary purchases, refunds, transfers between bank accounts and a transaction involving an owner or employee where those occur in the business. Compare the resulting reports with the intended treatment. Record the checks and corrections before using the system for live decisions.

Keep historical evidence accessible

Switching systems does not remove the need to retain the underlying records. The SARS record keeping guidance explains that obligations depend on the circumstances, including whether returns, audits or disputes remain outstanding. Do not delete an old archive merely because an import succeeded.

Save the source spreadsheets, relevant reports and documents in formats that authorised people can still read. Check whether formulas, linked files or protected sheets are needed to understand a calculation. A values-only export can be useful, but it may not preserve the explanation contained in the original workbook.

Test retrieval after the handover. Ask the reviewer to find the evidence for an older transaction without assistance from the person who built the spreadsheet. Record where the archive is held and who maintains access.

Agree responsibilities and access before the first month

Identify who creates invoices, captures purchases, reviews bank matches, approves corrections and closes the month. Give users access suited to their duties, with appropriate approval arrangements. A shared login makes it harder to understand who changed a record.

Agree how missing documents will be requested and where they should be stored. Decide who maintains customer and supplier details and how bank-detail changes are checked. The migration should include these working responsibilities as well as the data files.

Plan the first monthly review. Compare the key balances and investigate unexpected results early, when the imported records and decisions are still fresh. Use the monthly close checklist to establish the recurring process after the change.

Watch for overlapping bank imports at the changeover

An imported spreadsheet may already contain transactions that the new bank feed downloads again. Agree the last imported date and check whether the feed includes the same day or earlier history. The software may offer duplicate detection, but the reviewer should still inspect the boundary rather than assume it catches every overlap.

A repeated description is not conclusive proof of duplication. Two legitimate payments can have the same amount and description. Compare the bank reference, date and account, then check the actual statement before removing an entry. Equally, a transaction whose date differs between an export and a settlement report may still represent the same event.

Save the import file and the import result, including rejected rows. A successful upload message may coexist with records that did not load. Reconcile the number and value of imported items against the intended dataset, explain exceptions and keep the review with the migration pack before enabling further automated processing.

What completion should look like

A completed handover has an agreed cutoff, reconciled opening data, a readable archive, documented category mapping and a list of remaining issues. It should be possible to explain which historical detail is inside the new system and where the rest can be found.

Do not use “the software is running” as the only completion test. Confirm that the owner can obtain the required reports and that the person maintaining the books can trace balances to evidence. Resolve any material difference before treating the new reports as dependable.

For help preparing the financial handover, enquire about monthly bookkeeping. If the account structure also needs to support decision making, discuss management accounts. Include the current files, business structure and proposed changeover date in the enquiry rather than sending login credentials.