CORAA University / Free fieldwork tool

Internal audit fieldwork testing tracker

Track RCM tests, samples, evidence status, exceptions, reviewer progress and report readiness across P2P, O2C, R2R, H2R, inventory, treasury, compliance and ITGC.

Build RCM Plan samples

Fieldwork profile

Entity

Engagement

Period

Fieldwork lead

Tests

Workflow

54%

Evidence

51%

In testing

Reviewed

Exceptions

Blocked

Testing tracker

Objective	Procedure	Exception	Review note
Only approved vendors are created or amended in ERP.	Select vendor master changes and agree request, approval, GST/PAN validation and maker-checker evidence.	No exception noted in selected items.	Complete reviewer sign-off before closing the test.
Invoices are matched to PO and GRN before payment.	Test invoice samples for PO, GRN, approval, tax coding, duplicate check and payment release trail.	Three invoices lacked documented quantity tolerance approval.	Validate evidence completeness, rating and management discussion before reporting.
Credit limits are approved before release of customer orders.	Test customers exceeding threshold for credit approval, ageing review and override documentation.		Complete reviewer sign-off before closing the test.
Manual journals are approved with adequate support.	Select high-value and unusual journals; inspect preparer, approver, support, posting date and reversal logic.		Complete reviewer sign-off before closing the test.
Exit cases are removed from payroll and system access on time.	Select exits and agree resignation/termination, F&F, payroll stop date, access revocation and asset recovery.		Complete reviewer sign-off before closing the test.
Slow-moving and obsolete stock is identified and reviewed.	Review ageing report, movement history, NRV basis, write-off approvals and provision computation.	Ageing report is not reviewed monthly for two warehouse locations.	Validate evidence completeness, rating and management discussion before reporting.
Bank payment rights match approved mandate and delegation matrix.	Compare bank portal users with board-approved mandate, delegation matrix and terminated-user list.		Complete reviewer sign-off before closing the test.
TDS liabilities are reconciled with books and returns before filing.	Agree books, challans, returns, 26AS/TIS where relevant, interest computation and open reconciliation items.	Two immaterial timing items cleared before filing.	Complete reviewer sign-off before closing the test.
Leaver users are disabled in ERP and finance applications promptly.	Match HR exit list with ERP, bank portal and reporting-tool active users; test closure dates and approver evidence.	Four users remained active beyond the policy timeline.	Validate evidence completeness, rating and management discussion before reporting.

P2P

65%

2 tests; 1 exceptions; 1 evidence blockers.

O2C

15%

1 tests; 0 exceptions; 1 evidence blockers.

R2R

45%

1 tests; 0 exceptions; 0 evidence blockers.

H2R

40%

1 tests; 0 exceptions; 1 evidence blockers.

Inventory

65%

1 tests; 1 exceptions; 0 evidence blockers.

Treasury

15%

1 tests; 0 exceptions; 1 evidence blockers.

Tax/Compliance

80%

1 tests; 0 exceptions; 0 evidence blockers.

ITGC

65%

1 tests; 1 exceptions; 0 evidence blockers.

Where it fits

From testing to review-ready testing

The fieldwork tracker sits between the RCM/sampling plan and the observation report. It keeps test status, evidence blockers, exceptions and reviewer readiness visible before management discussion.

Need the surrounding workpapers? Use the RCM builder, sampling plan generator, observation report generator and dashboard pack.

How an internal audit fieldwork tracker works

Internal audit fieldwork fails quietly when evidence requests, RCM test steps, sample status and exception drafting live in separate files. A tracker gives the audit manager one view of which controls are still waiting for evidence, which tests are in progress, which exceptions need management discussion and which rows are ready for review.

This tracker is structured around the RCM: cycle, test reference, control objective, procedure, population, sample size, evidence owner, evidence status, test result, rating and reviewer. It does not replace the evidence file; it makes the fieldwork file navigable.

The export is designed for weekly fieldwork calls. The Excel version gives a detailed tracker, cycle summary, exception handoff and review meeting pack. The PDF gives a concise status summary that can be attached to fieldwork updates.

Worked example - P2P fieldwork review before draft report

A P2P review has vendor master, invoice matching and payment release tests. Vendor master testing passed, but invoice matching has missing tolerance approval evidence and some PBC items are still partial.

Inputs

Evidence statusPartial for invoice testing

ResultException

RatingMedium until management discussion

Output

Cycle summaryP2P has blockers and one exception

Next stepEscalate evidence, complete exception summary, move to observation report after reviewer approval

The tracker separates fieldwork status from final reporting. An exception can be visible in fieldwork before it is mature enough for the report pack.

Common mistakes

Using the tracker as evidence

The tracker is an index and status view. Evidence still needs to be retained with source reports, screenshots, approvals, sample selections and reviewer notes.

Calling an item cleared before reviewer approval

A test may be completed by the preparer but still need review. Keep “Ready for review” and “Reviewed” separate.

Letting exceptions skip rating rationale

Exceptions should move into the report only after condition, criteria, cause, effect, recommendation, rating and management response are supportable.

Ignoring blocked evidence requests

Partial or pending evidence should be escalated early. Otherwise fieldwork completion looks high while key tests remain unsupported.

Frequently asked questions

What is an internal audit fieldwork testing tracker?+

It is a control-test status file that tracks RCM tests, sample size, evidence owner, evidence status, testing status, result, exception summary, rating, reviewer and due date.

Is this the same as an RCM?+

No. The RCM defines risks, controls and test procedures. The fieldwork tracker manages execution of those tests during fieldwork and shows what is blocked, cleared, reviewed or ready for reporting.

Should exceptions be reported directly from this tracker?+

No. The tracker identifies report candidates. Final observations should be drafted with evidence, criteria, cause, effect, recommendation, rating rationale, management response and reviewer approval.

Can this be used for P2P, O2C, R2R and ITGC audits?+

Yes. The default rows cover common cycles, and rows can be edited for any internal audit assignment or industry programme.

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 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 RCM builder →Internal audit sampling plan generator →Observation report generator →Dashboard pack generator →Cycle-wise internal audit programmes →

Share this tool

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