Ebook
❌

Uncovering Procurement Excellence

A definitive to solve your procurement issues
*
*
*
mypropixel('TYASuite','77106032334ffefe6f989f697174bdc8');

Maverick Spend in Procurement: How to Identify and Reduce It

Maverick Spend in Procurement
blog dateSep 30, 2026 | 25 min read | views 142

Maverick spend in procurement is purchasing that falls outside an organization's approved buying policies, supplier requirements, contract terms, or authorization process. Examples include buying from an unapproved supplier, committing to a purchase before approval, or paying a different price from the one agreed upon in a contract without an authorized exception.

The difficulty is that these purchases can look ordinary in financial records. An invoice may be paid on time and booked to the correct cost center, while the purchasing decision behind it bypassed a required control.

To identify maverick spending, procurement and finance teams need to compare transactions with the rules that applied when the purchase was made. This guide explains what to check, how to distinguish exceptions from violations, how to calculate the amount, and how to address the causes.

What counts as maverick spend in procurement?

The definition should start with your organization's procurement policy. A purchase becomes non-compliant when it bypasses a requirement that applies to that transaction.

Common situations include:

• A requester selects a supplier without completing the required vendor approval.

• A department places an order before obtaining the necessary authorization.

• A purchase uses pricing outside an applicable contract without an approved variation.

• A required purchase order is created only after the organization has committed to the supplier.

• Related purchases are deliberately divided to bypass an approval threshold.

The distinction matters: an invoice without a PO is a warning sign, but it is not automatically maverick spend. Your policy may permit certain utility bills, statutory payments, or other expenses through a different approval route.

Similarly, an emergency purchase can be compliant if an authorized exception process was followed. The review should establish whether the applicable control was met and whether the exception was documented.

Why off-process purchasing deserves attention

⇒ The financial effect of uncontrolled purchasing extends beyond the value of the invoice. A department may pay an acceptable price for one purchase while creating a larger problem for budgeting, supplier management, or approval accountability.

⇒ Consider a maintenance team that regularly orders materials before raising a request. Finance sees the cost only when invoices arrive, so outstanding commitments are missing from the view used to manage the budget. Procurement may also miss an opportunity to consolidate demand across sites. The team gets the materials it needs, but the organization loses spend visibility over decisions that have already created obligations.

⇒ Off-contract purchasing can create another difficulty. Negotiated terms may include delivery commitments, warranties, payment periods, or service responsibilities, as well as price. A comparison based only on unit cost can overlook those differences. An apparently cheaper purchase may not provide the same commercial protection or support.

⇒ There is also a practical workload effect. When authorization or order details are missing, accounts payable may need to contact the requester, department manager, and supplier before processing an invoice. These follow-ups consume time and make it harder to establish who approved what.

⇒ The purpose of a review is to make these effects visible. Report the amount of confirmed non-compliant spending separately from verified price differences, processing effort, and unresolved commitments. Do not describe the entire value of a policy violation as a financial loss: the organization may still have received useful goods or services. A more precise report helps management choose an appropriate response.

Maverick spending examples and how to review them

The following scenarios are illustrative. They show how similar-looking purchases can require different conclusions once the evidence is examined.

Example one: An urgent maintenance purchase

⇒ A plant needs a replacement part to restart production. The approved supplier cannot deliver within the required time, and the maintenance manager buys from a local distributor. The invoice appears in the review as an unapproved supplier purchase.

⇒ Before classifying it, check whether the emergency purchasing procedure was applied. Was an authorized person consulted? Was the exception recorded within the period required by the policy? Were essential supplier checks completed? If the organization permits this route and the evidence supports it, record an authorized exception.

⇒ If the required authorization was skipped, the transaction may be non-compliant even though the operational need was real. The corrective action could include improving regional supplier coverage and explaining the emergency approval route. Simply telling the plant to avoid local purchases may leave the underlying delivery problem unresolved.

Example two: A service started before approval

⇒ A department agrees to a three-month consulting engagement through email. The supplier begins work, but the purchase request is submitted only after the first invoice arrives. A PO is subsequently approved and created.

⇒ Review the agreement date, approval history, and policy requirement. A later PO may help link the invoice to the engagement, but it does not change the date on which the organization committed to buy. If prior approval was required, record the control failure and its cause.

⇒ For recurring services, clarify renewal ownership and the point at which a new commitment requires approval. That can prevent a repeat more effectively than treating every invoice as an isolated exception.

Example three: A price difference with an explanation

⇒ A contract lists a component at INR 70,000 per unit. An invoice shows INR 76,000, so the transaction is flagged for a possible pricing deviation. The purchasing team explains that the supplied item included an additional specification and that an authorized amendment covered the difference.

⇒ Check the amendment, specification, and effective date. If the variation was valid, the higher price is not evidence of an unauthorized purchase. If no supporting approval exists and the original terms applied, classify the deviation accordingly.

⇒ This example shows why an automated flag should start a review rather than determine its outcome. Reliable procurement compliance reporting depends on matching commercial context with transaction data.

Prepare the data before drawing conclusions

⇒ Data quality can change the apparent size of the problem. Before producing a baseline, confirm that the review includes all intended purchasing channels. A report built only from POs can miss direct invoices, corporate card purchases, and employee reimbursements. A report built only from invoices can miss commitments for which the supplier has not yet billed.

⇒ Choose the reporting basis explicitly. If you use invoiced spend, keep commitments awaiting invoices in a separate report. If you use committed spend, establish how cancellations, partial delivery, and subsequent changes will be handled. Avoid combining both amounts without a reconciliation, since that can count the same purchase twice.

⇒ Clean supplier identifiers, remove duplicate transaction records, and agree on how credit notes affect the totals. Where multiple currencies are included, use an agreed conversion basis consistently. Reconcile the data with finance so unexplained differences are identified before conclusions are shared.

⇒ Historical context is equally important. A supplier approved today may not have been approved when the purchase occurred. A current contract price may differ from the rate that applied during the review period. Preserve the relevant dates and versions rather than applying today's records retrospectively.

⇒ Missing evidence should remain visible. If approval records are incomplete, label the transaction as awaiting evidence and assign someone to resolve it. Treating every missing record as a violation can overstate the problem; ignoring missing records can understate it. A separate unresolved category makes the limitation clear while keeping the review moving.

Data you need to identify maverick spend

Begin with a defined period, such as the previous quarter, and collect records covering the same scope. Match purchasing commitments and related invoices so that one purchase is not counted repeatedly across systems.

 

Data source

Fields to collect

What it helps establish

Purchase orders

PO number, supplier ID, requester, value, creation date, approval date

Whether an order followed the required process

Invoice records

Invoice ID, supplier ID, amount, invoice date, PO reference

Whether billed purchases link to purchasing records

Vendor master

Supplier ID, approval status, approval date

Whether the supplier was approved at the relevant time

Contracts

Supplier, covered items or services, agreed rates, validity dates

Whether applicable contract terms were followed

Approval history

Approver, decision, timestamp, applicable authority

Whether the right person approved the commitment

Card and expense records

Merchant, purchaser, date, amount, purpose, authorization

Whether purchases outside the PO system were permitted

Exception records

Reason, approver, scope, validity

Whether a deviation was authorized

 

Use stable identifiers where possible. Supplier names alone can be unreliable because spelling variations and duplicate vendor records can create false matches or false alarms.

How to identify maverick spend: Five practical checks

 

1. Compare suppliers against the approved vendor list

Match the supplier on each purchase with the approved vendor master. Check the approval status at the time of the purchase, rather than relying only on the supplier's current status.

For an unmatched supplier, verify whether the record is a duplicate, whether the policy required approval, and whether an exception was authorized. Repeated purchases from the same unapproved supplier deserve a closer review of the business requirement and the approval process.

2. Check whether a required PO existed before commitment

Identify non-PO spend and orders created after the purchase was committed. Review order confirmations, service engagements, or other available evidence to establish the commitment date.

Comparing invoice and PO dates is useful for screening, but it may not reveal the full sequence. An invoice date alone does not always show when the organization agreed to buy.

Exclude documented policy-approved non-PO categories from the violation total. Keep unauthorized retrospective POs visible as a separate finding.

3. Compare purchases with applicable contract terms

Check the supplier, contract validity, covered item or service, and agreed price. Where prices differ, compare equivalent quantities, specifications, taxes, freight, and scope before concluding that there is a breach.

For example, a higher unit rate may reflect a different product specification or an approved contract amendment. A confirmed deviation requires evidence that the original terms applied and that no authorized variation covered the purchase.

4. Review approval authority and timing

Verify that the purchase received the approval required by its value, category, department, and other policy conditions. Check that the approver had the appropriate authority and that authorization occurred at the required stage.

An approval recorded after delivery may explain how the invoice was processed, but it does not necessarily satisfy a requirement for approval before commitment.

5. Investigate related purchases below approval limits

Group transactions by supplier, requester, department, purpose, and date. Look for purchases that appear to be parts of one requirement but were submitted separately below a threshold.

If approval is required above INR 50,000, three related orders of INR 20,000, INR 18,000, and INR 17,000 may warrant investigation. Their combined value is INR 55,000, but that pattern alone does not prove an attempt to bypass approval. Check the business purpose and the policy's aggregation rules before classifying the orders.

A maverick spend review checklist

Use a review table to keep screening results separate from confirmed findings.

 

Warning sign

Evidence to examine

Question to resolve

Supplier absent from approved list

Vendor approval history and exception record

Was supplier approval required and obtained?

Invoice without a PO

Expense category, policy, alternative approval

Was this an authorized non-PO purchase?

PO created after commitment

Order confirmation and approval timestamps

Did the purchase bypass prior authorization?

Price above contract rate

Contract, specification, freight, approved variations

Were applicable commercial terms breached?

Missing or unsuitable approval

Authority matrix and decision history

Did an authorized person approve at the required stage?

Repeated orders below a threshold

Related requirements and aggregation rules

Were orders separated to avoid required approval?

 

Assign each reviewed transaction a clear outcome: compliant, authorized exception, confirmed non-compliant, or awaiting evidence. This makes the report actionable without overstating the findings.

Maverick spend calculation with a worked example

Use a consistent definition and scope:

Maverick spend (%) = Confirmed non-compliant procurement spend ÷ Total procurement spend in the same scope × 100

Count each purchase once, even if it failed multiple controls. Otherwise, a purchase with both a missing PO and an unapproved supplier would inflate the total.

Illustrative calculation

A company reviews INR 2 crore of procurement spend for one quarter. The initial screening flags INR 40 lakh. After review:

Review outcome

Amount

Policy-approved non-PO expenses

INR 10 lakh

Documented authorized exceptions

INR 5 lakh

Confirmed non-compliant purchases

INR 20 lakh

Purchases still awaiting evidence

INR 5 lakh

Total initially flagged

INR 40 lakh

 

The confirmed maverick spend rate is:

INR 20 lakh ÷ INR 200 lakh × 100 = 10%

The INR 5 lakh awaiting evidence should be reported separately. It should not be treated as confirmed non-compliance until the review is complete.

Keep the reporting basis consistent, including the period, included categories, currency, and treatment of taxes and credits. Use the same basis for the numerator and denominator so that comparisons remain meaningful.

Metrics that make the findings actionable

The overall maverick spend percentage is a starting point. It becomes more useful when management can see where the deviations occur and which control needs attention.

⇒ Confirmed non-compliant spend by department

Report both the value and its share of the department's spend within the same scope. A large department may have the highest absolute amount but a relatively low rate, while a smaller team may have a recurring issue affecting a larger share of its purchases. Use both views when deciding where to investigate.

⇒ Retrospective purchase orders

Track purchases for which a required PO was created after commitment. Define the timing rule clearly, because comparing only invoice dates can miss earlier unauthorized commitments. Distinguish recurring service renewals, emergency purchases, and ordinary goods orders to identify different causes.

⇒ Unauthorized supplier and contract deviations

Separate spending with suppliers lacking required approval from confirmed departures from applicable contract terms. These categories can overlap, so they should not be added together to calculate total maverick spend without removing duplicate transactions.

⇒ Unresolved cases and corrective actions

Record how many cases await evidence, their value, and how long they have remained unresolved. Also track whether agreed actions were completed and whether the same issue recurred in the next period. A reduction in the headline rate is more credible when unresolved cases have not simply increased.

There is no single target that fits every organization. Establish a reliable baseline, agree improvement priorities, and compare like-for-like periods. If the policy or reporting scope changes, explain the change so that readers do not mistake a different definition for better performance.

Common review mistakes to avoid

⇒ One mistake is counting every warning sign as a confirmed breach. A missing PO, a higher price, or a new supplier can be legitimate under the applicable policy. Keep the evidence review separate from initial screening.

⇒ Another is focusing on transactions while overlooking patterns. A single urgent purchase might need a documented exception. Repeated urgent purchases from the same location might reveal an unsuitable supplier arrangement or a planning gap. Investigating the pattern can lead to a more useful remedy.

⇒ Avoid assuming that spend under management is the exact inverse of maverick spend. Managed purchasing can still contain a control violation, and permitted expenses may sit outside a particular procurement platform. Define each measure independently rather than subtracting one percentage from 100 to infer the other.

⇒ Do not report suspected savings as achieved savings. An invoice rate above a comparable contract rate may identify a potential opportunity, but realized savings require a clear baseline and evidence of the subsequent outcome. Keep purchase value, identified price variance, and actual savings in separate fields.

⇒ Finally, avoid turning the review into a list of blame. Discuss confirmed findings with the people who understand the purchasing requirement. Ask what happened, which rule applied, and what would allow the next purchase to follow the approved process. Accountability remains necessary, but corrective action should address the cause as well as the individual transaction.

How to reduce maverick spend in procurement

Use the findings to choose the remedy. Different causes need different actions.

♦ Address supplier coverage gaps

If a site repeatedly buys outside the approved list because existing suppliers cannot meet its needs, review that coverage. Add suitable suppliers through the required onboarding process and make approved options easy for requesters to find.

♦ Clarify non-PO and emergency purchasing rules

Specify which categories can use an alternative purchasing route, who can authorize them, and what evidence must be retained. A clear exception process helps teams handle urgent requirements without creating an informal workaround.

♦ Remove avoidable approval delays

Examine where requests wait and why. Clarify approval ownership, provide permitted delegation for absences, and remove redundant steps where the policy allows. Preserve the approvals required for the risk and value of the purchase.

♦ Make contract terms accessible

Give requesters access to applicable supplier arrangements, pricing, and covered categories. Review repeated price deviations with both the supplier and the purchasing team to identify whether the cause is awareness, scope, or contract maintenance.

♦ Follow up on repeated deviations

Review recurring issues with the responsible department. Record the cause, corrective action, owner, and follow-up date. Escalate deliberate or repeated bypasses through the organization's established process.

Agree on ownership for the review

⇒ Procurement should help define supplier and contract requirements. Finance should validate the spend basis, reconciliation, and treatment of invoices or credits. Department managers and requesters should explain the business circumstances behind flagged purchases. The authorized policy owner should resolve ambiguous exceptions and approve changes to the purchasing rules.

⇒ Assign a review owner to keep these activities connected. Maintain a register containing the transaction reference, finding, evidence, classification, cause, action owner, and follow-up status. This gives the next reviewer enough context to understand the decision without repeating the investigation.

⇒ Use restricted access for the detailed register where it contains supplier bank information or employee data. Management reporting can summarize the findings without distributing unnecessary sensitive details. Clear ownership and an accessible audit trail make the process repeatable even when team members change.

A practical first-month review plan

 

Stage

Action

Output

Week 1

Agree the review scope and policy rules; collect purchasing records

Defined baseline and data set

Week 2

Run the five checks and validate flagged transactions

Confirmed findings and unresolved cases

Week 3

Discuss recurring issues with procurement, finance, and requesters

Root causes and assigned actions

Week 4

Report the baseline and agree the next review

Repeatable monitoring process

 

This is a suggested starting plan; adjust it to the volume and quality of your records. Continue monitoring confirmed maverick spend, retrospective POs, unauthorized supplier spend, and unresolved exceptions using consistent definitions.

How TYASuite supports the review process

TYASuite procurement software brings purchase requests, vendor records, approvals, and purchase orders into a structured workflow. Connected records can help procurement and finance teams trace purchasing decisions and examine deviations.

The review still depends on your configured policies, complete data, and a documented exception process. Use the findings to improve the purchasing workflow and keep checking whether the changes address the causes.

 

 

 

 

TYASuite

Vikas Mandawewala

Vikas Mandawewala is a Rank Holder Chartered Accountant and Rank Holder Company Secretary with 25+ years of experience across India and the US in finance, audit, risk management, and compliance. An ex-KPMG professional, he brings deep expertise in financial controls, regulatory compliance, and business advisory. He holds multiple global certifications, including CPA (US – NY & CO), CIA (US), and CISA (US), and is also a Registered Valuer in India.