CORAA University / Free evidence tool

Internal audit evidence escalation tracker

Track overdue PBC requests, evidence blockers, escalation level, fieldwork impact, alternate procedures, owner response and reporting consequence before delays weaken the audit file.

Build PBC list Track fieldwork

Escalation profile

Entity

Engagement

Period

Fieldwork lead

Open items

High impact

Avg overdue

Limitations

Observations

Evidence escalation tracker

Evidence	Purpose	Alternate procedure	Owner response	Next action	Score
Invoice register with PO, GRN, tax code, approval and payment reference	Invoice three-way match and duplicate payment testing	Run vendor ledger analytics and test available high-value invoice support until full register is received.	Register extraction pending from shared-services IT.	Escalate extraction delay to Finance Controller with revised due date.	87 4 days overdue
Warehouse-wise stock ageing with last movement date and NRV/provision flag	Slow-moving inventory and provision testing	Use inventory dump plus goods-issue history to reconstruct ageing for selected SKUs.	Report sent without last movement field; revised report requested.	Agree acceptable source report fields before restarting sample selection.	100 6 days overdue
Active ERP users, leaver list, privileged role listing and last-login report	Leaver access and privileged user testing	None required if received files reconcile to HR exit list.	Listings shared; bank portal report still separate.	Perform completeness tie-out before sample testing.	28 0 days overdue
Monthly TDS payable reconciliation, challans, return acknowledgements and interest workings	TDS filing and reconciliation control testing	Tie GL control accounts to available challans and list unreconciled months separately.	June reconciliation under review by external consultant.	Escalate open months and agree management representation if not received.	96 7 days overdue
Credit-limit approval listing and override orders for top customers	Credit control override testing	Run ageing and blocked-order report while approval listing is awaited.	Owner committed to share by revised due date.	Recheck status after revised due date.	42 0 days overdue
Latest delegation of authority matrix and board-approved policy changes	Control design and approval authority mapping	Use prior approved matrix only for background; do not conclude on current design until current policy is evidenced.	Updated matrix pending board ratification.	Document limitation and identify tests affected by missing authority matrix.	100 5 days overdue

PBC-INV-03 / Inventory

100

Escalate to CFO/CXO and document potential limitation or report impact.

PBC-ELC-02 / Entity-level

100

Escalate to CFO/CXO and document potential limitation or report impact.

PBC-TAX-02 / Tax/Compliance

Escalate to CFO/CXO and document potential limitation or report impact.

PBC-P2P-04 / P2P

Escalate to CFO/CXO and document potential limitation or report impact.

PBC-O2C-05 / O2C

Monitor until due date.

Where it fits

From PBC to evidence-controlled fieldwork

The escalation tracker sits between the PBC list and fieldwork tracker. It turns missing documents into visible blockers, alternate-procedure decisions and reporting consequences before the file reaches review.

Start with the data request list, track testing in the fieldwork tracker, then move supported exceptions into the observation report generator.

How an internal audit evidence escalation tracker works

Internal audit evidence delays are not just administrative delays. Missing source reports can block sample selection, prevent completeness checks, weaken operating-effectiveness conclusions and delay management discussion. A good tracker separates ordinary follow-up from evidence gaps that affect scope or reporting.

This tracker ranks open requests by status, days overdue, escalation level and fieldwork impact. Received evidence is not treated as closed until the reviewer accepts completeness and relevance in the audit file.

The export is built for weekly fieldwork calls: one sheet for all requests, one for escalation meetings, one for alternate procedures and one for reporting impact. That makes the tracker useful for auditors, CA firms and enterprise internal audit teams.

Worked example - inventory ageing report is unusable

The inventory team provides an ageing report without last movement date. The auditor cannot conclude on slow-moving stock and NRV provision testing from the file received.

Inputs

StatusRejected

Fieldwork impactHigh

Report consequenceAlternate procedure needed

Output

Escalation actionEscalate to process head/CFO and agree acceptable report fields

Alternate workReconstruct ageing from inventory dump and goods-issue history for selected SKUs

The tracker makes the evidence quality issue visible before the testing file falsely appears complete.

Common mistakes

Treating partial files as complete evidence

Partial evidence may support background understanding but not necessarily testing. Keep “Partial”, “Rejected” and “Not available” separate from “Received”.

Escalating without fieldwork impact

Escalations should explain what test is blocked, which assertion is affected and whether alternate procedures can address the same risk.

Using alternate procedures too casually

Alternate work is not automatically equivalent. The reviewer should decide whether it addresses completeness, accuracy, occurrence, authorization or cut-off sufficiently.

Waiting until report drafting

Evidence blockers should be escalated during fieldwork. Late escalation creates avoidable scope limitations and weak management responses.

Frequently asked questions

What is a PBC delay tracker?+

It is a tracker for evidence requested from management or process owners, showing owner, due date, status, follow-up, escalation level, fieldwork impact and next action.

When should an evidence request be escalated?+

Escalate when evidence is overdue, incomplete, rejected, unavailable, or blocks sample selection, control testing, alternate procedure design or report finalisation.

Does received evidence mean the request is closed?+

No. The evidence should still be checked for completeness, relevance, period coverage, source-system reliability and reviewer acceptance before the audit file relies on it.

Can missing evidence become an internal audit observation?+

Sometimes. Missing evidence may indicate weak record retention, poor system reporting, delayed ownership or a scope limitation. It should be reported only after professional review and management discussion.

Authoritative sources

ICAI

ICAI IASB - Standards on Internal Audit — ICAI publishes Standards on Internal Audit covering assignment planning, evidence, documentation, reporting and follow-up.

MCA

Companies (Accounts) Rules, 2014 - Rule 13 — Rule 13(2) frames internal audit scope, functioning, periodicity and methodology through Audit Committee or Board consultation.

Always confirm against the latest version of the source. Regulations evolve and amendments are common.

Related calculators

Internal audit data request list →Fieldwork testing tracker →Observation report generator →Dashboard pack generator →Internal Audit module →

Share this tool

Last reviewed: 2026-08-30 · For informational purposes only — not professional advice.