Confirmations, Rollforwards, and PBC Tracking: The Offshore Audit Checklist

Confirmations, Rollforwards, and PBC Tracking: The Offshore Audit Checklist

Audit efficiency depends on more than completing testing procedures. It also requires timely confirmations, accurate rollforward schedules, organized supporting documentation, and consistent communication between the audit team and the client.

For US CPA firms, these activities can consume a significant amount of time during interim testing, year-end audits, and busy season. Missing bank confirmations, incomplete account reconciliations, outdated schedules, and unanswered Prepared by Client (PBC) requests can delay fieldwork and create additional review work.

Offshore audit support can help firms manage these recurring tasks by organizing documentation, maintaining trackers, preparing schedules, monitoring outstanding items, and keeping workpapers ready for review.

However, offshore audit support works best when responsibilities are clearly defined, documentation standards are consistent, and the engagement team's review process remains intact.

This guide provides a practical checklist for managing three important audit activities: confirmations, rollforwards, and PBC tracking.

1. Why Confirmations, Rollforwards, and PBC Tracking Matter

These activities address different parts of the audit process, but they share a common objective: helping the audit team obtain, organize, and evaluate the evidence needed to complete the engagement.

• Confirmations help auditors obtain relevant evidence directly from external parties, such as banks, customers, or other counterparties.

• Rollforwards help update previously prepared schedules or interim testing to reflect activity through the relevant year-end or reporting date.

• PBC tracking helps the engagement team monitor requested client documents, outstanding information, and unresolved questions.

When these processes are poorly coordinated, even a well-planned audit can experience unnecessary delays.

Quick Audit Workflow Checklist

Before fieldwork begins, confirm that:

• The audit team has identified the key accounts and audit areas requiring attention.

• Confirmation requirements have been assessed and assigned.

• Relevant interim schedules have been identified for rollforward procedures.

• The PBC request list has been prepared and shared through approved channels.

• Each major task has an assigned owner and target date.

• Client dependencies and information gaps are documented.

• Workpapers follow the firm's documentation standards.

• Review responsibilities and escalation procedures are clear.

The objective is to make audit progress visible, evidence traceable, and outstanding work easier to manage.

2. Audit Confirmations: A Checklist for Better Tracking and Follow-Up

External confirmations can provide important audit evidence about financial statement balances and other information held by independent third parties.

Depending on the engagement and applicable auditing standards, confirmation procedures may involve bank balances, accounts receivable, debt arrangements, or other relevant financial relationships.

The challenge is not simply sending a request. The audit team must identify the appropriate confirming party, maintain control over the process, monitor responses, investigate exceptions, and determine whether sufficient appropriate audit evidence has been obtained.

Offshore support can assist with administrative coordination and tracking, provided the engagement team's responsibilities are preserved.

Audit Confirmation Preparation Checklist

Before requests are initiated

• Identify accounts and relationships for which confirmation procedures are planned.

• Review the relevant trial balance and supporting schedules.

• Obtain the necessary contact information through approved procedures.

• Prepare a confirmation tracker with unique reference numbers.

• Record the requested information, assigned owner, and target dates.

• Prepare draft requests or supporting information for auditor review, where appropriate.

• Confirm the approved confirmation method and communication channel.

During the confirmation process

• Track the status of each request.

• Record when a request is issued by the authorized audit team.

• Monitor responses and outstanding requests.

• Flag returned or undeliverable requests.

• Identify responses that contain differences or incomplete information.

• Record follow-up requirements and the responsible team member.

• Escalate nonresponses and unusual results according to engagement procedures.

When responses are received

• Link the response to the relevant confirmation request and workpaper.

• Compare the confirmed information with the accounting records.

• Document differences for investigation.

• Identify responses that require additional audit procedures.

• Track the status of alternative procedures where required.

• Ensure the engagement team evaluates the results before concluding the audit area.

What Should an Audit Confirmation Tracker Include?

A well-designed confirmation tracker helps the team understand the status of every request without repeatedly searching emails or workpapers.

Tracker FieldPurposeClient or entityIdentifies the relevant audit engagementAccount or audit areaLinks the request to the appropriate balance or assertionConfirming partyIdentifies the bank, customer, or other external partyRequest referenceProvides a unique identifierRequest statusShows whether the request is pending, responded to, or requires follow-upDate issuedRecords when the authorized team sent the requestResponse dateRecords when a response was receivedException statusHighlights differences requiring investigationFollow-up ownerIdentifies who is responsible for the next actionWorkpaper referenceLinks the request and response to supporting documentationFinal dispositionRecords the engagement team's documented resolution status

Common Confirmation Issues to Watch For

1. Nonresponses

A missing response does not automatically mean the related balance is incorrect. It does mean the engagement team must evaluate the situation and determine the appropriate next steps under the applicable standards.

Offshore support can flag nonresponses, maintain follow-up records, and organize supporting documents for alternative procedures when required.

2. Differences between confirmed and recorded balances

A confirmation may reveal timing differences, unapplied payments, disputed invoices, recording errors, or other discrepancies.

The difference should be documented and investigated rather than automatically treated as an error or cleared without support.

3. Incorrect or incomplete contact information

An incorrectly addressed request can delay the process and may affect the reliability of the response.

The team should follow the firm's approved procedures for validating contact details and resolving returned requests.

4. Weak documentation

A tracker showing that a confirmation was completed is not, by itself, sufficient documentation of the audit conclusion.

The workpapers should establish what evidence was obtained, how exceptions were evaluated, and what conclusions the engagement team reached.

Important control: For PCAOB-regulated audits, the auditor must maintain control over the confirmation process in accordance with the applicable requirements. Offshore staff may assist with preparation and tracking, but should not independently take over confirmation responsibilities that belong to the auditor.

3. Audit Rollforwards: Keeping Schedules Current Through Year-End

Rollforward procedures help an audit team update relevant financial information from an earlier date to the period-end date.

For example, an account may have been tested during interim fieldwork. The engagement team may then need to evaluate transactions and changes occurring between the interim testing date and year-end.

The procedures required depend on the account, assessed risks, applicable auditing standards, and engagement circumstances.

A rollforward should not be treated as a simple date change or a routine spreadsheet update. It must be supported by appropriate evidence and procedures.

Audit Rollforward Checklist

Step 1: Identify the schedule to be updated

• Identify the relevant account or audit area.

• Confirm the original testing date and the required period-end date.

• Obtain the latest trial balance or relevant supporting report.

• Locate the previously reviewed schedule or workpaper.

• Confirm the firm's rollforward requirements for that account.

Step 2: Reconcile the updated information

• Confirm that the opening balance agrees with the previously supported balance.

• Obtain activity for the period between the original testing date and year-end.

• Reconcile the updated schedule to the relevant accounting records.

• Identify unexplained differences.

• Investigate changes in account balances or underlying assumptions.

• Document relevant adjustments and supporting references.

Step 3: Perform the required procedures

• Identify significant transactions during the rollforward period.

• Evaluate unusual or unexpected movements.

• Obtain supporting documentation for selected transactions.

• Perform additional procedures when required by the engagement plan.

• Consider whether the updated information affects the original audit conclusions.

• Escalate exceptions that require additional audit judgment.

Step 4: Complete the workpaper

• Update the schedule through the appropriate reporting date.

• Link relevant supporting documentation.

• Document procedures performed and results obtained.

• Record unresolved questions.

• Submit the workpaper for review.

• Address review notes and track their resolution.

Which Audit Schedules May Require Rollforward Work?

Depending on the engagement, rollforward procedures may apply to areas such as:

• Fixed asset and depreciation schedules.

• Inventory records and related testing.

• Accrued expenses and other liabilities.

• Accounts receivable and accounts payable.

• Debt and interest schedules.

• Equity and retained earnings.

• Selected revenue and expense accounts.

• Other balances previously tested at an interim date.

The nature and extent of work should be determined by the engagement team. Not every account requires the same rollforward procedure, and some areas may require different or additional testing.

Common Rollforward Mistakes

Using outdated source data: A schedule cannot be reliably updated if it uses an incomplete or superseded trial balance.

Failing to reconcile balances: Changes between the interim date and year-end should be traceable to relevant accounting records.

Ignoring unusual movements: Unexpected account changes may indicate errors, reclassifications, unusual transactions, or other matters requiring investigation.

Copying prior-year explanations: Previous explanations may not apply to the current period. Supporting information should reflect the actual transactions and circumstances being audited.

Closing workpapers without sufficient support: A completed spreadsheet is not a substitute for documenting the procedures performed, evidence obtained, and conclusions reached.

How Offshore Teams Can Support Rollforward Work

Qualified offshore audit support professionals can assist with:

• Updating schedules using approved source data.

• Reconciling account balances to supporting records.

• Organizing transaction-level documentation.

• Preparing lead schedules and supporting workpapers.

• Identifying unusual movements for further investigation.

• Maintaining open-item and review-note trackers.

• Updating cross-references and documentation.

• Preparing workpapers for review by the engagement team.

The audit team remains responsible for determining the appropriate procedures, evaluating evidence, resolving significant exceptions, and reaching audit conclusions.

4. PBC Tracking: Managing Client Requests Without Losing Visibility

PBC stands for Prepared by Client. A PBC list identifies information, schedules, documents, and explanations requested from the client to support the audit.

PBC tracking becomes particularly challenging when an engagement involves multiple client contacts, several audit areas, overlapping deadlines, and repeated requests for missing information.

A well-maintained tracker helps the audit team identify blockers before they affect fieldwork or completion dates.

PBC Tracking Checklist

Before fieldwork

• Prepare a request list based on the engagement plan.

• Organize requests by audit area.

• Assign a unique reference number to each request.

• Define what constitutes a complete response.

• Assign a responsible client contact where known.

• Set target dates based on engagement milestones.

• Share requests through the firm's approved communication and document management systems.

While collecting documents

• Record the date each request is issued.

• Track whether the request is not started, pending, partially received, or complete.

• Record the date documents are received.

• Link received documents to the relevant request.

• Check whether submissions contain the requested information.

• Identify missing schedules or supporting documentation.

• Follow up on overdue items according to the agreed process.

• Escalate requests that threaten critical deadlines.

Before closing a request

• Confirm that the requested documents have been received.

• Verify that the submission is sufficiently complete for the next step.

• Record any additional questions raised by the audit team.

• Link the supporting documents to the relevant workpaper.

• Confirm whether further client information is required.

• Update the request status and record the next action.

• Close the request only when the firm's defined criteria are satisfied.

Recommended PBC Tracker Fields

FieldWhy It MattersRequest IDPrevents confusion between similar requestsAudit areaConnects the request to the relevant workstreamDocument or information requestedClearly defines what the client needs to provideClient contactIdentifies the person responsible for respondingRequest dateShows when the request was issuedDue dateSupports deadline managementCurrent statusMakes outstanding work visibleDate receivedRecords when the client submitted the informationCompleteness checkIdentifies missing or incomplete documentsFollow-up notesRecords communication and unresolved issuesAudit team ownerAssigns responsibility for the next actionWorkpaper referenceConnects the information to audit documentation

PBC Status Categories to Use

Keep the status definitions consistent across the engagement.

• Not Started: The request has been identified but has not yet been issued.

• Requested: The request has been sent to the client.

• Pending: The team is waiting for a response.

• Partially Received: Some, but not all, required information has been provided.

• Received—Under Review: The documents have arrived and are being evaluated for completeness.

• Follow-Up Required: Additional information or clarification is needed.

• Complete: The request has met the firm's criteria for completion.

• On Hold: The request is temporarily blocked for a documented reason.

A request should not automatically be marked complete simply because a file has been uploaded. The relevant team member should verify that the submission meets the request's defined requirements.

PBC Tracking Problems That Cause Audit Delays

Vague requests: Asking for "supporting documents" without specifying the required period, account, or information can lead to incomplete submissions.

No clear owner: When no one is responsible for follow-up, requests can remain open longer than necessary.

Outdated status updates: An inaccurate tracker can create duplicate requests and unnecessary communication.

Unstructured document storage: Files saved in inconsistent locations make it harder to identify the latest version and connect documents to workpapers.

Late escalation: A missing document may affect several audit procedures. Delaying escalation can compress the time available for review and resolution.

No distinction between receipt and completion: A received document may still be incomplete, inconsistent, or unsuitable for the intended procedure.

5. How to Integrate Confirmations, Rollforwards, and PBC Tracking

These processes should operate as connected workstreams rather than isolated spreadsheets.

For example, a PBC request may relate to an account schedule needed for rollforward work. The updated schedule may reveal a difference that requires additional supporting documentation. A confirmation may then provide evidence relevant to the same account.

If each activity is tracked separately without consistent references, the engagement team may struggle to understand how outstanding tasks affect one another.

Integrated Audit Workflow Checklist

Step 1: Set up the engagement tracker

• Create a central task tracker or use the firm's approved audit workflow platform.

• Define workstreams for confirmations, rollforwards, and PBC requests.

• Assign each task a unique reference.

• Record the owner, due date, current status, and next action.

• Link related requests and workpapers where appropriate.

Step 2: Establish task dependencies

• Identify which rollforward schedules depend on client-provided data.

• Identify confirmation requests that require additional information.

• Link open PBC items to affected audit procedures.

• Highlight tasks that could delay review or completion.

• Establish escalation rules for critical dependencies.

Step 3: Monitor progress regularly

• Review overdue and blocked items.

• Identify upcoming deadlines.

• Follow up on pending client submissions.

• Check confirmation response status.

• Review unresolved rollforward differences.

• Assign owners to new issues.

• Update the tracker after each material change.

Step 4: Prepare for audit review

• Verify that completed tasks have appropriate documentation.

• Check that workpapers are linked to supporting evidence.

• Identify unresolved exceptions and open questions.

• Confirm that review notes have assigned owners.

• Prepare a concise status report for the engagement manager.

• Escalate matters requiring professional judgment.

6. How Offshore Audit Support Can Improve Workflow Efficiency

Offshore audit support can help accounting firms manage the coordination and documentation workload associated with audit engagements.

The most effective model uses defined responsibilities, standardized procedures, and review checkpoints to help the US engagement team focus on risk assessment, significant findings, and professional judgment.

Offshore Audit Support Checklist

An appropriately trained offshore team may assist with:

• Maintaining confirmation trackers.

• Organizing confirmation requests and responses under auditor-controlled procedures.

• Monitoring nonresponses and outstanding follow-ups.

• Preparing rollforward schedules from approved source data.

• Reconciling account balances and supporting schedules.

• Maintaining PBC request lists.

• Tracking missing documents and client follow-ups.

• Organizing audit evidence and workpaper references.

• Updating task statuses and deadlines.

• Preparing open-item summaries for the engagement team.

• Organizing review notes and tracking resolution.

• Maintaining consistent documentation according to the firm's methodology.

What Should Remain With the Engagement Team?

Offshore support does not transfer the engagement team's professional responsibilities.

Depending on the applicable standards and engagement arrangements, the authorized audit team retains responsibility for matters such as:

• Determining the nature, timing, and extent of audit procedures.

• Maintaining required control over confirmation procedures.

• Evaluating the relevance and reliability of audit evidence.

• Investigating significant discrepancies.

• Making materiality and risk-related judgments.

• Evaluating whether sufficient appropriate audit evidence has been obtained.

• Reviewing significant findings and conclusions.

• Reaching the final audit conclusions and fulfilling reporting responsibilities.

The division of work should be documented and consistent with applicable professional standards, firm policies, confidentiality obligations, and engagement requirements.

7. Quality-Control Checklist for Offshore Audit Workpapers

Offshore audit support should be measured by the quality and traceability of the work, not simply the number of tasks completed.

Before a workpaper is submitted for review, use the following checklist.

Workpaper Quality Review

• The workpaper identifies the relevant client, period, and audit area.

• Source data comes from an approved location.

• Calculations and reconciliations have been checked.

• Supporting documents are clearly referenced.

• The workpaper agrees with the relevant accounting records where applicable.

• Differences and unusual movements are identified.

• Open questions are clearly documented.

• Procedures performed are described accurately.

• Review notes and outstanding actions are tracked.

• The workpaper follows the firm's documentation requirements.

• Sensitive information is stored and shared using approved systems.

• The workpaper is submitted to the designated reviewer.

Metrics Audit Firms Can Monitor

Firms can use a small set of operational metrics to identify bottlenecks and improve their processes.

MetricWhat It Helps MeasureConfirmation response statusProgress in obtaining external evidenceOutstanding PBC requestsRemaining client information dependenciesOverdue request rateFrequency of missed request deadlinesRollforward completion rateProgress on assigned schedule updatesWorkpaper review-note rateRecurring documentation or preparation issuesFirst-pass acceptance rateHow often workpapers meet review expectations without significant reworkOpen-item agingHow long unresolved tasks remain outstandingOn-time task completionReliability against agreed internal deadlines

These metrics should be interpreted in context. For example, a low confirmation response rate may reflect third-party response delays rather than offshore preparation performance.

The purpose is to identify the cause of a bottleneck, assign responsibility for addressing it, and improve the audit workflow.

8. Data Security and Confidentiality in Offshore Audit Support

Audit workpapers may contain confidential financial information, bank records, customer details, contracts, and other sensitive client data.

Before using offshore support, firms should assess the legal, regulatory, contractual, and professional requirements that apply to the engagement and the transfer or disclosure of information.

Audit Data Security Checklist

• Use approved audit software and document management platforms.

• Apply role-based access controls.

• Require multifactor authentication where available.

• Use approved secure channels for file sharing.

• Limit access to the information required for each role.

• Maintain appropriate access and activity logs.

• Define confidentiality and data-handling requirements.

• Review applicable client agreements and data-transfer restrictions.

• Establish a process for removing or updating access when assignments change.

• Train team members on security and incident-reporting procedures.

Security should be part of the offshore operating model from the beginning, not an afterthought.

9. How Intellgus Can Support Your Audit Workflow

For US CPA firms, the objective of offshore audit support is to increase operational capacity while maintaining the firm's documentation standards, quality controls, and review responsibilities.

Intellgus provides offshore accounting staffing solutions designed to support the operational needs of US businesses and accounting firms.

Depending on the engagement, offshore professionals can assist with accounting documentation, reconciliation support, workpaper preparation, schedule updates, PBC tracking, and workflow coordination.

For audit-related engagements, firms should define the scope of support, the required qualifications, the permitted access to client data, the review process, and the responsibilities retained by the engagement team.

A structured workflow can help firms:

• Organize supporting documentation.

• Improve visibility into outstanding requests.

• Track confirmation status and follow-ups.

• Prepare schedules for review.

• Identify missing information earlier.

• Reduce avoidable administrative follow-up.

• Maintain consistent workpaper organization.

• Coordinate tasks across multiple audit workstreams.

Explore Intellgus Offshore Accounting Services to learn more about offshore accounting support for your firm's operational needs.

Final Audit Readiness Checklist

Before considering these workstreams ready for review, confirm that:

Confirmations

• Requests and responses are tracked.

• Nonresponses and exceptions are identified.

• Supporting evidence is linked to the relevant workpapers.

• The authorized audit team has evaluated the results.

Rollforwards

• Updated schedules reflect the relevant reporting period.

• Balances reconcile to appropriate accounting records.

• Significant changes and exceptions are documented.

• Required procedures and review steps have been completed.

PBC tracking

• Requests have clear owners and due dates.

• Outstanding items are visible and regularly reviewed.

• Received documents are checked for completeness.

• Unresolved dependencies are escalated.

Quality and security

• Workpapers meet firm documentation standards.

• Review notes have assigned owners.

• Sensitive information is handled through approved systems.

• Responsibilities between offshore support and the engagement team are clearly defined.

Confirmations, rollforwards, and PBC tracking are more than administrative tasks. They are connected parts of an organized audit workflow that helps teams monitor evidence, identify outstanding work, and keep engagements moving toward completion.

For US CPA firms, offshore audit support can add value when it combines trained professionals, structured tracking, reliable documentation, and appropriate quality controls.

The goal is not simply to complete more tasks. It is to make audit work more organized, traceable, and ready for professional review.