Large firms use layered approval systems that route payments based on amount, vendor, and risk instead of sending everything to one person
A large company cannot have one person approve every payment—the bottleneck would stop operations. Instead, treasury departments build approval matrices that automatically route a payment to the right approver based on what it is, who it is going to, and how much it costs. A $500 office supply order might need one signature. A $50,000 contract with a new vendor might need three. A $2 million wire to an established bank might need two.
The goal is speed without risk. Payments move faster because they do not wait in a queue behind unrelated transactions. Risk stays controlled because high-value or unusual payments still get human review—just from someone with authority over that specific type of transaction, not from a generalist approver who has to understand everything.
This structure works because it separates the work. One team handles the mechanics—matching invoices to purchase orders, checking that the amount is correct. Another team approves based on policy. A third team executes the payment once it is approved. When something goes wrong, the system shows exactly which step failed and who was responsible.
Key Takeaways
- Approval matrices route payments to different approvers based on amount, vendor type, and risk level rather than sending all payments to one person.
- Most large firms separate invoice verification from approval from payment execution so that errors are caught before money moves.
- Automation flags payments that do not match their purchase order or that come from new vendors, which slows those payments but catches fraud.
- The three-way match—comparing the purchase order, the invoice, and the receipt—is the standard control that most large companies use to prevent overpayment and duplicate payments.
- Treasury systems log every approval and every change, so auditors and fraud investigators can see the full history of any payment.
How approval matrices work in practice
An approval matrix is a table that says: if the payment is this type and this amount, this person approves it. A typical structure might look like this:
| Payment Type | Under $10,000 | $10,000–$100,000 | Over $100,000 |
|---|---|---|---|
| Routine vendor (established contract) | Department manager | Department manager + finance | CFO |
| New vendor (first payment) | Department manager + finance | Finance director + CFO | CFO + board approval |
| Wire transfer or ACH over $50,000 | Not applicable | Finance director + treasurer | Treasurer + CFO |
| Payroll | Payroll manager + finance | Payroll manager + finance | Payroll manager + finance |
The matrix is built into the company's accounting software. When an invoice is entered, the system checks the vendor, the amount, and the payment method, then automatically routes it to the right approver. That approver sees only the payments they need to see, not a pile of everything.
The matrix changes based on what the company has learned. If fraud happened with a certain vendor type, the company might move that vendor up a tier so that all payments to them need an extra signature. If a department has a clean record, the company might lower the approval threshold for their routine payments.
The three-way match that stops overpayment and fraud
Before any payment is approved, the invoice has to match two other documents: the purchase order (what the company ordered) and the receipt (what actually arrived). This is called the three-way match, and it is the most common control in large company treasuries.
The system compares three things: Did the invoice come from the vendor listed on the purchase order? Is the amount on the invoice the same as the amount on the purchase order? Does the quantity match what was received? If any of these three do not line up, the payment is flagged and held until someone investigates.
This catches several common problems. A vendor might invoice for 100 units when only 50 were ordered. A receiving clerk might have entered the wrong quantity into the system. An invoice might arrive twice by accident. A fraudster might send a fake invoice from an email address that looks like the real vendor's but is not. The three-way match does not catch everything, but it catches enough that most large companies treat it as non-negotiable.
When a mismatch is found, the payment does not move forward until someone with authority resolves it. That person might contact the vendor, check the receiving records, or cancel the invoice if it is a duplicate. The system logs what happened and who made the decision.
Automation flags high-risk payments before they reach an approver
Large companies use software rules to identify payments that need extra scrutiny before they even reach a human approver. These rules catch patterns that might indicate fraud or error.
Common flags include: a payment to a new vendor that is unusually large, a payment that is significantly different from the vendor's normal invoice amount, a payment to a vendor in a high-risk country, a wire transfer to a bank account that is different from the one on file, or multiple invoices from the same vendor on the same day. When a payment triggers a flag, it either goes to a specialist reviewer or it is held until someone manually clears it.
Automation also catches duplicate invoices by comparing invoice numbers, amounts, and dates across all invoices in the system. If the same invoice number appears twice, or if two invoices from the same vendor have the same amount and date, the system flags it.
The trade-off is that flagged payments move slower. A routine payment might be approved in hours. A flagged payment might take days because it needs manual review. Large companies accept this delay because the cost of a fraudulent payment or an overpayment is much higher than the cost of a few days of slower processing.
Segregation of duties keeps one person from controlling the whole process
Large companies divide payment work into separate roles so that no single person can approve a payment, execute it, and then hide it. This is called segregation of duties, and it is a standard control in any company that handles other people's money.
A typical split looks like this: one person (or team) enters the invoice and verifies it against the purchase order. A different person approves the payment. A third person executes the payment by initiating the wire or ACH. A fourth person reconciles the bank account to make sure the payment actually went out and was not duplicated. If fraud happens, it requires at least two people to be involved, which makes it much harder to hide.
The system also tracks who did what and when. Every approval, every change to an invoice, every payment execution is logged with a timestamp and a user ID. Auditors can pull this log and see the full history of any payment. If someone approves a payment that should not have been approved, or if a payment is executed to the wrong account, the log shows exactly who was involved.
Vendor management systems reduce approval delays for trusted suppliers
Once a vendor has been used many times and has a clean record, large companies often move them into a preferred vendor or master vendor category. Payments to these vendors can be approved faster because the company has already done the background work.
When a vendor is set up as a master vendor, the company stores their bank account information, tax ID, and contract terms in the system. When an invoice arrives from that vendor, the system can automatically match it to the purchase order and flag it for approval without waiting for manual verification. The approval threshold might also be lower—a payment to a master vendor might need only one signature instead of two.
New vendors go through a vetting process before they can be added to the master list. The company checks their business registration, tax status, and banking information. They might also run a background check or verify references. This upfront work takes time, but it pays off because all future payments to that vendor move faster.
If a vendor's status changes—they miss a delivery, they send a fraudulent invoice, or they are acquired by another company—the company can downgrade them back to standard status, which means their payments go back to the slower approval process.
Real-time dashboards let treasury teams see approval bottlenecks
Modern treasury systems show dashboards that display how many payments are waiting at each approval stage, how long they have been waiting, and who is holding them up. This visibility lets treasury managers spot bottlenecks and fix them before they become a problem.
A dashboard might show: 47 payments waiting for department manager approval, 12 waiting for finance director approval, 3 waiting for CFO approval, and 8 flagged for manual review. If the CFO has 3 payments sitting for two days, the treasury manager can follow up. If a department manager has 20 payments waiting, the treasury manager might ask if they need help or if the approval threshold should be adjusted.
The dashboard also tracks approval times. If payments to a certain vendor are taking longer than usual, or if a particular approver is slower than others, the system flags it. This data helps the company identify training needs or process changes that could speed things up.
Frequently Asked Questions
What happens if an approver is out of the office?
Most companies set up a backup approver or a delegation rule in their system. If the primary approver is out, payments automatically route to their backup. Some companies also set a time limit—if a payment has not been approved in 24 hours, it escalates to the next level. This prevents one person's vacation from stopping all payments.
Can a payment be approved without going through the three-way match?
Large companies can override the three-way match, but it requires a higher-level approval and is logged in the system. This is used for situations like emergency repairs or rush orders where the purchase order was not created in time. The override is tracked so auditors can see when it happened and why.
How do companies handle payments from multiple departments?
Each department has its own approval matrix based on their spending patterns and risk level. A marketing department might have different thresholds than a manufacturing department. The system routes each payment to the right approver based on which department submitted it.
What if a payment is rejected during approval?
The approver sends it back to the person who submitted it with a reason—usually a mismatch in the three-way match, a missing document, or a policy violation. That person has to fix the issue and resubmit. The payment goes back to the approval queue and is treated as a new submission.
How do large companies prevent approvers from rubber-stamping payments?
Auditors periodically review a sample of approved payments to make sure the approver actually checked them. If an approver approves payments without reviewing the supporting documents, or if they approve payments that should have been flagged, they lose approval authority. Some companies also rotate approvers so that different people review different payments over time.