Free course · Foundation · 6 lessons · about 90 minutes
Internal controls and fraud prevention for finance teams
A practical, self-paced course for finance managers, controllers and accounts teams in Indian companies. You will learn how controls are designed, documented and tested, how to set up segregation of duties and master data controls in your accounting system, how the common finance frauds work and how to spot them early, and how to build a culture where controls are part of the daily routine.
What you will be able to do
- Explain the purpose of internal controls, the five COSO components and the Indian internal financial controls context
- Prepare a risk and control matrix for a process such as procure-to-pay
- Design segregation of duties, maker-checker and master data controls in an ERP or accounting system
- Recognise common finance fraud schemes and their red flags
- Test the design and operating effectiveness of a control and document the evidence
- Build a control culture with policies, a delegation of authority matrix, a whistleblower channel and data analytics
Lesson 1: Why controls matter
Controls are how a finance team gets the right answer every time, not just when the best person is at their desk. They protect the company’s money, its numbers and its people.
What an internal control is
An internal control is any step, check or setting that reduces the chance of something going wrong, or makes sure it is caught quickly if it does. A manager approving a purchase order is a control. So is a system that refuses to post a journal that does not balance, and so is a monthly bank reconciliation reviewed by someone who did not prepare it.
Controls serve three broad aims: reliable financial reporting, efficient and lawful operations, and safeguarding assets, including cash, inventory and data.
The control environment comes first
The control environment is the tone set by the board and senior management: whether integrity is expected, whether people know their responsibilities, and whether shortcuts are rewarded or questioned. A strong checklist cannot survive a weak environment. If a director can tell the accounts team to “just release it, I’ll send the approval later” and nobody pushes back, every downstream control is optional.
Types of control
| Type | What it does | Example |
|---|---|---|
| Preventive | Stops an error or fraud before it happens | Payment cannot be released without a second approver |
| Detective | Finds it after it happens, so it can be corrected | Monthly review of the vendor master change report |
| Manual | Performed by a person | Controller reviews and signs the bank reconciliation |
| Automated | Performed by the system, the same way every time | ERP blocks an invoice that does not match the PO and goods receipt |
Good control design mixes them. Preventive controls are usually cheaper than cleaning up later, and automated controls do not get tired at month-end. Detective controls catch what slips through. Many controls are IT-dependent manual controls: a person reviews a system report, so the report itself must be complete and accurate.
COSO at a high level
The most widely used framework is the COSO Internal Control – Integrated Framework (updated in 2013). It organises controls into five components:
- Control environment: integrity, oversight, structure, competence and accountability.
- Risk assessment: identifying what could go wrong, including fraud risk, and how likely and serious it is.
- Control activities: the approvals, reconciliations, reviews and system settings that address those risks.
- Information and communication: reliable data and clear communication of responsibilities.
- Monitoring activities: checking that controls keep working and fixing gaps.
The 2013 framework supports these components with 17 principles. You do not need to memorise them; you need to recognise that a single control rarely stands alone.
The Indian context: internal financial controls
The Companies Act, 2013 uses the term internal financial controls (IFC). In broad terms, the directors’ responsibility statement of a listed company confirms that IFC have been laid down and are adequate and operating effectively, and the statutory auditor of many companies reports on the adequacy and operating effectiveness of IFC with reference to the financial statements. ICAI has issued a Guidance Note on the audit of these controls. Certain smaller private companies have been exempted from the auditor’s IFC reporting. confirm whether directors’ and auditors’ IFC reporting applies to your company, and the current exemption criteria, with your CA or company secretary.
Lesson check
Four questions. Get 3 right to complete the lesson. Your progress is saved in this browser.
Lesson 2: The risk and control matrix
A risk and control matrix (RCM) is the map of your controls. It shows, for each process, what could go wrong and exactly what stops it.
Start with a walkthrough
Before writing anything, follow one real transaction from start to finish. For procure-to-pay, pick one purchase and trace it: requisition, purchase order, goods receipt, invoice, booking, payment, and the entries in the ledger. At each step ask: who does this, in which system, what document is created, and who checks it? Collect copies of the documents and screenshots. Walkthroughs reveal the gap between the policy manual and what people actually do.
From risks to key controls
For each step, write the risk as something that could go wrong in the financial statements or the cash: “payment made for goods not received”, “invoice booked twice”, “expense recorded in the wrong period”. Then identify the controls that address each risk. A key control is one you rely on to prevent or detect a material error; if it fails, the risk is not covered by anything else. Not every check is a key control, and an RCM with 300 key controls usually means nobody has prioritised.
What each row records
- Risk ID and description, and the assertion it affects (existence, completeness, accuracy, cut-off, valuation).
- Control ID and description: who does what, how often, using which information, and what happens to exceptions.
- Type: preventive or detective, manual or automated.
- Frequency: per transaction, daily, weekly, monthly, quarterly, annual.
- Owner by role, not just by name, so the matrix survives staff changes.
- Evidence: what proves the control was performed (sign-off, system log, review notes).
- Key or non-key.
An example for procure-to-pay
| Risk | Control | Type / frequency | Owner | Evidence |
|---|---|---|---|---|
| R1: Purchases made without authority | C1: POs above ₹1,00,000 need approval in the ERP as per the delegation of authority matrix | Preventive, automated / per PO | Purchase head | ERP workflow log |
| R2: Payment for goods not received or at the wrong price | C2: Three-way match of PO, goods receipt and invoice; mismatches above tolerance are blocked | Preventive, automated / per invoice | AP lead | System configuration and blocked-invoice report |
| R3: Fictitious or altered vendor | C3: Vendor creation and bank changes approved by a second person after documents and call-back | Preventive, manual / per change | Finance controller | Signed change form, call-back note |
| R4: Duplicate payment | C4: ERP duplicate-invoice check on vendor, invoice number and amount; weekly duplicate report reviewed | Preventive and detective / weekly | AP lead | Reviewed report with comments |
| R5: Liabilities not recorded at month-end | C5: Review of goods received not invoiced (GRNI) and accrual of open items | Detective, manual / monthly | Financial controller | Signed GRNI schedule and accrual journal |
Write controls people can test
“Payments are reviewed” is not a control description. “The finance manager reviews the payment run against approved invoices before releasing it in the bank portal, and initials the run sheet” is. A good description answers who, what, when, how, and what happens when something is wrong.
Lesson check
Four questions. Get 3 right to complete the lesson. Your progress is saved in this browser.
Lesson 3: Segregation of duties and system access
No single person should be able to start, approve, record and hide a transaction. Segregation of duties and access controls make that true in your system, not just on paper.
The basic idea
Split four kinds of duty between different people: authorising a transaction, recording it, having custody of the asset (cash, stock, the bank portal), and reconciling or reviewing it. When one person holds two of these for the same transaction, they can make an error or commit a fraud and also conceal it.
Common conflicts in finance
| Duty A | Duty B | Why it conflicts |
|---|---|---|
| Create or edit vendors | Process or release payments | Can add a fake vendor or change bank details, then pay it |
| Post journals | Approve journals | Can post and approve their own adjustments |
| Raise purchase orders | Record goods receipts | Can buy and confirm receipt of goods that never arrived |
| Handle cash or receipts | Post customer receipts or credit notes | Can take cash and hide it with a credit note |
| Prepare the bank reconciliation | Release payments in the bank portal | Can make an unauthorised payment and reconcile it away |
Small teams cannot always separate everything. Where a conflict is unavoidable, add a compensating control: for example, the CFO reviews every payment made to a vendor whose details changed in the month, or reviews a report of journals posted by the person who also approves them.
Maker-checker
Maker-checker means one person enters (makes) and a different person approves (checks) before the transaction takes effect. Set it up in both the ERP and the bank portal, and make sure the checker actually looks at supporting documents. A checker who approves 200 items in four minutes is not a control.
Access controls
- Role-based access: build roles from the duties above, and give users roles, not individual permissions.
- Joiners, movers, leavers: access is requested and approved before it is given, changed when people move, and removed on the last working day.
- Periodic access review: each quarter, department heads confirm that their team’s access is still needed, and the review is documented.
- Privileged and generic IDs: limit administrator and “super user” access, avoid shared IDs, and log what privileged users do.
- Bank portal tokens and passwords are never shared, even during leave.
Master data controls
Many frauds start with master data, not with transactions. For vendors, require supporting documents before creation (PAN, GSTIN where registered, a cancelled cheque or bank letter), verify GSTIN and PAN details on the official portals, and use bank account validation where your bank offers it. Every change to bank details is approved by a second person after a call-back on a number already on file. Review a master data change log every month, and block or deactivate vendors that have not been used for a long period.
Audit trail in accounting software
The Companies (Accounts) Rules require companies using accounting software to use software with an audit trail (edit log) feature that records each change and cannot be disabled, applicable from the financial year starting 1 April 2023. confirm the current requirement and how it applies to your systems with your CA. Treat the edit log as a control tool: review edits to posted entries, especially after the period is closed.
Lesson check
Four questions. Get 3 right to complete the lesson. Your progress is saved in this browser.
Lesson 4: Common fraud schemes and red flags
Most finance frauds are not clever. They succeed because a familiar pattern was not recognised in time. Learn the patterns and the red flags become obvious.
Why fraud happens
The fraud triangle describes three conditions that usually appear together: pressure (debt, targets, personal problems), opportunity (weak controls, too much trust in one person) and rationalisation (“I’ll pay it back”, “the company owes me”). Finance teams cannot remove pressure, but they control opportunity.
The schemes you will meet
| Scheme | How it works | Red flags |
|---|---|---|
| Vendor bank change fraud | A fraudster, often using a hacked or look-alike email, asks you to pay a real supplier’s invoice into a “new” account | Urgency, a slightly different email domain, a change just before a large payment, a request not to call |
| Duplicate payments | The same invoice is paid twice, by error or deliberately, with the refund later diverted | Same amount and vendor in a short period, invoice numbers with small differences (INV-2207, INV2207, 2207) |
| Ghost vendors | A fictitious vendor is created and paid for services never delivered | Vendor address or bank account matching an employee’s, no GSTIN, round amounts, services with no deliverable |
| Ghost employees | Payroll pays someone who has left or never existed | Salaries to accounts shared with other employees, no leave or attendance records, no tax or PF deductions in line with peers |
| Expense fraud | Personal costs claimed, receipts altered, or one claim split to stay under an approval limit | Several claims just under the limit, missing original bills, claims on holidays |
| Revenue manipulation | Sales booked early, fictitious sales, or goods shipped at quarter-end and returned afterwards | A spike in sales in the last days of a period, credit notes early in the next period, receivables growing faster than sales |
Worked example: a duplicate payment
Ashvan Components Pvt Ltd (fictional) received invoice INV-2207 from a supplier for ₹3,00,000 plus GST of ₹54,000, a total of ₹3,54,000. It was paid on 5 August. On 19 August the same invoice was keyed again as “INV2207”, so the ERP’s exact-match duplicate check did not trigger, and it was paid again.
- Total paid: ₹3,54,000 × 2 = ₹7,08,000. Overpayment: ₹7,08,000 − ₹3,54,000 = ₹3,54,000.
- How to catch it: run a weekly report that strips spaces, hyphens and leading zeros from invoice numbers and flags the same vendor and amount within, say, 60 days.
- What to fix: recover the amount, correct the input tax credit position with your tax team if the invoice was claimed twice, and tighten the duplicate check.
Worked example: split expense claims
A policy says claims above ₹5,000 need a department head’s approval. An employee submits three claims on the same day for one client dinner: ₹4,900, ₹4,800 and ₹4,950. Total: ₹4,900 + ₹4,800 + ₹4,950 = ₹14,650, almost three times the limit, yet each claim passes on its own. The red flag is several claims just under a threshold on the same date.
What to do when something looks wrong
- Do not confront or tip off the person you suspect. Preserve the documents and system logs.
- Escalate through the channel your policy sets: your manager, the CFO, internal audit or the whistleblower channel.
- For a bank-change fraud, contact your bank immediately: the first hours matter for recalling a payment.
Lesson check
Four questions. Get 3 right to complete the lesson. Your progress is saved in this browser.
Lesson 5: Testing controls
A control you have never tested is an assumption. Testing tells you whether the control is designed to work and whether it actually worked all year.
Design versus operating effectiveness
| Design effectiveness | Operating effectiveness | |
|---|---|---|
| The question | If performed as described, would this control address the risk? | Was it actually performed, as described, throughout the period? |
| How | Walkthrough, inspect the control description, consider what could still go wrong | Test a sample of occurrences and inspect the evidence |
| Example | Does the payment review compare the run to approved invoices, or just glance at the total? | For 25 payment runs in the year, is there a signed run sheet with approved invoices attached? |
Test design first. There is no point sampling a control that would not catch the problem even when done perfectly.
Ways to gather evidence
- Inquiry: asking the owner. Useful, but never enough on its own.
- Observation: watching the control being done. Only shows that one moment.
- Inspection: examining sign-offs, review notes, system logs and approvals.
- Re-performance: doing the control again yourself, such as re-running a reconciliation. The strongest evidence.
Sampling basics
For manual controls, you test a sample of occurrences. The sample size depends on how often the control operates and how much you rely on it. Auditors and internal audit teams use their own methodology tables; an annual control may be tested once, a monthly control a few times, and a control performed many times a day needs a larger sample, often 25 or more. Select items at random or spread across the whole period, not just the months that were easy. For automated controls, testing the configuration once, together with good IT general controls over changes to the system, can be enough.
Worked example: evaluating exceptions
Kavera Foods Ltd (fictional) has 1,200 vendor payments in the year. The control: each payment above ₹50,000 is approved by the finance manager in the ERP before release. The tester selects 25 payments spread across the year and finds one released without approval.
- Exception rate in the sample: 1 ÷ 25 = 4%.
- For a key preventive control, most methodologies expect zero or near-zero exceptions in a sample of this size, so one exception usually means the control is not operating effectively unless the tester can show it was an isolated case, often by extending the sample.
- Next, check whether the unapproved payment was valid, and whether another control (such as the monthly vendor statement reconciliation) would have caught an invalid one.
Good evidence
Evidence should show who performed the control, when, what they looked at and what they did with exceptions. A tick with no date is weak. A reconciliation signed two months after the period end shows the control did not operate on time.
Remediation
- Find the root cause: unclear instructions, system setting, workload, a new joiner.
- Fix it and assign an owner and a date.
- Let the fixed control run for long enough to have several occurrences.
- Retest and record the result. A deficiency is closed only when the retest passes.
Lesson check
Four questions. Get 3 right to complete the lesson. Your progress is saved in this browser.
Lesson 6: Building a control culture
Controls last when people understand why they exist and when doing the right thing is the easy path. Culture is what holds the matrix together.
Policies people actually read
Keep policies short, specific and easy to find: procurement, payments, expenses, journal entries, vendor master, IT access, gifts and conflicts of interest. Each should name an owner, say when it was last reviewed, and explain what to do in an exception. Train new joiners on the ones that affect them, and ask for an annual acknowledgement.
Delegation of authority matrix
A delegation of authority (DoA) matrix says who can approve what, up to what amount. It turns “get it approved” into a clear rule and gives the ERP workflow its settings. The thresholds are a company decision; this one is only an illustration.
| Transaction | Up to ₹5,00,000 | ₹5,00,001 to ₹50,00,000 | Above ₹50,00,000 |
|---|---|---|---|
| Purchase order (budgeted) | Department head | CFO | Managing director |
| Purchase order (not budgeted) | CFO | Managing director | Board or committee |
| Manual journal entry | Finance manager | Financial controller | CFO |
| Write-off of receivables | CFO | Managing director | Board or committee |
Rules that make a DoA work: approvals are based on the total value of a contract, not on each invoice, so splitting a ₹60,00,000 contract into two POs of ₹30,00,000 does not lower the approver; nobody approves their own transaction; and temporary delegation during leave is recorded in writing with a start and end date.
Whistleblower basics
Many frauds are discovered through a tip, not an audit. A good whistleblower or vigil mechanism offers more than one channel (email, phone, an independent hotline), allows anonymous reports, protects people who report in good faith from retaliation, and sends serious matters to someone independent of the people involved, such as the audit committee chair. The Companies Act, 2013 and SEBI’s listing regulations require a vigil mechanism for listed companies and certain other classes of companies. confirm whether a vigil mechanism is mandatory for your company and what it must include. Separately, statutory auditors have duties to report certain frauds they come across in the course of the audit. confirm the current auditor fraud-reporting thresholds and process with your CA.
Continuous monitoring with data analytics
Instead of waiting for the annual audit, run simple tests on your own data every week or month. Most need only an ERP export and a spreadsheet:
- Duplicates: same vendor, amount and normalised invoice number.
- Vendor and employee match: compare vendor bank accounts, PANs, phone numbers and addresses with the employee master.
- Bank changes followed by payment: any vendor paid within, say, 30 days of a bank detail change.
- Journals: entries posted at weekends, late at night, by unusual users, to rarely used accounts, or in round amounts after the close.
- Threshold clustering: many POs or claims just below an approval limit.
- Dormant vendors that suddenly receive payments.
Give each test an owner, record what was found and closed, and add new tests when a new risk appears. A short monthly controls dashboard for the CFO keeps the subject visible.
Lesson check
Four questions. Get 3 right to complete the lesson. Your progress is saved in this browser.
Final test and certificate
15 questions drawn from a bank, marked on the server. Score 11 or more (70%) for a certificate of completion with a public verification link and an “Add to LinkedIn” button.
Go to the final test- FEMA for importers
- Export compliance
- TDS and GST essentials
- Ind AS foundations
- Close and consolidation
- FP&A essentials
- Corporate finance essentials
- Treasury and cash management
- Cost and management accounting
- Import procurement & SCF
- EPC projects and tenders
- Companies Act compliance
- Payroll compliance
- IFRS, US GAAP and Ind AS
- Excel for finance teams
- AI for finance teams
General information for learning, not professional advice. Laws, rates and standards change: confirm with the official source or your adviser before acting. Last reviewed 15 November 2026.