Record for this area

Requisition and guided buying

The path from what a machine is documented doing to the party holding the record that makes the result official, with how well each step is backed. Where the sources settled nothing, the step says so.

What a machine is documented doing

Established by the evidence. EXECUTION on O-2 by a configured deterministic workflow rule; every capability marketed as agentic was evidenced extracting pre-filling routing recommending or advising
The record it touches

Established by the evidence. O-2 requisition approval state; O-3 catalog or punchout item entry; O-4 contract-price catalog record; O-5 buying-policy rule
What still has to happen first

Established by the evidence. CONFIGURABLE - the binding act is machine-performable on a configured path and the documentation itself asks what expenditures can be automatically approved

A source describes this step a document describes this step at the point where it matters The passage attaches automating to identification rather than to the approval

The workflow process can also be configured to skip the review tasks and automatically approve the purchase requisition
the source's own words, quoted exactly
What makes the change count

Established by the evidence. OpenPeppol and OASIS define the catalogue form; the FAR Council sets the value envelope inside which it operates
Who holds the official record

Established by the evidence. JAGGAER One and Dynamics 365 hold the requisition; the GSA FAS Catalog Platform holds the MAS catalog record
What the area relies on

Established by the evidence. FAS Catalog Platform (FCP) — the platform holding the MAS catalog record and publishing it to GSA Advantage; The Federal Acquisition Regulation as the buying-policy and threshold rule record; Commercial Platforms Program — the awarded-platform channel through which federal micro-purchases may be made

The action that makes it official Transition of the requisition to Approved (O-2); award of the catalog modification (O-4) Done by SOFTWARE for O-2 on a configured path; the register operator for O-4. It counts because of a record state held by the buying system. A machine can do this, on a path the buyer configured in advance rather than by any judgement of its own.

What this area could not settle

What could this area not settle?

What this area recorded against its own findings, in its own words.

Recorded against itself by this area

12 nil routes; SAP Oracle and Coupa vendor estates blocked or undated entirely; two publishers at the three-event cap with further qualifying artifacts available

10 dated acts by institutions or vendors

12 searches recorded here that found nothing

6 capabilities examined

6 systems examined

Can the act be undone, and by whom?

not observable We looked and the sources we inspected did not settle it.

Question by question

What did the evidence settle, dimension by dimension?

Eighteen structural dimensions, each carrying its own evidence state and what it does not establish.

What the evidence settled for this area, question by question
Question asked	What the evidence says	What it does not tell you
consequential-object `D01`	Established by the evidence. O-2 requisition approval state; O-3 catalog or punchout item entry; O-4 contract-price catalog record; O-5 buying-policy rule	Not recorded by the method used for this area
object-holder `D02`	Established by the evidence. JAGGAER One and Dynamics 365 hold the requisition; the GSA FAS Catalog Platform holds the MAS catalog record	Not recorded by the method used for this area
grammar-or-form-setter `D03`	Established by the evidence. OpenPeppol and OASIS define the catalogue form; the FAR Council sets the value envelope inside which it operates	Not recorded by the method used for this area
composer `D04`	Established by the evidence. The preparer submits the requisition; the vendor submits the catalog file	Not recorded by the method used for this area
validator `D05`	Established by the evidence. The purchasing agent verifies; GSA awards the modification	Not recorded by the method used for this area
binder `D06`	Established by the evidence. MACHINE-PERFORMED ON O-2 - the workflow can be configured to skip review tasks and automatically approve; AWARD by the register operator for O-4	ONE OF TWO AREAS where a machine performs the binding act.
deterministic-automation `D07`	Established by the evidence. YES for O-2, on a configured deterministic path: the workflow process can also be configured to skip the review tasks and automatically approve the purchase requisition	THE CLEANEST DETERMINISTIC BINDER IN THE CORPUS: all seven chain steps coded from ONE artifact. The artifact poses the configuration question 'What expenditures can be automatically approved?' - a setting, not a practice. It names no customer, no deployment.
agentic-capability `D08`	Established by the evidence. Every capability marketed as agentic was evidenced extracting, pre-filling, routing, recommending or advising	Creating, drafting, pre-filling and submitting a requisition were evidenced repeatedly and ruled OUTSIDE the objects because none alters what a buyer is entitled to request.
furthest-deterministic-action `D09`	Established by the evidence. Transition of the requisition to Approved - THE BINDING ACT for O-2	Not recorded by the method used for this area
furthest-agentic-action `D10`	Established by the evidence. JAGGAER Purchase Requisition Approval Recommendations - automating the IDENTIFICATION of low-risk requisitions	The stop is DESCRIBED: the passage attaches 'automating' to identification rather than to the approval.
reversibility `D11`	Not answered by the evidence we checked: We looked and the sources we inspected did not settle it.. Not coded and not observable We looked and the sources we inspected did not settle it.	Not recorded by the method used for this area
externality-radius `D12`	Established by the evidence. O-4 is awarded and held on a public register (the GSA FAS Catalog Platform); the FAR Council sets the value envelope	Established for O-4. Not established for O-2, which is internal to the buying system.
counterparty-assent `D13`	A source states this does not happen: A source addressed it and said no.. For O-2 no counterparty assents and no reviewer need act - the workflow can be configured to skip the review tasks entirely	Not recorded by the method used for this area
rule-codifiability `D14`	Established by the evidence. The binding act for O-2 is a buyer-owned configuration setting evaluated by the workflow engine	The vendor's own documentation frames it as a setting. This establishes that software SETS the state; it does not establish that any buyer runs it this way, or how widely.
institutional-closure `D15`	A source states this does not happen: A source addressed it and said no.. For O-2, no institution, register, transaction infrastructure or counterparty must recognize the approval - it is a record state internal to the buying system. For O-4, GSA awards and holds	THE DECISIVE CONTRAST WITH goods-receipt-acceptance, and the pair that cannot be explained by vendor or object family (TA-03).
authoritative-state-centralization `D16`	Established by the evidence. SPLIT: JAGGAER One and Dynamics 365 hold the requisition; the GSA FAS Catalog Platform holds the MAS catalog record	C-009: GSA BOTH holds the record AND displaces one of the document forms governing it - form-defining and record-holding are not always separate parties.
consequence-of-error `D17`	Not answered by the evidence we checked: We looked and the sources we inspected did not settle it.. What follows an erroneously auto-approved requisition is not established We looked and the sources we inspected did not settle it.	The documentation poses the exposure question - 'What expenditures can be automatically approved?' - and does not answer it.
accountability `D18`	Not answered by the evidence we checked: We looked and the sources we inspected did not settle it.. No stable answerable party evidenced We looked and the sources we inspected did not settle it.	Not recorded by the method used for this area

Capabilities

What is each capability evidenced doing?

The mode records that a named subject performs an operation. It does not record what kind of performer that subject is, and several rows disclaim an agentic mechanism in their own limitation.

Capabilities examined in this area
Capability	How far it goes	What it does	Human work still needed	What this does not tell you
Coupa approval chains and per-user approval limits, as described in Coupa's own Approvals documentation. `C-001`	prepares the work, stops before it counts	Composes the approval chain by reading monetary limits and inserting approvers: 'If the original requester has a self approval limit less than the requisition, expense report, or invoice, then Coupa adds their next approver to the approval chain.'	Every approval act in the composed chain. No inspected passage states that Coupa sets the approval state itself.	Does not establish that Coupa sets any requisition's approval state. Establishes only that Coupa reads monetary limits and composes the chain of humans who will. The exclusion is a statement about what this artifact evidences, not about the product's capability.
The Dynamics 365 Supply Chain Management purchase requisition workflow, configurable to skip review tasks. `C-002`	performs the operation itself	Sets the requisition's approval state without a review task being performed: 'The workflow process can also be configured to skip the review tasks and automatically approve the purchase requisition.' The configuration question the documentation itself poses is 'What expenditures can be automatically approved?'	Configuring the workflow, and defining which expenditures may be automatically approved. The approval act itself is performed by the workflow process on the configured path.	This is deterministic workflow automation configured by the buying organisation, NOT an agentic capability, and the row must not be read as evidence of one (operating rule 7). It establishes that software sets the approval state on a configured path; it does not establish that any adaptive or agentic capability does, that any buyer runs it this way, or how widely the configuration is used. No prevalence claim of any kind rests on this row.
The submitRequisition action on the purchaseRequisitions resource in the Oracle Fusion Cloud Procurement REST API. `C-003`	the sources do not settle whether it acts or only prepares	A machine interface (HTTP POST) that submits a requisition for approval and, under two named conditions, causes the approvals workflow not to run. What state the requisition then holds is not stated.	Not established, and that is precisely the unresolved point: if the approvals workflow is bypassed, no artifact states whether a human approval remains outstanding.	Does not establish that any Oracle capability sets a requisition's approval state, and does not establish that it does not. This is a refusal on a named gap, not on absence.
Zip's suite-wide AI agents for intake and requests, including AI-powered workflow routing, AI-assisted intake and the Price Negotiation Agent. `C-004`	prepares the work, stops before it counts	Routes the requester ('Requesters are intelligently guided to the correct intake form, internal catalog, external marketplace, or third-party system'), composes the request ('Purchase requests can now be pre-filled with AI-extracted details from documents'), and advises ('instant answers on spend limits or compliance requirements').	Every state change on every in-scope object. No inspected passage describes an operation that changes one.	Naming a catalog as a destination a requester is guided to is not an operation on the catalog record. The exclusion rests on what the vendor's own artifact describes and says nothing about the product's quality, adoption or capability.
JAGGAER One 24.3 Purchase Requisition Approval Recommendations, and the 'Guide Me' Wizard guided-buying experience. `C-005`	prepares the work, stops before it counts	Identifies low-risk requisitions and presents that assessment to approvers. The Guide Me wizard provides 'infrequent buyers an easy step-by-step, structured guided buying experience ensuring compliance with every purchase.'	The approval act. A recommendation addressed to an approver presupposes the approver.	Establishes an assessment presented to an approver, not a change to any approval state. The word 'automating' in the passage governs identification and is not evidence that any approval is performed by software.
None identifiable. The artifact's subject is 'An AI agent', which names no offering under test. `C-006`	does not apply here	As described: 'grabs the requisition' (read), 'checks vendor details and pricing against current contracts' (read of O-4), 'confirms budget availability' (read, not an encumbrance state change on O-6), 'generates and routes the PO' (write to X-A).	Not established; the artifact states 'without any manual work' and describes no mechanism.	The exclusion is of this artifact's described capability, not of GEP. It says nothing about any named GEP offering, none of which was tested here. 'automatically' and 'without any manual work' are the words T-15 names and no mechanism passage accompanies them.

Infrastructure

Whose systems does this area run on?

What part each system plays was decided by what it does to the area's records, never by what kind of company runs it. Where the sources leave that open the entry says so, because an open question is not a kind of system.

Systems examined in this area
System	Who runs it	What part it plays	What it does to the official record
Peppol BIS Catalogue (T19) and Peppol BIS Punch Out (T77) — the specifications governing the permissible form of the catalog record and the punch-out cart `C-007`	OpenPeppol AISBL, Post-Award Community	form-defining-body	mutates — the Peppol BIS Catalogue and Punch Out specifications, held and versioned by OpenPeppol itself; none-established — the catalogue and punch-out INSTANCES, which OpenPeppol neither holds nor transmits
The UBL 2.4 Catalogue Schema `C-008`	OASIS Open — Universal Business Language Technical Committee	form-defining-body	mutates — the UBL Catalogue Schema, held and versioned by OASIS; none-established — catalogue instances, which OASIS neither holds nor transmits
FAS Catalog Platform (FCP) — the platform holding the MAS catalog record and publishing it to GSA Advantage `C-009`	U.S. General Services Administration	authoritative-register	holds — the MAS catalog record, in the FAS Catalog Platform itself; accepts-or-rejects — catalog additions and changes, which publish only on GSA's award of the modification in eMod
The Federal Acquisition Regulation as the buying-policy and threshold rule record `C-010`	Federal Acquisition Regulatory Council — OFPP/OMB, DoD, GSA and NASA	authoritative-register	holds — the Federal Acquisition Regulation itself; mutates — the thresholds and purchasing requirements within it, which bind every Federal buyer
Transaction Set 832 Price/Sales Catalog `C-011`	X12 (Accredited Standards Committee X12)	form-defining-body	mutates — the 832 transaction set definition, held and versioned by X12; none-established — the 832 instances, which X12 neither holds nor transmits
Commercial Platforms Program — the awarded-platform channel through which federal micro-purchases may be made `C-012`	U.S. General Services Administration	authoritative-register	holds — the awarded-platform list and the programme rules, which determine the permissible channel; none-established — the catalog records on the awarded platforms, which the platform operators hold

Claims

What may be said from this area, and what may not?

Each one carries how far it is backed and, where it was recorded, the exact stronger sentence that may never be written from it.

CL-01 Observed

One inspected first-party artifact states that a requisitioning system can be configured to set a purchase requisition's approval state with no review task performed by a person: 'The workflow process can also be configured to skip the review tasks and automatically approve the purchase requisition.'

The strongest thing against it None was found. No inspected artifact states that this configuration is unavailable or that a human act is required on the skip-review path.

What may not be said from this Must NOT be phrased as 'requisition approval is now automated', 'AI approves requisitions', or any statement implying prevalence, adoption or agentic capability.

CL-02 Observed

The capability evidenced setting the approval state is deterministic workflow automation configured by the buying organisation. Every capability in this area that is named or marketed as agentic was evidenced doing something else: extracting, pre-filling, routing a requester, recommending, or advising.

The strongest thing against it JAGGAER's Purchase Requisition Approval Recommendations is the nearest approach: it places a machine operation directly on the approval of a requisition. It is refused because the passage attaches 'automating' to the identification of low-risk requisitions and not to the approval.

What may not be said from this Must NOT be phrased as 'agentic procurement tools cannot approve requisitions' or as any claim about product capability. The evidence is about what artifacts describe.

CL-03 Observed

Creating, drafting, pre-filling or submitting a requisition was evidenced repeatedly; each of these was ruled outside this area's objects before discovery began, because none of them alters what a buyer is entitled to request.

The strongest thing against it None was found.

What may not be said from this Must NOT be phrased as 'agents only draft requisitions' — CL-01 records a machine-set approval state on a different row.

CL-04 Pattern

The permissible form of the catalog record in this area is set by bodies that hold no instance of it, and each of the three names the systems that do: the seller's punch-out system and the buyer's local ERP system, the implementing ERP vendors and public authorities, and the trading partners exchanging the EDI document.

The strongest thing against it C-009: GSA's FAS Catalog Platform both holds the catalog record and, in its own channel, displaces one of these document forms (EV-09). Form-defining and record-holding are not always separate parties.

What may not be said from this Must NOT be phrased as a general property of procurement, and must NOT be stated as a ranking or a count of how much of the market these bodies govern.

CL-05 Observed

The rule determining what a buyer may request, and below what value without further competition, was changed three times inside the observation window by institutions that operate none of the buying systems the rule governs.

The strongest thing against it None was found. No inspected artifact shows a buying-policy rule in this area being changed by a party that operates the buying systems.

What may not be said from this Must NOT be phrased as a rate, a trend, an acceleration or a forecast of institutional rule-making.

CL-06 Not established

No causal link is established between any institutional rule change in this area and the behaviour of any platform, product or buying system.

The strongest thing against it EV-07 and C-012 both name the federal micro-purchase, which is the closest the evidence comes to a link. It establishes that the threshold governing a channel changed; it establishes nothing about how the channel or its operators responded.

What may not be said from this Must NOT be softened into 'institutional rule changes drive platform behaviour' or any causal phrasing.

CL-07 Observed

Where a catalog record's price is carried into the buying moment through a public register, the state change that makes an addition or change effective is an award performed by the register's operator, and the automatic step is the publication that follows it.

The strongest thing against it The deletion limb itself: 'For deletions, the details submitted on the Product or Services Plus File will automatically publish when the modification is submitted in eMod.' Removal from the catalog passes no award gate.

What may not be said from this Must NOT be phrased as 'catalog publication is automated' without the award gate stated in the same sentence.

CL-08 Not established

Whether a requisition submitted through Oracle Fusion Cloud Procurement's REST interface reaches an approved state when the approvals workflow is bypassed is not established.

The strongest thing against it None. No artifact was found stating either the presence or the absence of an approved state on this path.

What may not be said from this Must NOT be reported as evidence that Oracle does not set approval states, nor as evidence that it does.

CL-09 Observed

At the cutoff register of 2025-12-31 the participant population contains one qualified row, and at the current register of 2026-08-15 it also contains one qualified row. This is a statement about evidenced state changes on this area's objects in inspected public artifacts, and it is not a statement about how many relevant products exist.

The strongest thing against it C-003 sits unresolved at both registers on a named gap; had that gap been closed either way, the count could differ.

What may not be said from this Must NOT be phrased as a share, a rate, a proportion of the market, or as evidence that few products do this.

CL-10 Observed

The seven-step chain was coded end to end on one mechanism in this area, and the binding step — the transition to an approved requisition — is evidenced as performable by software on a configured path.

The strongest thing against it Every other mechanism inspected in this area failed to complete the chain at the binding step, and in each case the step that failed to complete was a step no artifact described.

What may not be said from this Must NOT be phrased as 'a machine agent completes the procurement chain' or as any statement about agentic capability completing it.

CL-11 Observed

The event series for this area contains ten dated events against a target of twelve to twenty, and every claim resting on it carries that shortfall as a disclosure limitation.

The strongest thing against it None applicable.

What may not be said from this Must NOT be reported as a complete or representative record of activity in this area.

Dated acts

What dated acts touch this area's records?

A list, in date order. It is not a timeline and carries no rate: the collection capped each publisher, so this is a floor on what was retrievable rather than a count of what occurred.

Dated acts touching this area
Date	Kind of act	Consequence recorded	Source
2024-01-29 `day precision`	workflow expansion	none stated	source
2024-04-22 `day precision`	institutional rule change	Changes what a Federal buyer must request: 'FAC 2024-05; FAR Case 2022-006, Item 1', effective 'May 22, 2024.'	source
2024-06-20 `day precision`	institutional rule change	A new version of the permissible form of the catalog document is ratified at OASIS Standard level.	source
2024-11 `month precision`	institutional rule change	The permissible content of the punch-out cart and the catalogue message is extended.	source
2024-12-12 `day precision`	named deployment	none	source
2025-05-21 `day precision`	institutional rule change	The change carries a compliance date: 'Mandatory use from: 2025-08-25.'	source
2025-08-27 `day precision`	institutional rule change	Changes the value below which a buyer may request without further competition: 'Simplified acquisition threshold: increased from $250,000 to $350,000', 'FAC 2025-06, FAR Case 2024-001', 'Effective: October 1, 2025.'	source
2025-09-16 `day precision`	institutional rule change	The rule governing simplified procedures is displaced for one agency's workforce, reorganised into 'lifecycle-based subparts (presolicitation, solicitation/evaluation/award, postaward, micro-purchases)'.	source
2025-11-21 `day precision`	workflow expansion	none stated	source
2025-11-24 `day precision`	institutional rule change	The change carries a compliance date after the frozen cutoff: 'Mandatory use from: 2026-02-23.'	source

Routes that returned nothing

Where did the search stop, and why?

A route that returned nothing establishes that the route returned nothing. A missing capture is a property of the archive, never a property of the world.

Retrieval routes that returned nothing
Source checked	How it failed	What was recorded
federalregister.gov	HTTP 302 redirect to https://unblock.federalregister.gov/ — a bot gate on a cross-host redirect	BLOCKED HOST. Resolved by retrieving the identical documents from the GPO govinfo mirror; EV-02 and EV-07 rest on govinfo.
SAP Help Portal (guided buying / Buying and Invoicing approval process management)	Page served as a JavaScript application shell; no body text retrievable ('SAP Help Portal \| SAP Online Help' header only)	BLOCKED ESTATE. SAP holds candidate offerings for this area and NO SAP unit could be admitted to either population. This is a disclosure-boundary gap, not an absence.
Oracle Cloud readiness 'What's New' and product documentation	Four URLs inspected across the 24C, 25A and 26A estates and the REST API reference; NONE carried a page-visible date. Release labels ('24C', '25A') are not dates (operating rule 4).	NIL ROUTE FOR EVENTS. The estate supported one qualification row (C-003) with the no-date limitation recorded, and contributed no event.
Coupa product documentation and release-note index	The Approvals documentation PDF carries no page-visible date. The release-note index carries page-visible release names ('September 2025 Release (R43)') but no feature entries naming requisitions, approvals, catalogs or contract pricing.	NIL ROUTE FOR EVENTS. Supported one qualification row (C-001) with the no-date limitation recorded.
Amazon Business punchout and integration content	No dated in-window first-party artifact located describing a state change on an record in scope for the area.	NIL ROUTE. Amazon Business is named on GSA's own artifact as an awarded Commercial Platforms operator (C-012) but was NOT admitted as a unit in its own right on this evidence.
Acquisition.gov FAR Overhaul Part 13 model deviation text	Retrieved and inspected. Page-visible date 'Sep 18 2025', inside the window, issued by the FAR Council — but the page names NO record in scope for the area and does not state what it changes about simplified procedures, micro-purchases or thresholds.	REFUSED ON PLACEMENT (T-03; stop condition 6). A dated in-window artifact was declined rather than admitted to raise the event count. The substance is carried by EV-08, whose artifact does name the object.
X12 EDI Standard release schedule	Retrieved and inspected. Page-visible dates present ('008060 (Available February 2025)', '008050 (Available January 2024)'), both in window — but the 832 Price/Sales Catalog is not named anywhere on the dated page.	REFUSED ON PLACEMENT (T-03; stop condition 6). This is the cause of C-011's unresolved-at-cutoff standing.
OASIS press announcement of UBL 2.4	Retrieved and inspected. Page-visible date '27 Jun 2024', in window — but names no record in scope for the area ('the leading interchange format for business documents', '93' document types).	REFUSED ON PLACEMENT. EV-03 rests instead on the specification itself, which carries both a page-visible date and a passage naming the Catalogue.
DFARS Sustainable Procurement final rule (DFARS Case 2024-D024)	Retrieved and inspected. Page-visible date 2024-08-15, in window, and a new publisher (DoD) that would have diversified the actor set — but the rule states of itself: 'None of the changes in this rule affect the DFARS substantively. This rule does not alter policy or requirements stated in the DFARS.'	REFUSED ON SUBSTANCE. A rule-record change that alters no entitlement fails this area's inclusion boundary. Declining it cost the event series a distinct actor.
Zip and GEP dated first-party announcements	Both dated and in window (2025-10-21, 2025-11-04) and both retrieved. Zip's operations act on the requester and the request under composition (X-I, O-1); GEP's writes land on the purchase order (X-A).	REFUSED ON PLACEMENT. Two dated in-window vendor artifacts declined. Both support qualification rows (C-004, C-006) where the placement question is not asked the same way.
Ivalua platform release announcements	The release naming purchase-requisition functionality is dated '29 August, 2023', BEFORE observation_window_start (2024-01-01). The IVA Studio launch is dated after the frozen cutoff.	OUT OF WINDOW at both ends. No Ivalua unit admitted.
Microsoft Dynamics 365 release-plan wave overviews	Inspected for in-window procurement features. The wave overview's own date is after the frozen cutoff, and the procurement-adjacent agent it describes writes to purchase orders (X-A).	NIL ROUTE FOR EVENTS. The Microsoft estate supported the area's only qualified the capabilities examined row (C-002) from product documentation, and contributed no event.