What Is A Compliance Audit?
The documented procedures are the part an auditor can see. Start from the HR Compliance Policies and Procedures Manual for the employment side, or the Small Business Policies and Procedures Manual for a broader documented base.
The letter arrives, or the customer questionnaire does, and the word audit lands in your inbox. The first question is rarely how to pass. It is what is actually going to be asked for, and whether the records exist in a form somebody outside the business can read.
A compliance audit is narrower and more mechanical than most people expect. It checks one operation against one defined set of rules, and documented evidence forms its backbone, often alongside interviews, observation, or system testing. This article defines the term, separates it from the internal audit it gets confused with, and then does something the definition pages skip: it works through the exact evidence set an auditor asks for on a single real requirement, so you can see the shape of the request before it arrives.
What Is a Compliance Audit?
A compliance audit is a formal review that tests whether an organization is following a specific external rule, using documented evidence and any interviews, observations, or tests required by the engagement. The rule can be a federal regulation, a state filing requirement, a licence condition, an industry standard, or a clause in a customer contract. The audit does not primarily judge whether your process is efficient or sensible. It judges whether it matches the requirement and whether you can prove it.
Three things commonly frame the scope of a compliance audit before it starts. First, the criteria: the exact rule being tested, often cited down to a section number. Second, the period under review, which is usually a defined stretch of time. Third, the population: the employees, transactions, sites, or records the auditor may examine.
Which rules apply to you depends on what you sell, how you employ people, and where you operate. The Small Business Administration states that a business’s legal responsibilities depend on its type and location, and its guidance on staying legally compliant directs owners to applicable filing, licensing, permit, and recordkeeping requirements.
That is the useful mental model. There is no single compliance audit. There is a compliance audit against a named requirement, and a business of any size is usually exposed to several of them at once.
Who Runs a Compliance Audit?
Four common parties commission compliance audits, and the difference matters because it changes what happens when something is wrong.
- A regulator or agency. A government body tests you against a statute or regulation it enforces. The outcome can carry back pay, penalties or a corrective order.
- An accredited certification body. A registrar audits a management system against a published standard and issues or withholds a certificate.
- A customer or prime contractor. A buyer audits you against the terms of a contract or a supplier code before awarding or renewing work.
- Your own organization. You commission the same test internally, before anybody else does, to find and close the gaps while they are still cheap.
The fourth case is the one you control, and it is why a documented internal audit checklist is worth building before an external party sets the agenda. The evidence an external auditor wants often overlaps with what your own reviewer would examine, although the scope and consequences can differ.
A compliance auditor’s role is narrow by design. They gather evidence against stated criteria, perform the tests required by the engagement, and report findings. Where independence rules apply, process advice is kept separate from the audit conclusion so the auditor does not end up reviewing their own work.
Compliance Audit vs Internal Audit
These two terms overlap enough to cause real confusion, because an internal audit can include compliance testing. This practical comparison focuses on the primary yardstick, while recognizing that an internal audit can also examine governance, risk, and control effectiveness.
| Dimension | Compliance audit | Internal audit |
|---|---|---|
| Measured against | An external rule, standard or contract clause | Your own policies, controls and objectives |
| Question asked | Does this meet the requirement? | Is this control working and is the risk covered? |
| Typical trigger | A regulator, certification cycle, customer or licence renewal | An annual plan set by management or the board |
| Scope | Narrow, fixed by the cited criteria | Broad, set by risk and reset each cycle |
| Usual output | A conformity or nonconformity finding | A recommendation to improve |
| Who sees it | Often an outside party | Usually management only |
The practical consequence is about tolerance. An internal audit can conclude that a control is weak but acceptable given the risk. A compliance audit has far less room for that judgment, because the requirement either was met during the period or it was not. If you want the mechanics of how evidence gets tested in either case, the walkthrough of internal audit testing covers sampling and test design in detail.
What an Auditor Actually Asks For: A Worked Evidence Set
Definitions of compliance audits are easy to find. What is harder to find is the document list. So here is one requirement, worked all the way down to the artefacts, using federal wage and hour recordkeeping as the example because many covered employers must maintain these records.
The requirement is 29 CFR Part 516, the recordkeeping regulations under the Fair Labor Standards Act. The Department of Labor summarises it in Fact Sheet 21, which states that every covered employer must keep certain records for each non-exempt worker, that the Act requires no particular form for the records, and that the records must be accurate.
Read that carefully, because it shows the logic of this compliance test. The FLSA does not prescribe a particular record form, but it does require specific content. The issue is therefore whether the required data is complete and accurate, not whether every employer uses the same filing system.
Here is the list of basic records the fact sheet says a covered employer must maintain, paired with an illustrative small-business artefact that may carry each item. The second column is an operational example, not a regulator-prescribed format. Assemble it column by column and you have built the evidence pack before anybody asks for it.
| Required data item | Where the proof normally lives |
|---|---|
| Employee’s full name and social security number | Signed new hire form and payroll master record |
| Address, including zip code | Payroll master record |
| Birth date, if younger than 19 | New hire file, age verification |
| Sex and occupation | Payroll master record and job description |
| Time and day of week when the workweek begins | Written pay policy and payroll system configuration |
| Hours worked each day | Timecards, clock export or signed schedule exception record |
| Total hours worked each workweek | Weekly timesheet summary |
| Basis on which wages are paid | Offer letter or pay rate change form |
| Regular hourly pay rate | Payroll register |
| Total daily or weekly straight-time earnings | Payroll register |
| Total overtime earnings for the workweek | Payroll register |
| All additions to or deductions from wages | Deduction authorisations and payroll register |
| Total wages paid each pay period | Payroll register and general ledger posting |
| Date of payment and the pay period covered | Pay stub and bank payment file |

Two more details in the same fact sheet decide whether the pack survives contact with an auditor. The first is retention, and it is not a single period. Fact Sheet 21 states that each employer shall preserve for at least three years payroll records, collective bargaining agreements, and sales and purchase records, while the records on which wage computations are based, such as time cards, piece work tickets, wage rate tables, work and time schedules, and records of additions to or deductions from wages, should be retained for two years.
The second is access. The fact sheet is explicit that these records must be open for inspection by the Division’s representatives, who may ask the employer to make extensions, computations, or transcriptions. Records that exist but cannot be produced in a readable form during the visit are a practical failure even when the underlying data is complete.
That is a reusable pattern. Take a named requirement, extract the specific items it demands, name the artefact that carries each item, confirm the retention period, and confirm somebody can retrieve it on request. Repeat for every requirement that applies to you and you have built a compliance evidence register. It is one of the most useful things an operations manager can produce before a first audit.
The Compliance Audit Process, Step by Step
A common operating pattern for compliance audits has six stages, although the order and terminology vary by regulator, standard, contract, and engagement.
Step 1: Scope and Criteria Are Fixed
The auditor states the rule being tested, the period under review and the sites or entities included. Ask for this in writing. An audit without a written scope tends to expand during fieldwork.
Step 2: The Document Request Arrives
You receive a list of records, usually with a deadline that is shorter than you would like. This is where a prepared evidence register converts weeks of scrambling into a morning of retrieval.
Step 3: Documents Shape the Interviews and Tests
Document review commonly establishes what your written policies and procedures say should happen. Gaps found there can shape later interviews, observations, and tests, but the exact sequence depends on the engagement.
Step 4: A Sample Is Tested
The auditor may select a sample of employees, transactions, or records and trace each one to its supporting evidence. Sample results contribute to findings alongside any interviews, observations, system tests, or full-population checks in scope.
Step 5: Findings Are Raised and You Respond
Each finding cites the requirement, the evidence examined and the gap. You get an opportunity to supply missing evidence or dispute the reading before the report is finalised. Use it, and supply documents rather than explanations.
Step 6: Corrective Action Is Agreed and Verified
You commit to a fix with an owner and a date, and the auditor verifies it, either at the next visit or through submitted evidence. A closed finding needs proof, not a promise.
Compliance Audit Examples by Requirement
The evidence-set pattern above works on any requirement. Three short examples show how differently the same pattern lands depending on the rule.
Wage and Hour Recordkeeping
Criteria are the FLSA recordkeeping regulations. Evidence is the payroll and timekeeping pack described above. The Wage and Hour Division publishes the supporting material itself, with tools, fact sheets, posters and other guidance organized by topic, including compliance toolkits by industry, so the criteria are not a secret you have to reverse engineer.
Workplace Injury and Illness Records
Criteria here come with a much longer clock. Under 29 CFR 1904.33, you must save the OSHA 300 Log, the privacy case list if one exists, the annual summary, and the OSHA 301 Incident Report forms for five years following the end of the calendar year the records cover. The same section requires you to update stored 300 Logs during that storage period when newly recordable cases are discovered or a classification changes, which is a maintenance obligation, not just a filing one.
Federal Award Spending
Some compliance audits are triggered by a number rather than by an event. Under 2 CFR 200.501, a non-federal entity that expends $1,000,000 or more in federal awards during its fiscal year must have a single or program-specific audit conducted for that year. Entities below the threshold are exempt from federal audit requirements for that year, but the same section states that their records must remain available for review or audit. Exempt from the audit is not the same as exempt from the records.
Notice what the three have in common. Each names a specific artefact, each attaches a retention period, and each assumes somebody can produce the record on request. That is the evidence backbone they share.
Can You Fail a Compliance Audit?
Many compliance audits report findings or nonconformities rather than a simple pass or fail grade. The labels and consequences vary by governing framework. Some schemes distinguish minor from major findings, while regulators and customers may use different terminology and remedies.
Three common failure modes are worth testing in advance, and only one of them is about actually breaking the rule.
- The requirement was genuinely not met. Overtime was miscalculated, a licence lapsed, a required form was never filed. This is the real thing and it needs a real fix.
- The requirement was met but cannot be evidenced. The work happened, the record does not exist, was not retained for the required period, or cannot be retrieved. An auditor can only conclude from evidence.
- Practice has drifted from the written procedure. Your documented process says one thing and the sample shows another. This one is often found during the document review before any testing begins.
The second and third failure modes are documentation problems wearing a compliance costume, and they are the ones a business can eliminate in advance.
How To Prepare Before the Auditor Arrives
Preparation is not a special project. It is building, once, the evidence register the audit will ask you to produce anyway.

- List the requirements that actually apply. Employment, tax, licensing, safety, privacy, industry rules, and every compliance clause sitting inside a live customer contract. Cite each one down to the section.
- Name the artefact for every requirement. One row per required item, one named document per row, one named owner. Blank cells are your finding list, found early and for free.
- Record the retention period beside each artefact. Retention differs by rule, from two years on the records that support wage calculations to five years on OSHA injury records. A single company-wide retention rule will be wrong in both directions.
- Write the procedure down. A compliance audit reads your written process first. If it does not exist, the auditor has nothing to test practice against, and you have nothing to defend it with. The guide to workplace policies and procedures covers how to structure that documentation.
- Test a sample yourself. Pick five employees or five transactions and trace them end to end. Self-testing can surface issues an auditor may also identify.
- Fix the retrieval problem. If producing a record takes days, that is a finding in waiting. Controlled indexing, permissions, version history, and retrieval workflows in management system software can make the evidence set easier to maintain and produce.
Do this once and the audit stops being an event you brace for. It becomes a request you already have an answer to.
Frequently Asked Questions
What is an example of a compliance audit?
A Wage and Hour Division review of your payroll and timekeeping records against the FLSA recordkeeping regulations is a common example. The auditor names the period, requests the payroll register and time records for a sample of non-exempt employees, and checks that each required data item is present, accurate and retained for the required period.
Can you fail a compliance audit?
Many compliance audits issue findings or nonconformities rather than a simple pass or fail grade. The labels and consequences depend on the governing framework. A serious unresolved finding may affect a certificate, contract, or licence, while a regulatory audit may carry remedies such as back pay or penalties where the applicable law allows them.
What is the role of a compliance auditor?
The compliance auditor gathers evidence against stated criteria, performs the tests required by the engagement, and reports findings. The role is deliberately narrow. Where independence rules apply, process advice should remain separate from the audit conclusion.
How is a compliance audit different from an internal audit?
The difference is the yardstick, not the auditor. A compliance audit measures you against an external rule, standard or contract clause and asks whether the requirement was met. An internal audit measures you against your own policies, controls and objectives and asks whether the control is working and the risk is covered. An internal team can perform either one.
How long should you keep records for a compliance audit?
Retention is set by each requirement, not by a general rule. Under the FLSA recordkeeping regulations, payroll records, collective bargaining agreements, and sales and purchase records are preserved for at least three years, while the records wage computations are based on are retained for two. OSHA injury and illness records run five years past the end of the calendar year they cover. Record the period next to each artefact rather than applying one company-wide default.
What should you do if you cannot find a requested record?
Disclose the gap promptly, explain what you do hold, and ask the auditor or regulator whether secondary evidence is acceptable. Do not alter or backfill a record deceptively. Then treat the missing record as a corrective action with an owner and a date so the retrieval problem is fixed, not just the immediate request answered.
Make the Documentation Line the Easy One
A compliance audit is an evidence test with a regulator’s letterhead, a certification standard, or a contract behind it. The rule should be identified, the required items should be clear, and applicable retention periods should be recorded. What separates a difficult audit from a quiet one is whether somebody wrote the procedure down and whether the evidence can be produced on the day it is requested.
So build the evidence register before anybody asks for it, write the procedures that the register points to, and test a sample yourself. The audit then examines a system you already understand, rather than discovering one you have been running by memory.
Editable employment compliance policies and procedures covering the recordkeeping and documentation an employment audit asks to see.
Review the HR compliance manualA broad documented base across accounting, HR, IT and operations, ready to edit into your own process language.
Review the business manualThe writing guide for turning an evidence register into documented procedures an auditor can actually test against.
Review the writing guide