Best Practices for Optimizing Purchase Requisitions, Invoices, and Payment Approvals

Creating a comprehensive and efficient purchase requisition, invoice, and payment approval process is crucial for organizations to maintain operational efficiency and financial control. Given the diversity in practices across companies, it’s beneficial to consolidate best practices that can serve as a guideline for establishing or refining these processes. This blog aims to outline these best practices, incorporating examples and illustrations to provide clear insights.

Understanding approval authority matrices

An approval authority matrix is a framework used by organizations to define who can approve expenditures and at what thresholds. The complexity of these matrices can vary based on the organization’s size, structure, and operational needs. Here are some foundational best practices:

1. Layered approval levels based on purchase value

A common practice is to implement multiple levels of approval based on the value of the purchase. For example, purchases under $1,000 might only require approval from a direct manager, while those exceeding $10,000 require additional sign-off from a department head or even the CFO. This tiered approach ensures that higher-value transactions receive more scrutiny.

PURCHASE VALUEPURCHASE VALUEAPPROVAL LEVEL 2APPROVAL LEVEL 3
Up to $1,000Direct ManagerN/AN/A
$1,001 – $5,000Direct ManagerDepartment HeadN/A
$5,001 – $10,000Direct ManagerDepartment HeadCFO
Over $10,000Department HeadCFOCFO

2. Department and expense type consideration

Some organizations adjust approval levels based on the department making the purchase or the type of expense. For instance, IT hardware purchases might follow a different approval path than marketing expenses due to the specialized knowledge required to evaluate such expenses.

DEPARTMENTEXPENSE TYPEPURCHASE VALUEAPPROVAL LEVEL 1APPROVAL LEVEL 2
ITHardwareAnyIT ManagerCFO
MarketingAdvertisingUp to $10,000Marketing ManagerCFO
OperationsSuppliesUp to $5,000Operations ManagerDepartment Head

3. Vendor purchase aggregation

Tracking gross purchases from the same vendor across multiple requests helps in negotiating better terms and identifying opportunities for bulk discounts. This also ensures better internal financial control. This approach requires a more sophisticated tracking system but can lead to significant cost savings.

VENDOR PURCHASE TOTAL ACROSS MULTIPLE PURCHASESAPPROVAL REQUIREMENT
Up to $5,000Direct Manager
$5,001 – $20,000Department Head
Over $20,000CFO

This can be additional authority metrics in addition to 1 or 2 outlined as above.

4. PO-based vs. Non-PO-based invoices

The process for approving invoices can differ for purchase order (PO) based and non-PO-based transactions. PO-based approvals typically follow a more streamlined process since the purchase has already been pre-approved at the requisition stage. Non-PO transactions may require additional verification steps to ensure they are legitimate and necessary.

INVOICE TYPEPURCHASE VALUEAPPROVAL LEVEL 1APPROVAL LEVEL 2APPROVAL LEVEL 3
PO-BasedAnyPre-approved*N/AN/A
Non-PO-BasedUp to $1,000Direct ManagerN/AN/A
Non-PO-Based$1,001 – $5,000Direct ManagerDepartment HeadN/A
Non-PO-Based$5,001 – $10,000Direct ManagerDepartment HeadCFO
Non-PO-Based>= $10,000Not permittedNot permittedNot permitted

* PO-Based invoices are considered pre-approved at the requisition stage but may require final verification through system based matching logic..

5. Unified vs. Separate invoice and payment approvals

While a few companies combine invoice approval and payment authorization into a single step, most others separate these processes to add a layer of control. Separating these steps can help in identifying discrepancies before payments are made.

For example for company A the invoice approval could be as per the following table:

INVOICE TYPEPURCHASE VALUEAPPROVAL LEVEL 1APPROVAL LEVEL 2APPROVAL LEVEL 3
PO-BasedAnyPre-approved*N/AN/A
Non-PO-BasedUp to $1,000Direct ManagerN/AN/A
Non-PO-Based$1,001 – $5,000Direct ManagerDepartment HeadN/A
Non-PO-Based$5,001 – $10,000Direct ManagerDepartment HeadCFO
Non-PO-Based>= $10,000Not permittedNot permittedNot permitted

And for the same company the payment approval would be as follows:

PURCHASE VALUEAPPROVAL LEVEL 1APPROVAL LEVEL 2APPROVAL LEVEL 3
Up to $1,000Direct ManagerDepartment HeadFinance Controller
$1,001 – 5,000Department HeadFinance ControllerN/A
$5,001 – 10,000Department HeadFinance ControllerCFO
>=$10,001Department HeadCFOCEO

6. Hierarchical vs. decoupled approval structures

Organizations must decide whether the approval hierarchy should mirror the organizational structure or if it should be decoupled to allow for more flexible and efficient processing. Decoupling can be advantageous in organizations where cross-departmental purchases are common.

APPROVAL STRUCTUREPURCHASE VALUEAPPROVAL ROLE 1APPROVAL ROLE 2
HierarchicalUp to $5,000Direct ManagerDepartment Head
HierarchicalOver $5,000Department HeadCFO
DecoupledUp to $5,000Project ManagerFinance Controller
DecoupledOver $5,000Procurement SpecialistCFO

Critical success factors for approval authority matrices

Implementing the best authority metrics does not automatically make a company’s approval process optimal and efficient. The following factors play a critical role in that. 

Conclusion

To conclude, with the right mix of policy, process, and technology, organizations can ensure that their procure-to-pay approval cycles are both efficient and effective, paving the way for fiscal responsibility and long-term success.