Medius vs Ramp

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 running 12,000 invoices a month across dozens of NetSuite dimensions, Ramp's AI coding operates through its AP Agent and Accounting Agent (available on Ramp Plus). The documented learning mechanism has two layers. First, a per-vendor pattern engine: the auto-coding agent is configured 'on a per vendor per accounting field basis' and builds mappings between invoice PDF fields and accounting codes, showing prior mappings and updating them as invoices accumulate from each vendor (Ramp Bill Pay OCR help article). …

Limitations: Ramp does not publish a per-customer retraining pipeline, a documented model isolation mechanism, or a measurable accuracy lift curve that this buyer could benchmark against their own 12,000-invoice history: the 85% auto-coding claim is an aggregate figure across all Ramp customers, not a per-customer trajectory. …

Requirement evaluated: Extract and validate tax identification numbers, remittance addresses, and payment terms from invoice headers, flagging mismatches against the vendor master record.

For a healthcare AP team processing invoices from distributors like McKesson or Cardinal Health, Medius operates at the legitimacy and vendor-identity stage of the pre-processing journey. At invoice ingestion, Medius Capture extracts both header and line-level data and matches it 'against the proper corresponding master data,' routing invoices that cannot be resolved to a unique vendor in the vendor register to a 'New vendor' exception queue. …

Limitations: TIN validation is used as a vendor identification mechanism at ingestion, not a post-identification cross-check that explicitly flags when the TIN printed on the invoice differs from the TIN in the matched vendor record; healthcare organizations handling pharmaceutical distributors with complex tax structures may need …

Requirement evaluated: Extract and validate tax identification numbers, remittance addresses, and payment terms from invoice headers, flagging mismatches against the vendor master record.

For a healthcare AP team receiving invoices from distributors like McKesson or Cardinal Health, Ramp operates at the vendor profile level rather than performing a true invoice-header-vs.-vendor-master comparison at capture time. On the TIN dimension: Ramp stores vendor tax details in each vendor profile and automatically verifies the stored TIN against IRS (US) or VIES (EU) records once tax information is entered, but this is a vendor-master-level verification, not a check that compares a TIN extracted from an incoming invoice against the stored vendor record. …

Limitations: The specific pre-payment control this buyer requires, an automated flag when an extracted invoice TIN, remit-to address, or payment term deviates from the vendor master record, is not documented in Ramp's Bill Pay or Vendor Management help center for any of the three fields. …

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 coding dozens of fields per invoice in NetSuite, including GL account, location, department, class, project, tax fields, and several custom dimensions, Ramp's certified SuiteApp integration directly reads the buyer's NetSuite schema and imports all of those fields into the Ramp coding UI, including custom segments. Ramp's official NetSuite overview documentation states explicitly that 'Ramp imports all fields, including custom ones, from NetSuite to ensure comprehensive transaction coding,' and that for segments to be coded in Ramp they must simply be visible on the Credit Card, Bill, and/or Bill Payment Forms in NetSuite. Custom fields are supported at both the header (body) …

Limitations: Custom fields must be active and visible on the relevant NetSuite transaction forms (Credit Card, Bill, Bill Payment) for Ramp to detect and sync them; fields that are inactive or not surfaced on those forms will not appear in Ramp's coding UI. …

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

For a $250M tech company running NetSuite as its ERP of record, Medius delivers this requirement through a dedicated, cloud-managed NetSuite connector that is part of Medius's own product suite. Medius is a fully approved NetSuite vendor and holds 'Built for NetSuite' certification for its AP Automation and Pay SuiteApps, meaning the integration is built on Oracle's SuiteCloud platform and maintained by Medius without custom development or third-party middleware. …

Limitations: Medius operates as an external platform that syncs into NetSuite rather than processing entirely inside the NetSuite UI, so finance staff will work across two interfaces during AP processing; this is by design for the deeper automation Medius provides, but represents a change management consideration for a team current …

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

For a $250M technology company replacing a manual email-and-Slack PO process that currently dumps invoices into NetSuite by hand, Ramp's Bill Pay module handles the full push natively. Invoices are ingested via OCR into Bill Pay, matched against POs (Ramp supports PO syncing with NetSuite, Sage Intacct, and QuickBooks), routed through configurable approval workflows, and then synced automatically to NetSuite as Vendor Bills at Transactions → Payables → Enter Bills — not as journal entries — so they land directly in the AP payment queue. …

Limitations: Some advanced NetSuite features (multi-currency FX handling, SuiteTax line-level detail, and certain amortization workflows) are noted as available to Ramp Plus customers, so the buyer should confirm their plan tier covers the full NetSuite feature set they need. …

Requirement evaluated: Simple receipt confirmation workflow: designated receiver confirms delivery with quantity, condition, and date

For a $250M tech company deploying Medius against NetSuite, goods receipt data for three-way matching is architected to flow from the ERP rather than from a native Medius receiver screen. Medius's own documentation on invoice matching states that 'upon delivery of the goods or services, the buyer often needs to register a goods receipt in the ERP or procurement system,' and that enabling automated 3-way matching requires GR data to 'synchronize seamlessly between the ERP system and the AP automation solution.' When a GR is missing, Medius's 'Show goods receipt deviation first' workflow can route the invoice to a responsible user before handling price deviations, but this is a deviation-manag …

Limitations: In a Medius AP Automation plus NetSuite deployment (the most common configuration), the receiving confirmation step happens in NetSuite via Item Receipt, not inside Medius: a buyer's designated warehouse receiver would need NetSuite access rather than a Medius-native workflow. …

Requirement evaluated: Simple receipt confirmation workflow: designated receiver confirms delivery with quantity, condition, and date

For a $250M technology company running NetSuite and preparing for IPO, Ramp Procurement does offer a native item receipt workflow tied to purchase orders. Once an admin enables 3-way match on a Spend Program, a 'Receive' button appears on approved POs; clicking it generates an item receipt that updates the PO's receiving status (Not Received, Partially Received, or Fully Received). For inventory line items coded with NetSuite or QBO inventory item fields, the receiver can edit the quantity received per line, enabling partial receipt support. …

Limitations: The absence of a role-isolated 'designated receiver' (the original requester can confirm their own delivery, which conflicts with SOX-adjacent segregation-of-duties requirements) and the inability to sync Ramp-created item receipts to NetSuite are the two material gaps for this buyer. …

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: Complete audit trail meeting SOX-adjacent control requirements for our IPO preparation

For a $250M company preparing for an IPO, Ramp offers a multi-layered audit infrastructure that covers most SOX-adjacent controls but has documented gaps in completeness. The central mechanism is a dedicated Audit Log in company settings: <cite index="10-9,10-10,10-11">it is described as "a consolidated place to track all actions made by Ramp and fellow teammates across Ramp," explicitly framed to help companies "Stay SOX Compliant" and "keep track of key changes such as changes made to bank account information, vendor information, etc."</cite> <cite index="21-16,21-17,21-18">The log covers a canonical catalog of approximately 200 tracked actions (e.g., "Sign in," "Request revision," "Reimbu …

Limitations: <cite index="30-13,30-14">The audit log has a documented coverage gap: "not all admin actions are currently tracked in the audit log, including some integration setup events and older administrative behaviors," and Ramp instructs users to assume untracked actions simply are not captured.</cite> For IPO preparation, thi …

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: Batch approval capability for recurring invoices from the same vendor (e.g., monthly telecom bills across 6 locations)

For a multi-location services company processing recurring telecom bills from the same vendor across 6 sites, Ramp's Bill Pay module supports batch approval through two complementary mechanisms. First, the 'For approval' queue supports a checkbox multi-select UI: <cite index="1-2">approvers can approve multiple bills at once by selecting the check box to the left of the bills on the Bill Pay > For approval tab</cite>, enabling a single approver action to clear all pending telecom bills in one step rather than opening each individually. …

Limitations: <cite index="23-11,23-12,23-13">Only bills formally set up as a recurring series appear in the Recurring Bills panel; Ramp does not automatically detect recurring payment patterns from individually created bills, so telecom invoices arriving as separate PDFs across 6 locations will appear as individual bills unless del …

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

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

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

Requirement evaluated: Real-time AP dashboard: invoice aging, approval queue depth, processing cycle time, spend by vendor/category/entity

For a 3-person AP team at a $120M services company processing 1,800 invoices per month across 2 Sage Intacct entities, Ramp delivers AP visibility through several separate surfaces rather than a single consolidated dashboard. Invoice aging is available as a downloadable Summary or Detailed AP Aging Report from the Bill Pay tab: <cite index="1-5,1-6,1-7,1-8">Ramp generates two AP aging reports, a Summary report that groups rows by vendor and invoice due date, and a Detailed report at the invoice level; both bucket total amounts owed by age based on due date.</cite> Multi-entity support is present: <cite index="1-11">multi-entity customers can choose to download a report that includes bills ac …

Limitations: The AP aging report is a downloadable CSV rather than a live refreshing dashboard panel, which means your AP team will not see aging bucket totals update automatically between exports. End-to-end processing cycle time (invoice receipt to payment) …

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: Automatic combination of multiple approved invoices to the same vendor into a single payment, with the matching criteria used for combination clearly stated

For a $120M services company running bi-weekly check runs and monthly ACH batches across 1,800 invoices per month, Ramp's Batch Payments feature in Ramp Bill Pay directly addresses this requirement. Once auto-batching is enabled in Bill Pay settings, Ramp automatically groups approved bills into a single combined payment when they share three criteria: the same vendor, the same payment date, and the same payment details (method, timelines, and source/destination accounts). Auto-batching is on by default for all vendors, with an optional vendor-level filter in settings to include or exclude specific vendors from batching. …

Limitations: Card payments cannot be included in a batch, so any vendor paid via Ramp virtual card or existing card will receive a separate per-bill transaction rather than a consolidated payment. …

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: Handle multi-line PO matching where individual lines are allocated to different production jobs, work orders, cost centers, or projects. Match invoice lines to the correct PO line and allocation, even when the vendor invoice groups items differently than the PO.

A manufacturing AP team handling multi-line, multi-allocation invoices would use Ramp's Bill Pay PO matching flow: once an invoice is uploaded, Ramp's OCR scans for the PO number and suggests a match; the AP user then clicks 'Match a PO line item' to pull per-line coding (GL account, dimensions, project task, custom fields) from the corresponding PO line into the bill. Per the Syncing Ramp Purchase Orders into accounting help article, coding is inherited line-by-line from the PO, and per the Business Central PO support article, each synced PO line carries description, unit cost, quantity, project task, and custom dimensions. …

Limitations: The buyer's ERP is Dynamics 365, and Ramp's PO import and 3-way match feature is documented only for NetSuite, Sage Intacct, and QuickBooks Online; the D365 Finance and Operations integration does not document equivalent PO-level matching capability, creating a hard ceiling for this buyer's stack. …

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: Integration setup assistance included in implementation; not a separate SOW or additional cost

For a $120M services company running 2 Sage Intacct entities, Ramp's integration setup is designed as a guided, self-serve process rather than a vendor-led professional services engagement. The buyer connects Ramp to Sage Intacct from within the Bill Pay tab by enabling Web Services in Intacct, creating a dedicated Ramp web services user, and entering credentials directly in the Ramp UI. …

Limitations: The buyer cannot rely on a publicly documented commitment that Ramp will provide integration setup assistance as a standard included deliverable: Ramp's own implementation guide explicitly defers 'Ramp's specific involvement or resource commitments during implementation' to individual account team conversations. …

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

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

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

Requirement evaluated: Vendor communication log: track every inquiry and response to eliminate the 6 hours/week our team spends on status calls

For a 3-person AP team currently fielding 6 hours per week of vendor status calls, Ramp addresses this through three interlocking mechanisms in Ramp Bill Pay. First, <cite index="1-3,1-4,1-5,1-6">Ramp's Vendor Portal allows vendors who receive bill payments to easily manage and track those payments; vendors receive an email notification about an incoming payment, create a portal account, and can then view pending bill payments and track their progress.</cite> <cite index="1-13">When tracking payments, vendors see different bill statuses that indicate where the payment is in the customer's process, from 'Invoice received' through payment delivery.</cite> Second, <cite index="12-3,12-4,12-5,12 …

Limitations: Vendor portal enrollment is optional: <cite index="2-17">Ramp Vendor Portal accounts are entirely optional for vendors</cite>, meaning utilities, one-off subcontractors, or non-tech-savvy suppliers in this buyer's 1,800-invoice monthly volume may not register, leaving proactive email notifications as the only call-defl …

Requirement evaluated: The solution must maintain a complete, timestamped audit trail for every invoice action, including capture, coding change, approval, rejection, and payment, stored in a way that can be exported and cross-referenced against the corresponding NetSuite transaction record, supporting the internal audit and compliance requirements common in entertainment businesses with investor or studio reporting obligations.

For an entertainment business running NetSuite with investor and studio reporting obligations, Medius maintains a continuous, timestamped audit record across the full invoice lifecycle. Starting at capture, every invoice is automatically archived and its entire processing history is logged: AI extraction decisions, coding changes, routing steps, approvals, rejections, exceptions flagged by fraud detection, and payment execution are all captured as system events. As Medius documents: 'auditors can quickly access timestamped records of every action — from submission to approval to payment' (Medius e-invoicing blog, May 2025). …

Limitations: Publicly available documentation describes the export path primarily through invoice search gadget exports to Excel and hyperlinked report fields, rather than a documented single-click structured export that pairs every raw Medius event record side-by-side with the corresponding NetSuite internal transaction ID in one …

Requirement evaluated: Every soft-stop override must be captured in a persistent, tamper-evident audit trail that records the requester's identity, the budget dimension breached, the overage amount at time of override, and any approver who authorized the exception. The buyer specifically cited override audit trails as a requirement, and this log must be queryable for compliance review without manual reconstruction.

For a buyer running procurement requisitions on Ramp against Workday Adaptive budgets, Ramp does provide a centralized Audit Log positioned for SOX compliance that allows filtering by actor name, date range, and keywords to investigate actions. When a Bill Pay submission policy is overridden, the requester must supply a reason and that reason is recorded in the audit log alongside the bill record. Similarly, Policy Agent overrides for expense reviews are noted to appear in the audit log. …

Limitations: Ramp's audit log captures authentication events, administrative changes, and policy override reasons as free-text notes on individual records, but no documentation confirms that the specific budget dimension breached and the overage amount at override time are stored as structured, locked event fields queryable across …

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

For a multi-location services company forwarding emailed invoices and uploading scanned mail, Ramp Bill Pay's OCR engine automatically ingests documents via an AP forwarding email address or direct drag-and-drop upload, then parses and pre-fills a draft bill within roughly 30 to 60 seconds. At the base OCR tier, the system extracts vendor name, invoice number, due date, payment account details, and line items. The Smart OCR tier (available on Ramp Plus) …

Limitations: Payment terms are not extracted from the invoice as a structured term string (e.g., '2/10 Net 30' with an early-pay discount trigger); instead, Ramp captures the due date via OCR and stores net day terms on the vendor profile, so early-payment discount terms printed on the invoice face would not be parsed into actionab …

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: Support evaluated receipt settlement (ERS) where payment is generated automatically upon goods receipt confirmation without requiring a vendor invoice, for suppliers enrolled in the program.

This manufacturing buyer requires ERS: payment generated automatically upon goods receipt confirmation, with no vendor invoice submitted at all, for enrolled suppliers. Ramp's entire AP architecture is invoice-centric. Every documented payment pathway begins with a vendor-submitted bill: <cite index="13-1">with automated bill pay, you upload a vendor invoice and the software generates a bill with line items and payment details.</cite> Even Ramp's most advanced 3-way matching workflow, including its Dynamics integration, explicitly requires an invoice document as the initiating input. …

Limitations: Ramp has no supplier enrollment program, no self-billing module, and no GRN-triggered disbursement workflow. This is a structural gap, not a configuration shortfall: Ramp's payment engine cannot initiate a disbursement without a vendor-submitted invoice as its input, which is the defining characteristic that ERS is des …

Requirement evaluated: The solution must support project-level or production-level cost coding at the invoice line level, allowing each line to be allocated to a specific NetSuite project, job, or custom segment that represents a production, so that below-the-line and above-the-line costs in entertainment productions can be tracked and reported separately without manual GL journal entries.

For an entertainment business running NetSuite, Medius handles production-level cost coding at the invoice line level through its dimension coding framework. During onboarding, Medius pulls the full coding schema directly from NetSuite: as the official May 2025 product definition states, 'the structure of coding dimensions—including both standard and custom dimensions—is determined during the data gathering phase... Medius imports all coding dimensions directly from Oracle NetSuite.' This means any NetSuite dimension representing a production—whether a standard Class/Department or a custom segment configured to track above-the-line vs. …

Limitations: The May 2025 NetSuite product definition PDF excerpt is slightly truncated at the passage describing custom dimension activation, so it is not explicitly confirmed whether NetSuite SuiteGL-based Custom Segments (as distinct from standard custom fields) …

Requirement evaluated: The tool must function purely as a procurement enforcer and not require the buyer to rebuild, maintain, or duplicate budget structures inside the procurement platform itself. Budgets are authored exclusively in Workday Adaptive Planning, and the vendor's value proposition must be enforcement fidelity against externally composed budgets, not a competing budget-authoring workflow that would create a second source of truth.

For a buyer on Sage Intacct with budgets authored in Workday Adaptive Planning, Ramp's 'Budgets' module accepts externally authored budget values via CSV upload, but only after an administrator first defines the dimension schema natively inside Ramp. As documented in Ramp's own setup guide, the workflow is: define dimensions inside Ramp (e.g., accounting department, location), download a Ramp-generated template, populate it with budget values from Adaptive, and upload it back. …

Limitations: Ramp requires the buyer to re-create the budget dimension structure inside Ramp before CSV values from Adaptive Planning can be ingested, making it a partial second source of truth rather than a pure enforcer of externally authored budgets. …