AI agents in procurement

Procurement is one of the most structured conversations two companies have: request a quote, compare offers, issue a purchase order, confirm it, ship, invoice, pay. The transaction steps have had electronic standards for decades. The steps around them, such as clarifying a spec, negotiating a delivery date, answering an onboarding questionnaire or disputing an invoice line, often still move by email and meetings. Both sides want those steps faster, which makes procurement one of the more natural places for agents from different companies to talk directly.

Where agents meet today

EDI and cXML

X12 covers the order-to-cash documents:

X12 set	Name
850	Purchase Order
855	Purchase Order Acknowledgment
856	Ship Notice/Manifest
810	Invoice
820	Payment Order/Remittance Advice

cXML is another format for the same documents. Its site describes it as a protocol for business documents between procurement applications, e-commerce hubs and suppliers, covering catalogs, PunchOut, purchase orders with changes, order confirmations, ship notices and invoices.

What neither format carries well is the negotiation before the order and the reasons behind a disputed line after it. An RFQ with three rounds of clarifications has no standard message. That is the part an agent exchange would carry, ending in an 850 or cXML order that the existing systems already accept.

Supplier onboarding

Before a supplier gets a first order, the buyer collects tax, banking, insurance and compliance documents, and often a security questionnaire. Each buyer asks in its own format. An agent exchange lets the supplier’s agent answer once from its own records, with each answer tied to a document the buyer can verify.

An RFQ as an agent exchange

Illustrative:

1. The buyer’s agent sends an RFQ to three approved suppliers’ agents: part number, quantity, required date, delivery terms.
2. Each supplier’s agent asks clarifying questions or returns a quote with price, lead time and validity.
3. The buyer’s agent compares quotes against its limits and either awards within them or asks a person to approve.
4. The award becomes an 850 or cXML order, and the supplier’s 855 or confirmation closes the loop.

The negotiation in steps 1 to 3 is the part that has no standard message today. Steps 4 onward already have one.

Top use cases

Use case	Who talks to whom	What it replaces
RFQ to purchase order	Buyer agent and supplier agents	Emailed RFQs, spreadsheets of bids, clarification threads
Vendor onboarding and KYC	Buyer agent and supplier agent	Portal uploads and repeated document requests
Vendor security questionnaires	Buyer security agent and supplier trust agent	Long spreadsheets answered by hand
Invoice disputes and collections	Accounts payable agent and accounts receivable agent	Emails and calls about short payments and mismatched lines
NDA exchange and scheduling	Legal or sales agents on each side	Redline ping-pong before a first meeting

After the purchase, support tickets follow the same pattern; see IT vendor support.

Regulatory considerations

Business-to-business purchasing has less sector-specific regulation than consumer markets. The rules that matter most for agents concern contract formation, who you may trade with, and supply-chain reporting. Checked on 26 September 2026. This is not legal advice.

Contracts formed by agents

• United States. The federal E-SIGN Act says a contract relating to interstate or foreign commerce may not be denied legal effect solely because electronic agents were involved in forming it, as long as the agent’s action is legally attributable to the person to be bound. Attribution is the practical question: whose agent was it, and was it acting within what that company authorized?
• Canada. Ontario’s Electronic Commerce Act, 2000 states that a contract may be formed by the interaction of electronic agents (section 20). Section 21 covers errors: a transaction between an individual and another person’s electronic agent is not enforceable against the individual if the individual made a material error, the agent gave no chance to prevent or correct it, and the individual acted promptly on discovering it. Other provinces have their own electronic commerce statutes.

Sanctions screening

• United States. OFAC publishes the Specially Designated Nationals list. OFAC states that SDNs’ assets are blocked and US persons are generally prohibited from dealing with them.
• Canada. Global Affairs Canada publishes the Consolidated Canadian Autonomous Sanctions List covering sanctions under the Special Economic Measures Act and the Justice for Victims of Corrupt Foreign Officials Act. The government notes the list may not be up to date and points readers to the regulations themselves.

A buyer’s agent that can award business needs a screening step before the award, the same as a human buyer.

Forced labour in supply chains

• United States. Under the Uyghur Forced Labor Prevention Act, CBP presumes that goods made wholly or partly in Xinjiang, or by an entity on the UFLPA Entity List, are barred from import unless the importer rebuts that with clear and convincing evidence. CBP has enforced it since 21 June 2022.
• Canada. The Fighting Against Forced Labour and Child Labour in Supply Chains Act requires reporting entities to report to the Minister by 31 May each year on the steps taken in the previous financial year to reduce forced and child labour risk.

Both regimes run on supplier evidence, which is the kind of document exchange agents can structure and keep a record of.

Privacy

Supplier contact data is personal information. In Canada, Bill C-36, introduced on 15 June 2026 to replace Part 1 of PIPEDA, is at second reading in the House of Commons.

Where to start

1. Pick a narrow, frequent exchange. Purchase order acknowledgments and delivery-date confirmations are high volume and easy to check against the 855 or cXML confirmation.
2. Write the agent’s authority down. Spending limits, approved suppliers, and which terms it may accept. A signed, scoped mandate makes that authority checkable by the other side. Delegated authority explains the pattern.
3. Keep the order on existing rails. Let agents negotiate, then emit the 850 or cXML order the supplier’s systems already ingest.
4. Put screening before award. Sanctions and forced-labour checks belong in the buyer agent’s flow, with the evidence stored.
5. Keep a signed record. When an invoice is disputed months later, both sides need the same record of what was agreed and by whose agent.