How it works · Flow F6
Requisition to vendor payment with a three-way match
Requisitions, supplier discovery, RFQs, comparison, purchase orders, goods receipt, bill capture, 3-way match and payment run in one governed chain.
What the Procure to pay flow does
Procure to Pay covers buying from suppliers and paying them correctly.
A requisition is raised by hand or by a reorder rule, then approved per DoA. A supplier discovery agent proposes approved vendors and new candidates. RFQs go out and quotations are captured by parsing email. A comparison matrix ranks price, lead time, quality score and terms. Negotiation messages are drafted by an agent (A2) and sent by a human. The PO is issued (R3) and acknowledged in the vendor portal.
Goods arrive and are received with a quality check in Inventory. The supplier bill is captured by OCR and matched three ways: PO, goods receipt and bill. Mismatches go to an exception queue. Matches go to payment scheduling, which needs R4 approval before a bank or UPI payout. TDS and GST input credit are handled, the ledger is posted and the vendor score is updated.
Procurement and Inventory are Operations modules planned for W4 (Year 3). Payments through bank or UPI rely on licensed partners.
Every step on this page is an Action: a typed verb with a risk tier (R0 read-only to R4 irreversible or financial), a permission check and a reversibility class. Agents and humans call the same Actions, so the same approval rules apply whether a person clicks a button or a Digital Employee acts.
Procure to pay, step by step
Thirteen steps. Money moves only after a human approves.
- 1
1. Requisition
**Operations · Procurement · Inventory.** Raised by a person or by a reorder rule.
- 2
2. Approval per DoA
**Human gate · Approvals Inbox.** The requisition is approved per the delegation-of-authority matrix.
- 3
3. Supplier discovery
**Supplier discovery agent (Procurement).** Proposes approved vendors and new candidates with evidence.
- 4
4. RFQ and quotation capture
**Operations · Procurement.** RFQs are sent and quotations captured by parsing supplier emails.
- 5
5. Comparison matrix
**Procurement.** Price, lead time, quality score and terms side by side.
- 6
6. Negotiation drafts (A2)
**Procurement agent.** Drafts negotiation messages. A human reviews and sends.
- 7
7. Issue the PO (R3)
**Human gate.** The purchase order is issued and the vendor acknowledges it in the vendor portal.
- 8
8. Goods receipt and quality check
**Operations · Inventory & Warehouse.** GRN with a quality check.
- 9
9. Bill capture by OCR
**Finance · Accounts · Document Extractor utility agent.** The bill is read and fields extracted.
- 10
10. Three-way match
**Finance · Accounts.** PO, GRN and bill are matched.
- 11
11. Exception queue
**Finance.** Mismatches go to a human exception queue.
- 12
12. Payment scheduling and approval (R4)
**Human gate.** Payment is scheduled and approved with a second factor before a bank or UPI payout via a licensed partner.
- 13
13. Tax, ledger and vendor score
**Finance · Accounts · Tax Engine.** TDS and GST input credit, ledger posting and a vendor score update.
Segregation of duties
The same principal — or two agents with the same owner — cannot both create and approve a payment or a new vendor. This applies across human–agent pairs where the human owns the agent.
Wave
Procurement and Inventory are planned for W4 (Year 3). They are not part of the Year-1 product.
Apps involved
Each step runs as a typed, permissioned Action inside one of these apps. Nothing happens outside the Action contract.
Operations
Procurement handles requisitions, RFQs, comparison and POs; Inventory & Warehouse handles goods receipt and quality checks.
Learn moreFinance
Accounts captures bills, runs the 3-way match and posts the ledger; Payments Hub and Tax Engine handle payouts, TDS and GST.
Learn moreAI Workforce
Procurement agents discover suppliers and draft negotiations; the Document Extractor utility reads bills.
Learn moreOne3 Ecosystem
Vendor portals let suppliers acknowledge POs.
Learn morePlatform
Approvals Inbox and segregation-of-duties policies stop the same principal creating and approving a payment.
Learn moreQuestions about this flow
Can an agent pay a supplier?
No. Payment approval is R4. It always needs a human approval and a second factor.
What happens when the bill does not match?
It goes to an exception queue for a person to resolve. Nothing is paid on a mismatch.
Who sends negotiation emails?
An agent drafts them at A2. A human reviews and sends.
How are bank details in invoices handled?
A bank account read from an email is evidence for a proposed change only. Changing vendor bank details goes through an approved path with a human.
When is this flow planned?
Procurement and Inventory are planned for W4, in Year 3.
Shape Procure to Pay early
If you run purchasing on spreadsheets and email today, tell us where it breaks.
Apps involved
Where this happens in One3
Platform
One governed foundation for every human, AI agent, integration and channel
ExploreFinance
Bill, collect, pay, account, plan and comply on the records your business already keeps
ExploreOperations
Buy, stock, make, move, maintain and service physical goods on one Item master
ExploreAI Workforce
Rent ready-made AI Digital Employees that work for your team, with a monthly ROI statement
ExploreOne3 Ecosystem
The governed network of apps, agents, experts and partners around One3
ExploreMore in How it works
- Tenant onboarding
- Lead to cash
- Campaign loop
- Issue to resolution
- Hire to retire
- Order to delivery
- Record to report
- Idea to release
- Goal to outcome
- Agent lifecycle
- Model improvement
- Pack upgrade
- DPDP data-principal requests
- AI incident
- Rent a Digital Employee
- Switch to One3 in a weekend
- Monthly Agent Investment Statement
- Goal to verified statement