Medius vs Yooz

Requirement evaluated: Virtual card program with rebate revenue; we want to shift 30%+ of spend to virtual card

For a $120M services company currently running manual check and ACH runs through Sage Intacct, Medius Payments delivers a fully integrated virtual card program as part of its payment execution layer. Once invoices clear the AP automation workflow and are approved, Medius Payments generates a unique, single-use card number tied to the specific invoice amount and supplier, automatically dispatches remittance advice, and then imports card reconciliation reporting back into the connected ERP, closing the loop without manual uploads. …

Limitations: Virtual cards are available for US-based operations only, which is consistent with this buyer's profile, but any non-US supplier payments will not generate vCard rebates. …

Requirement evaluated: Virtual card program with rebate revenue; we want to shift 30%+ of spend to virtual card

For a $120M multi-location services company running 1,800 invoices per month across two Sage Intacct entities, Yooz delivers virtual card payments through its YoozPay module. Once an invoice completes the approval workflow, the AP team selects the invoice, specifies the payment amount, and chooses a payment method. If the supplier is enrolled to receive virtual cards, payment executes immediately via a single-use card number generated by Yooz's embedded payment partner, with remittance data written back to Sage Intacct automatically. …

Limitations: The buyer's specific goal of shifting 30%+ of spend to virtual card depends on proactive supplier conversion: identifying which of their existing vendors will accept card, actively enrolling them, and modeling card-eligible spend volume. …

Requirement evaluated: Vendor self-service portal: new vendor registration, W-9/W-8 submission, banking detail entry, invoice submission, payment status inquiry

For a $120M services company currently managing vendor onboarding entirely via email and manual data entry into Sage Intacct, Medius offers a dedicated, supplier-only self-service portal that covers all five sub-requirements in the buyer's ask. On the registration and onboarding side, <cite index="4-1,4-13">a dedicated self-serve portal gives suppliers the flexibility to respond to onboarding forms from all of their customers in one place; it is vendor management software that puts the onus on the supplier to onboard and maintain their details in a secure, self-service online portal.</cite> The buyer's AP team creates and issues onboarding forms in Medius Supplier Onboarding; <cite index="24 …

Limitations: Medius's onboarding questionnaires are configurable for document upload including tax forms, but no Medius documentation explicitly confirms a native W-9/W-8 collection workflow with IRS TIN matching or automated validation; buyers with high volumes of subcontractors who need structured, validated tax-form collection s …

Requirement evaluated: Vendor self-service portal: new vendor registration, W-9/W-8 submission, banking detail entry, invoice submission, payment status inquiry

For this $120M multi-location services company, Yooz addresses vendor connectivity primarily through two mechanisms. First, the platform's P2P module references 'connecting vendors and buyers through the Yooz Community' as part of its end-to-end suite, and Yooz's electronic invoicing materials describe 'supplier self-service portals' as a platform feature that enables vendor invoice submission and supports touchless processing. Second, the YoozPay add-on (a separately priced payment module) …

Limitations: The buyer requires five distinct portal capabilities: new vendor registration, W-9/W-8 submission, banking detail entry, invoice submission, and payment status inquiry. …

Requirement evaluated: Policy compliance reporting: percentage of spend through approved channels, contract compliance rate, approval policy adherence

For a $250M technology company with 35% maverick spend and a pressing need for policy compliance reporting, Medius delivers meaningful but AP-execution-centric visibility. On the AP side, the platform logs every invoice, approval, and workflow step digitally, and its dashboard/gadgets layer (documented in the Medius Success Portal) exposes configurable metrics including the ratio of invoices routed manually vs. automatically, invoice status proportions, and touchless-processing rates. …

Limitations: For this buyer's CFO, who needs discrete, auditable percentage metrics such as spend-through-approved-channels rate and approval policy adherence score, Medius's documented reporting centers on AP operational metrics (touchless rate, invoice status, manual routing ratio) …

Requirement evaluated: Policy compliance reporting: percentage of spend through approved channels, contract compliance rate, approval policy adherence

For a $250M technology company coming from an entirely manual, email-and-Slack approval process with 35% maverick spend, Yooz provides the underlying data infrastructure for compliance reporting but does not surface the three specific metrics the buyer named as pre-built, named reports. On the audit trail side, Yooz documents every approval action across its P2P workflow, recording who performed each action, when, and the outcome, and includes a read-only auditor role and an ISO 14641-1 compliant electronic archive accessible from the platform's product page. …

Limitations: Yooz's compliance reporting is AP-centric: reviewers note that reporting flexibility and configuration require effort, and the platform's documented pre-built reports cover invoice cycle times, exception rates, and approval durations rather than purpose-built procurement policy adherence scorecards. …

Requirement evaluated: Approved POs push to NetSuite automatically; payment status syncs back

For a $250M technology company currently creating POs manually in NetSuite, Medius replaces that manual workflow through its 'Built for NetSuite' certified SuiteApp, which extends NetSuite's existing procure-to-pay functionality rather than replacing it. Approved POs created in Medius Procurement flow directly into NetSuite via a cloud-managed connector that Medius maintains; no custom coding or file uploads are required. The integration is bi-directional: vendor master data, PO lines, and goods receipt data sync from NetSuite into Medius, and once an invoice clears the Medius approval and matching workflow, the posting (preliminary, cancel, and final) writes back to NetSuite automatically. …

Limitations: The depth of PO-line data flowing into the connector depends on the NetSuite integration package version in use; buyers should verify that the connector imports PO lines before goods receipts are confirmed, which is a configuration requirement Medius documents for its goods-receipt deviation routing feature. …

Requirement evaluated: Approved POs push to NetSuite automatically; payment status syncs back

For a $250M technology company currently managing all POs manually in NetSuite, Yooz offers a certified 'Built for NetSuite' connector that sits on the Oracle SuiteCloud Developer Network. <cite index="1-14">Yooz has been an Oracle NetSuite SuiteCloud Developer Network partner since 2019 and holds 'Built for NetSuite' status.</cite> The SuiteApp marketplace listing for Yooz explicitly states that the platform will <cite index="1-1,1-4">"automatically sync purchase requests, POs, invoices, and payments into your NetSuite ERP with no templates or workarounds needed."</cite> The connector's documented field mapping includes Purchase Order as a synced object alongside chart of accounts, class, c …

Limitations: Yooz's architecture is AP/invoice-first: PO data flows from NetSuite into Yooz for matching, and approved invoices flow back to NetSuite; the upstream scenario this buyer needs (POs originated and approved inside Yooz then pushed to NetSuite as native PO records) …

Requirement evaluated: AI-powered anomaly detection for unusual invoice patterns (spike in amount, new bank account, unusual vendor behavior)

For a 3-person AP team processing 1,800 invoices per month across 2 Sage Intacct entities with no current fraud controls, Medius addresses this requirement through its dedicated Fraud and Risk Detection module, which sits as an active layer within the invoice-to-pay workflow before approvals and payments are released. The module uses machine learning trained on the organization's own invoice history to continuously monitor for anomalies at the pre-approval stage: it flags duplicate invoices, detects changes in supplier banking details and payment information, identifies invoices from unapproved or new vendors, spots unusual amount patterns and deviations from established spending behaviors, …

Limitations: The Fraud and Risk Detection module requires Medius AP Automation and is a separately priced add-on; buyers must budget for it beyond the core AP automation license. …

Requirement evaluated: AI-powered anomaly detection for unusual invoice patterns (spike in amount, new bank account, unusual vendor behavior)

For a 3-person AP team processing 1,800 invoices per month across two Sage Intacct entities, Yooz addresses this requirement through its dedicated YoozProtect module, which operates at the pre-approval stage before any payment is executed. Three distinct mechanisms cover the buyer's named scenarios. First, for invoice pattern anomalies and document tampering: <cite index="28-6">advanced AI and machine learning forensically analyze invoice metadata, detect anomalies, and flag suspicious invoices before they can be processed, reducing the risk of fraudulent payments to unauthorized accounts.</cite> Second, for amount spikes: <cite index="28-7">statistical behavior analysis identifies irregular …

Limitations: The atypical amount detection relies on historical vendor payment benchmarks, so brand-new vendor relationships with no transaction history will have a thin baseline for behavioral modeling, reducing detection sensitivity in the early invoices from a new supplier. …

Requirement evaluated: Blanket PO support for contract-based spending with release tracking against the total commitment

For a $250M technology company that currently has no procurement system and 35% maverick spend, Medius offers two overlapping mechanisms that partially address blanket PO needs. First, the Medius I2P platform includes a 'Supplier Contract' document type that supports contract-based invoice matching: incoming invoices can be matched against a stored supplier contract rather than only a standard PO, and the MediusFlow product has included 'Contract Management functionality for 4-way match and real-time follow-up on invoice transactions and invoice plan' since at least 2014. …

Limitations: The specific release-tracking mechanism this buyer needs (each release drawing down a running balance against the parent commitment ceiling, with enforcement before a release is approved) …

Requirement evaluated: Blanket PO support for contract-based spending with release tracking against the total commitment

For a $250M technology company with significant contract-based spend across IT, professional services, and facilities, blanket PO support requires a master commitment record with a defined ceiling, individual release orders drawn against it, and real-time visibility into consumed versus remaining balance. Yooz's own blog content, authored by its product marketing team, explicitly lists blanket POs as one of four PO types the platform addresses, defining them as 'ongoing purchasing from a single vendor within a set spending cap,' and states that 'Yooz brings all of this together in a single platform, from catalog-driven purchase requests and smart approval workflows to AI-powered invoice capt …

Limitations: The critical sub-functions this buyer needs, specifically: creating a parent commitment record with a not-to-exceed ceiling, issuing named release orders that draw down against it, and surfacing a real-time consumed-versus-remaining-balance dashboard, are not documented in any Yooz help center, product page, or impleme …

Requirement evaluated: Automated three-way matching: PO to receipt to invoice with configurable tolerance (2% price, 5% quantity)

For a $250M technology company coming from a fully manual, email-based process, Medius delivers automated three-way matching as a core capability of its AP Automation module. When an invoice arrives, Medius's AI-powered capture extracts line-item data (vendor name, PO number, quantities, unit prices) and automatically connects it to the corresponding purchase order and goods receipt (GDR) already synced from NetSuite. …

Limitations: Medius relies on goods receipt data being registered and synced from NetSuite into Medius for the third leg of the match; since this buyer currently has no receiving process or system discipline, the ops team will need to establish a goods receipt confirmation workflow in NetSuite before three-way matching can operate …

Requirement evaluated: Automated three-way matching: PO to receipt to invoice with configurable tolerance (2% price, 5% quantity)

For a $250M technology company moving off manual email-and-Slack approvals, Yooz operates at the invoice processing and matching stage of the AP cycle. When a supplier invoice arrives (via email, PDF, scan, or electronic format), Yooz's AI-driven OCR extracts line-level data and compares it against the corresponding PO and goods receipt documents. Yooz explicitly markets three-way matching across all three documents: as its PO matching guide states, the system 'captures the invoice, pulls out all the line-level details, matches each line to the information on the PO and the goods receipt, and flags anything that does not align.' Goods receipt documents are listed as a natively captured docum …

Limitations: The buyer's specific requirement for separate price-tolerance (2%) and quantity-tolerance (5%) configuration is documented only at a general/marketing level; no help-center configuration guide was found confirming these are distinct, independently settable percentage fields in the admin UI. …

Requirement evaluated: Segregation of duties enforcement: person who enters cannot approve, person who approves cannot process payment

For a 3-person AP team at a multi-location services company, Medius enforces all three legs of segregation of duties through distinct, system-level mechanisms rather than policy-only controls. First, the `AllowInspectAndAttest` system parameter controls whether the user who reviewed and coded an invoice can also approve it: <cite index="33-15">setting this to 'No' means that a person who has reviewed a coding row can never approve the same row.</cite> Second, Medius includes a configurable Four Eyes Principle (4EP) …

Limitations: All three controls (AllowInspectAndAttest, Four Eyes Principle, Pay Approver Role) are configurable settings that must be deliberately activated during implementation; they are not all enabled out-of-the-box, so the buyer's implementation team must confirm each is turned on and that no threshold-based bypass exists (fo …

Requirement evaluated: Approval delegation with automatic expiration (e.g., delegate to backup for 5 business days while on PTO)

For a 3-person AP team at a multi-location services company where approvers routinely take PTO, Yooz addresses coverage gaps through a dedicated delegation management function built into its BPMN2 workflow engine. The Yooz Help Center confirms that delegation is self-service: the approver configures their own substitute before going on leave, and administrators can also set delegations on behalf of employees who become unexpectedly unavailable (for example, illness with no prior setup). …

Limitations: The Help Center article confirms the delegation mechanism and the dual access model (user self-service and admin override), but the retrieved text does not explicitly confirm whether expiration is configurable in business days specifically versus calendar days; verify this precision with Yooz during a demo if the busin …

Requirement evaluated: Spend analytics: top vendors, spend by GL category, month-over-month trending

For a $120M multi-location services company running two Sage Intacct entities, Medius addresses this requirement through Medius Analytics, a dedicated reporting module with out-of-the-box dashboards that are automatically available upon deployment. The module delivers a real-time spend analysis view covering cashflow, costs, and forecasts through pre-defined reports, dashboards, and KPIs, with drill-down capability to the individual supplier level for vendor performance monitoring. …

Limitations: Documentation confirms the named dashboards and the supplier- and dimension-level filtering mechanism, but the exact out-of-the-box layout of a 'top vendors' ranked list or an explicit MoM trend chart is not shown in public help articles; buyers should request a live demo of the Cashflow and Overview dashboards to conf …

Requirement evaluated: Export to Excel and scheduled report delivery to Controller and CFO

For your AP team of 3 processing 1,800 invoices per month across two Sage Intacct entities, Yooz addresses the Excel export half of this requirement through a dedicated named feature: YoozReports, a Microsoft Excel add-in launched in October 2023. As Yooz's CEO described at launch, it allows users to 'instantly access refreshed real-time data directly from Excel, eliminating the need for extra steps to sign-in and download from the Yooz platform,' pulling live AP KPIs, invoice volumes, cycle times, and workflow data into Excel on demand. …

Limitations: The scheduled push-delivery half of this requirement (automatic email delivery of AP reports to the Controller and CFO on a recurring cadence, with no action required from the recipient) …

Requirement evaluated: Two-way matching for service POs where no goods receipt applies

For a multi-location services company with subcontractor, facilities, and professional-services POs, Medius operates at pre-processing stages 2 and 5 (PO match and cost allocation) and explicitly supports 2-way matching as a configurable match type for service-based purchases. The Medius glossary directly answers the buyer's scenario: 'Can invoice matching be tailored for service-based purchases without a goods receipt? Yes. …

Limitations: The product definition documentation confirming the 2-way matching policy is drawn from MediusFlow/D365 integration specs dated 2017-2018; configuration options for the current Sage Intacct connector should be verified with Medius directly to confirm that the 2-way match policy is available and configurable at the PO-t …

Requirement evaluated: Per-vendor duplicate sensitivity configuration for vendors that legitimately reuse invoice numbers (e.g., recurring rent or utility billing)

For a services company with a mix of recurring fixed-amount vendors (rent, utilities) alongside subcontractors and ad-hoc suppliers, Yooz's duplicate detection engine operates at invoice capture and checks for matches across four criteria: Supplier, Document Number, Document Date, and Total including tax. <cite index="1-1,1-2">Yooz offers advanced management of duplicates based on those four criteria, and a configuration allows them to be combined to establish more or less drastic duplicate detection rules according to your needs.</cite> When a suspected duplicate is flagged, <cite index="1-5">Yooz indicates the invoices concerned with a hypertext link, allowing direct consultation of the fl …

Limitations: Configuring duplicate detection criteria globally to accommodate recurring vendors like a landlord or utility company that legitimately reuse invoice numbers would simultaneously weaken fraud detection across your entire 1,800-invoice-per-month volume; Yooz's documented configuration model does not isolate rule changes …

Requirement evaluated: Multi-entity support within the integration; we operate 2 entities in Intacct and plan to add a third

As a $120M multi-location services company operating 2 Sage Intacct entities with a third planned, you need an AP layer that can route invoices to the right entity-scoped workflow, post to the correct entity's GL, and scale to a third entity without re-implementation. Medius's own platform supports multi-entity environments through a 'company' construct with entity-scoped accounting templates, entity-aware approval routing, and virtual-company-level analytics visible from a single login, as documented in the Medius Success Portal. …

Limitations: The Sage Intacct connector is partner-delivered via Acuity Solutions, not a Medius-native integration, and its per-entity GL mapping, Intacct dimension carriage, and multi-entity field fidelity are not publicly documented; the buyer must verify these specifics with Medius and Acuity before contracting to confirm the co …

Requirement evaluated: Native, pre-built, bidirectional integration with Sage Intacct (not middleware-dependent)

For a multi-entity Sage Intacct shop like yours, Yooz connects through a certified, cloud-native direct integration listed on the Sage Intacct Marketplace under the AP automation category, with no separate third-party iPaaS or middleware layer required for Sage Intacct specifically. The integration operates bidirectionally: Sage Intacct pushes vendor master records, chart of accounts, PO data, and purchasing module receivers into Yooz in real time so that coding and 3-way matching work against live ERP data; once an invoice completes the Yooz approval workflow, Yooz posts the approved bill back to Sage Intacct along with the original invoice image, which is stored directly inside the Sage In …

Limitations: Documentation does not detail whether every Sage Intacct custom dimension and user-defined segment is carried across both of your entities at the line level, so the dimension depth of the integration across your specific Sage Intacct configuration should be confirmed during a structured demo or proof-of-concept. …

Requirement evaluated: Learning capability: accuracy should improve over time on our specific vendor invoice formats

For a 1,800-invoice-per-month services company starting from zero automation, Medius addresses this requirement through two complementary mechanisms in its invoice capture stage (pre-processing stage 1: legitimacy and initial data extraction). First, Medius Capture uses a proprietary multi-stage AI pipeline combining Siamese CNNs for document classification and Markov models for line-item extraction, trained on a global corpus of 2.4 billion+ invoice field data points including 393 million real-world human corrections across its customer base. Second, and directly relevant to per-vendor format improvement, SmartFlow (a proprietary CNN) …

Limitations: The precise boundary between global cross-customer model retraining and this buyer's tenant-specific model is not fully disclosed in public documentation; accuracy improvement on genuinely novel or low-volume vendor formats depends on correction volume from this buyer's own invoice corpus, and very infrequent suppliers …

Requirement evaluated: Learning capability: accuracy should improve over time on our specific vendor invoice formats

For your 1,800-invoice-per-month operation, Yooz's invoice field extraction uses what it calls a 'full-text' semantic analysis engine: the system reads the entire invoice using NLP and keyword detection rather than mapping fields to their physical position on a page. This means no template creation or zoning work is required before your first invoice is processed. …

Limitations: The buyer's requirement is explicitly about extraction accuracy improving over time on their specific vendor invoice formats. Yooz's extraction improvement is handled globally by Yooz specialists applying generic semantic model updates, not by a per-client feedback loop that builds vendor-specific recognition memory fr …

Requirement evaluated: Services catalog: pre-defined service offerings from preferred vendors (e.g., standard consulting day rates)

For a $250M technology company dealing with 35% maverick spend and no formal catalog discipline, Medius Procurement delivers an internal catalog mechanism that directly addresses this requirement. Administrators load approved goods and services items into an internal catalog with negotiated pricing tied to preferred vendors; end users then search and browse that catalog using a consumer-style shopping experience to create requisitions rather than free-texting requests. …

Limitations: The Medius Procurement module is a separately priced add-on; the core AP automation product in the fact sheet does not include catalog buying. Specific documentation on time-and-materials billing units (e.g., per-day, per-hour unit-of-measure configuration for service line types) …

Requirement evaluated: Punchout catalog integration with Amazon Business and CDW

For this $250M technology company needing live punchout sessions into Amazon Business and CDW, Yooz does not document a punchout catalog mechanism anywhere in its product materials. Yooz does include a purchasing module that supports catalog-driven purchase requests, from requisition through PO generation and into its core AP matching and payment workflow. However, three targeted searches of Yooz's website, blog, and documentation found no mention of cXML or OCI punchout protocols, no certified connector or pre-built integration with Amazon Business or CDW, and no supplier network through which those suppliers are already enrolled. …

Limitations: Without punchout support, this buyer's team would need to manually re-enter item details from Amazon Business and CDW into Yooz purchase requests, losing real-time pricing, live inventory availability, tax-exempt status enforcement, and contracted account pricing that punchout sessions preserve. …

Requirement evaluated: Centralized supplier database with self-service onboarding portal: vendors enter their own info, upload W-9, insurance, banking

For a $250M technology company currently managing 800+ vendors through email and manual NetSuite entry, Medius delivers this requirement through two integrated, named modules: Medius Supplier Onboarding and the Medius Supplier Portal. The flow is invitation-driven: your team creates and issues onboarding forms inside Medius Supplier Onboarding, and those forms are made available in the Medius Supplier Portal for each vendor to access and complete independently. Suppliers register, record, and update their own details in a single cloud-based location — including banking and contact information — without requiring your AP or ops team to key data on their behalf. …

Limitations: Medius's public documentation confirms banking/payment detail self-service and general regulatory document collection, but does not explicitly name W-9 collection or insurance certificate tracking with expiration alerts as discrete, labeled features — buyers should verify these specific US tax and insurance document wo …

Requirement evaluated: Contract repository: store agreements, track renewal dates, alert stakeholders 90/60/30 days before expiration

For a $250M technology company that needs to store vendor agreements, track renewal dates, and automatically alert department heads, legal, and procurement leads at 90, 60, and 30 days before expiration, Yooz has no native mechanism to deliver this. Yooz is an AP automation and procure-to-pay platform whose documented capabilities cover invoice capture, GL coding, PO matching, approval routing, fraud detection, and payment execution. Its help center confirms that users can attach files, including contracts, to supplier records and retrieve them via full-text search, but this is a general document filing function with no structured renewal-date metadata fields and no rule-based alert engine. …

Limitations: Delivering this requirement for the buyer would require procuring and integrating a separate, dedicated CLM platform (such as Ironclad, DocuSign CLM, or Agiloft) from a different vendor entirely. …

Requirement evaluated: Spend dashboards: real-time spend by vendor, category, department, location, and period

For a $250M technology company currently flying blind on 35% of its spend, Medius delivers this requirement through its dedicated Medius Analytics module, a separately licensed product that sits alongside AP Automation and Procurement. <cite index="32-1">The module provides "a full, real-time view into how money is spent across your organization delivered through pre-defined reports, dashboards and KPIs,"</cite> with named sub-sections in the product documentation covering AP Insights, Invoice Process Insights, User Insights, and a Procurement Dashboard. …

Limitations: Some dashboard gadgets in Medius Spend Management rely on a scheduled ETL job rather than a live data feed, meaning <cite index="13-4">"displayed data is based on ETL reporting data"</cite> for those panels, which introduces a batch-refresh lag rather than truly instantaneous data. …

Requirement evaluated: Tail spend analysis: identify high-transaction-count, low-dollar vendors for consolidation

For a technology company trying to rationalize 800+ vendors down to fewer than 300, Yooz offers basic vendor-level spend visibility through its dashboard and the YoozReports add-on. The platform captures invoice data across the purchase-to-pay cycle, and third-party aggregators describe its P2P capabilities as including 'budget management, spend analytics, and vendor statement reconciliation.' YoozReports surfaces KPIs through an Excel-based add-in that pulls real-time data on demand, allowing users to build custom reports and visualize metrics. However, Yooz's native analytics are focused on AP operations metrics: invoice volumes, processing times, approval durations, and payment status. …

Limitations: Yooz does not provide a native tail spend identification workflow: there is no out-of-the-box view that ranks vendors by transaction count versus total spend, flags high-frequency/low-value relationships, or generates consolidation recommendations. …

Requirement evaluated: Complete audit trail meeting SOX-adjacent control requirements for our IPO preparation

For a company preparing for an IPO, Medius provides a centralized, AP-side audit trail that captures every action taken across the invoice-to-pay lifecycle. <cite index="16-22,16-23">AP automation maintains compliance by creating well-organized workflows and maintaining clear audit trails, including generating detailed audit trails for every action taken on an invoice and enforcing approval hierarchies and role-based access controls.</cite> <cite index="0acd0c8e-5ffc-4d74-be76-7c3e3af721a7">Every invoice is automatically archived, ensuring accuracy, traceability, and audit confidence at any time.</cite> On the controls side, <cite index="7-1,7-3">automated vendor onboarding workflows and seg …

Limitations: Medius's audit trail is strongest on the AP side (invoice receipt, matching, approval, payment); upstream procurement controls (purchase requisition creation and pre-PO approval) …

Requirement evaluated: Our specific rules: under $1,000 auto-approved against budget, $1,000-$10K department head, $10K-$50K VP, $50K-$100K VP + Finance, over $100K VP + Finance + CFO

For a $250M technology company replacing email/Slack approvals, Yooz's BPMN2 workflow engine handles the buyer's five-tier approval policy directly. Administrators configure threshold-based routing rules that read the purchase amount and automatically route to the correct role: below $1,000 requests move through a 'no-touch' auto-approval path tied to budget availability (Yooz tracks budget in real time against 'defined budget period, categories, and rules'); $1K-$10K routes to a single department head; $10K-$50K to a VP; and the $50K-$100K and $100K+ tiers use Yooz's documented parallel approval gates, where VP and Finance (or VP, Finance, and CFO) …

Limitations: A verified user review flags that when multiple approvers at the same tier must each act, the practical experience can feel sequential rather than truly simultaneous, suggesting that parallel-gate configuration for the $50K-$100K and $100K+ tiers may require careful setup and testing to execute as designed. …