Basware vs Medius

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

For a 3-person AP team where the same individuals currently enter, approve, and initiate payments, Basware enforces segregation of duties through a combination of role-based access controls and workflow task assignment in its AP Automation platform. Control Objective 10 of Basware's documented AP Automation application controls states that 'logical access into AP Automation system is restricted to authorized personnel only and that the user roles are adequately segregated,' and the platform's approval workflow architecture explicitly requires that 'each invoice must be reviewed and approved by a separate person.' Roles are configured in P2P Administration as distinct permission sets (invoice …

Limitations: The separation between entry and approval is enforced through role configuration rather than a hard-coded self-approval block at the system level, so administrators must ensure that no single user is granted both the processing and approver rights during setup and during any role reassignment. …

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: Cash flow forecasting based on approved and pending payables with due date distribution

For a $120M services company managing 1,800 invoices per month across two Sage Intacct entities, Basware delivers cash flow forecasting through its Basware Insights analytics layer, specifically via the Committed Spend Dashboard. This dashboard aggregates all open commitments spanning payment plans, purchase orders, and invoices at every stage of the pipeline, including both invoices still in the approval workflow and those already approved, into a unified forward-looking view. …

Limitations: Basware Insights is positioned toward globally operating organizations with over 50,000 invoice transactions per year; at roughly 21,600 annual invoices across two entities, this buyer sits below the stated target scale, which may affect commercial fit and implementation resourcing even though the capability itself is …

Requirement evaluated: Cash flow forecasting based on approved and pending payables with due date distribution

For a $120M multi-location services company currently flying blind on payables timing, Medius delivers a dedicated Cashflow Dashboard within its Medius Analytics module, listed as a named pre-built dashboard in the Medius help center documentation alongside the Overview, Capture Insights, and Straight Through Processing dashboards. The mechanism works because Medius sits in the pre-processing layer: every invoice, whether still in an approval queue or fully approved and awaiting payment, lives in the Medius pipeline with its due date, payment terms, and workflow status tracked in real time. …

Limitations: The Medius Analytics layer, which houses the Cashflow Dashboard, refreshes on a Medius-managed schedule rather than continuously, so the view is a periodically updated snapshot rather than a second-by-second live feed; the operational gadget dashboards do update in real time but are invoice-status views rather than for …

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

For a $120M services company running two Sage Intacct entities and targeting 30%+ of spend on virtual card, Basware does offer virtual card as one of four payment rails within its payment module (check, ACH, virtual card, and wire from a single application), and its launch documentation explicitly states that clients can 'generate rebates on their spend' through this payment capability. The CorPay technology partner page on Basware's current website confirms an ongoing relationship with a commercial card infrastructure provider, which is the typical mechanism for sourcing virtual card issuance and rebate revenue share. …

Limitations: Basware's primary buyer-revenue mechanism in its current marketing is early payment discounts (dynamic discounting funded by the buyer's own cash), which is structurally different from virtual card interchange rebates; a buyer focused on virtual card rebate revenue as a financial goal should confirm with Basware direct …

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

For a US-based multi-location services company aiming to convert 30%+ of AP spend to virtual card, Medius delivers this through Medius Payments (their own payment module, priced separately from the core AP automation product). Once invoices are approved in the AP workflow, Medius Payments routes each payment to the optimal method: virtual card, ACH, wire, or check. For virtual card transactions, Medius issues a unique, single-use card number tied to a specific invoice and dollar amount; after the supplier processes it, the card self-destructs, closing the payment loop back to the ERP. …

Limitations: Virtual cards through Medius Payments are available for US-based businesses only, which is not a blocker for this buyer but would be relevant if international supplier payments were added later. …

Requirement evaluated: Matched invoices push to NetSuite AP for payment processing (or integrate with our AP automation tool)

For this $250M technology company running NetSuite as its ERP, Basware's Invoice Lifecycle Management platform handles the full pre-payment journey: it captures invoices in all formats (PDF via SmartPDF, EDI, XML, e-invoice), pulls PO data from NetSuite or any external procurement system, and runs PO matching and coding automatically. Once an invoice reaches a matched or approved state, Basware automatically pushes it to the ERP for payment without AP staff manually re-entering data into NetSuite. …

Limitations: The Future Plc case study notes they were 'the first Basware customer to integrate Invoice Matching directly with Oracle NetSuite,' suggesting this NetSuite integration path requires API configuration and likely implementation services or a NetSuite-side developer rather than a zero-configuration, certified SuiteApp in …

Requirement evaluated: Matched invoices push to NetSuite AP for payment processing (or integrate with our AP automation tool)

For a $250M technology company running NetSuite as its ERP and currently processing POs manually, Medius delivers a purpose-built, certified integration that pushes matched and approved invoices directly into NetSuite AP for payment processing. Medius holds 'Built for NetSuite' SuiteApp certification across its Procurement, AP Automation, and Pay modules, meaning the integration follows NetSuite's own platform development standards and does not require custom connectors or third-party middleware. …

Limitations: The depth of the NetSuite write-back (which specific vendor bill fields, subsidiary dimensions, and custom segments are populated) is not enumerated in publicly available documentation; buyers running a complex NetSuite OneWorld configuration with many custom segments should validate field-level mapping during a proof …

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

For a multi-location services company replacing email-based vendor management, Basware delivers most of this requirement through two interconnected products: the Basware Supplier Management module (also called Vendor Manager) and the Basware Network Supplier Portal. When your AP team needs to onboard a new vendor, they send an invitation link through Supplier Management; the vendor self-registers with their company details, and once the invitation is sent, only the supplier user can update that data going forward. …

Limitations: The material gap for this buyer is the W-9/W-8 collection mechanism: Basware accepts these documents as configurable PDF uploads in Supplier Management, but there is no purpose-built tax form collection workflow with TIN matching, entity-type routing, or IRS validation, meaning your AP team retains the burden of review …

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: Multi-entity support within the integration; we operate 2 entities in Intacct and plan to add a third

Your scenario involves 2 active Sage Intacct entities with a third planned, all processed through a centralized 3-person AP team. Basware's platform is built around an organizational structure that accommodates multiple companies or entities within a single AP processing environment: its developer XML integration guide instructs customers to submit one master data file per ERP system and notes that 'the organization structure created in Basware AP Automation affects how data is loaded,' with company codes used as prefixes in external record identifiers (e.g., [companyCode]_[AccountCode]). …

Limitations: Basware carries genuine multi-entity architectural capability, but because the Sage Intacct integration is not a pre-certified marketplace connector, entity-level GL posting fidelity (posting to the correct Intacct entity ID, syncing each entity's chart of accounts and vendor master separately, and routing approval wor …

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: 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 800+ active vendors, Basware delivers policy compliance reporting through two integrated layers: the Basware Analytics/Insights module and the e-Procurement platform. The AP KPI Overview dashboard includes a dedicated 'Spend under control' metric, defined as the percentage of invoices matched to a PO or approved contract/payment plan, giving the CFO a direct read on what fraction of spend flows through sanctioned channels. <cite index="23-1,23-5">The AP KPI dashboard tracks four strategic KPIs including 'Spend under control' (invoices based on PO or payment plan automatically matched) …

Limitations: Basware's deepest compliance reporting (approval task tracking, contract compliance rate) requires deployment of both the e-Procurement module and Insights Pro, so the buyer's full three-metric picture is not available in the base AP Automation tier alone. …

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

For a $250M technology company currently operating with 35% maverick spend and no structured procurement system, Medius addresses all three dimensions of this requirement across its combined AP Automation, Analytics, and Procurement modules. On spend-through-approved-channels: Medius captures every invoice at line-level detail and provides real-time insight into non-PO and off-contract invoices, so procurement can see exactly where spend falls outside policy and measure what proportion moves through PO-backed, contract-backed channels versus not (Medius Procurement Professionals page). …

Limitations: Full compliance reporting across all three dimensions (maverick spend percentage, contract compliance, approval adherence) is most complete when both the Medius Procurement module and the AP Automation/Analytics modules are deployed together; the Procurement module is available as part of a subscription package rather …

Requirement evaluated: Data encryption at rest and in transit

For a $120M services company routing 1,800 invoices per month through Basware into Sage Intacct, all invoice data, vendor credentials, and payment information are protected at both storage and transmission layers. Basware's own published legal documentation explicitly states that 'network traffic over public Internet is encrypted and customer data in storage is encrypted,' with encryption key management handled using Hardware Security Modules (HSMs) in accordance with industry best practices. This covers both the data-at-rest requirement (invoice documents and financial records stored in Basware's cloud environment) …

Limitations: Basware does not publicly name specific cipher parameters (such as AES-256 key length or minimum TLS version) on its public trust pages; buyers who require contractual confirmation of these specifics, for example to satisfy an internal security questionnaire or cyber insurance requirement, must request the full SOC 2 / …

Requirement evaluated: Data encryption at rest and in transit

For a $120M multi-location services company handling invoice data, vendor credentials, and payment information across two Sage Intacct entities, Medius provides encryption controls at both the storage and transmission layers. On the storage side, Medius explicitly documents AES-256 encryption across its infrastructure, which is hosted in Microsoft Azure data centers with customer data separated into unique SQL databases per customer. On the transmission side, Medius's Trust Center confirms that Transport Layer Security (TLS) …

Limitations: Medius's publicly accessible Trust Center pages confirm AES-256 and TLS but do not enumerate the specific TLS version floor (1.2 vs. 1.3) in free-text form; buyers with contractual requirements for a minimum TLS version should request the full SOC 2 Type 2 report and Qualys detail from trust.medius.com to confirm. …

Requirement evaluated: PO status tracking: from approved through acknowledged, received, invoiced, and closed

For a $250M tech company currently managing POs through email and manual NetSuite entry, Basware Procurement (their P2P module) covers the full PO status lifecycle the buyer needs. Once a requisition is approved, Basware Procurement sends the order to the supplier and tracks discrete status transitions throughout. <cite index="27-1">Basware's exported purchase order schema documents the supported OrderStatus values as: "ReadyForOrder", "Ordered", "SupplierRejected", "SupplierConfirmed", "ModifiedBySupplier", "PartiallyReceived", "Received", "Canceled", "Rejected", and "Closed"</cite> — mapping directly to the buyer's required stages of approved, acknowledged, received, and closed. …

Limitations: Basware's core marketing and fact-sheet positioning centers on AP automation and invoice lifecycle management; the full PO lifecycle tracking described here requires the Basware Procurement (P2P) module, which is licensed separately from the AP Automation product. …

Requirement evaluated: PO status tracking: from approved through acknowledged, received, invoiced, and closed

For a $250M technology company moving off email-and-Slack approvals, Medius's P2P platform covers most of the required PO lifecycle stages within a single platform. Purchase requests are raised by employees, approvals are automatically routed, and POs are generated instantly inside Medius; the 'approved' stage is natively tracked. When invoices arrive, AI captures and matches them against POs and goods receipts (three-way match), advancing the PO through the 'received' and 'invoiced' stages, with every step described as auditable and synced to the ERP in real time (Medius P2P platform page). …

Limitations: For this buyer's specific requirement of tracking all five discrete stages (approved, acknowledged, received, invoiced, closed), the 'acknowledged' milestone is the material gap: Medius does not explicitly document supplier PO acknowledgment as a named, auto-promoted status in its native procurement module, and the exi …

Requirement evaluated: Non-PO invoice routing: automatic GL coding suggestions based on vendor history and invoice description

For a services company processing roughly 810 non-PO invoices per month (45% of 1,800) covering utilities, professional services, subscriptions, and insurance, Basware addresses this requirement through its SmartCoding module, a purpose-built ML-based feature within its AP Automation solution. When a non-PO invoice arrives, SmartCoding analyzes the supplier's historical coding patterns alongside multiple invoice dimensions (vendor name, invoice description, reference person, and other header attributes) and generates GL coding proposals automatically, presenting a ranked list of suggestions to the reviewer without requiring AP staff to look up or manually key codes. …

Limitations: SmartCoding's accuracy at go-live depends on the volume and consistency of historical coding data available to train the model; a buyer with no prior AP automation history in Basware will need a ramp period before proposals reach high confidence levels. …

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: Touchless processing target: 40%+ of PO invoices should require zero manual intervention from capture through posting

For a services company processing approximately 990 PO-based invoices per month (55% of 1,800), Basware's end-to-end touchless chain for PO invoices works as follows. First, SmartPDF ingests emailed PDF invoices from a single dedicated inbox, applies AI-based line-item and header extraction, and converts the PDF into a structured e-invoice with over 97% field accuracy; with the self-validation feature active, Basware documents that on average 92%+ of PDF invoices are processed automatically through capture with no manual correction needed. Second, the InvoiceAI suite (SmartPDF, SmartMatching, and the AP Matching Agent) …

Limitations: Achieving touchless processing on the 3-way-match portion of PO invoices (facilities, supplies, subcontractors) requires goods receipt confirmations to flow from Sage Intacct or the receiving workflow into Basware in real time; if GR records are entered late or inconsistently by warehouse or project staff, those invoic …

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: Supplier performance scorecards: on-time delivery rate, quality issues, invoice accuracy, responsiveness

For a $250M technology company moving off email-based purchasing, Basware's native scorecard coverage is strongest on the invoice accuracy dimension and weakest on the other three. Basware Insights (the analytics module) tracks AP-side KPIs including invoice processing times, approval cycle times, exception rates, and early payment discount capture, all derived from its invoice matching and PO processing engine. A third-party Basware reseller partner documents that Basware Analytics also surfaces supplier-level lead time, order fulfillment, and delivery quality data drawn from P2P transaction flows. …

Limitations: For this buyer's four required scorecard dimensions, only invoice accuracy has a clearly documented native mechanism in Basware's AP matching and analytics layer. On-time delivery (requiring goods receipt vs. …

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: 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 moving from ad-hoc Slack/email approvals to a structured five-tier spend policy, Basware's procurement workflow engine (Basware P2P / e-Procurement module) delivers the mechanism through configurable 'Workflow Steps' and 'Processing Limits.' Administrators define multi-step approval chains for purchase requisitions and purchase orders, and each workflow step carries a 'Processing Limit' setting that controls the monetary threshold at which a processor's authority is reviewed before the step is considered approved. …

Limitations: The specific dollar-band thresholds (e.g., the $1K auto-approve floor) must be configured during implementation by Basware's professional services team or a trained administrator; self-service threshold editing is not documented as a point-and-click UI feature, which could mean change requests go through a formal chang …

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: Savings tracking: show negotiated savings vs. list price, contract compliance rate, and consolidation opportunities

Your company's challenge of 35% maverick spend and 800+ active vendors maps partially onto what Basware's Analytics module and e-Procurement platform deliver. Basware Analytics, available as a packaged add-on to the P2P suite, provides standard dashboards and KPIs that surface maverick spending by category, supplier, and department, and explicitly supports efforts to 'consolidate spending and right-size your supply base.' At the point of purchase, the Basware Marketplace enforces negotiated catalog pricing and guides buyers to preferred suppliers, which captures compliance in real time rather than reporting it retrospectively. …

Limitations: The three specific metrics the buyer named: negotiated savings vs. list price (requires a stored list-price reference and a savings computation engine), contract compliance rate as a percentage KPI, and algorithmically surfaced consolidation opportunities, are not all documented as native Basware mechanisms; deeper con …

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: Guided buying: when an employee searches for a product category, surface preferred/contracted vendors and catalog items first

For a $250M technology company trying to eliminate its 35% maverick spend rate, Basware addresses this requirement through Basware Marketplace combined with Basware Purchase, its e-procurement module. When an employee needs to buy something, they enter the Marketplace's consumer-style shopping interface and either search by keyword or browse by category tile. …

Limitations: This capability lives in Basware's e-Procurement modules (Basware Purchase and Basware Marketplace), which are distinct from the AP automation suite that dominates Basware's current market positioning; the buyer must license and implement both the procurement and AP sides of the platform, which adds implementation scop …

Requirement evaluated: Mobile submission capability; our field team needs to submit requests from job sites

This buyer's field team needs to originate purchase requisitions from job sites, which requires mobile PR creation, not just mobile approval. Medius's documented mobile capability centers on a responsive web interface (no native app required) that allows users to access and act on documents from any HTML-compliant browser on phones or tablets. <cite index="35-1,35-2,35-3">Medius's responsive web design supports consistent use across PCs, laptops, tablets, and mobile devices with no app to download, and the mobile-friendly interface allows users to access, authorize, and comment on documents.</cite> However, every mobile-specific reference found is approval-centric: <cite index="16-1,16-5">Me …

Limitations: The material ceiling for this buyer is that Medius's mobile capability is structured around approver workflows (reviewing and approving invoices and requisitions in queue), not around field-side requisition origination. …

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 email/Slack approvals, Basware AP Automation provides genuine three-way matching across all three documents. <cite index="10-9">Purchase orders can be imported for 2-way matching without receipts and for 3-way matching with goods receipts.</cite> The goods receipt leg is ingested via Basware's XML or REST API, which carries row-level quantity, net price, and net sum for each GR line, <cite index="4-1,4-2">and the 'Matching against goods receipts' option configures whether the Order Matching function includes matching against goods receipts; when enabled, the Order Matching function matches purchase invoices to the receipt row of the order.</cite> Tol …

Limitations: The current-platform (Alusta/Neo) tolerance configuration documented in Purchase Invoice Settings applies a single total-level percentage or monetary threshold comparing invoice total to order-row total; independent price-axis (2%) and quantity-axis (5%) …

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 …