Practical perspectives

Tail-Spend RFQ Approval Thresholds: A Buyer Worksheet

Define when a routine RFQ may proceed, when an award needs a buyer and which exceptions must stop automation.

On this page
  1. Define the eligible pool
  2. Assign authority
  3. Test an exception
  4. Keep an audit record

An automated RFQ may save time while still leaving the organization responsible for supplier eligibility and the award. A single monetary cutoff is not enough: the same value can represent a repeat purchase or an unqualified new supplier.

Use this worksheet with the tail-spend sourcing guide. It is a pilot design, not a recommended universal spending policy.

1. Define an eligible event before a threshold

Start with a category, region, requester group, currency, specification template and approved supplier pool. Keep sole-source, regulated, new-supplier and contract-conflict requests outside automatic awards until the appropriate owner reviews them. A low price does not remove these checks.

Illustrative pilot rules; replace with your policy
ConditionRoutine pathEscalation
Approved category and supplierTemplate RFQ may be sent to the approved pool.Missing item detail pauses invitations.
Award below pilot limitRecommendation may proceed under assigned authority.Any supplier exclusion failure goes to a buyer.
New or unqualified supplierNo automatic invitation or award.Supplier qualification owner reviews.
Nonstandard terms or sole sourcePause automated award.Commercial or legal reviewer decides.

2. Separate event, recommendation and award authority

Specify whether the system may draft an RFQ, send it, rank responses, recommend an award or actually commit the order. These are distinct permissions. Record who owns each rule, who may override it and what evidence is required. Keelvar describes sourcing automation ↗; Fairmarkit describes tactical buying rules ↗. Neither publication substitutes for your own delegated authority.

  • Send: Which approved suppliers can receive this request?
  • Recommend: Which mandatory criteria must a bid satisfy before scoring?
  • Award: Which user or rule may commit a supplier, and at what limit?
  • Handoff: Who confirms the purchasing record reflects the approved decision?

3. Test the exception, not only the straight path

Run the same purchase twice. In the first run, all three suppliers qualify and respond on identical terms. In the second, the cheapest bid misses a mandatory delivery condition. Verify that the system displays the exclusion, asks an authorized buyer for a decision and does not silently convert the lowest price into an award.

For an SAP-connected extension, confirm which controls live in the extension and which come from SAP Ariba or another system. Kyyte’s SourcifAI guide ↗ is useful for mapping this integration boundary.

4. Reconcile the event with the order

Minimum evidence to retain
DecisionEvidenceFailure signal
RFQ invitationRequest version, eligible supplier list and time sent.Unqualified supplier receives an invitation.
Bid comparisonBid versions, mandatory exclusions and scoring rule.Noncompliant lowest bid ranks first.
AwardApprover, limit, override reason and supplier notice.Supplier notified before approval.
Purchase handoffOrder ID and accepted price, quantity and dates.Write-back fails but event appears complete.

Measure exception rate, buyer effort and order reconciliation as well as cycle time. An automation that looks faster but conceals manual cleanup is not a successful pilot.

Sources