Reason for Audit Delays #3: Weak PBC Packs—How to Build Audit-Ready Schedules That Prevent Back-and-Forth

That document set is the PBC pack: Prepared-By-Client schedules and supporting evidence.

When the PBC pack is strong, auditors can test efficiently, resolve queries quickly, and complete fieldwork on schedule. When the PBC pack is weak, the audit slows down for a simple reason: the audit team is forced to spend time reconstructing support that should already exist—tying numbers, chasing documents, and validating logic that was not clearly presented.

Across Jamaica and the wider Caribbean, weak PBC packs are one of the most common causes of late audits because they create friction at every step: planning, testing, review, partner sign-off, and final reporting. The good news is that this is one of the most fixable problems in audit readiness—because it is a matter of structure, discipline, and presentation.

This article explains what makes a PBC pack “audit-ready,” the common PBC failures that create delays, and a practical framework you can adopt to deliver schedules “first-time-right.”

What a PBC pack is—and why it matters more than you think

A PBC pack is not “whatever documents the auditor asks for.” It is a curated, structured package that:

• ties directly to the final trial balance

• explains what each balance represents

• provides supporting evidence

• demonstrates management’s review and control

• makes it easy for an auditor to trace and test

Audits run late when organizations treat PBC requests as a reactive checklist. The most efficient audits occur when management provides a proactive, organized PBC pack that anticipates the audit team’s needs.

If you want a reliable audit timeline, you must treat the PBC pack as a deliverable that is planned, prepared, reviewed, and controlled.

The “weak PBC pack” symptoms auditors see immediately

A PBC pack is weak when it shows any of the following:

1. Schedules don’t tie to the trial balance
   Numbers appear without a clear linkage to the ledger, or the audit team must guess which accounts are included.

2. Evidence is missing or scattered
   Documents are sent through email chains, WhatsApp messages, personal devices, or multiple drive folders without indexing.

3. Inconsistent formats and unclear logic
   Different preparers use different formats and naming conventions. Supporting calculations lack transparency.

4. No cross-referencing
   The schedule and evidence are not linked. Auditors waste time locating invoices, contracts, and approvals.

5. Data dumps instead of audit-ready schedules
   Large reports are exported from the system, but they are not summarized, reconciled, or explained.

6. No management review evidence
   There are no sign-offs, review notes, or evidence that management validated the schedules.

7. Late delivery in fragments
   Schedules arrive in partial form over many days, making it difficult to plan and execute testing.

Each of these issues forces auditors to stop, query, and re-test. Multiply that across multiple cycles and multiple reporting areas, and delay becomes inevitable.

What an “audit-ready” PBC pack looks like

An audit-ready PBC pack has three characteristics: traceability, completeness, and usability.

1) Traceability: everything ties back to the trial balance

Every schedule should:

• state the TB line and account numbers covered

• show the TB balance (per ledger)

• reconcile the schedule total to the TB balance (no unexplained differences)

2) Completeness: evidence supports the numbers and the story

Every material balance should have:

• reconciliation where applicable

• supporting documents (contracts, invoices, statements, filings, approvals)

• explanations for unusual movements, provisions, estimates, or judgments

3) Usability: easy for auditors to test without asking follow-ups

Usability is often neglected. It includes:

• clear file naming

• logical folder structure

• a consistent schedule format

• an index that tells the auditor where everything is

If auditors can find and test evidence quickly, the audit moves quickly.

The PBC pack framework: how to build it properly

Step 1: Create a PBC Index (the single best audit accelerator)

A PBC Index is a spreadsheet or document that lists every deliverable, with:

• item number

• description

• owner

• due date

• status

• file link/location

• notes (e.g., “pending board approval,” “awaiting bank confirmation”)

This is the audit’s navigation system. It prevents confusion and reduces repetitive requests.

Step 2: Use a standard folder structure (same every year)

A proven structure is:

01_Governance & Planning

• engagement letter, timelines, audit planning notes

• board minutes, AGM documents

• accounting policies and memos

02_Financial Statements & Trial Balance

• final TB, mapping, JE listing

• draft financial statements and disclosure checklists

03_Cash & Banking

• bank recons, statements, confirmations, FX support

04_Receivables & Revenue

• AR ageing, bad debt provision, revenue cut-off support, key contracts

05_Payables & Expenses

• AP ageing, supplier reconciliations, accrual schedule support

06_Payroll & Statutory

• payroll summaries, statutory deductions reconciliation, remittance proofs

07_Inventory

• count packs, variance logs, valuation support, obsolescence analysis

08_Fixed Assets

• FAR/GL recon, additions/disposals, depreciation schedule

09_Tax

• current tax computation, deferred tax schedules, filings and assessments

10_Intercompany & Related Parties

• intercompany matrix, confirmations, related party register and approvals

11_Debt & Equity

• loan agreements, covenant calculations, share movements, minutes

12_Other / Subsequent Events

• events after year-end, commitments, contingencies, legal letters (if applicable)

This structure works for SMEs, groups, and regulated entities because it aligns to audit cycles.

Step 3: Standardize schedules (“first-time-right” templates)

At minimum, standardize:

• lead schedules (tie to TB)

• reconciliation templates

• provision and estimate templates (bad debts, inventory obsolescence)

• accrual schedules

• intercompany matrix

• movement schedules for fixed assets, debt, equity

Standardization improves audit speed because auditors learn your “language.” It also reduces internal time spent reinventing schedules each year.

Step 4: Build cross-referencing into every schedule

A schedule should reference the evidence by:

• document name

• document ID (or file name)

• page reference where relevant

Example: If an accrual includes legal fees, the schedule should point to the engagement letter, invoice, and approval.

Cross-referencing is what prevents “back-and-forth.”

Step 5: Implement review and sign-off

Every PBC schedule should have:

• prepared by

• reviewed by

• date

• review notes (if any)

Management sign-off is not cosmetic. It tells auditors the schedule is controlled and reduces follow-up questions.

The five PBC schedules that cause the most delays (and how to fix them)

1) Lead schedules that don’t tie to TB

Fix: include TB balance, schedule total, and reconciling difference explanation. No schedule should be delivered without a tie-out.

2) Accrual schedules with weak support

Fix: add evidence for each material accrual, include basis (contract/invoice/timing), and include cut-off logic.

3) Provisions and estimates (bad debts, inventory obsolescence)

Fix: document the policy, method, assumptions, and evidence. Provide a movement schedule (opening, additions, reversals, closing).

4) Intercompany balances presented as “net” or “plug”

Fix: provide an intercompany matrix by entity and counterparty, with documentation for charges and settlements.

5) Revenue support delivered as a data dump

Fix: summarize and reconcile revenue by stream, provide key contracts, and include cut-off evidence for period end.

PBC delivery timing: the “batching” rule that improves audit speed

One of the fastest ways to reduce audit delays is to change how you deliver PBC items.

Avoid: sending schedules one by one over weeks.

Adopt: deliver in batches aligned to audit cycles:

• Batch 1 (Planning): TB, draft FS, policies, key agreements

• Batch 2 (Core): cash, AR, AP, payroll, tax

• Batch 3 (Complex): inventory, fixed assets, intercompany, provisions

• Batch 4 (Final): subsequent events, representation letter drafts, final disclosures

Batching improves audit planning and reduces repeated queries.

A practical 21-day plan to build an audit-ready PBC pack

If you are behind, you can still get audit-ready quickly.

Week 1: Structure and index

• set up folder structure

• build the PBC index

• assign owners

• upload TB, draft FS, JE listing

Week 2: Core schedules and evidence

• cash and bank

• AR and revenue support

• AP and accruals

• payroll and statutory deductions

• tax schedules

Week 3: Complex schedules and governance

• inventory pack (if applicable)

• fixed assets

• intercompany and related parties

• board minutes and key approvals

• subsequent events review

By day 21, most organizations can reach “audit-ready” status if ownership and deadlines are enforced.

Tools and practices that make PBC packs easier (even without major systems)

You do not need expensive systems to improve PBC quality. You need discipline.

Simple practices that work:

• file naming conventions (Year_End_Account_Schedule_Version_Date)

• single evidence repository (one drive, one structure)

• version control (avoid “final_final_v7”)

• PBC index updated daily during fieldwork

• one finance point of contact for audit coordination

Where possible, consider a document management platform, but do not wait for technology to fix a process problem.

Closing perspective: the PBC pack is your audit experience

A weak PBC pack makes the audit feel like friction. A strong PBC pack makes it feel like verification.

In practical terms, PBC excellence:

• shortens fieldwork

• reduces follow-ups

• decreases audit fatigue

• improves realization and internal efficiency

• strengthens governance and reporting credibility.

If your organization wants on-time audits, PBC quality is one of the highest-return improvements you can make—because it is largely within your control.

Next Step: request a proposal

If your organization wants to reduce audit delays by improving PBC pack quality, schedule structure, and evidence traceability, Dawgen Global can support you with Audit Readiness, PBC Pack Design, and Close Acceleration (“Close Sprint”) across Jamaica and the wider Caribbean.

Request a proposal by emailing [email protected] with the subject line: “PBC Pack Proposal Request”. Please include your year-end date, industry, number of entities/locations, whether inventory is material, and your current audit timeline. We will respond with a structured scope, deliverables, and an execution timetable tailored to your organization.