What is the maker-checker process?
The maker prepares something that matters: a payment, a sanction, a change to a borrower’s bank details, a manual journal. The checker is a different person who looks at it and either approves or sends it back. Until the checker acts, nothing happens.
You will also hear it called doer-checker (common in Indian banks and NBFCs), the four-eyes principle or dual control. Same idea. The person who creates a transaction should never be the one who authorises it. That single rule catches a surprising number of honest mistakes, and it makes fraud a lot harder.
Why maker-checker matters: what the data says
Most fraud and costly error inside organisations gets through a gap in controls, not a clever trick. The Association of Certified Fraud Examiners studied 2,402 occupational fraud cases across 143 countries for its Occupational Fraud 2026 report (released 19 May 2026). More than half of the cases involved either a lack of internal controls or an override of existing controls, and the median loss was $104,000 per case. Tips were the most common way frauds were found, at 43% of cases, which means many are not caught by the controls at all. A working maker-checker control attacks both problems: it adds the missing second person, and when the system enforces it, nobody can quietly skip it.
Where you actually need it
In a lending or fund business, the list is longer than most people expect:
- Credit sanctions, where the analyst prepares and someone with the right limit signs off.
- Disbursements and drawdowns. The person who raised the request shouldn’t release the money.
- Investment committee decisions, prepared by the deal team and approved by the committee.
- Vendor and borrower master data. Bank-account changes are the classic fraud route.
- Limit, rate and policy changes. If it changes a control, the change itself needs a control. Published delegation-of-powers documents show how limits are usually set: see approval limits in 18 Indian documents.
- Manual journal entries, especially the "one-off adjustment" kind.
How it breaks in email and Excel
Picture a Friday evening. An analyst emails a spreadsheet to the credit head with "please approve". The reply comes back from a phone: "Approved." On paper, that’s maker-checker. In practice, three things have gone wrong.
Nothing stopped the analyst from sending it to a colleague who didn’t have the authority for that amount. The approval isn’t tied to the version of the spreadsheet that was reviewed, and that file gets edited again on Monday. And three months later, when internal audit asks for every approval above ₹5 crore last quarter with the approver’s name, somebody loses two days in Outlook search.
None of this is anyone being careless. The tools just weren’t built to enforce the control.
How maker-checker relates to the audit trail rule for Indian companies
Since the financial year starting 1 April 2023, a company in India that keeps its books in accounting software must use software that records an audit trail of every transaction, keeps an edit log of each change with its date, and cannot have the audit trail switched off. This comes from the proviso to Rule 3(1) of the Companies (Accounts) Rules, 2014, explained in ICAI’s The Chartered Accountant journal.
The two controls answer different questions. The edit log shows what changed in the books and when. Maker-checker shows who allowed a change before it happened, and that a second person looked at it. Approvals that sit in email, outside the accounting software, are covered by neither.
What good automation looks like
When maker-checker runs inside a proper workflow, a few things change:
- The system won’t let a maker approve their own item. You don’t rely on people remembering.
- Approvals route by amount and product to someone whose limit covers it, and escalate above that.
- Committees get quorum rules. Two out of three, or all members, whatever your policy says.
- The checker approves a specific version. If anyone edits it afterwards, it goes back for approval.
- Pending items have an SLA. They don’t sit in someone’s inbox while they’re on leave.
- Every action lands in an audit trail that can’t be quietly edited: who, what, when, and on whose behalf.
Do you need a big system or a custom build for this?
Usually not. Teams traditionally got maker-checker by buying a large core system that has it baked into certain modules, or by asking developers to build approval logic into an internal tool. Both work. Both are slow to change, and your process will change: a new limit, an extra approver, a new product.
A no-code workflow platform is the third route. You set up the form the maker fills in, define the checker roles and limits, and the platform enforces them and writes the audit trail. When policy changes, your ops team updates the setup instead of raising a ticket. That’s how Averoic works, and teams typically go live in a few weeks.
| Route | Who enforces maker ≠ checker | Changing a limit or approver | Approval record |
|---|---|---|---|
| Email + Excel | People remembering the rule | Update the policy and tell everyone | Spread across inboxes and file versions |
| Module in a core system | The system, in the modules that have it | Vendor change or configuration project | Inside that system only |
| Custom build | Code your developers wrote | A development ticket and a release | Whatever was built in |
| No-code workflow platform | The workflow, for every process you set up | Your team edits the setup | One audit trail across processes |
Five questions to test your own setup
- Can a maker ever approve their own item? The honest answer should be "the system won’t let them".
- Does routing follow amount and authority, or whoever happens to be on the email?
- If an approved record changes, does it go back for approval?
- Could you list every approval, approver and timestamp for last quarter in ten minutes?
- Can you see what’s pending right now, and who is sitting on it?
“At UTI Alternatives, managing our investments in primary NCDs and private equity requires precise process documentation and flawless audit readiness. Enterprise SaaS platforms from large MNCs proved both cost-prohibitive and too rigid for our bespoke requirements. Averoic solved this by developing a robust platform tailored to our entire investment lifecycle.”
This guide is general information, not legal, audit or regulatory advice. Set your controls, limits and delegations from your own policies and professional advisers.
Works with alternative lenders, AIFs, NBFCs and insurers in India on approvals, maker-checker controls and audit readiness.
See how your own process would run on Averoic — configured, not coded, with maker-checker controls and a complete, time-stamped audit trail built in.
Frequently asked questions
What is a maker-checker system?
Software that enforces maker-checker instead of trusting people to follow it: it blocks the maker from approving their own item, routes each item to a checker whose authority limit covers it, shows the checker what changed, and records who made, checked and approved it, and when.
What should the checker see before approving?
Exactly what changed (the before and after values), the source documents, and the maker’s reason. Approving a whole record you did not compare is a signature, not a check.
What is the maker-checker process?
It is a dual control where one person (the maker) creates or initiates a transaction and a different person (the checker) reviews it and approves or rejects it before it takes effect. It enforces segregation of duties and is standard in banks, NBFCs, funds and insurers.
Is maker-checker the same as the four-eyes principle?
Yes. Maker-checker, the four-eyes principle and dual control all describe the same rule: no single person can both create and authorise a sensitive action.
What is the doer-checker process?
Doer-checker is another name for maker-checker, widely used in Indian banks and NBFCs. The doer enters or prepares a transaction, and a different person, the checker, verifies it against the source documents and approves or returns it before it takes effect.
What is a maker-checker example?
A credit analyst prepares a loan sanction note (maker), and a credit head whose limit covers the amount reviews and approves it (checker). Other common examples: a disbursement request and its release, or a change to a borrower’s bank account details and its verification.
Can maker-checker be automated without coding?
Yes. A no-code governed workflow platform such as Averoic lets you configure maker and checker roles, authority limits, multi-level or committee approvals and SLA escalations, and it records the audit trail automatically.
How does maker-checker work with effective dating, for example a rating or limit change?
The maker enters the change with the date it should take effect, the checker approves it, and the system applies it only from that date. The old value stays on record for the period it applied, so you can always show which rating, rate or limit was in force on any past date and who approved the switch.
What should a maker-checker audit trail capture?
Who created the item, who approved or rejected it, when each step happened, which version was approved, any delegation or on-behalf-of action, and the comments. It should be tamper-evident so nobody can quietly edit it later.
Can an AI agent be the maker in a maker-checker process?
Yes, and that is the safest way to use one. Let the agent prepare the item and have a person, or an independent check, approve it before it takes effect. Three rules matter: give the agent the smallest limits for anything that cannot be undone, such as refunds, write-offs or changes to a supplier’s bank details; make the checker look at the actual change and its source document, not the agent’s own summary; and check totals per vendor and per period, because an agent working for speed can split one large order into several small ones. Record the agent, the person it acted for and the approver on every action.
How do governance tools combine maker-checker approval with effective dates?
The maker proposes a change, such as a new rating or limit, with the date it should take effect; the checker approves it; and the system keeps the earlier version, so you can always show what applied on any date and who approved the change.