AvidXchange vs Medius

Requirement evaluated: The system must support configurable approval-authority limits that tie dollar thresholds and invoice attributes to specific roles or named individuals, so that invoices above a defined amount or of a defined type are blocked from advancing without a qualifying approver on record. Authority limit configurations and any changes to those configurations must themselves be logged in the immutable audit trail, so auditors can reconstruct who held what authority at any point in time.

For a PE-backed company on NetSuite preparing for IPO-level SOX scrutiny, AvidXchange's AvidInvoice workflow engine supports dollar-threshold-based authority limits tied to roles and named individuals: administrators configure conditional workflow steps so that invoices exceeding a defined dollar amount (the vendor's own blog cites a $15,000 CFO escalation as a representative example) are automatically routed to a designated role group, blocking advancement until a qualifying approver within that role has acted. …

Limitations: The hard-block enforcement of dollar-threshold routing to roles is documented, but AvidXchange provides no evidence that changes to approval-authority configurations (threshold edits, role membership changes, rule additions) are captured in a timestamped, user-attributed, immutable audit trail. …

Requirement evaluated: The system must support configurable approval-authority limits that tie dollar thresholds and invoice attributes to specific roles or named individuals, so that invoices above a defined amount or of a defined type are blocked from advancing without a qualifying approver on record. Authority limit configurations and any changes to those configurations must themselves be logged in the immutable audit trail, so auditors can reconstruct who held what authority at any point in time.

For a PE-backed company on NetSuite preparing for IPO, Medius delivers a well-documented approval-authority matrix through its MediusFlow module. <cite index="10-1,10-2,10-3,10-4">Approval rights are configured on roles with two enforced dimensions: a maximum approval amount per invoice (the total across all coding rows a user may approve on a single invoice) …

Limitations: The material gap for this IPO-prep buyer is the Admin log's separation from the transaction audit trail and the absence of confirmed immutability: if auditors cannot pull a single, tamper-evident record showing who held what authority limit at what point in time (before/after values, timestamps, actor identity), the co …

Requirement evaluated: The system must provide auditor-ready compliance reporting that can produce, on demand, a complete control evidence package for any invoice or payment: the immutable event log, the SoD enforcement record, the authority limit in effect at the time of approval, the chain of custody, and the duplicate check result. This reporting must be exportable without requiring database-level access or vendor professional services, so that the buyer's internal audit and external auditors can pull evidence independently during IPO-readiness reviews and ongoing SOX testing cycles.

For a PE-backed NetSuite company building toward IPO-readiness, AvidXchange provides a per-invoice audit trail that timestamps every action from receipt through payment, accessible via the buyer's portal without requiring database access or vendor professional services. The platform's FAQ confirms that users can 'create searches, run reports and export your invoice data history in Excel, PDF, or view the data in HTML' at any time, with invoice data retained for up to seven years. …

Limitations: For IPO SOX testing cycles, the material gap is that AvidXchange's audit exports cover the event log and approval workflow history, but there is no documented mechanism to produce a single, per-invoice control evidence package that surfaces the SoD enforcement record, the authority limit active at approval time, and th …

Requirement evaluated: The system must provide auditor-ready compliance reporting that can produce, on demand, a complete control evidence package for any invoice or payment: the immutable event log, the SoD enforcement record, the authority limit in effect at the time of approval, the chain of custody, and the duplicate check result. This reporting must be exportable without requiring database-level access or vendor professional services, so that the buyer's internal audit and external auditors can pull evidence independently during IPO-readiness reviews and ongoing SOX testing cycles.

For a PE-backed NetSuite company preparing for an IPO and SOX testing cycles, Medius provides a documented end-to-end AP audit trail with several relevant control layers, but falls short of the full bundled, on-demand compliance evidence package the buyer requires. On the control side, Medius logs every step across the AP lifecycle: invoices are automatically archived at capture, and the platform commits that 'all risk is automatically flagged, mitigated and logged across the AP lifecycle.' Role-based access control enforces segregation of duties, with a documented 'Pay Approver Role' enforcing separation between invoice processing and payment authorization. …

Limitations: The material gap is not in whether Medius logs events, but in whether those logs are assembled into an auditor-ready, single-artifact evidence package per invoice or payment that is independently exportable by internal audit and external auditors without vendor involvement. …

Requirement evaluated: The system must provide a self-service vendor portal where suppliers can submit invoices directly, check payment status, and respond to queries from AP, reducing inbound email volume and giving AP a single structured intake channel. For the buyer's three-entity structure, the portal must allow vendors to indicate or confirm which legal entity the invoice is addressed to at submission time, so that entity-level routing can begin without manual AP triage.

For a buyer running three D365 Finance legal entities, AvidXchange offers the AvidXchange Supplier Hub: a free, self-service portal where enrolled vendors gain 24/7 visibility into invoice and payment statuses with granular states (Received, Pending Approval, Approved, Sent, Paid), configurable email notifications for status changes, and export tools for reconciliation. However, the Supplier Hub is explicitly not an invoice submission channel. AvidXchange's own documentation states directly: 'No, suppliers will continue to invoice their customers as they currently do' — meaning submission happens via email to a dedicated address or P.O. box, not through a structured portal intake form. …

Limitations: The buyer's core requirement — that vendors confirm the target legal entity at submission time so that entity-level routing begins without manual AP triage — is not addressed by any documented mechanism in the Supplier Hub or AvidPay Network portal. …

Requirement evaluated: The system must provide a self-service vendor portal where suppliers can submit invoices directly, check payment status, and respond to queries from AP, reducing inbound email volume and giving AP a single structured intake channel. For the buyer's three-entity structure, the portal must allow vendors to indicate or confirm which legal entity the invoice is addressed to at submission time, so that entity-level routing can begin without manual AP triage.

For this buyer's three-entity D365 Finance environment, Medius provides a dedicated Supplier Portal described as a 'single point-of-entry for suppliers to view, register, record and update their details in a cloud-based location.' During supplier registration, the portal requires suppliers to configure their own legal entities before they can begin invoicing customers, establishing the supplier-side identity. …

Limitations: The core gap for this buyer is the absence of documented evidence that the Medius Supplier Portal surfaces a buyer-entity selection field at invoice submission time: the intake mechanism Medius documents is per-company email routing (an AP-managed step), meaning AP staff must still triage or pre-sort submissions by ent …

Requirement evaluated: The AP automation system's audit trail must integrate with Oracle NetSuite at full field fidelity, meaning that every AP event recorded in the AP tool (coding, approval, payment posting) must produce a corresponding, reconcilable record in NetSuite with no dimensional data loss across NetSuite's custom segments, subsidiaries, and transaction fields. A gap between what the AP tool records and what NetSuite receives creates an unauditable seam that external auditors will flag during SOX review; the integration must eliminate that seam entirely.

For a PE-backed company on NetSuite preparing for IPO, AvidXchange deploys its AvidSuite for NetSuite (AFN) product, built directly on the Oracle SuiteCloud Computing Platform. This architecture places the integration inside NetSuite's own development framework rather than via a flat-file or generic middleware bridge. The AFN SuiteApp carries invoice images, payment records, and payment log data directly inside the NetSuite UI, and its official fact sheet on SuiteApp.com claims a 'detailed audit trail and payment controls' delivered within Oracle NetSuite. …

Limitations: The two-system audit trail architecture means that AvidXchange's approval and coding history lives primarily in AvidXchange's platform, and only the posted transaction result reaches NetSuite; auditors reviewing SOX controls will need to reconcile across both systems, which is precisely the seam the buyer's requirement …

Requirement evaluated: The AP automation system's audit trail must integrate with Oracle NetSuite at full field fidelity, meaning that every AP event recorded in the AP tool (coding, approval, payment posting) must produce a corresponding, reconcilable record in NetSuite with no dimensional data loss across NetSuite's custom segments, subsidiaries, and transaction fields. A gap between what the AP tool records and what NetSuite receives creates an unauditable seam that external auditors will flag during SOX review; the integration must eliminate that seam entirely.

For a PE-backed NetSuite company preparing for SOX review, Medius connects to NetSuite via a certified, cloud-managed connector that holds 'Built for NetSuite' certification, meaning it follows Oracle SuiteCloud platform development standards and best practices. The integration is positioned as bidirectional: master data flows from NetSuite into Medius so coding dimensions are available during AP processing, and posted invoices, approvals, and payment events flow back to NetSuite's AP ledger. …

Limitations: The 'Built for NetSuite' certification and cloud-managed connector are genuine positive signals, but Medius has not publicly documented field-level coverage of NetSuite custom segments and subsidiary dimensions in its connector; the presence of a simplified FX API path and 'standardized integrations' framing means this …

Requirement evaluated: The system must perform automated duplicate invoice detection at the pre-processing stage, using configurable matching logic across vendor ID, invoice number, invoice date, and invoice amount, with tolerance rules for near-duplicate scenarios. Detected duplicates must be flagged and routed to an exception queue rather than silently suppressed, and the detection event and disposition must be recorded in the audit trail to demonstrate to auditors that duplicate controls were operating at the time of each processing run.

For a PE-backed company on Oracle NetSuite preparing for IPO-level SOX audit scrutiny, the bar for duplicate detection is a documented, configurable, pre-processing engine with per-event audit log entries auditors can inspect. AvidXchange's marketing and FAQ documentation confirms that its AvidInvoice platform creates <a href='https://www.avidxchange.com/resources-home/frequently-asked-questions/'>an 'audit trail of the steps performed in processing your invoices'</a> and that its <a href='https://www.avidxchange.com/resources-home/frequently-asked-questions/'>invoice automation software mirrors current approval processes and workflows, helping reduce duplicate payments</a>. …

Limitations: For a SOX audit readiness program on NetSuite, the undocumented gap is precise: AvidXchange has not publicly specified whether duplicate detection runs at the pre-processing intake stage or only at payment time, whether matching logic is configurable across multiple fields with near-duplicate tolerance bands, or whethe …

Requirement evaluated: The system must perform automated duplicate invoice detection at the pre-processing stage, using configurable matching logic across vendor ID, invoice number, invoice date, and invoice amount, with tolerance rules for near-duplicate scenarios. Detected duplicates must be flagged and routed to an exception queue rather than silently suppressed, and the detection event and disposition must be recorded in the audit trail to demonstrate to auditors that duplicate controls were operating at the time of each processing run.

For a PE-backed company on NetSuite preparing for SOX readiness, Medius operates a dedicated duplicate detection engine at the import stage (pre-processing, before any workflow step). <cite index="16-2,16-3">The system defines what constitutes a duplicate by specifying a standard definition; the default is that a duplicate occurs when two invoices with the same vendor, invoice number, and year in the invoice date are present in the system at the same time.</cite> <cite index="16-7">If an invoice is imported and found to be a duplicate according to this definition, it is automatically placed in the Import Error queue with an error message that the invoice is a duplicate.</cite> This satisfies …

Limitations: The buyer's requirement explicitly calls for configurable matching logic across vendor ID, invoice number, invoice date, AND invoice amount with tolerance bands for near-duplicate scenarios. …

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

For a multi-location services company with a large subcontractor and facilities PO volume, AvidXchange addresses 2-way matching through the AvidBuy + AvidInvoice combination. When a supplier emails an invoice, AvidInvoice captures line-item data and AvidBuy automatically matches it to the corresponding PO without requiring a goods receipt or delivery confirmation record. The AvidInvoice product page explicitly confirms the platform supports both '2-way (PO and Invoice) …

Limitations: Public documentation confirms 2-way match as a selectable mode but does not expose whether individual line-level fields (e.g., quantity) can be toggled off for value-only matching on service lines where quantity is not meaningful; this configuration detail should be confirmed with AvidXchange during implementation scop …

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

For a $120M services company where 55% of invoices are PO-backed (including subcontractors and facilities spend with no physical goods receipt), Medius supports PO-to-invoice matching that operates on value and amount comparison rather than requiring a delivery confirmation record. When an order invoice enters the system, <cite index="29-1,29-3">it is automatically matched against the purchase order, and based on how the matching goes, the invoice receives a matching status.</cite> The key configuration mechanism for service POs is the `MatchOrderInvoiceAmount` system parameter: <cite index="28-1">administrators activate this parameter and enter the maximum permitted deviation in currency un …

Limitations: The default Medius order matching flow includes an 'Awaiting delivery' status that holds invoices when a PO has no registered delivery record in the purchasing system; for service POs, this queue must be bypassed through configuration (using value-based `MatchOrderInvoiceAmount` parameters rather than quantity/receipt …

Requirement evaluated: The system must enforce role-based access controls (RBAC) at a granular level, limiting each user's visibility and action permissions to only the invoices, vendors, GL accounts, cost centers, and approval queues relevant to their role. Permission assignments and any changes to them must be logged with the identity of the administrator who made the change and the timestamp, so that access creep and unauthorized permission escalation are detectable during a SOX audit.

For a PE-backed NetSuite company on the IPO track, AvidXchange's AvidInvoice module delivers a documented role-based permissions framework administered through the Portal Administrator's Admin dashboard. The mechanism works as follows: administrators navigate to the 'Manage Permissions' screen, select a task from the Task column, and assign or remove roles using the Roles Addition and Removal Controls interface; the system confirms updates on save. …

Limitations: The material ceiling for this buyer is the absence of documented, exportable permission-change audit logs at the application level: AvidXchange evidences RBAC configuration capability and a general AP workflow audit trail, but does not publicly document that every role assignment change is captured with administrator i …

Requirement evaluated: The system must enforce role-based access controls (RBAC) at a granular level, limiting each user's visibility and action permissions to only the invoices, vendors, GL accounts, cost centers, and approval queues relevant to their role. Permission assignments and any changes to them must be logged with the identity of the administrator who made the change and the timestamp, so that access creep and unauthorized permission escalation are detectable during a SOX audit.

For a PE-backed company on NetSuite preparing for SOX, Medius (via MediusGo) provides a structured role-based permission model administered through its Administration Tool. <cite index="15-4,15-5,15-6">Invoices and permissions are managed through users and roles, where a user represents a personal login with all activity linked to that login, and roles control which functions and permissions each user has.</cite> <cite index="6-10,6-11,6-12,6-13,6-14,6-15">Role permissions are set per company entity and cover approval rights (which amounts and coding values the role may approve), report and search access rights, special approval rules, coding rights, and administration tool rights.</cite> <c …

Limitations: The material gap for this SOX buyer is the second half of the requirement: no documented mechanism was found showing that permission assignments and changes to them are logged with the identity of the administrator who made the change and a timestamp, which is the specific evidence SOX auditors need to detect access cr …

Requirement evaluated: The system must support consolidated payment runs that sweep approved payables across all 9 productions in a single execution, posting payments and remittance back to Sage Intacct with full dimensional fidelity (profit center, GL account, and any other active Intacct dimensions) per line. The payment run must not require a multi-entity or subsidiary structure in Sage Intacct, since the buyer operates as one legal entity and separate books would break this consolidated process.

For a media production company running 9 profit centers inside a single Sage Intacct entity, AvidXchange processes the payment run centrally through AvidPay without requiring a multi-entity or subsidiary structure. The Sage Intacct Marketplace listing confirms <cite index="1-1,1-6">AvidXchange offers a robust API integration with next-level data syncing, including invoice images and custom dimensions</cite>; and the partner overview sheet corroborates that <cite index="2-3">the API-enabled integration extends well beyond the basics of AP, including support for custom dimensions.</cite> AvidXchange's own multi-entity blog explicitly addresses the single-entity, multi-unit scenario: <cite inde …

Limitations: The critical unconfirmed question for this buyer is whether AvidPay's payment posting loop-back to Sage Intacct writes full dimensional data (profit center, GL account, any other active Intacct dimensions) …

Requirement evaluated: The system must support consolidated payment runs that sweep approved payables across all 9 productions in a single execution, posting payments and remittance back to Sage Intacct with full dimensional fidelity (profit center, GL account, and any other active Intacct dimensions) per line. The payment run must not require a multi-entity or subsidiary structure in Sage Intacct, since the buyer operates as one legal entity and separate books would break this consolidated process.

This media production company runs 9 productions as profit centers inside one Sage Intacct legal entity and needs a single payment run that sweeps all approved payables, posts payments back to Intacct with full dimensional fidelity, and requires no multi-entity or subsidiary structure. Medius Pay is positioned as an embedded payment module that initiates payments once invoices are approved and syncs results back to the ERP. Per Medius's payments product page, the module handles 'payments via multiple channels (USA via ACH, Check, Wire, or VCard) …

Limitations: The Sage Intacct integration is delivered through a third-party partner (Acuity Solutions), not a Medius-native connector, and there is no public documentation confirming that payment postings carry full Intacct dimensional fidelity (profit center, custom dimensions) at the line level back to the ERP. …

Requirement evaluated: The system must enforce invoice visibility isolation across all 9 active productions within a single Sage Intacct legal entity using dimension-based or permission-based access controls, not separate entity or subsidiary configurations. Each production's AP team must be restricted to viewing, editing, and acting only on invoices coded to their own production's profit center, replicating Intacct's profit center dimension as the isolation boundary without fragmenting the chart of accounts or the book of record.

This media production company needs AvidInvoice to restrict each production's AP team to viewing only invoices coded to their own Sage Intacct profit center, without creating separate entities. AvidInvoice does carry a role-based permission system: <cite index="21-2,21-3">the application is configured with default roles that correlate to specific permissions, and these roles are designed to give the Portal Administrator full control over what business functions should be enabled or restricted from internal users.</cite> Separately, <cite index="41-6">the Sage Intacct API integration supports 'next-level data syncing, including invoice images and custom dimensions,'</cite> confirming that Int …

Limitations: For this buyer's 9-production setup, AvidXchange's permission architecture controls who can act on an invoice but does not document a mechanism that prevents a production AP user from discovering or viewing invoices coded to a different profit center via search or reporting, meaning the isolation boundary exists in the …

Requirement evaluated: The system must enforce invoice visibility isolation across all 9 active productions within a single Sage Intacct legal entity using dimension-based or permission-based access controls, not separate entity or subsidiary configurations. Each production's AP team must be restricted to viewing, editing, and acting only on invoices coded to their own production's profit center, replicating Intacct's profit center dimension as the isolation boundary without fragmenting the chart of accounts or the book of record.

For a media production company running 9 active productions as profit centers inside one Sage Intacct legal entity, Medius offers role-based and dimension-based controls that partially address the isolation requirement, but the architecture has a material ceiling. On the permission side, Medius roles carry a 'Report and Search access rights' tab that controls which invoices a role can search and view in the system; these rights are scoped per company in Medius's data model. (Source: 'Roles, report and search access rights' on MediusGo Customer Portal — see sourceUrl.) …

Limitations: Medius's invoice visibility controls are scoped to the company object, not to a sub-company dimension value; a production AP user who shares the same Medius 'company' as other productions will be able to see invoices for those other productions in the inbox and search, unless each production is configured as a separate …

Requirement evaluated: The system must support 3-way matching of purchase order, receipt confirmation, and invoice for goods and subcontractor-based transactions in construction, where receipt confirmation is captured as a project manager or superintendent contribution within the pre-processing workflow rather than assumed from a warehouse scan. 2-way matching that skips receipt confirmation is insufficient for a construction environment where work confirmation comes from field personnel, not a receiving dock.

For a multi-location construction company on NetSuite needing receipt confirmation from field personnel rather than a warehouse dock, AvidXchange's AvidInvoice module explicitly supports both 2-way and 3-way matching: <cite index="9-12">AvidInvoice supports 2-way (PO and Invoice) and 3-way matching (PO, Invoice and Receipt).</cite> The construction-specific AvidSuite product page names this directly: <cite index="31-1">match invoices against POs and receipts (3-way match)</cite> as a listed capability. …

Limitations: The material ceiling for this buyer is that AvidXchange's 3-way match is a document-matching control, not a receipt-confirmation workflow step: the system expects a receipt document to already exist and matches against it, rather than routing the receipt confirmation question to a field-side PM or superintendent as an …

Requirement evaluated: The system must support 3-way matching of purchase order, receipt confirmation, and invoice for goods and subcontractor-based transactions in construction, where receipt confirmation is captured as a project manager or superintendent contribution within the pre-processing workflow rather than assumed from a warehouse scan. 2-way matching that skips receipt confirmation is insufficient for a construction environment where work confirmation comes from field personnel, not a receiving dock.

For a multi-location construction company on NetSuite where subcontractor receipt confirmation comes from field personnel rather than a warehouse dock, Medius supports genuine 3-way matching (PO, goods delivery receipt, and invoice) as a named, documented product capability. <cite index="23-1,23-5">The platform can automatically match invoice line details against purchase orders, goods receipts, and/or contracts to resolve discrepancies in invoices, POs, and receivables.</cite> The RAD (Rapid Application Delivery) …

Limitations: Medius's 3-way match is designed around goods receipts that originate as records in NetSuite before or during invoice processing; for subcontractor invoices where no ERP goods receipt exists, the missing-GR exception route can direct the invoice to a responsible user, but this is reactive exception handling rather than …

Requirement evaluated: SuiteTax data must pass through the AP automation layer without loss or transformation: tax codes, tax groups, nexus assignments, and tax amounts calculated or assigned in the buyer's NetSuite SuiteTax configuration must be carried on the invoice record written back to NetSuite exactly as they would appear if the invoice were entered natively in NetSuite. The vendor must confirm whether their NetSuite connector uses the SuiteTax API endpoints directly or applies a tax abstraction layer that could introduce discrepancies, and must document any known SuiteTax field gaps in their current connector.

For a shared-services AP team running Oracle NetSuite OneWorld across 14 subsidiaries, the operative question is whether AvidXchange's connector writes invoice records back to NetSuite in a way that is fully compatible with the SuiteTax engine: populating tax codes, tax groups, nexus assignments, and per-line tax amounts as SuiteTax expects, rather than passing a flat tax total that bypasses the SuiteTax calculation and posting logic. AvidXchange documents its NetSuite integration as an API-based connector that syncs 'invoice images and expense line items' between the two systems, and its product page confirms the API integration carries coding data back to NetSuite. …

Limitations: No public documentation from AvidXchange confirms SuiteTax API endpoint usage, discloses whether a tax abstraction layer is applied on write-back, or enumerates SuiteTax field gaps; the buyer cannot assess SOX-grade tax compliance posture for this requirement without a direct technical disclosure from AvidXchange. …

Requirement evaluated: SuiteTax data must pass through the AP automation layer without loss or transformation: tax codes, tax groups, nexus assignments, and tax amounts calculated or assigned in the buyer's NetSuite SuiteTax configuration must be carried on the invoice record written back to NetSuite exactly as they would appear if the invoice were entered natively in NetSuite. The vendor must confirm whether their NetSuite connector uses the SuiteTax API endpoints directly or applies a tax abstraction layer that could introduce discrepancies, and must document any known SuiteTax field gaps in their current connector.

For a shared-services AP team running NetSuite OneWorld across 14 subsidiaries, the SuiteTax writeback question sits at the final and most technically sensitive stage of the pre-processing journey: the moment a processed invoice record is posted to NetSuite as a vendor bill. Medius holds 'Built for NetSuite' certification for its AP Automation and Procurement SuiteApps, which confirms adherence to SuiteCloud platform development standards, and its help center notes that PO-based invoices can use 'SaC' (Same as Cost) …

Limitations: The buyer's SOX audit trail and 14-subsidiary SuiteTax compliance requirement demand confirmed connector behavior at the field level: which tax fields are written, in which format, and via which NetSuite API. …

Requirement evaluated: Occasional contributors including project managers, superintendents, and contract owners must be able to complete their specific contribution actions, receipt confirmation, terms verification, or cost allocation responses, entirely from email, Microsoft Teams, or a mobile interface without creating an account in or logging into the AP automation platform. The buyer explicitly named these three channels as the access requirement for occasional users who will not adopt another system login.

This construction company needs PMs, superintendents, and contract owners to confirm receipt, verify terms, and allocate costs from email, Teams, or mobile without creating a platform account. AvidXchange's design philosophy runs directly counter to this requirement: the platform's own documentation explicitly frames its value as moving approvals off email and onto the AvidXchange platform. …

Limitations: Every contributor in AvidXchange's approval model, including occasional participants like PMs and superintendents, must be provisioned as a named licensed user with a password before they can take any action. …

Requirement evaluated: Occasional contributors including project managers, superintendents, and contract owners must be able to complete their specific contribution actions, receipt confirmation, terms verification, or cost allocation responses, entirely from email, Microsoft Teams, or a mobile interface without creating an account in or logging into the AP automation platform. The buyer explicitly named these three channels as the access requirement for occasional users who will not adopt another system login.

This construction company needs PMs, superintendents, and contract owners to perform receipt confirmation, terms verification, and cost allocation responses entirely from email, Microsoft Teams, or a mobile interface without creating a platform account. Medius offers two relevant access mechanisms. First, 'Actionable Emails': approvers can approve, reject, or comment on expense invoices directly from Outlook without logging into the application each time; however, this feature requires O365 authentication, meaning the contributor must have an active Microsoft 365 account and that identity must be provisioned within the Medius tenant. …

Limitations: The Actionable Emails feature requires O365 authentication and a provisioned Medius identity, not truly account-free access; the mobile solution requires a platform login; and no native Microsoft Teams integration for invoice contribution actions is documented, meaning all three of the buyer's named channels fail the ' …

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

AvidXchange's multi-location services buyer processes 1,800 invoices per month, starting from zero with no prior machine-learned history: this is exactly the scenario where the ramp behavior of the learning system matters most. AvidXchange addresses the learning requirement through a recently expanded AI capability within its AvidInvoice Invoice Capture feature. …

Limitations: Because accuracy improvement runs through both the ML model and human indexers, the learning feedback loop is co-dependent on indexer quality: a G2 reviewer documented that when an indexer selects a wrong vendor, 'the Avid indexers will continue to choose the wrong vendor going forward for future invoices from that ven …

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: Native, pre-built, bidirectional integration with Sage Intacct (not middleware-dependent)

For your two-entity Sage Intacct setup processing 1,800 invoices per month, AvidXchange connects via a direct API integration built on its own AvidConnect Platform, listed as a certified partner in the official Sage Intacct Marketplace. The integration operates bidirectionally: it pulls vendor master data, GL accounts, and custom Sage Intacct dimensions into the AvidXchange workflow for invoice coding and approval, then pushes approved invoices back into Sage Intacct for posting, along with payment status updates from AvidPay. …

Limitations: The documented data syncing covers custom dimensions and invoice images, but independent sources note that AvidXchange's invoice coding relies partly on human-assisted processing rather than fully automated AI at the line-item level, which may affect how quickly dimension tags flow back into Sage Intacct post-coding. …

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: AI-powered anomaly detection for unusual invoice patterns (spike in amount, new bank account, unusual vendor behavior)

For a $120M services company processing 1,800 invoices monthly across two Sage Intacct entities, AvidXchange delivers its anomaly detection primarily through the AvidPay payment module rather than at the invoice ingestion or pre-processing stage. The AvidPay product page states that 'AI runs continuously in the background to help detect anomalous behavior and optimize fraud rules, so your protection gets smarter over time,' and lists 'Continuous risk reduction with AI-enabled fraud platform' as a named product capability. …

Limitations: The documented anomaly detection operates at the payment release stage (within AvidPay), not during the invoice capture and approval pre-processing stages where your AP team of three would benefit most from real-time risk signals. …

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