Supply Chain · Procurement

Purchase requisition to purchase order, in one flow

A requisition is raised once, with its cost object and destination on every line. Approval, sourcing, RFQ, quote comparison, award and the purchase order follow from it. Nothing is retyped, and every document carries its own number and its lineage.

From need to order

Six steps, each one a page in the product, each one numbered and approved.

1
Requisition
Lines with item, quantity, need-by date, destination warehouse and cost object. Routes to its approval tier on save. Bulk import from a sheet.
2
Sourcing cockpit
For each approved line the engine proposes direct PO, RFQ or subcontract from the approved vendor list and the item-vendor matrix. Override, then generate.
3
RFQ
One RFQ per sourcing event with its own number. Sent to several vendors at once with terms and attachments at run level.
4
Quotes
Vendors quote from a link; offline quotes are recorded by the buyer. Revisions are numbered. Landed cost in base currency ranks them.
5
Award
Award a vendor per line or whole. The award enters its approval tier; the PO is built from the quote one-to-one.
6
PO, receipt, invoice
PO auto-sent on approval. GRN against PO lines. Purchase invoice three-way matched; reconciliation flags the rest.

How a line is sourced

The cockpit treats each requisition line on its own merits.

Inside the product

Requisitions

Raise demand and advance it to sourcing. Project, budget line and destination warehouse are set per line and flow forward; the header is derived from the lines, so multi-site requisitions need no splitting.

Per-line cost object and destination warehouse
Auto-routing to the approval tier, chain previewed on the form
Need-by date drives the long-lead planner

Sourcing

Source approved requisitions. The engine proposes direct PO, RFQ or subcontract per line from the approved vendor list; review, override, and generate the purchase documents. RFQ and PO terms plus attachments are set once for the run.

Preferred source from the item-vendor matrix by default
Split RFQs by commodity category
Run-level terms and attachments snapshotted on every document

RFQs and quotes

Draft, send, collect and compare quotes, including vendor quotes sent without an RFQ. Lifecycle tiles show drafts, sent, quotes received, awarded and moved to PO.

RFQ number per sourcing event; vendor codes and revision numbers
Landed-cost comparison with FX, freight and delivery basis
Vendor responds from their supplier login or a secure link

Purchase orders

Buyer-side purchase orders with ordered value, receipts, invoices, payment and full lineage from requisition to invoice. Your template, your terms, per-line ship-to, GST.

Commercial terms stored as data, copied one-to-one from the quote
Templated reminders to the vendor contact; delayed POs on tiles
Signature policy and a DRAFT watermark until approved

Purchase invoices and reconciliation

Supplier invoices with three-way match against PO and GRN. Reconciliation auto-matches invoices, receipts and orders over a date range and routes discrepancies for approval.

Line-level match: ordered, received, invoiced
Discrepancies flagged and approved, not silently accepted
Every delivery fully invoiced before the PO closes

Speaks your market's language

The documents keep their meaning across markets; the labels follow yours.

Requisition

Indent · PR · material request

Sourcing event

Enquiry round · tender · bid package

Award

L1 selection · vendor finalisation · comparative statement approval

Questions buyers ask

Is there a submit button on the requisition?: No. A requisition routes to its approval tier the moment it is created. If no tier applies, it proceeds straight to sourcing. The form shows the approval chain before you save.
Can one requisition become several purchase documents?: Yes. The sourcing cockpit decides per line: a direct PO where a contract rate exists, an RFQ where quotes are needed, a subcontract order where a vendor does the work. One requisition can produce all three.
How are quotes in different currencies compared?: Quotes are ranked on landed cost in your base currency using the FX rates you maintain, with freight, charges and delivery terms included.
What happens when a quote is awarded?: The award goes to its approval tier. On approval, the PO is created from the quote one-to-one (prices, payment schedule, charges, discount) and e-mailed to the vendor on your template. Rejecting or superseding withdraws the pending award.
Does it do three-way matching?: Purchase invoices match against the PO and the GRN line by line. Purchase reconciliation auto-matches invoices, receipts and orders over a date range and flags discrepancies for approval.

Send your first RFQ today

Import items and vendors from a sheet, raise a requisition, and let sourcing take it from there.

Get started free Explore the product

Loading…

From need to order

Six steps, each one a page in the product, each one numbered and approved.

Requisition

Lines with item, quantity, need-by date, destination warehouse and cost object. Routes to its approval tier on save. Bulk import from a sheet.

Sourcing cockpit

For each approved line the engine proposes direct PO, RFQ or subcontract from the approved vendor list and the item-vendor matrix. Override, then generate.

RFQ

One RFQ per sourcing event with its own number. Sent to several vendors at once with terms and attachments at run level.

Quotes

Vendors quote from a link; offline quotes are recorded by the buyer. Revisions are numbered. Landed cost in base currency ranks them.

Award

Award a vendor per line or whole. The award enters its approval tier; the PO is built from the quote one-to-one.

PO, receipt, invoice

PO auto-sent on approval. GRN against PO lines. Purchase invoice three-way matched; reconciliation flags the rest.

Inside the product

Requisitions

Per-line cost object and destination warehouse
Auto-routing to the approval tier, chain previewed on the form
Need-by date drives the long-lead planner

Sourcing

Preferred source from the item-vendor matrix by default
Split RFQs by commodity category
Run-level terms and attachments snapshotted on every document

RFQs and quotes

Draft, send, collect and compare quotes, including vendor quotes sent without an RFQ. Lifecycle tiles show drafts, sent, quotes received, awarded and moved to PO.

RFQ number per sourcing event; vendor codes and revision numbers
Landed-cost comparison with FX, freight and delivery basis
Vendor responds from their supplier login or a secure link

Purchase orders

Buyer-side purchase orders with ordered value, receipts, invoices, payment and full lineage from requisition to invoice. Your template, your terms, per-line ship-to, GST.

Commercial terms stored as data, copied one-to-one from the quote
Templated reminders to the vendor contact; delayed POs on tiles
Signature policy and a DRAFT watermark until approved

Purchase invoices and reconciliation

Supplier invoices with three-way match against PO and GRN. Reconciliation auto-matches invoices, receipts and orders over a date range and routes discrepancies for approval.

Line-level match: ordered, received, invoiced
Discrepancies flagged and approved, not silently accepted
Every delivery fully invoiced before the PO closes

Questions buyers ask

Is there a submit button on the requisition?

No. A requisition routes to its approval tier the moment it is created. If no tier applies, it proceeds straight to sourcing. The form shows the approval chain before you save.

Can one requisition become several purchase documents?

Yes. The sourcing cockpit decides per line: a direct PO where a contract rate exists, an RFQ where quotes are needed, a subcontract order where a vendor does the work. One requisition can produce all three.

How are quotes in different currencies compared?

Quotes are ranked on landed cost in your base currency using the FX rates you maintain, with freight, charges and delivery terms included.

What happens when a quote is awarded?

The award goes to its approval tier. On approval, the PO is created from the quote one-to-one (prices, payment schedule, charges, discount) and e-mailed to the vendor on your template. Rejecting or superseding withdraws the pending award.

Does it do three-way matching?

Purchase invoices match against the PO and the GRN line by line. Purchase reconciliation auto-matches invoices, receipts and orders over a date range and flags discrepancies for approval.