luckpandaTL;DR: Invoice approval is the check a business runs on every supplier bill before paying it. Someone confirms the goods or service arrived, the price matches what was agreed, the tax details are valid, and a person with the right authority signs off. In India, slow approvals now cost money too: GST input tax credit reverses after 180 days unpaid, and MSME suppliers must be paid within 45 days.
Invoice approval means formally accepting a supplier's invoice as correct and payable. A clear invoice approval process has five parts: capture the invoice, match it against the purchase order and goods receipt, validate the tax details, route it to the person authorised for that amount, then release it for payment with an audit trail. Approving invoices this way stops duplicate payments, inflated bills and fake vendors, and keeps the books and the tax return in step.
What is the invoice approval process?
The invoice approval process is the set of steps between receiving a vendor bill and paying it. Most small businesses run seven steps:
- Receipt. The invoice arrives by email, on paper, or as an e-invoice with an IRN (Invoice Reference Number) and QR code.
- Data capture. Someone, or OCR, records the vendor, invoice number, date, GSTIN, HSN or SAC codes, taxable value and tax.
- Verification and matching. The invoice is compared with the purchase order (PO) and the goods receipt note (GRN).
- Exception handling. Price or quantity differences go back to the buyer or the vendor. The usual fix is a credit note or a corrected invoice, never an edit to the vendor's document.
- Approval. The approver with authority for that amount and cost centre signs off.
- Payment. Accounts schedules payment by the due date or the statutory limit, whichever comes first.
- Reconciliation and records. The payment is matched to the bill, and in India the invoice is checked against GSTR-2B before input tax credit is claimed.
What is two-way, three-way and four-way matching?
Matching is how an approver proves an invoice is right without phoning anyone. Choose the level by risk:
| Match | Compares | Use it for |
|---|---|---|
| Two-way | PO and invoice (price, quantity ordered) | Services, subscriptions, low-value repeat buys |
| Three-way | PO, GRN and invoice (adds quantity received) | Physical goods and stock: the default for inventory |
| Four-way | PO, GRN, inspection report and invoice | Goods that need a quality check before acceptance |
Set a tolerance so small rounding differences do not block a bill. A common rule is to auto-pass differences under 1% or a fixed small amount, and send anything larger to the buyer. Write the tolerance down; an unwritten tolerance becomes "whatever the approver felt like."
Who approves an invoice, and what do they check?
An approver needs two things: the authority for that amount, and a checklist for the document.
Who should approve an invoice? An approval matrix
An approval matrix (or delegation of authority) states who can approve what, by amount and by type. This is an example structure for a 10 to 50 person business. The amounts are illustrations to adapt, not a standard:
| Invoice amount (example) | With matching PO and GRN | Without a PO |
|---|---|---|
| Up to Rs 25,000 | Auto-approve after three-way match | Department head |
| Rs 25,000 to Rs 2,00,000 | Department head | Department head and finance |
| Above Rs 2,00,000 | Finance head | Finance head and a director |
| Any amount, new vendor or changed bank details | Finance, after verifying the change by phone on a known number | Same |
Two rules matter more than the thresholds:
- Segregation of duties. The person who raises the PO, the person who receives the goods and the person who approves payment should not be the same. COSO's Internal Control Integrated Framework lists segregation of duties as a core control activity. In a three-person business, at least split "approve" from "pay".
- Delegation when people are away. Name a backup approver for every level so invoices do not sit in someone's inbox during leave.
What should an approver check on the invoice itself?
An approver should check that the document is a valid invoice before checking the amount. For an Indian GST tax invoice, Rule 46 of the CGST Rules requires, among other things:
- supplier name, address and GSTIN, and your GSTIN as recipient;
- a consecutive serial number of up to 16 characters, unique for the financial year;
- the date, description, HSN or SAC code, quantity and taxable value;
- the tax rate and amount split into CGST and SGST, or IGST, and the place of supply;
- the supplier's signature or digital signature.
Then three checks that catch most bad invoices:
- IRN present when required. E-invoicing has applied to businesses with aggregate turnover above Rs 5 crore since 1 August 2023 (Notification 10/2023-Central Tax). If the supplier should have generated an IRN and did not, the document is not a valid invoice, and the credit on it is at risk. You can verify an IRN on the e-invoice portal.
- Duplicates. The same vendor, invoice number and amount should never be approved twice. Search by vendor and invoice number, not by amount alone.
- Bank details. A changed bank account on an invoice is the classic sign of invoice fraud. Confirm it through a contact you already have, never through the email that carried the change.
LuckPanda's GSTIN checker checks the format and checksum of a supplier GSTIN. It does not do a live government lookup.
Why do invoice approval delays cost money in India?
Late approvals in India create tax and interest costs, not just unhappy vendors. Four rules set the clock:
| Rule | What it says | Effect of slow approval |
|---|---|---|
| CGST Act s16(2), second proviso | Pay the supplier, including tax, within 180 days of the invoice date | Input tax credit claimed must be added back to output tax; you claim it again once you pay |
| CGST Act s16(4) | Claim credit by 30 November after the financial year ends | Invoices approved too late lose the credit for good |
| MSMED Act 2006, s15 | Pay micro and small suppliers by the agreed date, at most 45 days from acceptance (15 days if nothing was agreed) | Compound interest at three times the RBI bank rate, with monthly rests, under s16 |
| Income-tax Act s43B(h) | From AY 2024-25, sums owed to micro and small enterprises past the s15 limit are deductible only when paid | The expense moves out of the year if still unpaid at year end |
The MSMED Act counts acceptance as deemed if you raise no objection within 15 days of delivery (MSMED Act 2006, s2(b)). So a disputed invoice needs a written objection inside that window, not just a hold in someone's inbox. Under Rule 37, the 180-day reversal is reported in GSTR-3B for the period after the 180 days run out.
Two practical consequences for your approval process:
- Tag MSME vendors (by their Udyam registration) when you onboard them, and set their approval deadline to 30 days so payment can still run by day 45.
- Track the invoice date, not the received date. Both the 180-day and the 45-day clocks start from documents the supplier controls.
Outside India the pressure is lighter but real. In the UK, the Late Payment of Commercial Debts (Interest) Act 1998 lets a supplier charge interest at 8% above the Bank of England base rate, plus fixed compensation of 40, 70 or 100 GBP depending on the size of the debt.
What goes wrong with manual invoice approval?
Manual invoice approval fails in the same few ways in almost every business:
- Lost invoices. Bills sit in personal inboxes, on WhatsApp or on a desk, and nobody can see who has them.
- No status. Accounts cannot tell a vendor whether a bill is approved, disputed or unseen.
- Rubber-stamping. Approvers see only a PDF, not the PO or GRN, so they approve by trust.
- Duplicate and fraudulent payments. Without one register, the same invoice is paid twice, or a fake vendor gets in.
- Missed deadlines. Nobody tracks the 180-day or 45-day clock until the GST return or the tax audit finds it.
How do you automate invoice approvals?
You automate invoice approvals by writing your rules down once and letting software apply them to every bill. Look for these features in invoice approval software:
- Rule-based routing by amount, vendor, department and whether a PO exists, with multi-level approval.
- Matching of PO, GRN and invoice with a set tolerance, so clean invoices skip a human.
- Data capture by OCR or e-invoice JSON, so nobody re-types GSTINs.
- Audit trail that records who approved what and when, kept for at least the GST record period (72 months after the annual return due date under CGST s36).
- Due-date and statutory alerts for MSME and 180-day limits.
- Accounting integration, so an approved bill posts once and the payment matches it.
- Mobile approval and delegation for approvers who travel.
Roll it out in this order: map your current flow, write the approval matrix, start with one vendor category, then widen. Measure average days from receipt to approval and the share of invoices that auto-match.
Can AI approve invoices?
AI can prepare an invoice for approval, but a person should approve it. Agents are good at reading invoices, filling bill drafts, finding the matching PO and flagging differences. The final yes, and the payment, should sit with someone accountable. That is how LuckPanda works: its Workspace module gives agents API and MCP keys that can create and revise drafts but are refused for issuing, sending and paying. Approval rules that decide who signs off on which documents and amounts are being built, so for now it is a manual sign-off. See how agents connect and the approvals page.