Internal control over financial reporting examples fall into a few recognizable patterns once you see them in action: a manager’s approval before a purchase order goes out, a monthly bank reconciliation, a system that blocks an invoice when it doesn’t match the purchase order, a supervisor’s sign-off on every new hire’s pay rate. Each one exists to keep an error or a fraud from ending up in the financial statements. This article walks through the main types of controls, then shows what they look like inside the transaction cycles that produce most of a company’s numbers.
Preventive and Detective Controls
The first way controls get classified is by when they act.
Preventive controls stop errors before they enter the financial records. Requiring a manager’s approval for any purchase order above a set dollar threshold is preventive: the unauthorized spend never gets into the system. Segregation of duties is the other classic example. Splitting the ability to authorize a transaction, record it, and handle the related asset across different people makes it much harder for any single person to both commit and conceal fraud.
Detective controls catch errors after the fact. The textbook example is a monthly bank reconciliation, where someone compares the company’s cash ledger to the bank statement and investigates every difference. The error has already happened, but the reconciliation finds it in time for correction before the financial statements are finalized. Supervisory review of journal entries works the same way: a manager examines supporting documents for unusual postings after the entries have been made.
A healthy control system uses both. Preventive controls are cheaper because you avoid the cleanup, but no preventive control catches everything, so detective controls sit behind them as a safety net.
Manual and Automated Controls
The second classification is how the control gets performed.
Manual controls rely on a person’s judgment or physical action. A warehouse team counting inventory is manual. So is verifying a new vendor’s taxpayer identification number through the IRS’s online TIN matching tool before issuing the first payment.1Internal Revenue Service. Taxpayer Identification Number (TIN) Matching Tools Manual controls are flexible, but they depend on the person remembering to perform them correctly every time, which is where the risk lies.
Automated controls are programmed into IT systems and run without human intervention once configured. An ERP system that blocks a sales order when the customer’s receivable balance exceeds their credit limit is an automated preventive control. A system that rejects a vendor invoice when the amount deviates from the purchase order by more than a set tolerance is another. Automated controls are highly consistent, but they’re only as reliable as the IT environment supporting them, which is why IT general controls (covered below) matter so much.
Entity-Level and Process-Level Controls
The third classification is scope.
Entity-level controls span the whole organization rather than targeting a specific transaction. The company’s code of conduct, the whistleblower hotline, the internal audit function’s reporting relationship to the audit committee, and management’s formal risk assessment process are all entity-level.2The Institute of Internal Auditors. Internal Audit Oversight – The Audit Committee They set the conditions under which everything else operates. A code of conduct that leadership visibly ignores signals to employees that the detailed controls don’t really matter either.
Process-level controls are the granular, transaction-specific activities that live inside a particular business cycle. The three-way match in accounts payable, the daily cash reconciliation in the revenue cycle, and the payroll register comparison are all process-level. They’re where most day-to-day control work happens, and they only work reliably when the entity-level foundation underneath them is solid.
Revenue Cycle Examples
Revenue controls focus on making sure sales are real, recorded in the right period, and valued correctly. Segregation of duties is central. The person who records a sale should not be the same person who handles the cash receipt, and whoever authorizes a credit memo should not also process the sales adjustment.
Before goods ship, many companies run a three-way comparison of the sales order, shipping document, and invoice. The system won’t generate the invoice until the shipping document confirms the goods have left the warehouse. On the cash side, daily reconciliation of cash received against the amount deposited catches discrepancies quickly.
For companies with complex pricing arrangements, a separate control layer addresses revenue recognition under current accounting standards. That layer typically requires documented analysis of variable consideration (discounts, rebates, contingent pricing) and formal sign-off when contract modifications occur. Cross-functional review involving sales, legal, and finance helps confirm performance obligations are identified correctly, because the salespeople who negotiated the contract often understand its economics better than the accountant recording it.
Expenditure Cycle Examples
Expenditure controls make sure the company pays only for goods and services it actually received, at prices it actually agreed to. The anchor is the three-way match: every vendor invoice is compared against the purchase order (what was ordered) and the receiving report (what arrived). When those three documents don’t agree within a small tolerance, the system flags and holds the payment.
Before a new vendor is added to the master file, an independent person verifies the vendor’s legitimacy and a separate manager approves the addition. This prevents fictitious vendors, one of the more common fraud schemes. Larger payments often require escalating approval authority; a payment above $50,000, for example, might need the treasurer’s digital signature. As a detective control, someone independent of accounts payable periodically reviews the payable listing for anomalies like long-outstanding debit balances or duplicate payments.
Cloud-based software subscriptions create a modern wrinkle. A SaaS contract auto-renews, and the spending can sprawl across departments without centralized visibility. Effective controls include a centralized subscription register, IT security and compliance review before procurement, monitoring actual usage against licensed seats, and flagging upcoming renewals for renegotiation. Without them, companies routinely pay for duplicate tools and unused licenses for months before anyone notices.
Payroll Cycle Examples
Payroll controls guard against fictitious employees, unauthorized pay rate changes, and incorrect payments. A key preventive control requires that every new hire and every pay rate change be formally approved by a supervisor who is independent of both HR and the payroll processing function. Time records need manager approval before payroll runs.
On the detective side, comparing each payroll register to the prior period’s is one of the simplest and most effective checks available. Any significant jump in total payroll dollars or headcount triggers an investigation. The bank reconciliation for the payroll disbursement account should be performed by someone who wasn’t involved in preparing or approving the payroll run. This separation makes it extremely difficult for a single person to add a ghost employee and pocket the payments undetected.
Inventory and Fixed Asset Examples
These controls verify that the physical assets a company claims to own actually exist and are valued correctly on the balance sheet. The foundational control is the periodic physical inventory count, typically performed annually, with results reconciled to the perpetual records.3Public Company Accounting Oversight Board. AS 2510 – Auditing Inventories All significant variances between the physical count and the records must be investigated, approved by management, and adjusted. Companies with strong perpetual inventory systems and good IT controls can supplement annual counts with cycle counting throughout the year.
For fixed assets, disposals and sales require formal authorization documenting the reason and the expected proceeds. Sale proceeds are then reconciled to the authorized disposal form and the asset’s recorded net book value. Periodic physical inspections of high-value equipment confirm assets are where the records say they are. RFID tagging and automated tracking systems have made this far more practical for companies with large, dispersed asset bases, allowing real-time location monitoring and faster detection of missing items.
IT General Controls
Every automated control described above depends on the integrity of the IT systems running it. If someone can change a program’s logic, access data they shouldn’t see, or bypass an approval workflow, the automated controls built on top of that system become unreliable. IT general controls (ITGCs) protect the technology infrastructure itself, and auditors evaluate them as part of every ICFR assessment.4Public Company Accounting Oversight Board. Auditing Standard No. 12 – Identifying and Assessing Risks – Appendix B
They fall into four main categories:
- Access to programs and data. Restricting system access so employees can only reach what their job requires: password policies, role-based access provisioning, promptly disabling terminated employees’ accounts, and limiting privileged administrator access to a small number of authorized personnel.
- Change management. Controlling how software and system configurations are modified. Changes go through a formal request, testing, approval, and migration process, and the person who writes the code shouldn’t be the same person who moves it into production.
- Program development. Governing how new systems and applications are built or acquired, following a structured lifecycle with documented requirements, testing against those requirements, and formal acceptance before going live.
- Computer operations. Job scheduling, backup and recovery procedures, and incident monitoring. A nightly batch job that transfers HR termination data to the access management system is an automated ITGC that supports access controls across every other application.
ITGC failures cascade. If change management is weak, someone could alter the three-way matching logic in the accounts payable system and the automated control would stop catching mismatches without anyone realizing. This is why auditors often start their ICFR work by evaluating ITGCs before testing the process-level controls that depend on them.
When These Controls Fail
Not every control failure is equally serious, and the classification determines who has to know about it. PCAOB standards recognize three tiers.
A deficiency exists when a control’s design or operation doesn’t allow employees to catch or prevent misstatements in the normal course of their work. A deficiency in design means a necessary control is either missing or wouldn’t achieve its objective even if performed perfectly. A deficiency in operation means a properly designed control isn’t being executed correctly or by someone with the right authority.5Public Company Accounting Oversight Board. AS 2201 – An Audit of Internal Control Over Financial Reporting That Is Integrated with an Audit of Financial Statements
A significant deficiency is more serious than a standalone deficiency but less severe than a material weakness. It’s important enough that the people overseeing financial reporting, typically the audit committee, need to know about it.
A material weakness is the most severe classification. It means there’s a reasonable possibility that a material misstatement in the financial statements won’t be caught in time. When a material weakness exists, management must disclose it publicly in the company’s annual report on Form 10-K and cannot conclude that ICFR is effective. The company must also disclose material changes to its controls on a quarterly basis as it works through remediation.6U.S. Securities and Exchange Commission. Office of the Chief Accountant and Division of Corporation Finance The market tends to punish these disclosures harshly, which is why remediation speed becomes a genuine business priority rather than just a compliance exercise.
One boundary worth naming: the examples in this article are drawn from common practice, not from mandated dollar thresholds. Actual thresholds and control designs vary by company size, industry, and risk profile, and the specific rules an individual filer must follow depend on where it falls in the SEC’s filer categories and what framework its auditors are applying.