How to Create an Approval Queue in an ERP: Bills, Orders and Payments Waiting With the Right Person
For owners, finance managers and accountants of Indian SMEs who approve money going out: one queue, clear limits, and a record of every decision.
The question of how to create approval queue rules usually comes up after something slips: a supplier bill paid twice, or a purchase order raised above the limit because the owner was travelling. The fix is a queue, with rules about what lands in it.
Most approvals in Indian SMEs still happen on WhatsApp or at the owner's desk. That is quick, but it leaves no record, and items that nobody asked about simply wait. A supplier chases, and only then does anyone discover the bill was never approved.
This guide covers how an approval matrix is designed, an illustrative example from a Jalandhar sports goods maker, and how Apragya's Finance and Accounting app runs the queue.
How to create an approval queue, step by step
An approval queue collects the documents that need a decision before money moves: supplier bills, purchase orders, payment batches, credit notes and journal entries above a limit. Each approver sees only what is waiting for them.
The rules behind the queue are the approval matrix. A matrix states the document type, the condition (amount, department, supplier, category), the approver and whether a further level is needed. Keep it short and test it with real documents before switching off the old way.
Every decision should carry a reason when it is a rejection, and every approver should have a named stand-in for leave and travel.
- List the documents that need approval before posting or payment.
- Set the amount limits for each approver.
- Add a second level for large amounts, new suppliers or sensitive categories.
- Compare bills with their orders and receipts before they reach the approver.
- Name a stand-in for each approver, for a set period.
- Require reasons on rejection and review the queue's oldest items weekly.
What informal approvals cost
Items waiting unseen
A bill sits for weeks because nobody knew it was pending.
Over-limit spend
Orders above a limit go through when the approver is away.
Variances missed
A bill above its order is approved without anyone noticing.
No reasons
A rejected request comes back unchanged.
An example: a Jalandhar sports goods maker's Monday queue
Take an illustrative maker of cricket bats and footballs with about sixty staff. On Monday the finance manager's queue holds fourteen items: supplier bills, three purchase orders, a payment batch and a credit note for a returning dealer.
The Monday queue, item by item
- Willow supplier billAgrees with its order and receipt.Matched
- Leather supplier billRate above the purchase order.Mismatch
- Purchase order, stitchingAbove limit; needs the owner too.Pending
- Payment batchTwelve bills due this week.Ready
- Dealer credit noteReturn quantity confirmed by stores.Checked
- Freight billWaiting eleven days; moved to the top.Overdue
Eleven items were approved in twenty minutes. The stitching order went on to the owner as a second level, and the leather bill was rejected with a note asking the supplier to correct the rate. When the corrected bill arrived, it came back into the same queue.
How Apragya runs the invoice approval workflow
Step 1 of 5
Set the rules
Limits by amount, department, supplier or category, set by the admin without code.
- Set the rules: Limits by amount, department, supplier or category, set by the admin without code.
- Route the document: Bills, orders, payments and credit notes land in the right person's queue.
- Check it first: An agent compares the bill with its order and receipt and notes any variance.
- Decide: Approve, reject with a reason, modify, or escalate to the next level.
- Record it: Every decision is written to the audit log with the person who made it.
Designing an approval matrix in ERP
A useful matrix is short. Most SMEs need three rules: a limit per approver, a second approval above a higher amount or for a new supplier, and a stand-in when the approver is away. More rules than that tend to slow everything without adding control.
Approvals on chat, compared with Apragya
| Feature | Chat and desk approvals | Apragya approval queue |
|---|---|---|
| What is pending | Whatever someone mentions | A queue sorted by age |
| Limits | Remembered | Set as rules |
| Order and receipt check | Rarely done | Variance shown on the bill |
| Approver away | Work stops | Delegation to a named stand-in |
| Rejection | A call | A reason on the record |
Checked against public information on 16 September 2026.
What sets Apragya apart in the purchase approval process
Sorted by age
The oldest item rises to the top.
Variances shown
A bill that disagrees with its order says where.
Two-person rules
A second approval above an amount or for a new supplier.
Delegation
A stand-in for a set period, with the real decider recorded.
Notifications
Email, Slack or WhatsApp Business, so the queue comes to you.
On the phone
The same queue in the phone-friendly web app.
Read more on the approval queue feature. Bills that pass the queue are matched under three-way match exceptions, and payroll teams use the approval inbox for salary runs.
Getting started
- Write down who approves what today, and up to what amount.
- Turn that into two or three rules.
- Name a stand-in for each approver.
- Send one week of bills and orders through the queue.
- Review what waited longest and adjust the rules.
After a week, the queue usually shows which approver was the real bottleneck.
What it costs to start
Approval queues, answered
Can approvals happen on a phone?
What happens when the approver is travelling?
Can two people be required?
Is the requester told about a rejection?
What does it cost to start?
See everything waiting on you, oldest first
Set two or three approval rules and send this week's bills through the queue.