Medius vs Stampli

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 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 SOX readiness, Stampli provides the transaction-side of this requirement with solid depth. Stampli's predefined and dynamic approval workflows allow administrators to configure spending thresholds and condition-based rules that determine which approvers must be involved at each dollar tier: the workflow builder supports rules based on amount, department, cost center, vendor type, and other invoice attributes, and the system can automatically block approval or escalate when a threshold is crossed rather than issuing a soft warning. …

Limitations: The material ceiling for this SOX-readiness buyer is configuration-change logging: Stampli documents an immutable transaction audit trail thoroughly, but does not publicly confirm that changes to the approval authority configurations themselves (threshold edits, role reassignments, workflow rule modifications) …

Requirement evaluated: The AI coding model must learn from this buyer's specific transaction history to improve dimension coding accuracy over time, using the 12,000 monthly invoices as the training corpus. The vendor must explain the actual mechanism (per-customer model, fine-tuning on approval history, rules derived from prior accepted coding, or equivalent) and must not describe a generic pretrained model as if it were customer-specific learning. The buyer's question, 'how does the per-customer model learn from our history,' must be answerable with a concrete mechanism and a measurable lift curve, not a marketing claim.

For a buyer processing 12,000 invoices a month across dozens of NetSuite coding fields, Medius's learning mechanism is delivered through SmartFlow, a CNN-based proprietary model that auto-codes GL account, tax fields, approver values, and coding dimensions for non-PO invoices. The mechanism is explicitly company-specific: according to Medius's invoice automation product page, SmartFlow is 'trained on your historical actions and enriched by 2.4 billion+ invoice field data points across Medius's global customer base,' and a Medius Chief Architect confirmed in a published interview that 'our machine learning technology uses pattern recognition to capture invoices, code them correctly, and route …

Limitations: Medius does not publish a measurable lift curve showing accuracy improvement as a function of invoice volume past the cold-start '95% after two invoices' benchmark, so the buyer cannot verify the concrete progression their 12,000 monthly invoices would drive. …

Requirement evaluated: The AI coding model must learn from this buyer's specific transaction history to improve dimension coding accuracy over time, using the 12,000 monthly invoices as the training corpus. The vendor must explain the actual mechanism (per-customer model, fine-tuning on approval history, rules derived from prior accepted coding, or equivalent) and must not describe a generic pretrained model as if it were customer-specific learning. The buyer's question, 'how does the per-customer model learn from our history,' must be answerable with a concrete mechanism and a measurable lift curve, not a marketing claim.

For a buyer processing 12,000 invoices a month across dozens of NetSuite dimensions, Stampli's Billy operates a documented two-layer learning architecture. The base layer is a proprietary business reasoning model trained on billions of decision points across Stampli's entire customer base; <cite index="20-6,20-7">Billy is described as 'a proprietary business reasoning AI trained on billions of decision points across every aspect of P2P' that 'helps operate every task with the full context of a customer's processes, preferences and history.'</cite> The customer-specific layer sits on top: <cite index="1-19">Billy 'codes invoices line by line, applying GL accounts, departments, and custom dime …

Limitations: The buyer's requirement calls for a concrete mechanism with a measurable lift curve, but Stampli does not publish the technical specifics that would fully satisfy this test: the documentation does not explicitly confirm whether Billy maintains a per-tenant isolated model or a shared global model with customer-specific …

Requirement evaluated: The system must support full NetSuite custom segment coding, not only the standard NetSuite dimensions (GL account, location, department, class, project). The buyer explicitly calls out 'several custom dimensions' as part of their standard coding workflow. A vendor whose data model is limited to NetSuite's out-of-the-box fields cannot serve this buyer; the integration layer must read the buyer's NetSuite custom segment configuration and expose those segments as codeable targets in the AP automation UI and AI coding engine.

For a buyer running NetSuite with dozens of coding fields including several custom dimensions, Medius addresses the requirement through a direct schema import from NetSuite at onboarding. The May 2025 Medius AP Automation for Oracle NetSuite product definition states explicitly: 'The structure of coding dimensions, including both standard and custom dimensions, is determined during the data gathering phase of the customer onboarding process. …

Limitations: The product definition document describes the custom dimension import as part of the customer onboarding process, which implies configuration effort at implementation rather than a self-service, real-time sync; if the buyer adds new custom segments to NetSuite post-go-live, it is unclear from available documentation wh …

Requirement evaluated: The system must support full NetSuite custom segment coding, not only the standard NetSuite dimensions (GL account, location, department, class, project). The buyer explicitly calls out 'several custom dimensions' as part of their standard coding workflow. A vendor whose data model is limited to NetSuite's out-of-the-box fields cannot serve this buyer; the integration layer must read the buyer's NetSuite custom segment configuration and expose those segments as codeable targets in the AP automation UI and AI coding engine.

For a buyer with dozens of coding fields including GL account, location, department, class, project, and several custom dimensions, Stampli's NetSuite integration reads the buyer's live NetSuite schema rather than a fixed list of standard fields. Its real-time API connection automatically mirrors both custom transaction body fields and custom line-level fields into the Stampli coding UI, with no re-engineering required when the buyer adds new custom segments in NetSuite. …

Limitations: Billy the Bot's auto-suggestion confidence on any given custom segment is a function of coding history volume for that segment: newly created or rarely used custom segments will require more human corrections before the AI stabilizes its suggestions, which is a standard ML learning-curve constraint rather than a struct …

Requirement evaluated: Support extraction from non-standard invoice formats common in the tech industry: cloud usage reports, contractor time sheets, conference sponsorship invoices, and developer tool subscription notices.

For a tech-sector buyer whose invoice mix includes SaaS subscriptions, contractor invoices, conference sponsorships, and cloud infrastructure bills, Medius Capture ingests documents arriving by paper, email, EDI, and e-invoice, then applies a proprietary multi-stage AI pipeline, including Siamese CNNs for document classification and SmartFlow, a convolutional neural network trained on 2.4 billion+ invoice field data points drawn from across Medius's customer base, to extract and code data without requiring explicit template configuration per vendor. …

Limitations: Cloud usage reports from providers like AWS, GCP, and Azure present the hardest extraction challenge in this buyer's format mix: they contain dozens to hundreds of line-level SKU rows with usage quantities, rates, and credits in complex tabular layouts that differ structurally from traditional invoice PDFs, and Medius …

Requirement evaluated: Support extraction from non-standard invoice formats common in the tech industry: cloud usage reports, contractor time sheets, conference sponsorship invoices, and developer tool subscription notices.

A tech company sending cloud usage reports (AWS, GCP, Azure), contractor timesheets, conference sponsorship invoices, and developer tool subscription notices needs its AP platform to extract structured data from those inherently non-standard layouts. Stampli's Billy AI handles this at stage 1 of the pre-processing journey (legitimacy and data capture): Billy automatically extracts key invoice data using OCR and AI trained on a large cross-customer dataset, and its capture layer is described as handling 'various invoice formats' including multi-page and multi-invoice documents without requiring up-front template training. …

Limitations: The most material ceiling for this buyer is format intake: Stampli's email ingestion channel accepts only PDF (and, per the product page, DOCX, PNG, or JPG) attachments, meaning cloud usage reports delivered as CSV, HTML, or inline email body text fall outside the automated capture path and require manual conversion be …

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: Virtual card program with rebate revenue; we want to shift 30%+ of spend to virtual card

For a $120M multi-location services company looking to shift 30%+ of spend to virtual card, Stampli offers two complementary native mechanisms within Stampli Direct Pay. The first is Stampli Card: when an invoice is approved, the AP team can pay the vendor using a single-use virtual card generated per transaction; the vendor receives card details via the Stampli Vendor Portal or a secure link and processes it to collect funds. Vendor Managers can invite vendors to accept card payments in bulk from the Vendor Management screen. …

Limitations: The rebate ceiling is documented at 'up to 1%' with no publicly enumerated volume tiers, so the buyer cannot negotiate a higher rate through platform volume alone; actual rebate earned will also depend on whether vendors are enrolled in the Paymode network (for E-Payments) …

Requirement evaluated: The vendor must provide demonstrable evidence, through references or case studies from distribution or similarly PO-heavy industries, that their tool has closed a receiving gap comparable to the one described: organizations where employees were not recording receipts and three-way match was nonfunctional, and where the tool's proactive receipt confirmation workflow measurably increased receipt capture rates. This is a vendor evaluation criterion, not a configuration requirement, and is specifically scoped to operational procure-to-pay, excluding strategic sourcing, RFQ, or supplier onboarding capabilities.

The buyer's scenario is a distribution company where warehouse and operations staff are not entering goods receipts in NetSuite, leaving three-way match nonfunctional. Medius does operate at the invoice-processing stage and surfaces missing goods receipts as a deviation type: a documented product feature called 'Show goods receipt deviation first' routes invoices with missing GRs to the responsible user before price deviations are handled, prioritizing GR resolution in the AP workflow (Medius Customer Success Top Tips, success.medius.com). …

Limitations: No published Medius case study explicitly documents a before/after measurement of goods receipt capture rates in an organization where employees were not recording receipts, nor does Medius publish evidence of a proactive outbound notification workflow that prompts warehouse or receiving employees to confirm delivery w …

Requirement evaluated: The vendor must provide demonstrable evidence, through references or case studies from distribution or similarly PO-heavy industries, that their tool has closed a receiving gap comparable to the one described: organizations where employees were not recording receipts and three-way match was nonfunctional, and where the tool's proactive receipt confirmation workflow measurably increased receipt capture rates. This is a vendor evaluation criterion, not a configuration requirement, and is specifically scoped to operational procure-to-pay, excluding strategic sourcing, RFQ, or supplier onboarding capabilities.

This buyer needs documented proof that Stampli has already solved the specific problem of employees not recording goods receipts in distribution or comparably PO-heavy industries, with measurable receipt capture rate improvements as evidence. Stampli's product documentation confirms a relevant mechanism: <cite index="dfe7f444-80d5-46eb-8b6e-53926559ed94">Stampli AI connects POs, receipts, and invoices in real time, notifies teams when items are received or missing, and keeps ERP records in sync.</cite> The PO support page further documents that users can <cite index="11-2,11-3">resolve discrepancies with tracked questions and responses and confirm receipt directly on the invoice processing p …

Limitations: Stampli's public case study library does not surface a distribution-industry or PO-heavy reference where the documented starting condition was nonfunctional three-way match due to employees not recording receipts and the documented outcome was a measurably higher receipt capture rate. …

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 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 company on Oracle NetSuite preparing for IPO-level SOX scrutiny, Stampli delivers most of the underlying control evidence but stops short of assembling it into a single, pre-built, on-demand compliance package per invoice. The core audit trail mechanism is strong: <cite index="25-1">every change, comment, approval, and document is preserved in a complete, immutable audit trail with role-based access controls and visibility, making it easier to maintain oversight and respond to audits.</cite> Stampli explicitly states that <cite index="33-2">the audit trail cannot be modified or deleted, ensuring data integrity for compliance and audit purposes,</cite> satisfying the immutabil …

Limitations: The material gap for an IPO-readiness buyer is the absence of a documented, pre-built 'control evidence package' report that bundles all five required elements (immutable event log, SoD record, authority-limit-at-time-of-approval, chain of custody, duplicate check result) …

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 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 Oracle NetSuite preparing for SOX audit, Stampli provides configurable role-based access controls at both the user and role levels, enforcing which invoices, GL accounts, cost centers, and approval queues each user can see and act on. <cite index="26-3,26-4">Stampli offers granular permission settings that let you control exactly who can see specific information; permissions can be set at both the user and role levels, allowing you to share or withhold information for all or a specified subset of invoices.</cite> <cite index="24-5">Standard and customizable user permissions and roles are used to deploy internal controls and deter fraud.</cite> <cite index="40-1">Ev …

Limitations: The documented gap is the meta-audit layer: Stampli's public documentation and help center confirm immutable invoice-action audit trails and SOC 2 Type 2 certification, but provide no evidence that administrator-level permission changes (role reassignments, permission escalations, user access modifications) …

Requirement evaluated: Perform automated matching of purchase order, goods receipt (GRN), and invoice. Support configurable tolerance thresholds by commodity type, vendor, plant, or dollar amount.

For a manufacturing company running multi-commodity procurement through NetSuite, Medius's 'Connect' and 'Match' workflow stages execute true 3-way matching: the system links extracted invoice lines to PO lines and Goods Receipt (GRN) data synced from NetSuite, then identifies deviations before routing. Invoices with all deviations within tolerance bypass the 'Analyze' queue and move directly to touchless approval; out-of-tolerance exceptions route to a designated reviewer for resolution. Tolerance configuration is supported in two forms: 'connection tolerances' (which determine whether Medius auto-links an invoice line to a PO/GRN line when amounts are not an exact match) …

Limitations: The documented tolerance architecture segments rules by supplier and by company, but not by commodity category or plant/receiving location. This is a material gap for the buyer's manufacturing scenario, where the same supplier may ship raw steel (requiring a +/-2% tolerance), precision-machined components (requiring ex …

Requirement evaluated: Perform automated matching of purchase order, goods receipt (GRN), and invoice. Support configurable tolerance thresholds by commodity type, vendor, plant, or dollar amount.

For a manufacturer running NetSuite with diverse commodity categories requiring different tolerance bands, Stampli delivers true 3-way matching at the item receipt level: it ingests live PO and GRN data from NetSuite on a continuous sync cycle and compares invoice quantities, prices, and amounts against both documents before any approval action is taken. …

Limitations: The buyer's requirement for distinct tolerance profiles by commodity category (e.g., exact match for hazardous chemicals and precision parts, +/-2% for raw steel by weight, +/-5% for MRO) …

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: 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 work confirmation comes from project managers and superintendents rather than a receiving dock, Stampli's 3-way matching capability covers the mechanics of PO-receipt-invoice comparison but draws its receipt data from ERP-sourced records rather than from a field-personnel contribution step inside Stampli's pre-processing workflow. Stampli's AI 'connects POs, receipts, and invoices in real time' and performs both 2- and 3-way matching with configurable tolerance rules, partial-receipt processing, and line-level exception flagging. …

Limitations: The material ceiling for this buyer is that Stampli's 3-way match depends on a receipt record existing in NetSuite before matching runs; in a construction environment where no dock scan generates that record, a PM or superintendent would need to first enter an item receipt in NetSuite for the third leg of the match to …

Requirement evaluated: The system must support role-based cross-unit visibility grants, so that designated users (central accounting staff, controllers, or payment administrators) can view and act on invoices across all 9 productions simultaneously, while production-level AP users remain restricted to their own unit. This is the mechanism that makes centralized payment runs possible without granting every AP clerk access to every production's invoice queue.

For a media company running 9 productions as profit centers inside one Sage Intacct legal entity, Medius provides a layered RBAC architecture that enforces intra-entity data isolation without creating separate books. The mechanism operates across three documented layers. First, <cite index="34-1,34-5,34-6">the role form's 'Coding rights' tab restricts which dimension values a user can access when coding invoices; an administrator enables dimension-level filtering in System Configuration, then assigns each role only the profit center codes belonging to its production, so a production-A AP clerk cannot select or see production-B cost centers.</cite> Second, <cite index="27-1,27-2">the role for …

Limitations: The documentation confirms dimension-scoped coding rights and search access, but does not explicitly state that the live work queue inbox filters invoice list visibility by dimension value independent of workflow addressee assignment: if invoices are routed to a shared queue rather than a production-specific queue, an …

Requirement evaluated: The system must support role-based cross-unit visibility grants, so that designated users (central accounting staff, controllers, or payment administrators) can view and act on invoices across all 9 productions simultaneously, while production-level AP users remain restricted to their own unit. This is the mechanism that makes centralized payment runs possible without granting every AP clerk access to every production's invoice queue.

For a media production company running 9 profit centers inside one Sage Intacct legal entity, Stampli's AP Assignments feature is the primary mechanism that delivers production-level isolation with simultaneous cross-unit visibility for central staff. Assignments are configurable operational buckets: each production gets its own assignment, and each assignment can receive invoices automatically via a dedicated email address with pre-coded invoice fields. …

Limitations: Stampli's documentation confirms assignment-level access grants but does not detail whether the cross-assignment visibility grant for central users extends to a single consolidated payment queue with line-level filtering by production; buyers should verify in a demo that the payment authorization screen allows a paymen …

Requirement evaluated: Track partial shipments against PO lines, match invoices against received quantities, and maintain open PO balances for backordered items. Prevent overpayment by blocking payment for quantities not yet received.

For a manufacturer tracking partial shipments across multiple delivery events on a single PO line, Medius routes the incoming invoice through its order-matching engine, which compares extracted invoice lines against delivery lines (goods receipts) synced from NetSuite via a certified SuiteApp connector. When an invoice arrives before all ordered quantities have been received, the system automatically places it in a dedicated 'Await Delivery' queue, holding it from payment progression until the missing GRN data is available: 'If an order invoice that has been imported...is found to be partial without deliveries (all item rows to which the invoice relates are not delivered), the invoice can be …

Limitations: The quality of partial receipt tracking depends directly on the timeliness of item receipt sync from NetSuite into Medius; the Medius documentation itself notes that invoices may arrive in the system before deliveries are transferred from the purchasing system, meaning a lag in NetSuite GRN posting creates a window whe …

Requirement evaluated: Track partial shipments against PO lines, match invoices against received quantities, and maintain open PO balances for backordered items. Prevent overpayment by blocking payment for quantities not yet received.

For a manufacturing buyer dealing with raw material and component partial shipments, Stampli addresses this requirement primarily through its live NetSuite data sync layer. Item receipt records created in NetSuite flow into Stampli every two hours (or on-demand), and Billy performs 3-way matching against actual received quantities rather than PO quantities alone. Stampli's validation algorithm flags discrepancies where invoiced quantities exceed confirmed received quantities, holds those invoices in an exceptions queue before payment, and explicitly supports one-PO-to-many-invoice and many-PO-to-one-invoice scenarios including partial shipments and cross-department orders. …

Limitations: The payment hold mechanism depends entirely on NetSuite item receipts being finalized before Stampli's next sync cycle (up to 2-hour lag), meaning invoices arriving before the GRN is entered in NetSuite may clear matching without a valid receipt in place. …

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

For a two-entity Sage Intacct environment growing to three, Stampli operates within a single platform account that mirrors Intacct's entity hierarchy directly. At invoice ingestion, entities are assigned automatically: AP staff email invoices to a dedicated alias that encodes the Intacct entity key (e.g., companyID+Entity-KEY@mystampli.com), and Stampli pre-populates the working entity on the invoice record before any human touches it (Stampli Help Center, 'Email Address for Auto Assigning Invoices to Entities'). …

Limitations: The multi-location payment feature (Direct Pay) must be enabled at the account level for entity-isolated payment runs; buyers should confirm this is included in their contracted tier before go-live. …

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: Data encryption at rest and in transit

For a multi-location services company moving from manual email-and-spreadsheet AP to an automated platform, data protection must cover every touchpoint: invoice ingestion, in-platform processing, ERP sync to Sage Intacct, and payment execution. Stampli addresses all of these on its published Security Policy and Practices page. <cite index="1-4">All data sent to or from Stampli is encrypted in transit using 256-bit encryption.</cite> <cite index="1-1,1-2">API and application endpoints are TLS/SSL only, using only strong cipher suites.</cite> <cite index="1-3">Data at rest is encrypted using an industry-standard AES-256 encryption algorithm.</cite> For the highest-sensitivity fields your AP te …

Limitations: Stampli's security policy page does not specify the minimum TLS version enforced (e.g., TLS 1.2 vs. 1.3), nor does it detail key management practices such as rotation schedules or HSM usage; buyers with formal information security policies requiring those specifics should request Stampli's full security whitepaper or d …

Requirement evaluated: Budget must be checked and enforced at the moment a purchase request is submitted, before any PO is issued or card charge is authorized, using budget data sourced from NetSuite. Requests that would exceed available budget must be blocked or escalated, not merely flagged after approval, so that the current pattern of unchecked spend is structurally prevented.

This buyer's core problem is structurally unchecked spend: no one confirms receipt, and budget is never enforced before a PO is issued. Medius Procurement addresses the enforcement side directly via a configurable mode on its budget control feature: <cite index="6-1,6-2">"Enforce a hard stop at checkout, or allow the spend to continue with additional approval through the workflow. …

Limitations: The buyer requires budget data "sourced from NetSuite," but the documented integration architecture flows primarily from Medius to NetSuite (POs written back for commitment tracking), not from NetSuite budget records into Medius's enforcement engine; if Medius operates an internal budget ledger rather than querying Net …

Requirement evaluated: Budget must be checked and enforced at the moment a purchase request is submitted, before any PO is issued or card charge is authorized, using budget data sourced from NetSuite. Requests that would exceed available budget must be blocked or escalated, not merely flagged after approval, so that the current pattern of unchecked spend is structurally prevented.

This distribution company's core problem is unchecked spend commitments that bypass budget before a PO is issued, so the relevant question is whether Stampli enforces budget at the moment a purchase request is submitted, using data drawn from NetSuite. Stampli has a dedicated Budget Management module that integrates directly into the procurement request workflow: <cite index="5-4">Stampli Procurement ensures every request begins with budget validation, GL context, and clear approval ownership before money is committed</cite>, and <cite index="13-7">Budget Management provides comprehensive real-time tracking that compares budgeted amounts against actual and committed spending</cite>. …

Limitations: The material ceiling for this buyer is that Stampli's Budget Management module maintains its own budget ledger, and no source confirms a live two-way sync with NetSuite's native budget module; if the distribution company's budget-of-record lives in NetSuite, the two could drift, partially recreating the visibility gap …

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: 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 14-subsidiary OneWorld environment running SuiteTax, Stampli's NetSuite connector operates within the AP pre-processing layer (stages 1 through 5 of the pre-processing journey) and writes approved invoice records back to NetSuite via a token-based, real-time API integration that carries SuiteTax data in both directions. Stampli's product page states that it 'reads, writes, and calculates every tax scenario' and specifically claims 'SuiteTax and Legacy Tax compatibility,' supporting transitions between the two engines without downtime. …

Limitations: The buyer requires explicit confirmation that Stampli uses SuiteTax API endpoints directly rather than an abstraction layer, and a documented list of any known field gaps in the connector; neither exists in any publicly available Stampli source found, which is a material ceiling for a SOX-regulated 14-subsidiary enviro …