Use control totals and validation to verify imported data
Compare record counts, debit and credit totals, account balances and independent source evidence to detect errors in a migration.
Section 3.4 · Computerised accounting systems
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
Imported debits equal imported credits, but the import has fewer records than the source. Is it complete?
What you will learn
- Use count and value control totals
- Reconcile debits, credits and selected accounts
- Explain why validation and an independent review are needed
Set totals before and after every import batch
Before importing, calculate source record counts and value totals for the batch. After import, compare accepted, rejected and duplicated counts, debit and credit totals, and selected control-account balances. Record the expected totals and actual results in a conversion control sheet.
A debit-credit total can balance while individual entries are omitted or mapped to the wrong accounts. Compare control accounts, customer and supplier detail, inventory quantities, bank balances and document counts to suitable source reports. Use unique references and validation rules to detect records outside expected ranges.
Make an independent check part of the evidence
A preparer should not be the only person to approve their own conversion. An independent reviewer checks the source report, mapping, batch totals, exception log, reconciliations and evidence of corrections. High-risk balances receive more detailed checks.
If totals differ, stop approval and investigate. Record the cause, correction, reviewer and retest. The control total is a signal, not an explanation; a successful comparison supports completeness for the tested scope but does not prove every field is correct.
Pause and explain
Who should approve a conversion reconciliation where practical?
Worked example
The source ledger has 420 transactions, debits $310,000 and credits $310,000. The imported file has 418 transactions, debits $309,500 and credits $309,500. State the control exceptions and the first action.
Show the worked solution
- The import is short by two transactions and $500 on each side relative to the source totals.
- Although imported debits equal credits, the batch is incomplete compared with the source.
- Compare transaction IDs and reject logs, trace both missing records and correct only after identifying their source and date.
Answer The batch is missing two records and $500 on each side. Equal debits and credits do not resolve the completeness exception; trace IDs and rejection logs.
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.
The source batch contains 75 receipts totalling $48,600. The imported batch has 74 receipts totalling $47,950. Calculate exceptions and state two controls to run.
Give me a hint
Subtract imported counts and totals from source figures.
Compare my reasoning
- One receipt is missing by count; value difference is $650.
- Compare receipt references with the source cash-book and import exceptions.
- Reconcile the bank/cash control and customer allocations, then have the correction reviewed.
One $650 receipt is missing. Check document references, bank/cash and customer allocations, correct with evidence and obtain review.
Look for these in your work
- One receipt is missing by count; value difference is $650.
- Compare receipt references with the source cash-book and import exceptions.
- Reconcile the bank/cash control and customer allocations, then have the correction reviewed.
A system receives 300 invoices. The source batch totals $225,000 debits and credits; the new system totals $224,100 on each side. Counts match. What does the $900 difference tell you and what does it not tell you?
Give me a hint
Equal record counts do not prove each amount or field is unchanged.
Compare my reasoning
- The batch is short by $900 on both sides even though count and debit-credit equality match.
- This may be an amount, mapping or omitted-value issue; compare transaction values, not just counts.
- Trace the difference to documents and import logs; do not approve because the records are balanced.
The totals are $900 below source. Matching counts and balanced sides are insufficient; trace transaction values and mappings to find the cause.
Look for these in your work
- The batch is short by $900 on both sides even though count and debit-credit equality match.
- This may be an amount, mapping or omitted-value issue; compare transaction values, not just counts.
- Trace the difference to documents and import logs; do not approve because the records are balanced.
A conversion report shows exact control totals, but a sample reveals invoice dates shifted from December to January. Explain why the transfer still fails and what to correct.
Give me a hint
Control totals cover amounts and counts but not necessarily date fields or period classification.
Compare my reasoning
- The amounts may match while a field-level error changes the accounting period.
- Revenue, receivables, tax and reporting cutoffs may be misstated even though totals agree.
- Correct the date mapping, rerun period and account validations, review affected entries and document the approval and retest.
The batch is not reliable because dates are materially mis-mapped. Correct the date field, test period cutoffs and affected reports, then document review and retest.
Look for these in your work
- The amounts may match while a field-level error changes the accounting period.
- Revenue, receivables, tax and reporting cutoffs may be misstated even though totals agree.
- Correct the date mapping, rerun period and account validations, review affected entries and document the approval and retest.
Common mistakes
- Treating balanced debits and credits as proof the source was fully imported
- Approving unexplained count or total differences
- Using a control total without documenting its source and period
What can you explain now?
What does an import control-total comparison test?
Compare with the explanation
Whether counts and values agree with the defined source batch
It helps reveal omissions or duplicates within the checked batch, though it does not prove every field is correct.
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 four independent control totals or reconciliations that can help test a converted accounting batch.
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.