Opening balances for Cyprus bookkeeping: prove what the business owes and owns on day one

The opening bank balance agrees to the statement, the trial balance adds up, and the new ledger looks ready. Then a customer pays an old invoice that does not exist in the new system. Another supplier's balance appears twice. Those problems arise when a migration transfers totals without transferring the explanation behind them.

Opening balances represent the business at a particular date. They include money owed to the company and money the company owes, not just cash. This guide explains how to test that starting position. Use the broader accountant handover guide when arranging the transfer between providers.

Agree what the cutover date means

Choose the final date covered by the old records and the first date for new transactions. Every opening schedule should use that same boundary. A bank statement ending in September cannot prove an August cutover without the intervening movements being removed and explained.

Write down whether the new records include the full financial year, a limited transaction history, or balances only. A mid-year move may require year-to-date income and expense figures as well as balance-sheet accounts. Establish this with the person responsible for the reporting, rather than assuming a new software subscription creates a new accounting year.

The company's reporting work still sits within the financial-statement requirements in Companies Law section 142. A system change needs a continuity plan for those accounts.

Keep a signed or otherwise recorded acceptance of the boundary. It should name who completes the old period, who posts late documents, and how corrections cross between the records.

Collect the trial balance and the explanations

Request an account-level trial balance together with the general ledger. Obtain the customer and supplier open-item lists, bank reconciliations, processor statements, fixed-asset schedule, loan balances and relevant tax or payroll schedules. Retain the previous financial statements and the adjustments connecting them to the current ledger.

A trial balance showing receivables of \u20AC8,400 is incomplete as a migration pack if nobody can identify the invoices making up \u20AC8,400. The same applies to a liability described simply as taxes. Separate the authorities, periods, payments and any disputed amounts.

Do not replace supporting detail with a list of account names. The purpose is to be able to answer a future receipt, payment or enquiry. For company records, section 141 requires supporting evidence for transactions and balances. The migration should preserve that evidence even if the old system will no longer be used.

A worked opening-balance example

The following fictional balances illustrate the arithmetic. They exclude tax complications and are not a recommended chart of accounts.

The totals balance, but that proves only the debit-credit arithmetic. The bank needs a statement and reconciliation. Customer balances need an invoice-by-invoice listing. Equipment needs a register showing cost and depreciation. The loan needs an agreement and lender statement.

Suppose the customer schedule totals \u20AC8,100. The \u20AC300 difference might be an omitted invoice, a credit note or a misposted receipt. Posting \u20AC300 to retained earnings just to make the schedule agree hides the question. Find the transaction, decide its treatment and retain the correction evidence.

If an old supplier invoice is later paid, the payment reduces its opening payable. It is not a fresh expense. This is why the unpaid-item detail matters after the cutover, not merely during the import.

Avoid recording the opening items twice

There are different ways to load totals and open invoices, depending on the chosen system. Agree a method that produces one receivables balance and one payables balance. Loading the control accounts and then posting the same unpaid invoices as new sales or purchases can duplicate both balances and income or expenses.

Test a few examples before the complete migration. Include an unpaid invoice, a partially paid bill, a credit balance and a foreign-currency item. Check what happens when each is settled after the start date.

An import message confirms that data was accepted by a system. It does not establish that the accounting effect was correct. Compare the resulting reports to the agreed trial balance, open-item schedules and statement balances.

Our bank reconciliation guide explains the recurring statement checks. At cutover, make that comparison for every bank and processor before accepting the starting position.

Keep a controlled adjustment list

Use a list containing the issue, original amount, evidence, proposed correction, approver and posting reference. Distinguish an actual accounting error from a change in how accounts are named or grouped. The reporting consequences can be different.

Do not delete historical entries simply because the migration method cannot import them. Preserve a readable archive and an explanation of any aggregation. If only opening balances move, retain the old transaction detail where the company can retrieve it.

Choose how late documents will be handled. An invoice relating to the old period should go to the responsible reviewer, with instructions about which records and filings may need revision. Avoid separate people correcting the same item independently in both ledgers.

Accept the migration with a practical test

Compare the old and new trial balances by account mapping, not only by total. Compare outstanding customers and suppliers, cash, loans, owner balances and payroll or tax liabilities. Agree the result of any differences in writing.

Then run a small settlement test. A receipt against an old customer balance should clear the intended invoice without creating a second sale. A payment against an old supplier balance should reduce the intended payable. Record any residual difference and investigate it.

Finally, check that the next period can be closed normally. A ledger requiring repeated manual workarounds to interpret opening balances has not achieved a clean handover. A useful starting position is one another person can explain from the retained documents.

Related service: bookkeeping service page.

Questions about opening balances

Is a balanced trial balance enough?

No. Equal debit and credit totals show an arithmetic relationship. They do not prove that invoices exist, balances are recoverable, or every liability has been recorded. Use supporting schedules and statements.

Should I import every historical transaction?

Decide according to reporting needs, system capability and the availability of a reliable archive. A balances-only migration can be workable when the old detail remains accessible and the new opening items are complete.

What should I do with an unexplained difference?

Record it as an unresolved issue, investigate the supporting records and obtain an approved treatment. Do not use retained earnings or a suspense account as a permanent way to conceal the difference.

Does migration itself change the financial year?

A system cutover and a reporting-year decision are separate. Agree how year-to-date results and comparative records will remain usable. The bookkeeping service page is a relevant place to begin a discussion about the handover.