Moving Cyprus bookkeeping from Excel: migrate a reconciled ledger instead of a pile of sheets

An Excel workbook can be a sound record, a bank-transaction list, a sales register or several of those things mixed together. Moving it into a bookkeeping system starts by establishing which information you actually have. Uploading every sheet without that assessment can turn old uncertainty into a larger set of apparently precise entries.

The objective is a ledger someone can reconcile and continue. It is not necessarily to recreate every spreadsheet tab inside new software. Our software selection guide addresses choosing a system. This article covers preparing the data once you have agreed what the migration needs to achieve.

Classify the files before cleaning them

Inventory the workbooks and their purpose. Identify the bank-transaction list, sales invoices, purchases, payroll, assets and balances owed by customers or to suppliers. Record which files contain original data and which contain reports calculated from other sheets.

For example, a summary tab calculating annual sales is not another source of sales to import. Importing both its total and the underlying invoice rows would duplicate the same activity. A separate cash sheet might include owner funding alongside customer receipts. Those movements need different treatment even when they have the same sign.

Preserve read-only originals before changing anything. Note who produced each workbook, the last date updated and whether formulas depend on hidden rows or external files. Keep a version history for the cleaned migration copies so a reviewer can explain what changed.

Choose a migration approach that fits the evidence

Decide whether you need full transaction history, current-year history, or a starting set of balances with older records retained in an archive. Consider reporting needs and what the receiving system can accept. Do not let an attractive import button make that accounting decision for you.

Choose the last old-record date and the first new-record date. Every statement and opening schedule must use that boundary. If some sheets stop in June and others include July, identify the overlap before loading either period.

The company's records must still explain its transactions and balances under section 141. Keeping a clear archive and mapping is therefore more valuable than moving unexplained totals into a fresh screen.

A balances-only method requires the supporting open-item detail. The broader accountant handover guide explains the records to request when another provider owns part of the history.

Create a clean source table

Use one row per intended record with clear columns. A useful starting table includes date, source reference, counterparty, description, currency, amount, account classification and an evidence link. Depending on the record type, you may also need invoice date, due date, payment reference or tax classification.

Remove merged cells and presentation subtotals from the import copy. Standardise dates and signs. Check whether an amount is a net sale, tax-inclusive invoice total or bank receipt, and label it accordingly. Retain the original value rather than silently replacing it with a calculation nobody can reproduce.

Deduplicate using more than an amount and a date. Two valid bills can have identical values. Compare supplier, invoice number, document and payment reference. Flag uncertain matches for review instead of deleting them automatically.

Map the records without inventing treatment

Prepare an old-to-new account map. Show where different spreadsheet labels represent the same type of transaction, and where a single vague label needs investigation. A category called business costs can contain ordinary expenses, equipment purchases and owner payments.

Map contacts using a stable identifier. The same supplier might appear under its legal name, trading name and abbreviated bank description. Identify whether those entries belong to one counterparty before importing their outstanding balances.

Tax treatment should come from the underlying transaction and evidence, not the name of a spreadsheet column. For unresolved classification questions, assign a reviewer and leave the question visible. Where an IFRS-reporting business discovers a material prior-period error, IAS 8 sets the correction framework; migration is not a reason to hide the error in the current period.

A worked example of duplicate source data

A consulting company's sales workbook contains twenty invoices totalling \u20AC18,000. Its bank workbook contains \u20AC15,500 of customer receipts. A third summary sheet shows the difference as \u20AC2,500 unpaid.

The migration team initially proposes importing the twenty invoices, the receipts and the \u20AC2,500 receivables total as an additional opening item. That would duplicate the remaining receivable. The \u20AC2,500 is a calculated result of the invoices and receipts, not a new transaction.

The team chooses a full current-year import. It links receipts to the relevant invoices and checks that the resulting customer balance is \u20AC2,500. The summary sheet remains part of the reconciliation evidence but is not posted again.

Alternatively, a balances-only import at the agreed cutover would transfer the unpaid invoice detail totalling \u20AC2,500, with the older invoices and receipts retained in the archive. The method can differ. What matters is that the same history is not recorded twice.

These figures are illustrative and exclude VAT to keep the migration arithmetic visible. An actual file needs the correct treatment of its own invoices and tax records.

Test a small import before the complete file

Choose examples that expose the difficult cases: an unpaid invoice, a partial payment, a credit note, a supplier bill, a foreign-currency transaction and an owner-funded expense. Check their accounting effect and supporting-document link after the test.

Compare account totals, contact balances and transaction counts. Inspect whether dates or currencies were changed during parsing. Check whether a positive bank receipt has been interpreted as a payment or whether an opening balance created fresh revenue.

Follow each sample into a report. A technically accepted record can still have an unwanted accounting effect. Record the result of the test, revise the mapping and keep the approved import file distinct from earlier attempts.

Reconcile and approve the completed move

Compare every bank and payment account to its cutover statement. Compare customers and suppliers to open-item schedules. Check loan, owner, payroll and tax balances against their supporting records. The bank reconciliation guide explains the recurring statement comparison.

Keep an exceptions list with the issue, amount, evidence and person responsible. Decide who handles documents arriving after cutover. Do not allow the old workbook and new system to become parallel, independently edited versions of the same books.

Sign off the migration when the checks are complete and the remaining exceptions are understood. Keep a company-controlled copy of the old files, cleaned source tables, mapping and acceptance evidence. The next person should be able to trace the starting position without recreating the project.

Related service: bookkeeping service page.