Reason for Audit Delays #9: Controls and Documentation Break Down—How to Strengthen Evidence, Approvals, and Audit Trails Quickly

In audit season, delays are often blamed on “too many audit requests” or “auditors asking for everything.” In reality, the most common cause is simpler and more uncomfortable: the evidence is not audit-ready.

Auditors do not audit intent. They audit controls, documentation, and traceable evidence. When approvals are informal, audit trails are fragmented, and supporting documents are scattered across email chains, WhatsApp threads, personal devices, and inconsistent folders, audit work slows down—because every conclusion requires follow-up, reconstruction, and re-testing.

This challenge is particularly common across Jamaica and the wider Caribbean where finance teams often operate lean, processes have grown organically, and documentation standards may not have been formalized. The result is a predictable audit pattern:

• questions that should take minutes take days,

• testing expands because controls cannot be relied upon,

• review notes multiply because evidence is incomplete, and

• sign-off is delayed because auditors cannot finalize their conclusions.

This article addresses the ninth major cause of late audits: controls and documentation break down—and presents a practical, rapid approach to strengthen evidence discipline, approvals, and audit trails without creating bureaucracy.

Why documentation and controls failures delay audits (the audit logic)

Auditors design their work around two levers:

1. Reliance on controls (if controls are strong and evidenced, audit testing can be more efficient), and

2. Substantive testing (if controls are weak or not evidenced, auditors expand substantive procedures).

When documentation breaks down, auditors cannot rely on controls. They must:

• increase sample sizes,

• perform more detailed testing,

• request additional evidence,

• escalate issues to senior reviewers, and

• take more time to reach audit conclusions.

This is why documentation quality is not “administrative.” It is a direct driver of audit effort, audit fees, and audit timelines.

What “controls and documentation breakdown” looks like in practice

Auditors typically observe the same recurring patterns:

1) Approvals exist, but cannot be evidenced

Management says “this was approved,” but there is no documented approval trail—no signed purchase requisition, no email approval, no system approval workflow, no board minute extract, and no delegation-of-authority alignment.

2) Evidence is scattered and inconsistently stored

Invoices are in one folder, contracts in another, bank proofs somewhere else, and payroll evidence on personal drives. Version control is unclear.

3) Processes are performed, but not documented

For example:

• credit limits are “managed,” but there is no credit policy or approvals log.

• inventory shrink is “monitored,” but there is no shrinkage report or write-off approvals.

• journal entries are “reviewed,” but there is no review evidence.

4) Manual work is high, but controls are low

Spreadsheets drive key balances (accruals, provisions, intercompany, fixed assets), but there is no change control, review gate, or audit trail of who changed what and why.

5) Exception handling is informal

When exceptions occur—overrides, late postings, back-dated invoices, credit notes, write-offs—there is no exception log, no documented rationale, and no approval evidence.

These patterns create audit friction because auditors cannot distinguish between a controlled process and an uncontrolled one.

The “Audit Evidence Standard”: what auditors need to see

You do not need perfect systems. You need evidence that can be traced.

An audit-ready evidence standard typically includes:

• Traceability: every number can be traced to source documentation or system reports.

• Completeness: all key documents exist, not only some.

• Consistency: documents are stored in a consistent structure and naming convention.

• Integrity: evidence is controlled (versioning, approvals, limited edits).

• Review: there is proof that a knowledgeable person reviewed and approved key items.

If you can build these five qualities into your finance workflow, audit delays reduce dramatically.

The “Big Six” controls that cause the most audit delays when documentation is weak

Below are six high-impact control areas that, when undocumented, typically slow audits across Jamaica and the Caribbean.

1) Purchasing and payables approvals

Audit focus: authorization, completeness of liabilities, risk of unauthorized spend.

Common breakdowns:

• purchase orders not consistently used

• approvals not retained

• three-way matching not documented

Quick fix:

• implement a simple Delegation of Authority (DOA) matrix

• retain approval evidence (system workflow or email approvals saved centrally)

• maintain a three-way match checklist for material purchases

2) Revenue and credit controls

Audit focus: occurrence, cut-off, credit note controls, risk of fictitious sales.

Common breakdowns:

• back-dated invoices without approvals

• credit notes issued without reason codes or approvals

• delivery evidence missing

Quick fix:

• cut-off exception log (year-end especially)

• credit note register with reason codes and approvals

• standard delivery/acceptance evidence rules

3) Payroll approvals and changes

Audit focus: existence of employees, authorization of pay changes, accuracy of deductions.

Common breakdowns:

• salary changes approved verbally

• overtime approvals unclear

• termination documentation incomplete

Quick fix:

• retain HR approval documents centrally

• payroll change log with approvals

• monthly payroll reconciliation with sign-off

4) Journal entries and period-end adjustments

Audit focus: risk of management override; appropriateness of adjustments.

Common breakdowns:

• journals posted without documented support

• no review evidence

• late journals near year-end without explanation

Quick fix:

• journal entry (JE) pack for material journals: rationale + support + preparer/reviewer sign-off

• JE exception log for late or unusual entries

• restriction of posting rights and review of super-user access

5) Inventory adjustments and write-offs

Audit focus: existence, valuation, shrinkage risk.

Common breakdowns:

• adjustments posted without variance analysis

• write-offs without approvals

• shrinkage not analyzed

Quick fix:

• inventory variance log with root cause and approvals

• write-off approval workflow

• periodic shrinkage reports and trend review

6) Fixed assets and capex approvals

Audit focus: existence, classification, depreciation accuracy.

Common breakdowns:

• additions not supported by approvals/invoices

• disposals not documented

• FAR not controlled

Quick fix:

• capex approval pack for material additions

• disposal checklist and documentation retention

• FAR to GL reconciliation sign-off

The Evidence Operating Model: how to strengthen documentation without bureaucracy

Most organizations fail by trying to “document everything.” The better approach is to document what matters most and do it consistently.

Step 1: Define “Key Evidence Sets” by process

For most organizations, the key evidence sets are:

• revenue and cut-off

• purchasing and payables

• payroll and statutory

• inventory (if material)

• fixed assets

• journals and estimates

• tax and compliance.

For each set, define:

• minimum required documents

• who owns them

• where they are stored.

Step 2: Create a single evidence repository with a consistent structure

Use the PBC folder approach described in earlier articles. The key is one place, one structure, and consistent naming.

Step 3: Implement an approvals and exception log discipline

Not everything needs a log. But exceptions do. Maintain logs for:

• credit notes and returns

• back-dated invoices/dispatch notes

• manual journal entries above a threshold

• write-offs and adjustments

• non-standard related party transactions.

Logs reduce audit queries because they demonstrate control over exceptions.

Step 4: Build review gates into the close calendar

Evidence of review is a powerful audit accelerant. Require sign-off for:

• key reconciliations

• material accruals and provisions

• journal entry packs

• management review variance analysis.

Step 5: Standardize templates for high-risk schedules

Templates reduce rework and make evidence consistent. Standardize:

• JE support template

• variance analysis template

• approvals checklist template

• exception log templates.

The 30-day “Evidence Upgrade” plan (high impact, fast implementation)

If documentation has delayed audits before, use this plan:

Week 1: Evidence structure and governance

• establish document repository and naming standards

• publish DOA matrix and approvals retention rule

• create logs (JE, credit notes, write-offs, cut-off exceptions)

Week 2: Close pack discipline

• implement reconciliation sign-offs

• implement JE packs for material entries

• build management review variance analysis with sign-off

Week 3: Process evidence strengthening

• revenue cut-off evidence rules and register

• purchasing three-way match evidence for material spend

• payroll change log and statutory reconciliation

Week 4: Audit-ready packaging

• index evidence to PBC pack

• run an internal “mock audit” walkthrough of evidence traceability

• fix the highest friction points before external auditors arrive

By day 30, most organizations can shift from “evidence chasing” to “evidence ready.”

How to reduce audit testing through better control evidence (practical guidance)

Auditors can often reduce testing when they can rely on controls. You can support that outcome by providing:

• clear DOA and approval evidence

• consistent reconciliations with review sign-off

• controlled access (especially for journals and master data)

• exception logs and evidence of follow-up

• documented policies for key judgments (revenue, inventory, provisions)

These are not theoretical. They are the signals auditors use to determine whether they can test less and conclude faster.

Common pitfalls (and how to avoid them)

Pitfall 1: Creating policies but not evidence

A policy without evidence does not improve audit speed. The goal is not to write policies—it is to show controlled execution.

Pitfall 2: Over-documenting low-risk activities

This burns capacity. Focus on material balances and high-risk processes.

Pitfall 3: Storing evidence but not indexing it

If evidence exists but cannot be found quickly, it is operationally equivalent to missing evidence. Index and cross-reference.

Pitfall 4: No ownership of documentation

Assign owners per evidence set; otherwise accountability fails.

Pitfall 5: Weak change control over spreadsheets

If spreadsheets are material, lock formulas, control versions, and evidence review.

Documentation KPIs that predict on-time audits

• percentage of key reconciliations signed off by deadline

• number of material journals without JE packs (target zero)

• number of exceptions without approvals (target zero)

• average time to respond to PBC requests (target <48 hours during fieldwork)

• percentage of evidence stored in the correct repository (target high)

• number of late-stage audit queries due to missing documentation (target declining trend)

These metrics make evidence discipline measurable and sustainable.

Closing perspective: audits run late when evidence is weak—not when the audit is “hard”

Auditors cannot sign opinions based on confidence or familiarity. They sign based on evidence. When controls and documentation break down, audit effort expands, queries increase, and timelines slip.

The fix is not excessive bureaucracy. The fix is a practical evidence operating model:

• define key evidence sets,

• store evidence in a consistent repository,

• log and approve exceptions,

• enforce review gates, and

• standardize high-risk templates.

When you do that, audits move from chasing documents to verifying conclusions—and sign-off becomes faster and more predictable.

Next Step: request a proposal

If your organization wants to reduce audit delays by strengthening controls, approval evidence, documentation standards, and audit trails, Dawgen Global can support you across Jamaica and the wider Caribbean with Audit Evidence Readiness, Controls Documentation, Close Acceleration (“Close Sprint”), and end-to-end Audit + Compliance services.

Request a proposal by emailing [email protected] with the subject line: “Audit Evidence Readiness Proposal Request”. Please include your year-end date, key processes (inventory, payroll, multi-entity), whether you rely heavily on spreadsheets, and your current audit timeline. We will respond with a structured scope, deliverables, and an execution timetable tailored to your organization.

About Dawgen Global