Vendors keep their own bank and tax details current and see their orders and payment status themselves. Your team approves, matches and pays on one ledger.
Choose catalog lines or enter free text. Check budget now; warn or block by policy.
02
Approve
Route requests, POs, and bills by amount, department, vendor, category, and entity. Delegate out of office.
03
Order
Turn approval into a PO in one click—or automatically, when enabled. Send it to the vendor's portal.
04
Receive
Record goods receipts. Service orders need no receipt.
05
Bill
Email or upload bills. AI reads each one into a draft.
06
Match
Run 2-way or 3-way matching with tolerances.
07
Pay
Approve the run; a different person releases it. Pay by ACH or printed check, or export NACHA.
Vendor portal
Vendors maintain the record.
Your team approves the details that move money.
Contacts and tax formsVendors keep contacts current and upload W-9 or W-8 forms, which are read automatically. TINs are verified against the IRS; a mismatch holds payment until the vendor submits a corrected W-9.
Setup under approvalNew vendors are screened against US OFAC sanctions lists. Your team approves new vendors and bank details before first use; a bank change holds payment until a different person releases it.
Purchase ordersNew POs land in the vendor's portal with an email alert. Vendors can opt in to get the PDF by email too.
Payment statusVendors see received, approved, released, and paid.
Payments, ready to pay
Controls and audit
Built for a second set of eyes.
Approvals stay with people. Exceptions stay visible. Every step posts to the same ledger with a full audit trail.
PO control
Changes return for review
Vendors acknowledge POs in their portal. Change orders go back through approval.
Bill control
AI drafts. People approve.
Coding learns from your own history. A person approves every AI suggestion. Duplicate bills are caught.
Match control
Review only the breaks
Only mismatches land in the exceptions queue. Matching supports 2-way and 3-way checks with tolerances.
Payment control
Approval before release
Payment runs require approval and a second approver above a threshold. The run approver cannot release it, and a segregation-of-duties report surfaces conflicting access. Printed checks support Positive Pay.
