Delivering 11/20 to north gate laydown. Will call 24h ahead.
Earliest is the 20th.
To your buyer
PO PO-2417-119 is on time.ExpediteSwitch supplier
Step 5
It matches the delivery ticket
PO, signed ticket, invoice. Shorts held for the PM.
Matching 3 documents…Demonstration data
POQty 1000
✕
Packing slipQty 960
✕
InvoiceQty 1000
HeldBilled 1000. Received 960. On your desk with the slip.
The full process
MEP subcontractors: every step
What the agent does, where you decide, and the rules it checks.
I run every blue box.
Material need or buyout
Build bid package from estimate
Invite approved vendors & subs
Level bids vs budget
PM awards
Commit PO to cost code
Confirm delivery date
Log delivery ticket photo
Read the invoice
Matches PO & ticket?
No → hold for PM
Within budget?
No → flag change order
Code job & cost type
Waiver & COI on file?
No → request from vendor
Calculate retainage
PM approves invoice
Build payment run
You release payment
Paid, waiver logged
Agent does it You decide Rule check
Built for you
Construction procurement
12345
1Buyout vs. estimateBids leveled against budget
2Job & cost codesEvery line on the right job
3Delivery ticketsSigned on site, lost in trucks
4COIs & lien waiversNo waiver, no check
5RetainageHeld, tracked, released
Your controls
Your rules. Exactly.
Written once in plain English. Followed every time.
Submittal not cleared?Don't buy it
Over cost code budget?Flag a change order
No lien waiver?Hold the payment
Never, on any run
Buy ahead of the submittal
Accept a substitute model
Create or approve change orders
Code to a job not named
Release retainage on its own
When a rule says no
It stops and asks you.
Every held item lands in one queue with the documents, the values read and the rule that fired.
Approvals · 3 waitingDemonstration data
Hold for PMMatches PO & ticket?2 min
Flag change orderWithin budget?14 min
Request from vendorWaiver & COI on file?1 h
RUN-2291
Hold for PM
RuleMatches PO & ticket? No
Source PDFPO as savedRule result
I stopped here. Everything I read is attached. Your call.
ApproveSend back
The difference
Your team, before and after
Your team today and with the agent
Today
With your agent
Job coding
Fixed at month-end
Right on the PO
Delivery tickets
Lost in trucks
Photo logged, matched
Lien waivers
Chased by phone
Checked before the run
Retainage
Tracked in spreadsheets
Calculated every invoice
Your existing systems
No new systems!
The agent runs where you work.
ERP & project
Sage 300 CRE
Sage Intacct
Vista/Spectrum
CMiC
Procore
Foundation
Jonas
Acumatica CE
Primavera
Trimble
BuildingConnected
Siteline
Suppliers & pay
Home Depot Pro
Ferguson
Grainger
Fastenal
BILL
AvidXchange
Chase
Bank of America
Inbox & documents
Excel
Outlook
Gmail
Teams
SharePoint
Acrobat / PDF
DocuSign
Scans & photos
Screens differ by version and setup; we confirm the exact steps on your system before a pilot. Logos and product names identify systems only and belong to their owners; they do not imply a partnership or endorsement.
Hours back for your team
Your numbers
How many hours can you get back?
Your volume, your times, your labor cost. Estimates, not results.
90staff hours per month returned to buying work
$4,950labor capacity per month
$59,400labor capacity per year
Material requests × (minutes today − minutes with the agent) ÷ 60 × hourly cost
These are example assumptions, not results. Example assumptions for a mid-size MEP subcontractor: minutes cover submittal checks, quoting, comparison, PO entry and notifying the PM. Replace with your own numbers.
Demonstration
Watch recorded runs
These are real Acumatica runs from either side of purchasing, not the buyout above. The submittal run takes a curtain wall submittal through architect review to approved as noted, then hands off to procurement, which creates PO draft PO-40022. The PO-invoice run is AP after receipt: an invoice matched to a project PO and cost code, a receipt released and a bill entered. Neither shows quote comparison or budget checks.
Yes, that's the rule it starts from. It checks each item's submittal status and revision before buying, reads any approved-as-noted conditions, and leaves anything not cleared unissued with the reason stated.
How does it handle change orders?
It doesn't create or approve them. If a line depends on a change order that isn't approved, or would push a cost code past its remaining budget, the agent holds it and sends it to the PM with the numbers.
Can it work with Sage or Viewpoint?
It works through the screens your team already uses, in a signed-in user's session, so it isn't limited to one product. We have no partnership with those vendors, and screens differ by version and configuration, so we confirm the exact steps on your system before a pilot.
What if the PM's list has no cost codes?
The agent proposes codes from the job budget where the match is clear and sends the rest back to the PM. It won't guess a code to get a PO through.