Internal Control Weakness Examples: Causes, Costs, and Fixes

Common internal control weakness examples fall into five recurring categories: a weak control environment set by leadership, poor segregation of duties, sloppy authorization and transaction processing, information technology gaps, and broken monitoring. Any one of them can range from a minor housekeeping issue to a material weakness that a public company has to disclose in its annual report. The examples below show what each looks like in practice and what separates a nuisance finding from one that puts the organization, or an individual officer, at real risk.

How Auditors Rank the Severity

Before looking at specific examples, it helps to know the three tiers the Public Company Accounting Oversight Board uses, because the same underlying error can land in any of them depending on scope.

  • Control deficiency: A control is missing or not operating as intended, but the gap is minor enough that it doesn’t require formal reporting to the board or audit committee.
  • Significant deficiency: A deficiency, or combination of them, serious enough to “merit attention by those responsible for oversight of the company’s financial reporting,” but not severe enough to be a material weakness.1Public Company Accounting Oversight Board. AS 2201 – An Audit of Internal Control Over Financial Reporting
  • Material weakness: A deficiency, or combination, where there is a “reasonable possibility” that a material misstatement of the annual or interim financial statements will not be prevented or detected on a timely basis.1Public Company Accounting Oversight Board. AS 2201 – An Audit of Internal Control Over Financial Reporting

An isolated user-access error at one location is a deficiency. The same error repeated across every financial application in the company is a candidate for material weakness. Scope and repetition change the tier more than the nature of the error itself.

Weak Control Environment

The control environment is the foundation. When leadership treats compliance as optional, specific controls built on top of it tend to fail regardless of how well they read on paper.

Indifferent Tone at the Top

The most damaging weakness rarely shows up on a flowchart. It’s a missing or unenforced code of conduct, inconsistent discipline for policy violations, or executives who openly dismiss audit findings. Staff read the signal and conclude the rules are decorative. Government Accountability Office standards frame it directly: the board and senior management “establish the tone at the top regarding the importance of internal control and expected standards of conduct,” and everything downstream depends on that tone being genuine.2Government Accountability Office. Standards for Internal Control in the Federal Government

Routine Management Override

Every control system leaves room for management to override a control when circumstances demand it. The weakness isn’t the override; it’s when overrides become routine. A CFO who regularly approves purchases above normal limits without documentation, or a controller who posts adjusting entries without review because “there’s no time,” is teaching the organization that controls are optional. Auditors specifically test for this pattern, because management’s ability to manipulate records makes override one of the hardest fraud risks to detect.3Public Company Accounting Oversight Board. AS 2401 – Consideration of Fraud in a Financial Statement Audit

Understaffed Control Functions

An internal audit team of two people covering a multinational operation is a weakness no amount of talent can overcome. Testing becomes a checkbox exercise focused on the highest-risk areas while everything else goes unreviewed for years. The same problem appears in accounting departments where one person handles everything from journal entries to bank reconciliations because nobody else is available. That staffing reality forces the exact role concentration that segregation controls exist to prevent.

Unclear Lines of Authority

When two managers each believe the other reconciles an intercompany account, the reconciliation doesn’t happen. Ambiguous ownership is one of the quietest failures because no alarm goes off when a task is simply never performed. It usually surfaces only during the audit, months later, when the auditor asks who owns the control and gets a different answer from each person asked.

Poor Segregation of Duties

This is the weakness auditors find most often, and the one that most directly enables fraud. The core rule: no single person should control an entire transaction from start to finish. Three functions should always be handled by different people: authorizing a transaction, recording it, and having custody of the resulting asset.

The textbook example is an accounts payable clerk who can create a new vendor, approve invoices from that vendor, and initiate payments. That combination lets one person set up a fictitious company, submit fake invoices, and pay themselves. The Association of Certified Fraud Examiners estimates organizations lose roughly 5% of revenue to fraud annually, with a median loss of $145,000 per case and a typical scheme running 12 months before detection.4Association of Certified Fraud Examiners. Occupational Fraud 2024 – A Report to the Nations Weak segregation is a major reason schemes survive undetected that long.

Other recurring segregation failures:

  • Payroll: One person adds new employees, sets pay rates, and processes payroll runs. Ghost employees become trivial to create.
  • Cash receipts: The person opening mail and listing checks also makes the bank deposit and posts to accounts receivable. Skimming a check and covering the shortage requires no help from anyone.
  • Inventory: A warehouse manager who records receipts and also handles physical custody can divert goods and adjust the records to hide the shortage.

The vendor master file deserves particular attention. When changes to vendor bank account numbers or addresses don’t require independent verification, an attacker who compromises a single set of credentials can redirect legitimate payments. Organizations that never audit their vendor master file for duplicates, dormant vendors, or vendors sharing addresses or bank accounts with employees are running a risk that grows with every payment they process.

Sloppy Authorization and Transaction Processing

Even with duties properly split, controls fail when the authorization layer is weak. Authorization defines who can approve what, up to what dollar amount, and under what conditions.

Ignored or Missing Approval Thresholds

A purchase order policy requiring dual approval above a set dollar amount is useless if procurement staff routinely skip the second signature. The design is fine; the operation is not. Auditors call that a “deficiency in operation.”1Public Company Accounting Oversight Board. AS 2201 – An Audit of Internal Control Over Financial Reporting The same pattern shows up with journal entries. If any accountant can post a six-figure adjusting entry without a reviewer’s sign-off, the financial statements are exposed to both manipulation and honest mistakes no one catches until the external audit.

Missing Credit Review on Sales

Revenue recognition weaknesses often start at the front end. Shipping a large order to a new customer with no credit review means the company has already incurred the cost of goods sold before learning whether the customer can pay. The result is overstated revenue, an inflated receivable, and an eventual write-off. Proper control requires the credit function to approve orders above a set threshold before fulfillment begins.

Incomplete Supporting Documentation

Every payment should be backed by a purchase order, a vendor invoice, and confirmation that the goods or services were received. Without that three-way match, organizations pay for things they never received, pay twice for the same delivery, or pay amounts that don’t match what was agreed. Incomplete records also make deductions hard to substantiate if the IRS examines the return. The IRS requires businesses to keep records that clearly show income and expenses, and the burden of proving those figures falls on the taxpayer.5Internal Revenue Service. Recordkeeping

Information Technology Gaps

IT controls sit underneath nearly every financial control. If someone can access, modify, or delete data without authorization, it doesn’t matter how well the accounting policies read.

Access Management Failures

The most common IT weakness is failing to promptly remove access when an employee leaves or changes roles. A departed accounts payable supervisor who keeps remote access to the payment system for six months after termination is an obvious risk, but it happens constantly because access removal depends on HR notifying IT, and that handoff breaks. Federal security standards require organizations to uniquely identify and authenticate each user and tie that identity to their actions in the system.6IDManagement.gov. Security Controls Mapping of Special Publication 800-53 Revision 5, Identification and Authentication Shared or generic logins violate that requirement entirely. When five people share one login, there is no way to determine which individual initiated a transaction.

Poor Change Management

Pushing a software update or configuration change straight into production without testing is the IT equivalent of surgery without reviewing the chart. A poorly tested ERP update can corrupt transaction data, break automated controls, or open security holes. Effective change management requires a testing environment, a documented approval process, and a rollback plan. Skipping any of those steps is a weakness that can halt financial processing entirely.

Untested Backups

Many organizations run daily backups but never test whether those backups actually restore to a working environment. An untested backup is an assumption, not a control. The weakness becomes catastrophic when a ransomware attack or hardware failure makes restoration necessary and the team discovers the backups are corrupt or incomplete. Storing backups in the same physical location as production compounds the problem: a single fire or flood can destroy both.

Delayed Patching

Failing to apply security patches to financial systems within a reasonable timeframe leaves known vulnerabilities open. This isn’t abstract. Cyber insurance underwriters now routinely deny claims when investigations reveal the breach exploited a vulnerability the organization knew about but hadn’t patched. In one publicized case, an insurer denied a ransomware claim because the company had not fully deployed multi-factor authentication despite certifying that it had.

Broken Monitoring and Review

Preventive controls stop errors before they happen. Monitoring controls catch what slips through. When monitoring fails, problems can run for months.

Late or Skipped Reconciliations

Reconciling a bank account quarterly instead of monthly means an unauthorized transaction can sit undetected for up to 90 days. For a cash account, that delay can be the difference between catching a $3,000 irregularity and discovering a six-figure embezzlement. High-risk accounts like cash, intercompany balances, and revenue clearing accounts need monthly reconciliation at minimum, reviewed by someone other than the preparer.

Rubber-Stamp Approvals

A supervisor who signs off on a payroll journal entry without reviewing time records, or approves an expense report without checking receipts, is performing a ritual rather than a control. The signature exists; the protection does not. This one is especially dangerous because it looks compliant on paper. It survives walkthrough testing and only surfaces during detailed transaction testing.

Ignored Exception Reports

Automated systems flag payments processed outside standard terms, journal entries posted after close, login attempts from unusual locations. When those reports pile up unread, the organization has built a detection system and disabled it. The fix isn’t better technology. It’s assigning clear ownership for each report and requiring documented follow-up on every flagged item.

No Follow-Up on Prior Audit Findings

When auditors identify a weakness and management acknowledges it in a remediation plan but never actually implements the fix, the weakness persists and a new one is added: a broken self-correction process. Auditors must communicate significant deficiencies and material weaknesses in writing to those charged with governance no later than 60 days after the audit report is released.7American Institute of Certified Public Accountants. AU-C Section 265 – Communicating Internal Control Related Matters Identified in an Audit That communication creates a paper trail. If the same weakness appears the next year, the auditor knows management was informed and chose not to act, which ratchets up the severity assessment.

Infrequent Physical Inventory Counts

An organization that counts inventory once a year and relies on estimated shrinkage for the other eleven months is guessing at its cost of goods sold. Cycle counting, where a portion of inventory is counted on a rotating schedule throughout the year, catches theft, spoilage, and recording errors far sooner. Without it, discrepancies accumulate silently until the annual count reveals a variance too large and too old to investigate effectively.

What Small Organizations Can Do When Segregation Isn’t Possible

Small businesses face a structural problem. A five-person accounting department can’t always avoid giving one employee multiple responsibilities that would be split among three people at a larger company. The GAO’s standards acknowledge that smaller entities face “greater challenges in segregating duties because of its concentration of responsibilities and authorities” and advise management to respond by adding review layers, randomly sampling transactions and supporting documents, taking periodic asset counts, and checking supervisor reconciliations.2Government Accountability Office. Standards for Internal Control in the Federal Government

The most effective compensating controls in practice:

  • Owner or manager review of bank statements: Someone outside the accounting function opens and reviews statements each month, catching unauthorized payments the processor would never self-report.
  • Dual authorization for payments: Two people approve any payment above a set threshold. Even if one person handles the entire AP process, the check or wire doesn’t go out without a second signature.
  • Automated matching and workflow tools: Software that matches invoices to purchase orders and flags exceptions removes reliance on one person’s judgment and creates an electronic trail.
  • Surprise audits: Unannounced reviews of petty cash, inventory, or expense reports create uncertainty for anyone considering fraud. The randomness is the point.

None of these fully replaces proper segregation, and an auditor will still note the underlying concentration of roles. But documented compensating controls show management has identified the risk and taken reasonable steps, which matters both for the audit opinion and in any later dispute over whether negligence occurred.

What Each Weakness Can Actually Cost

The consequences of these weaknesses depend on the type of organization, but they stack up quickly.

For public companies, federal law requires the CEO and CFO to personally certify in every annual and quarterly report that they have evaluated internal controls, disclosed any significant deficiencies or material weaknesses to the auditors and audit committee, and presented conclusions about control effectiveness.8Office of the Law Revision Counsel. 15 USC 7241 – Corporate Responsibility for Financial Reports Each annual report must include a management assessment of internal control effectiveness, and larger filers must have the external auditor attest to that assessment.9GovInfo. 15 USC 7262 – Management Assessment of Internal Controls SEC Rule 13a-15 reinforces this by requiring issuers to maintain internal control over financial reporting and to evaluate effectiveness quarterly and annually using a recognized framework like COSO.10eCFR. 17 CFR 240.13a-15 – Controls and Procedures Certifying a report that doesn’t comply can expose the officer personally to fines up to $1 million and up to 10 years in prison, rising to $5 million and 20 years if willful.11Office of the Law Revision Counsel. 18 USC 1350 – Failure of Corporate Officers to Certify Financial Reports

Beyond regulators, the market reacts. Companies disclosing material weaknesses underperform by roughly 5% over the 120 trading days after the announcement. Audit fees stay elevated for years after remediation, because auditors expand testing and sample sizes when they can’t rely on controls.

For any business, weak controls can trigger tax consequences. The IRS imposes a 20% accuracy-related penalty on underpayments attributable to negligence, and the statute defines negligence to include “any failure to make a reasonable attempt to comply” with the tax code.12Office of the Law Revision Counsel. 26 USC 6662 – Imposition of Accuracy-Related Penalty on Underpayments The IRS treats inadequate books and records as an indicator of negligence when deciding whether the penalty applies.13Taxpayer Advocate Service. Annual Report to Congress – Accuracy-Related Penalty Under IRC 6662(b)(1) and (2) Reasonable-cause relief exists, but the central question is whether the taxpayer made an effort to get the liability right. An organization with no controls over its financial data will struggle to make that argument.

Cyber insurance is the newer pressure point. Insurers now require specific IT controls as a condition of coverage: multi-factor authentication on all remote and administrative access, endpoint detection and response tools, documented patch management, tested backups, security awareness training, and a written incident response plan. Incomplete deployment counts as non-compliance, and a single unprotected server can be grounds for denying an entire ransomware claim on the basis of misrepresentation.