Glossary

Full-population testing

Full-population testing is testing every transaction in scope against a control, with no sampling.

Why Full-population testing matters to internal audit and controllers

Most audit testing still relies on samples. A clean sample says little about the items nobody looked at.

Testing the full population closes that gap for data-driven controls. Every exception is found, with its value and the people involved.

It brings a new problem: volume. A year of payments can return hundreds of hits, most of them business as usual, so the team needs a clear way to sort true exceptions from noise.

Some evidence cannot be tested from data. Stock counts and site visits still need people.

An example

A team tests whether purchase orders were approved before the invoice date. A small sample finds nothing. A test of every invoice in the year finds a cluster of late approvals at one plant. That points to a process problem worth fixing.

How IRAME handles it

IRA, IRAME's AI auditor, tests structured ERP and Excel data in full. GenAI in Document Forensics reads PDFs and scans and matches their fields to the transaction. Where your auditor still needs a sample, IRA proposes one and documents the method.

See Internal audit or read the story: Finance and accounts audit: 15 man-days of fieldwork down to about 4 man-hours.

Stop sampling. Let IRA test everything.

Bring one process. In 30 minutes we show you the exceptions IRA finds and the evidence behind each one.

Talk to sales