| Craftable | Multi-vendor orders enter a purchasing workflow with a recorded purchase request before placement.[1] [1] | Orders route by GL code, department, or budget overrun to named users, roles, or directors; orders are sent only after approval.[2] [2] | A configured GL budget overrun sends an order for approval before placement; budgets must be configured.[2] | Budgets reflect placed orders as well as invoices. Orders must be linked to invoices to avoid counting both.[3] [3] | Invoices are matched line by line to POs and delivery receipts; discrepancies are flagged before payment.[1] [1] | Craftable names QuickBooks, Sage, Acumatica, and Microsoft Dynamics GP with automatic GL mapping and invoice sync.[4] | Not documented |
|---|
| Supy | Staff create requisitions on web or mobile before PO generation.[5] | Separate requisition and PO workflows can route by role, outlet, or amount, with up to five sequential approval levels and an audit trail.[5] [5] [5] | Daily, weekly, or monthly ordering caps can be applied by user, supplier, item category, or outlet.[5] [5] | Not documented | Incoming invoices match to POs; pricing mismatches and other exceptions are flagged for review.[6] [6] | The Xero integration imports purchase invoices and creates journal entries based on Supy metrics. Exact sync cadence and plan restrictions are not stated.[7] [7] | Not documented |
|---|
| Controliza | In CAPEX, location managers request equipment through the app before approval and reception.[8] [9] | CAPEX requests route by amount, category, and cost center, with approval decisions logged by date, time, and responsible person.[8] [8] [9] | CAPEX investment budgets can be assigned by location, category, or period; approaching-limit alerts are documented. A mandatory budget block is not established.[8] [8] [9] | CAPEX shows approved investment, executed investment, and remaining budget by location, category, and period.[8] [9] | Not documented | ERP connectors include SAP Business One and NetSuite. The documented flow includes forecasts exported by cost center; this is not evidence of invoice posting.[10] [10] [10] | Not documented |
|---|
| BlueCart | Kitchen managers and purchasing staff raise orders for an approval workflow before placement.[11] [11] | POs over a configured amount or from new suppliers route through multiple approval steps to purchasing managers, with mobile approval.[11] | Site managers place orders within location spending limits; headquarters can flag off-contract spending for review. Formal budget reservation is not established.[11] | Not documented | Supplier invoice line items are compared with POs; price, quantity, and product discrepancies are flagged before payment approval.[11] | Not documented | Restaurant groups combine central ordering and deliveries split to sites with local ordering inside spending limits and one group reporting dashboard.[12] |
|---|
| Apicbase | The cart becomes an approval request rather than a supplier order when the daily supplier limit is exceeded.[13] | Over-limit outlet orders wait for a role-authorized approver. A single approver decides; approval chains and delegation are not supported in this documented workflow.[13] [13] [13] | Daily supplier limits hold outlet orders for approval. Only sent orders count; pending requests are excluded, so this is not a hard daily spend cap.[13] [13] | Not documented | Supplier invoices are checked against purchase orders and goods receipt, with price, quantity, and delivery discrepancies flagged.[14] | Not documented | Not documented |
|---|
| BirchStreet eProcurement | Items follow a standardized request, approval, and purchase workflow.[15] | Multi-layer approvals use departments, roles, budgets, events, and categories.[15] | The purchasing workflow enforces budget checks to prevent overspending.[15] | Not documented | Smart AP validates POs, receipts, and invoices using a three-way match, with approval and error-resolution visibility.[16] [16] [16] | Not documented | Not documented |
|---|
| MarketMan | Not documented | Not documented | Purchasing budgets, price limits, and permissions are configured to prevent overspending.[17] | Not documented | Invoice line items, quantities, and prices are matched to the PO; discrepancies require review before approval.[18] | QuickBooks Online and Xero receive approved invoices and payment records. MarketMan states it charges no integration fee; counterpart fees may apply.[18] [19] | Not documented |
|---|
| Fourth Purchase-to-Pay | Not documented | Not documented | Not documented | Fourth shows invoice commitments and creates goods-delivered-not-invoiced accruals, reversing them when matched.[20] | Invoices, electronic POs, and goods-received notes are matched. Receivers can record a reason for adjustments.[20] [20] | Not documented | Site menus restrict procurement choices to approved suppliers; authorization shows current spend against budget.[21] |
|---|
| ProcureDesk | Purchase requests enter a requisition workflow connected to the budget before commitment.[22] | Requests route by vendor, amount, category, or custom field, with email/mobile decisions and automatic escalation.[23] | Available budget is checked at requisition stage using committed spend plus the new request; hard or soft controls and policy exceptions are documented.[22] [22] [22] [24] | Pre-encumbrance tracking includes committed spend plus new requests when calculating available budget before approval.[22] [22] [24] | Pricing lists receiving, invoices, and basic three-way matching for Startup; discrepancies are sent to AP for exception review.[25] [25] [25] | Named connectors include QuickBooks, Xero, Bill.com, NetSuite, Intacct, and Business Central, with approved-PO sync within seconds. Pricing-page plan groupings conflict with broader homepage inclusion claims; exact plan eligibility is unknown.[25] [25] [26] [27] | Not documented |
|---|
| Order.co | Purchase requisitions enter a managed purchasing workflow before orders are placed.[28] | Requests route before purchase by location, cost center, user role, or amount; transaction and approval records support audits.[28] [29] | Pre-purchase approvals and enforced budget limits use automated spend tracking and alerts.[29] [29] | Real-time reporting shows committed spend from POs and approvals alongside payments before money leaves the business.[30] | Platform purchases populate the Order.co invoice; approved line items are validated and exceptions flagged for review.[30] [30] | QuickBooks Online, NetSuite, and Sage Intacct receive invoice data with line-level reconciliation; other accounting systems can use exports.[31] [31] [31] | Not documented |
|---|
