Plan a controlled transfer to a computerised accounting system
Set the conversion scope, responsibilities, timing and fallback before moving live accounting records.
Exam scope and assessment notes
Cambridge International AS & A Level Accounting 9706, 2026–2028 syllabus, Version 2. These lessons cover the process of transferring business accounts to a computerised accounting system and ways to maintain data integrity during conversion. No specific accounting application is required. Practice is self-checked, not an official Cambridge grade. Full timed Papers 1–4 and human subject-teacher review remain outstanding.
Before you begin
- Use the Topic 1.2 accounting-system skills: understand double entry, trial balances, control accounts, source documents and why complete records matter.
Work on paper. Try each question before revealing help, and explain why your method works.
Quick readiness check
Why is a cutover date needed?
What you will learn
- Define the conversion scope and cutover date
- Assign responsibilities and controls
- Explain why a documented fallback plan protects business records
Decide what moves and when
A conversion plan identifies the records to transfer, the opening date, the source of each balance and the person responsible for checking it. Decide whether the new system begins with opening balances only or also receives historical transactions, customer and supplier records, inventory details and supporting references.
Set a cutover date so that each transaction is recorded in one system under a clear rule. Define the final source-system close, data extraction, conversion, reconciliation, approval and go-live sequence. Business activity may continue during the project, so document how transactions entered after extraction will be captured.
Protect continuity and accountability
Assign separate preparation, conversion and review responsibilities where practical. Record the source files, conversion rules, totals, exceptions, approvals and date of each transfer. Take a secure backup of the source data and retain it according to the organisation's policy before making changes.
A fallback plan states who can stop the conversion, how the source records will be restored or accessed, and how transactions will be controlled if the new system is not ready. A deadline alone is not evidence that the records are accurate or that the system is safe to use.
Pause and explain
What is the purpose of a fallback plan?
Worked example
A wholesaler plans to move from paper and spreadsheets to a computerised ledger on 1 January. Name four decisions the project lead should document before conversion.
Show the worked solution
- Define whether the conversion includes opening balances, customer/supplier details, inventory and transaction history.
- Set the final extraction and cutover dates and specify how late December transactions are captured.
- Assign who extracts, imports, reconciles and approves the data; identify the backup and fallback route.
Answer Document the scope, cutover rules, responsibilities, reconciliation and approval steps, and the backup/fallback plan before moving records.
Try a topic test
Choose Easy, Normal or Difficult. Save your answers and open worked review after finishing.
Test this topic →From guided practice to a new situation
Write your answer and reasoning first. Use a hint only if you are stuck. The model solution is for self-checking; your written work is not automatically marked.
A company extracts its balances on 28 June but continues trading through 30 June. Give a two-day cutover control and name the approval needed before go-live.
Give me a hint
Account for activity after extraction and make the opening date explicit.
Compare my reasoning
- List transactions dated 29–30 June in a controlled cutover schedule.
- Enter those transactions once in the designated system or include them in a reconciled final source extract.
- Reconcile the closing source balances to the new opening balances and have an authorised reviewer sign off the difference report.
Capture 29–30 June activity in a documented cutover schedule, avoid duplicate entry, reconcile to the new opening figures and obtain independent approval before go-live.
Look for these in your work
- List transactions dated 29–30 June in a controlled cutover schedule.
- Enter those transactions once in the designated system or include them in a reconciled final source extract.
- Reconcile the closing source balances to the new opening balances and have an authorised reviewer sign off the difference report.
A project team has a 10-day conversion window. List a sensible sequence of five milestones from extraction to go-live.
Give me a hint
Order the activities so the checks occur before users rely on the new records.
Compare my reasoning
- Approve scope, owners and the cutover date; secure a source backup.
- Extract and clean data, map balances and import into a test environment.
- Run validation and reconciliations, resolve exceptions, obtain approval and only then go live with monitoring.
A sound sequence is plan and back up, extract/clean/map, test-import, reconcile and resolve exceptions, approve and go live with monitoring.
Look for these in your work
- Approve scope, owners and the cutover date; secure a source backup.
- Extract and clean data, map balances and import into a test environment.
- Run validation and reconciliations, resolve exceptions, obtain approval and only then go live with monitoring.
A director wants to skip a fallback plan because the conversion software has never failed before. Explain the business risk and a proportionate alternative.
Give me a hint
Focus on record access and transaction continuity if an unexpected conversion error occurs.
Compare my reasoning
- A failed or incomplete transfer could block billing, payments or reliable reporting even if past conversions succeeded.
- Retain a verified source backup and a controlled route to continue recording transactions during recovery.
- Set a stop/go decision and named approver based on reconciliation evidence, not on the software's history.
Past success does not guarantee this conversion. Keep a tested backup and continuity process, and make go-live conditional on documented reconciliation and approval.
Look for these in your work
- A failed or incomplete transfer could block billing, payments or reliable reporting even if past conversions succeeded.
- Retain a verified source backup and a controlled route to continue recording transactions during recovery.
- Set a stop/go decision and named approver based on reconciliation evidence, not on the software's history.
Common mistakes
- Choosing a go-live date without a transaction cutover rule
- Letting the same person prepare and approve every conversion control
- Deleting the source records after an import appears to finish
What can you explain now?
What should a conversion plan define before the data is moved?
Compare with the explanation
Scope, cutover, responsibilities, checks and fallback
Those decisions control what is transferred, who verifies it and what happens if conversion fails.
After trying it yourself, choose your next review. This is your self-assessment.
Your review choice appears on Today. Sign in to sync it across devices.
Make it stick
Name the five core things a project plan should settle before an accounting-system conversion begins.
If you needed the solution, close it and solve the problem again from a blank page. A correct answer is stronger when you can explain the reason for each step.