ISC · Information Systems and Data Management · 6 practice questions
AP-to-GL Batch Recovery: Fix, Reprocess, and Reconcile
When mapping errors block AP postings, correct the mapping and reprocess only failed transactions before reconciling. Below: a partially posted batch shows why replaying the full amount overstates AP.
Try one first
Hint
Focus on controls that directly address nightly interface failures and that promptly detect or prevent missing or duplicate transactions before the GL is updated.
Answer D. Automated interface controls (control totals, hash totals, automatic comparisons, and alerts) provide prompt detection and prevention of missing or duplicate transactions and reduce the likelihood that errors go unnoticed until month-end. Immediate alerts and automated reconciliation address the current failure mode directly and allow remediation before the GL reflects incorrect balances. While redesigning the system or manual reconciliations are options, automated interface controls are the most practical immediate preventive/detective fix.
Why not A: Daily manual reconciliations would detect discrepancies sooner than monthly review, but they are labor-intensive, prone to human error, and do not provide automated alerts or prevent incorrect postings. They are a compensating detective control rather than the more effective automated preventive/detective interface controls.
Why not B: Real-time posting would eliminate batch-interface risk but is typically costly, complex, and disruptive to implement. It is a longer-term architectural change rather than the immediate control change management requested.
Why not C: Supervisor approvals add oversight, but they are retrospective and depend on staff noticing failures; they do not automatically detect failed or mismatched transfers. This is a compensating control that does not address the lack of automated detection and is insufficient as the primary immediate fix.
Step by step
- Establish what actually posted
MidCo has no opening AP balance, and its source batch contains 100 invoices totaling $100,000. The job reports completion, but only 20 invoices totaling $20,000 posted successfully; mapping errors blocked the remaining 80 invoices totaling $80,000.
- Compare source and target
Compare the source batch of 100 invoices and $100,000 with the initial GL results of 20 invoices and $20,000. The missing postings are 80 invoices totaling $80,000.
- Identify the failed transactions
Use the processing results to identify the 80 failed invoices and distinguish them from the 20 successful postings. A job-completion message alone does not establish posting completeness.
- Correct the mapping
Correct the identified mapping error through approved change procedures before reprocessing.
- Reprocess only failed invoices
Reprocess only the 80 failed invoices totaling $80,000. Exclude the 20 invoices totaling $20,000 that already posted successfully.
- Reconcile the recovered balance
The recovered AP control account balance is $20,000 + $80,000 = $100,000, matching the AP subledger. Confirm that all 100 invoices posted once and that no failures remain.
- Reject the full-batch manual credit
A manual AP credit for the full $100,000 would produce $20,000 + $100,000 = $120,000. That overstates the correct $100,000 AP balance by $20,000 and leaves the failed interface unresolved.
Key points
- Remember: Recover the missing postings, not the full batch, because some invoices may already be in the GL.
- A completed job does not prove that every invoice posted successfully.
- Matching balances must be supported by the correct invoice postings, not just a manual adjustment.
How the exam traps you
- Manually credit AP for the full $100,000 source batch without checking which invoices already posted. Identify the $20,000 already posted, correct the mapping, and reprocess only the failed $80,000; then reconcile.
- Rerun all 100 invoices without excluding successful postings. Reprocess only the 80 failed invoices to avoid duplicating the $20,000 already posted.
- Wait for the next scheduled run despite a known mapping error. Correct the identified mapping error before reprocessing; another run does not fix the configuration.
Question 2
Hint
Focus on which data element the automated three-way match relies on after posting, and ask what happens if that element can later be changed.
Answer B. The automated three-way match uses the recorded receipt quantity as part of the evidence that the liability was properly established. Allowing that receipt record to be edited after an invoice auto-posts, without preserving the original quantity or forcing re-evaluation of the posted liability, undermines data integrity and auditability. The inability to retrieve the pre-change receipt quantity is the principal design flaw.
Why not A: This is tempting because segregation of duties is a classic internal control concern; however, many ERP implementations require receiving staff to record receipts and the stem does not indicate they approve invoices or payments. The more direct and serious problem here is that the source record used for the automated match can be altered after posting without preserving the original matched state.
Why not C: Timing can matter, and delaying posting until the edit window closed could be one mitigation. But early posting is not inherently fatal if the system versions the original data or triggers re-match logic after edits. The core defect is the ability to overwrite the matched receipt without retaining the original value or re-evaluating the posted liability.
Why not D: This sounds plausible because edits change inventory quantities, but the invoice originally posts to AP and GL from the same transaction. The scenario describes no automatic AP/GL mismatch; the more direct failure is loss of the original matching evidence and an impaired audit trail, not necessarily an AP-to-GL reconciliation break.
Question 3
Hint
Focus on which part of the system actually powers aging and credit holds: the control-account balance in the GL or the customer-level open-item records.
Answer A. The governing issue is data granularity at the system layer that drives the workflow. Aging, collections, and automated credit holds require customer- and invoice-level open-item detail in the A/R subledger; a summarized GL journal entry updates balances but does not create the records those workflows rely on. Even with accurate mapping and timely posting, the ERP cannot perform subledger-based customer monitoring for the combined business unless the subsidiary's transactions populate the subledger.
Why not B: This is tempting because credit decisions often feel timing-sensitive, and candidates may overfocus on real-time versus batch processing. But faster transmission does not solve the core problem if the ERP still receives only summarized balances; the workflows need customer open-item detail, not just fresher control-account totals.
Why not C: This choice is attractive because chart-of-accounts alignment is important for consolidated financial reporting and interface design. However, revenue account consistency affects financial statement classification and mapping, not whether the ERP can produce invoice-level aging or apply customer credit holds. Those functions depend on subledger records, not merely proper revenue coding.
Why not D: This sounds plausible because standardized terms and credit policies improve comparability and centralized decision-making. Still, those policies can only be applied effectively if the ERP has transaction-level receivable items tied to customers. Policy harmonization matters after the system has the right underlying subledger data; it is not the governing factor here.
Question 4
Hint
Determine whether the discrepancy is because incorrect postings are getting into the GL (prevention needed) or because they aren’t being found quickly enough (detection needed).
Answer B. The immediate cause was invoices being routed to a suspense account because the mapping table had no mapping for blank/'unassigned' vendor classes. Enforcing real‑time validation and blocking the interface posting when a mapping is missing prevents incorrect coding from entering the GL and forces resolution before posting. This is a preventive control at the point of entry, unlike the other choices which are primarily detective or longer‑term governance measures.
Why not A: This control addresses risks from improper manual journals, but the mispostings here were caused by an automated interface mapping failure. Restricting manual journals does not prevent invoices from being auto‑coded to a suspense account.
Why not C: More frequent reconciliations would detect the issue sooner and limit exposure, but they are detective rather than preventive and do not stop incorrect postings from occurring in the first place.
Why not D: Stronger master data governance helps reduce future data errors and is a valuable longer‑term measure, but periodic reviews are retrospective and would not by themselves block an invoice from posting with a missing mapping at the time of entry.
Question 5
Hint
Who implemented the change and what other duties did they have? Determine whether the problem is a failure to prevent an unauthorized change or a failure to detect it afterward.
Answer D. The primary problem is a preventive-control breakdown: one analyst both changed live production mappings and executed vendor payments, creating a segregation-of-duties conflict. In addition, there was no formal change-management process (no request, testing, or supervisory approval), which allowed an unauthorized production change to proceed. Detection controls (reconciliations, exception reports), interface robustness, and logging are secondary because they would have found the issue later rather than prevented the improper change.
Why not A: Tempting because better logging would aid investigation and accountability, yet audit logs are detective controls. They don't prevent an improper change or stop the employee from processing payments, so they are secondary to segregation-of-duties and change-management failures.
Why not B: Tempting because stronger reconciliations or exception reporting would have detected missing invoices sooner, but this answer addresses detection rather than the root cause. The key failure was preventive: an unauthorized change by someone with transactional authority.
Why not C: Tempting because the vendor ID format change precipitated the issue, but even a robust interface wouldn't stop an unauthorized manual edit by an employee who can both change mappings and process payments. The primary control gap concerns who could make and approve changes.
Question 6
Hint
Focus on which choice preserves the control-account-to-subledger linkage while still allowing timely recording when customer-level detail is incomplete.
Answer A. This preserves the integrity of the AR control account-to-subledger relationship in an integrated accounting system and prevents mismatches created by bypassing the subledger. Timely recording of receipts is still achieved by using an unapplied cash or suspense account until customer-level application is determined.
Why not B: This is tempting because more frequent reconciliations improve detection, but reconciliation is detective, not preventive; it does not stop the structural problem of the control account being updated outside the subledger.
Why not C: Thresholds and documentation may reduce volume of exceptions but still allow the control account to be updated independently of customer-level records; the structural mismatch remains even for well-documented entries.
Why not D: This avoids GL-subledger differences but delays recognition of valid cash receipts unnecessarily; using an unapplied cash/suspense account preserves timeliness without corrupting the control account.
Common questions
How do you fix a partially posted AP-to-GL batch?
Identify successful and failed postings, correct the mapping through approved procedures, and reprocess only the failures. Then reconcile the AP control account to the subledger.
Should I manually post the full AP batch to the GL?
No. Here, a $100,000 manual credit added to the $20,000 already posted would produce $120,000 of AP, overstating the correct balance by $20,000.
How do I confirm an AP-to-GL reprocessing job worked?
Verify that the 80 failed invoices totaling $80,000 posted without duplicating the 20 successful invoices. The GL should contain all 100 invoices and reconcile to the $100,000 AP subledger balance.
Watch it solved
A full CPA ISC task-based simulation on Enterprise and accounting information systems, worked step by step.
ISC Simulation: Mapping Controls Through Order-to-Cash on YouTube
Practice ISC like the real exam
The free ChatCPA simulator: real exam layout, timed testlets, starting with a question on this topic. No account needed to start.
Open the free simulator →More on Enterprise and accounting information systems
- ERP Cores, Hybrid Architectures, and Best-of-Breed
- ERP Revenue Recognition: Shipment vs. Invoice Date
- ERP Vendor Master Data Governance: One Controlled Source
- Auditing ERP Automated Controls: ITGCs and Data Conversion
- ERP Data Residency: When Local Laws Govern Deployment
All Enterprise and accounting information systems practice →
Questions from the ChatCPA bank of 17,658 CPA exam questions, each with a written reason for every wrong answer. ChatCPA is built by Nicholas Miller, CPA (Oregon #14907). How these pages are made. Spot an error? Tell us.