Request
A purchase request or requisition for items, categories, services or non-inventory purchases, with quotes and supporting documents.
Procurement
Request → approval → PO → confirmation → receipt → invoice matching → ERP, on one connected record.
Stream Procurement covers purchase requests and requisitions, configurable request and PO approvals, PO creation in the ERP, confirmation and amendment handling, partial and full receipts, two-way and three-way matching and the invoice that follows, with every step visible and connected.
Item, category, service and non-inventoryApproved POs created in the ERPReceipts synced back from D365Connected PR, PO, receipt and invoice history
Deeply connected to the ERPs finance teams run
The process
The complete procure-to-pay lifecycle in Stream
Each stage is a screen in Stream, not a concept. The request, the PO, the receipts and the invoice stay linked, so anyone can answer where a purchase is and what is still owed.
1Request
2Approval
3Purchase order
4Confirmation
5Receipt
6Invoice matching
7ERP
Approval
Configurable request approvals by amount, department, entity, project and role, with one-off approvers when needed.
Purchase order
The approved request creates a purchase order in the ERP (standard, blanket or release) and sends it to the vendor.
Confirmation
Vendor confirmation, date or quantity amendments and change orders tracked; amendments re-route through approval rules.
Receipt
Partial and full receipts recorded in the ERP or Stream and synchronized back to the request and PO.
Invoice matching
The vendor invoice matches to PO and receipt lines with tolerances; discrepancies route to the buyer.
ERP
The matched, approved invoice posts to the ERP with the PO reference; payment status flows back.
Capabilities, shown
Each procurement capability with the screen where it happens
Request
Purchase requests and requisitions with configurable approvals
Requesters choose items, categories, services or non-inventory purchases, attach quotes and specs, and submit. Approval routes by amount, department, entity, project and role, with additional or one-off approvers and a full approval history on the request.
- Item, category, service and non-inventory purchases
- Amount, department, entity, project and role-based routing
- Supporting documents and approval history
Order
Approved POs created in the ERP, confirmation and amendments tracked
Approved requests become purchase orders in the ERP: standard, blanket or release. Stream sends the PO to the vendor, tracks confirmation, reminds when it is overdue, and handles date, quantity and price amendments through your rules before the ERP is updated.
- Creation of approved POs in the ERP
- PO confirmation and amendment handling
- PO, receipt and invoice status visibility
Receive and match
Partial and full receipts, then two-way and three-way matching
Receipts recorded in the ERP (including D365 product receipts) synchronize back to Stream and attach to the PO. When the invoice arrives it matches line by line with price and quantity tolerances; variances and missing receipts route to the buyer or receiver.
- Partial and full receipts
- D365 receipt synchronization back to Stream
- Two-way and three-way matching with discrepancy routing
Monitor
Integration-error monitoring and connected history
PO creation, updates and invoice postings are logged with every attempt. Errors show the ERP message, are assigned and retried in Stream. The request, PO, receipts, invoice and payment appear as one connected history.
- Integration-error monitoring
- Connected PR, PO, receipt and invoice history
- Commitment and open-PO visibility
Also in procurement
Approvals, mobile and audit, shared with AP and expenses
Questions
Procurement FAQs
Can Stream create purchase orders in the ERP?
Yes. Approved requests create purchase orders in D365 Finance & Operations, Business Central, NetSuite and other supported ERPs through the integration, so the PO exists in the system of record and Stream tracks its lifecycle.
Do receipts recorded in the ERP show in Stream?
Yes. Product receipts and goods receipt notes recorded in D365 and other supported ERPs synchronize back to Stream and attach to the PO, so 3-way matching runs as soon as goods arrive.
How are PO amendments handled?
Quantity, price, date and line changes are captured as amendments. Depending on your rules they re-route through approval before the ERP PO is updated, and the history shows every version.
What is the difference between two-way and three-way matching?
Two-way compares the invoice to the PO (price and quantity within tolerance). Three-way also requires a receipt for the invoiced quantity. Stream supports both, per vendor, category or entity.
Is procurement required to use AP automation?
No. Many customers start with AP and switch on procurement later. Because both share vendors, dimensions, approvals and history, adding procurement does not mean a second system.
Next step
Map your procure-to-pay flow in Stream
Bring a recent purchase from request to payment. We will walk it through Stream and your ERP, including the receipts and the invoice match.