Set a transaction cutover and prevent gaps or duplicates
Control transactions around the conversion date so every invoice, receipt and payment appears once in the correct accounting period.
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
One supplier invoice appears in both systems after cutover. What is the risk?
What you will learn
- Apply a clear cutover rule to source transactions
- Identify duplicate, omitted and wrong-period entries
- Reconcile transaction counts and values across the conversion
Define the last transaction in the old system
A cutover rule states the final date and time for entering transactions in the old ledger, the first date in the new ledger and how documents crossing the boundary are handled. Base the rule on the transaction date and the organisation's accounting policy, not on whichever system is easier for the user.
Invoices, receipts, credit notes, supplier bills, payroll and bank transactions can arrive after extraction while relating to the period before cutover. Use a controlled outstanding-items list so they are posted once and in the correct period. Record who handles each item and which system receives it.
Use counts and value checks at the boundary
Compare counts and totals of transactions extracted, imported, rejected and posted after cutover. Reconcile batch debit and credit totals and compare source-document ranges for missing numbers. Sequence gaps need investigation because a gap may be a cancelled document, a missing transaction or a numbering rule change.
A duplicated invoice can overstate revenue, receivables or expenses; an omitted payment can understate cash or liabilities. Correct the transaction in the approved system, retain the supporting document and re-run the reconciliation.
Pause and explain
Why compare both transaction counts and monetary totals?
Worked example
The old system exports 160 sales invoices with total value $96,000. The new system imports 159 invoices totalling $95,400. Calculate the count and value differences and propose the first check.
Show the worked solution
- Count difference = 160 − 159 = 1 invoice.
- Value difference = $96,000 − $95,400 = $600.
- Compare the source invoice-number list with the import and rejection log to locate the missing $600 document.
Answer One invoice worth $600 is missing relative to the source export. Trace invoice IDs and the import rejection log before approving sales 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 batch has 240 supplier invoices totalling $180,000. The import shows 239 invoices totalling $178,750. Calculate the exception and give a two-step trace.
Give me a hint
Find both differences and use document IDs to locate the missing item.
Compare my reasoning
- One invoice is missing by count; the total-value difference is $1,250.
- Compare the source invoice-number range and import rejection list to locate the document.
- Check the source invoice and posting date, then import or post it once in the approved period and rerun count/value totals.
One $1,250 invoice is missing. Trace its ID and date, post it once under the cutover rule and reconcile again.
Look for these in your work
- One invoice is missing by count; the total-value difference is $1,250.
- Compare the source invoice-number range and import rejection list to locate the document.
- Check the source invoice and posting date, then import or post it once in the approved period and rerun count/value totals.
Opening sales batch includes 200 invoices. The new system has 201 records because invoice 478 appears twice for $950. What is the likely overstatement and the evidence to check?
Give me a hint
Identify duplicate value and use the invoice reference and audit history.
Compare my reasoning
- The duplicate may overstate sales and receivables by $950.
- Compare invoice 478 with the source document, customer account and import log to confirm whether one record is accidental.
- Reverse or remove only the duplicate under approval, then check invoice count and batch value against the source.
Potential overstatement is $950. Verify the source document and import log, correct the duplicate through an approved entry and reconcile the batch.
Look for these in your work
- The duplicate may overstate sales and receivables by $950.
- Compare invoice 478 with the source document, customer account and import log to confirm whether one record is accidental.
- Reverse or remove only the duplicate under approval, then check invoice count and batch value against the source.
A receipt dated 2 January clears a customer invoice dated 29 December. The conversion extracts are cut off at 31 December. Explain how to record the invoice and receipt without duplicating the balance.
Give me a hint
The invoice creates the receivable in December; the later receipt clears it in January.
Compare my reasoning
- Record the 29 December invoice in the December source-period balances or approved transaction import.
- Record the 2 January receipt once in the new period and allocate it to that customer invoice.
- Reconcile the opening receivable and January cash to the source and bank records; do not import the receipt as a second December invoice.
The invoice remains a December receivable at cutover; the January receipt is recorded once and allocated after cutover. Reconcile both periods to avoid duplicate sales or cash.
Look for these in your work
- Record the 29 December invoice in the December source-period balances or approved transaction import.
- Record the 2 January receipt once in the new period and allocate it to that customer invoice.
- Reconcile the opening receivable and January cash to the source and bank records; do not import the receipt as a second December invoice.
Common mistakes
- Posting a late invoice in both systems
- Using document number sequence alone as proof of completeness
- Counting a rejected transaction as imported
What can you explain now?
What does a transaction cutover rule prevent?
Compare with the explanation
Gaps, duplicates and wrong-period posting between systems
A written boundary clarifies which system owns each transaction and how late documents are controlled.
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
How do transaction count, value and document-sequence checks work together at cutover?
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.