Stampli vs Yooz

Requirement evaluated: 1099 preparation: automated classification, threshold tracking, and electronic filing

For a multi-location services company on Sage Intacct, Stampli's 1099 support operates as a data synchronization layer rather than a self-contained compliance engine. On the classification side, Stampli imports each vendor's 1099 status from the Intacct vendor master and surfaces that flag at the invoice line level during processing, allowing AP to confirm or override the 1099 designation per line before export. As Stampli's Sage Intacct integration page states, 'the system imports each vendor's 1099 status, then exports the same flags back to Intacct,' keeping year-end 1099 data in Intacct accurate. …

Limitations: Two of the three components the buyer requires are not delivered by Stampli itself: cumulative payment threshold tracking (the running $600 IRS limit per vendor) lives in Intacct's vendor master, not in Stampli, so any payments recorded outside Intacct's direct view risk creating gaps in the 1099 total; and electronic …

No public documentation covering this requirement was found on the documentation sources this vendor publishes. That is a limit of the public evidence, not a finding about the product.

Requirement evaluated: 1099 preparation: automated classification, threshold tracking, and electronic filing

For a $120M multi-location services company with subcontractors, utilities vendors, and professional services suppliers spread across two Sage Intacct entities, 1099 compliance requires automated vendor classification (NEC vs. MISC), running payment threshold tracking, and electronic filing with the IRS. Yooz's documented scope covers invoice capture, AI-based GL coding, PO matching, approval routing, and payment initiation through its Sage Intacct integration. …

Limitations: No Yooz-authored source, help article, or marketplace listing documents 1099 vendor classification, cumulative threshold tracking, or IRS e-filing as a Yooz feature. …

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

For a 3-person AP team at a $120M multi-location company needing to get data into the Controller's and CFO's hands, Stampli covers one of the two components of this requirement cleanly and leaves the other unresolved. On the export side, Stampli's Reports module offers an on-demand download button that produces either a CSV or XLSX file from any invoice report, including fully customized views with user-selected columns, date ranges, and advanced filters; the accrual report help article (Source 1) explicitly instructs users to 'Export the Report as an XLSX and open it in Excel,' and the Reports help article (Source 3, updated February 2026) …

Limitations: The Controller and CFO will not receive AP reports automatically in their inbox on a recurring schedule; someone on the AP team must manually run the report, export the XLSX, and email it, which introduces a manual step the buyer is specifically trying to eliminate. …

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: International wire payments to 8 overseas vendors with multi-currency support

For a $120M multi-location services company running Sage Intacct with 8 overseas vendors, Stampli Direct Pay's International Payments module covers the full cross-border payment workflow without leaving the AP platform. When an international invoice reaches the payment stage, the AP team initiates the wire or international ACH directly in Stampli: Stampli Direct Pay allows you to seamlessly pay vendors across 100+ countries, in USD or their local currency, without ever leaving Stampli. …

Limitations: The complete list of supported countries requires a direct conversation with Stampli (the product page references both 100+ and 150+ countries across different pages and directs buyers to confirm the full list with their AP experts). …

Requirement evaluated: International wire payments to 8 overseas vendors with multi-currency support

For your scenario of paying 8 overseas vendors in foreign currencies, Yooz's native payment module (YoozPay) does not provide this capability. Every documented enumeration of YoozPay's payment methods lists virtual card, ACH, eCheck, and paper check as the complete set of supported options. No international wire execution mechanism, foreign currency settlement, SWIFT/IBAN bank account collection, or FX conversion engine is described in any Yooz product page, launch documentation, or partner announcement. …

Limitations: YoozPay's payment execution is scoped to domestic US payment rails: ACH, virtual card, eCheck, and paper check. Your 8 overseas vendors requiring foreign-currency wire payments would need to be paid entirely outside Yooz, through your bank or a separate international payment platform, with no automated payment initiati …

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 processing recurring vendor invoices from landlords, utilities, and subscription providers who legitimately reuse invoice numbers, Stampli's Billy the Bot runs a three-stage duplicate detection process. At the registration stage, Billy separates flags into two categories: 'actual duplicates' (invoice number + vendor name + invoice year/date all match, which triggers a hard warning requiring cancellation or editing to proceed) and 'potential duplicates' (any other combination of three matching fields). …

Limitations: The per-vendor disable setting covers only the 'potential duplicate' warning tier; the 'actual duplicate' hard flag (triggered by an exact match of invoice number, vendor name, and invoice year) …

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. 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. …

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: Role-based access control with entity and department-level restrictions

For a $250M technology company running 4 US offices plus a Canadian development center, Stampli's role model directly addresses the need to restrict who can see and act on spend across entities and departments. Stampli separates access into three independently configured dimensions: visibility (which invoices, POs, vendors, or reports a user can see), actions (what that user can do: code, route, approve, pay, configure), and scope (whether access is limited to work assigned to the user, work matching configured criteria, or all applicable records). …

Limitations: The vendor help center documents Reviewer scope filtering by department and approval routing by subsidiary, but does not explicitly describe a hard entity-level visibility wall (i.e., a user in the US entity being physically unable to see Canadian entity invoices in the UI) …

Requirement evaluated: Role-based access control with entity and department-level restrictions

For a $250M technology company running 4 US offices and a Canadian development center with no current procurement controls, Yooz addresses this requirement through a documented Role-Based Access Control (RBAC) system: Yooz's own security page states that 'access rights are managed through an RBAC system, ensuring that each user can only access the data they strictly need.' This operates alongside multi-company and multi-department features (listed as named platform capabilities on Software Advice and Capterra), meaning users can be scoped to specific legal entities and departments rather than seeing all spend organization-wide. …

Limitations: Customer reviews note that configuring entity-level role restrictions becomes operationally complex at scale (one Capterra reviewer flagged difficulty when 'lots of entities' are in scope), and Yooz's publicly available help documentation does not detail the precise mechanism by which entity-level data isolation is enf …

Requirement evaluated: Role-based access control with entity-level restrictions

For a $120M services company running 2 Sage Intacct entities across 6 locations, Stampli delivers role-based access control with entity-level restrictions through two complementary mechanisms. First, at the ERP integration layer: Stampli mirrors Sage Intacct's multi-entity hierarchy exactly, and entity-level user restrictions configured in Intacct are automatically imported and enforced in Stampli, so finance admins configure access once in Intacct and Stampli applies the same security presets without a second setup step (Stampli Sage Intacct integration page, stampli.com/erp/sage-intacct/). …

Limitations: Entity-level restrictions in Stampli are sourced from Intacct's own security configuration; if entity permissions are not fully configured in Intacct, they will not automatically appear in Stampli. …

Requirement evaluated: Role-based access control with entity-level restrictions

For your two-entity Sage Intacct environment, Yooz enforces access control at the invoice-visibility layer inside the platform itself, meaning an AP user scoped to Entity 1 cannot see invoices belonging to Entity 2 in the Yooz queue, independent of what Sage Intacct permits downstream. Yooz's help center documentation describes the mechanism explicitly: each user is assigned one or more functional roles (accountant, validator, treasurer, and similar) and one or more 'companies' (Yooz's term for legal entities), so that access to invoices is restricted to the entities attached to that user's profile. …

Limitations: Role and entity configuration is managed by a platform administrator rather than through a self-service wizard, and one verified user review notes that configuration complexity grows as entity count increases; for your two-entity setup this overhead is low, but you should confirm the specific named role tiers (approver …

Requirement evaluated: Budget data pulled from NetSuite for real-time budget enforcement

For a $250M company currently running all budget oversight through NetSuite, Stampli offers a fully functional internal Budget Management module that enforces spend before commitment: when an employee submits a purchase request or a PO line is created, Stampli displays the applicable allocated, committed, spent, and remaining amounts in real time and can warn or hard-block a transaction when the budget would be exceeded. Stampli's Budget Management provides real-time visibility and control over organizational spending, allowing finance leaders to make informed spending decisions before a purchase occurs, with budget oversight integrated directly into the approval workflow. …

Limitations: The buyer's core requirement is budget data pulled from NetSuite for enforcement, but Stampli's documented limitation is that its budgets do not synchronize with an ERP budget module (Stampli Budget Management help article, updated 2026-07-13). …

Requirement evaluated: Budget data pulled from NetSuite for real-time budget enforcement

For your setup, where requests and approvals run through email and Slack and ops keys POs into NetSuite, Yooz would sit before PO creation. Employees raise purchase requests in Yooz, and its Budget Management function applies budget rules at each stage from request through invoice approval. Those rules can monitor, alert, or block specific expenses. Budgets are tracked by the budget period, categories, and rules you define in Yooz. A budget control tab shows committed, invoiced, and available amounts. …

Limitations: Nothing I found shows NetSuite budget amounts flowing into Yooz. If your CFO wants NetSuite to stay the single source of budget truth, you would likely maintain or load budgets separately in Yooz, which risks drift. …

Requirement evaluated: Hard-stop at budget limit with CFO override; soft warning at 80% utilization

For a $250M tech company looking to replace email-and-Slack approvals with enforced budget guardrails, Stampli's dedicated Budget Management module operates at the purchase request stage: before a PO is issued, approvers see real-time budget impact inline within the approval workflow. The module supports two distinct enforcement modes. In block mode, when a purchase request would exceed a budget limit, the system can automatically block approval; the vendor describes this as giving 'complete control over how strictly you want to enforce budget compliance.' In alert mode, budget owners receive automatic notifications when spending approaches critical thresholds, allowing for proactive managem …

Limitations: The two-tier control the buyer needs (hard-stop at 100% with a CFO-only bypass path, plus a simultaneous 80% soft warning) is not documented as a combined, layered control: Stampli's Budget Management presents block mode and alert mode as mutually exclusive configuration choices per budget, not as co-existing tiers on …

Requirement evaluated: Hard-stop at budget limit with CFO override; soft warning at 80% utilization

For this $250M technology company trying to eliminate 35% maverick spend, Yooz operates a native budget management module that spans the full P2P process, from purchase request creation through invoice approval. Administrators can manage budgets at every stage of the purchasing process, from creating a purchase request through invoice approval, by setting rules to monitor, alert, or block specific expenses. Rules can be set for monitoring, alerting, or blocking specific expenses at each stage of the P2P process. …

Limitations: Yooz documents the existence of monitor, alert, and block rules but does not publicly confirm that alert thresholds can be set at a percentage of utilization (e.g., exactly 80%) rather than at an absolute dollar amount after breach. …

Requirement evaluated: Price comparison when same item is available from multiple sources

For your move from email and Slack requests to controlled buying, Stampli gives requesters price-bearing sources inside the purchase request, but no documented tool that compares one item's price across vendors. Admins keep preferred item lists per request type with an editable name, price and link (Stampli Preferred Items page), and AI item suggestions can be limited to uploaded catalogs or preferred lists, with rates drawn from catalog costs (Stampli AI-Powered Item Suggestions page). Requesters can also choose Shop vendor sites inside a request and punch out to Amazon Business, where they see live pricing and the organization's negotiated pricing. …

Limitations: I found no side-by-side or ranked comparison of the same item across catalogs, punchout vendors or preferred-item entries. Your requesters would have to open each punchout or catalog source separately and compare prices themselves, which weakens the push to consolidate 800+ vendors toward fewer than 300. …

No public documentation covering this requirement was found on the documentation sources this vendor publishes. That is a limit of the public evidence, not a finding about the product.

Requirement evaluated: Price comparison when same item is available from multiple sources

For a company with 35% no-PO spend and 800+ vendors, the question is whether a requester sees competing prices for the same item before buying. Yooz documents a purchase-request-to-PO flow (create purchase requests, approval workflows, automatic PO generation, delivery tracking, budget monitoring), but I found no documentation of a catalog or side-by-side comparison of one item across suppliers. Yooz's own P2P material says it covers requisition, invoice processing and payment approval, and its requisition blog only advises requesters to review catalogs and preferred vendors. It does not describe a product feature for this.

Limitations: No Yooz help-center or product source describes comparing prices for the same item across vendors, so this must be confirmed in a demo. Yooz appears to center on AP automation, with purchase requests and POs as an extension, so a guided-buying catalog that steers the 800+ vendor base toward preferred suppliers should n …

Requirement evaluated: PO change order workflow: amendments require re-approval if they exceed original amount by more than 10% or $5,000

This $250M technology company needs system-enforced re-approval when a PO amendment exceeds the original authorized amount by more than 10% or $5,000, whichever is lower. Stampli's Procurement module documents configurable, threshold-based approval routing for new purchase requests: admins configure the overall routing sequence by defining which fields (department, amount, location) drive the multi-step process, and can define spending thresholds and condition-based rules that automatically determine when additional reviewers must be involved. …

Limitations: For this buyer, the critical gap is the absence of a documented delta-comparison engine on PO amendments: Stampli's approval rules fire on the total value of a new request, not on the incremental change relative to an already-approved PO baseline, so the dual-condition trigger (>10% OR >$5,000 above original) …

No public documentation covering this requirement was found on the documentation sources this vendor publishes. That is a limit of the public evidence, not a finding about the product.

Requirement evaluated: PO change order workflow: amendments require re-approval if they exceed original amount by more than 10% or $5,000

This $250M technology company needs a system that detects when a PO amendment exceeds the original approved amount by more than 10% or $5,000 and automatically re-routes it for approval before the change takes effect. Yooz does offer a purchasing module that covers requisition to PO creation, and its product page documents a BPMN2 workflow engine supporting sequential, parallel, and no-touch approvals with auto-escalation and auto-delegation. …

Limitations: No evidence exists that Yooz's workflow engine can be configured to evaluate the delta between an amended PO and its original approved value and trigger a new approval chain based on dual conditions (percentage and absolute dollar). …

Requirement evaluated: Automatic match-and-pass for invoices within tolerance, reducing AP workload to exceptions-only review

For a $250M tech company currently processing all invoices through manual email/Slack approval loops, Stampli's PO Matching module directly addresses the exceptions-only goal. When an invoice arrives, Billy the Bot (Stampli's AI) captures and extracts invoice data, then performs the three-way match automatically: comparing the invoice against the PO and the receiving record synced from NetSuite via bi-directional ERP integration. Stampli's PO Matching capability supports both 2-way and 3-way matching, easily handling complex scenarios such as blanket POs, multiple invoices, taxes, and freight charges. …

Limitations: Stampli is an AP automation layer that depends on PO and receiving records already existing in NetSuite; the buyer's current workflow of manually creating POs in NetSuite must be maintained (or replaced by Stampli's procurement module) for the match to fire. …

Requirement evaluated: Automatic match-and-pass for invoices within tolerance, reducing AP workload to exceptions-only review

For a $250M technology company moving from email/Slack approvals and manual NetSuite PO creation, Yooz replaces that entire bottleneck with an AI-driven capture-to-match engine. When a vendor invoice arrives (email, PDF, scan, or e-invoice format), Yooz's Smart Capture layer extracts line-level data including quantities, unit prices, product codes, and tax fields. …

Limitations: The 3-way match requires goods receipts to be logged in NetSuite before Yooz can clear an invoice; for the buyer's $30M direct materials spend, any lag in receiving confirmations from warehouse or operations teams will hold matched invoices in a pending state rather than triggering exceptions-only routing. …

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

For a $250M technology company managing 800+ vendors and concerned about contract visibility, Stampli's Advanced Vendor Management (AVM) add-on module provides a centralized document repository where contracts, W-9s, licenses, and insurance documents can be stored per vendor profile, with expiration dates set on each document. The system sends automated expiration notifications to both AP teams and vendors when documents are approaching their expiration dates, and can block invoice or payment processing for non-compliant vendors. …

Limitations: No documented evidence confirms that Stampli supports configurable multi-interval renewal alerts (e.g., 90, 60, and 30 days before expiration) directed at named internal stakeholders; the platform's expiration tracking appears oriented toward triggering vendor re-upload reminders and AP compliance blocks rather than de …

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: Automatic escalation: if approver has not acted within 48 hours, escalate to their manager with notification

For a 3-person AP team currently managing approvals through email chains, Stampli replaces that process with a configurable workflow engine that monitors approver response time and automatically acts when SLAs lapse. Stampli's documented escalation model works in two stages: automated reminders fire first, then, if the approver has still not acted after the configured wait period, escalation rules reroute the approval to an alternate or the approver's manager after the SLA lapses, with the escalation logged in the audit trail. …

Limitations: The most detailed escalation configuration documentation available from Stampli's help center describes this mechanism in the context of procurement request workflows; the invoice-specific approval help article (help.stampli.com/en/articles/2992566-approving-invoices) …

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 …

No public documentation covering this requirement was found on the documentation sources this vendor publishes. That is a limit of the public evidence, not a finding about the product.

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

For your 2 Intacct entities (with a third coming), Stampli connects once to Intacct through a Web Services user and syncs both the top-level organization and entity data, including vendors, GL accounts, locations and POs, into a single Stampli account. Stampli uses a Web Service User to automatically sync top level organization and entity data into Stampli. Stampli mirrors Intacct's multi-entity hierarchy in one unified platform and imports and enforces the same entity-level user restrictions configured in Intacct. …

Limitations: Stampli pays from one entity at a time: invoices from different locations or bank accounts become separate payments, even for the same vendor, and credits and prepayments cannot cross entities. …

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: Automatic extraction of: vendor name, invoice number, date, PO number, line items, amounts, tax, and payment terms

For a 3-person AP team currently keying 1,800 invoices per month from email and mail into Sage Intacct manually, Stampli's AI (Stampli AI, previously branded as Billy the Bot) takes over at the point of invoice receipt. Invoices arrive via email to a dedicated Stampli inbox or are uploaded directly; the AI then immediately extracts header and line-level fields without human intervention. Stampli's own product documentation confirms the extracted fields include vendor name, invoice number, PO number, line items, product descriptions, prices, credit/payment terms, and taxes, using a combination of OCR, machine learning, and natural language processing. …

Limitations: Line-item extraction accuracy on varied or lower-quality invoice formats (scanned paper, non-standard layouts from subcontractors or facilities vendors) improves over time as the system learns vendor-specific patterns; a third-party analysis notes that Stampli uses historical invoice data from specific vendors to impro …

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: 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 ad-hoc Slack/email approvals with enforceable thresholds, Stampli's Predefined Approval Workflows module addresses this requirement at the purchase request stage, before a PO is ever created, which is exactly where the buyer's 35% maverick spend originates. An admin uses the visual workflow builder to configure sequential, multi-level approval stages driven by the request amount field: the builder supports 'spending thresholds and condition-based rules that automatically determine when additional reviewers must be involved' (Stampli Predefined Approval Workflows help article, 2025-11-19). …

Limitations: The workflow builder documentation caps routing conditions at up to 5 configurable fields per workflow; since the buyer's entire hierarchy is driven by a single amount field, this cap is not binding for this requirement, but admins should verify that adding secondary conditions (e.g., department or entity) …

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. …