Medius vs Ottimate

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 monthly recurring telecom bills across 6 locations, Medius provides two complementary mechanisms. First, the Bulk Operation feature in the approver inbox allows a user to select multiple invoices that share the same type and workflow step, activating a 'Bulk Operation' button that processes all selected invoices together, a pattern Medius explicitly surfaces for Final Approval use cases rather than one-at-a-time opening. Second, and more directly targeted at recurring non-PO vendors, Medius released a 'Pre-Approved Invoices' feature (R118) …

Limitations: The Bulk Operation feature requires invoices to be at the same workflow step simultaneously, so invoices that arrive or are coded at different times across the 6 locations may not naturally converge for a single bulk action without deliberate queue management. …

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 routing monthly telecom bills from the same vendor across 6 offices, Ottimate offers two relevant mechanisms, neither of which is a true reviewer-facing batch approval action. First, Ottimate's Advanced Approvals system supports configurable 'approval policies' keyed to vendor, amount, GL code, and other invoice attributes: <cite index="24-1,24-2">there are multiple conditions within approval policies that keep an invoice in Pending Approval until the proper user approves them, including a vendor condition that specifies one vendor so all invoices from that vendor route consistently</cite>. …

Limitations: There is no documented bulk-select-and-approve action in Ottimate's queue view: an approver handling 6 monthly telecom bills must still open and approve each invoice individually, or configure auto-approve via Trust Score, which bypasses human review entirely rather than enabling a structured batch sign-off. …

Requirement evaluated: Early payment discount detection: auto-flag invoices with discount terms (2/10 net 30) and alert AP when deadline approaches

For a $120M multi-location services company currently missing discount windows entirely due to manual processing, Medius does surface cash discount information at the invoice level. <cite index="6-1,6-2,6-5,6-6,6-8">When an invoice is opened and the vendor offers a cash discount, the discount is displayed on the far right of the invoice header, showing the current discount percentage and the discounted amount relevant if the invoice is paid today.</cite> In the payments view, <cite index="10-2">due dates can be identified and sorted specifically to "take advantage of early payment discounts."</cite> Customer evidence confirms the platform's speed enables discount capture in practice: <cite i …

Limitations: The buyer's requirement is for proactive, automated flagging plus a deadline-proximity alert before the 10-day discount window closes. Medius documents cash discount display at the invoice header and due-date sorting in the payments view, but provides no evidence of a dedicated alert engine that detects discount terms …

Requirement evaluated: Early payment discount detection: auto-flag invoices with discount terms (2/10 net 30) and alert AP when deadline approaches

For a $120M multi-location services company processing invoices from email and physical mail, Ottimate's approach to early payment discounts operates primarily at the payment scheduling layer rather than at the invoice capture and alerting layer. <cite index='2-3'>The platform's product documentation states that "the system can highlight opportunities for early payment discounts and, conversely, help you avoid late payment penalties by setting reminders or even automating payments."</cite> At the VendorPay payment module, <cite index='97b49a47-1357-4f00-ba29-c2a8a3c73ff5'>Ottimate positions its value as helping teams "mitigate invoice risk, reduce overpayment, and optimize payment timing to …

Limitations: The buyer's requirement calls for automated flagging at the moment of invoice ingestion and deadline-proximity alerts before the discount window closes; Ottimate's documented capability appears to address payment timing optimization at the scheduling stage, meaning AP staff would still need to identify discount-eligibl …

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

For a 3-person AP team at a $120M services company needing to push AP reports to a Controller and CFO without manual intervention, Medius delivers through three layered mechanisms inside its reporting stack. First, the built-in Reports module supports configurable, saveable report templates across multiple AP data sources, with in-report grouping, filtering, totaling, and drill-down to underlying invoice documents; and critically, it includes native report scheduling so reports run and are delivered on a defined cadence without AP staff involvement. …

Limitations: Scheduled delivery format is documented as CSV, XML, or PDF; native .xlsx workbook delivery is not confirmed in available sources, though CSV is functionally equivalent for Excel-based analysis. The OData feed requires the recipient to initiate a data pull (Excel Power Query refresh) …

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

For a $120M services company whose Controller and CFO need regular AP reporting delivered to them without logging in, Ottimate provides two relevant mechanisms but covers only half the requirement. On the export side, <cite index="21-7">most report tables in the platform include an 'Export to CSV' button</cite>, and <cite index="23-6,23-7">Ottimate offers Standard and Advanced Reports covering aging, payments sent by period, invoice counts at workflow stages, and pending approvals</cite>. Spend analytics can be sliced by GL account, category, location, and time period through the Insights module. …

Limitations: The scheduled delivery half of the requirement is unconfirmed: the Controller and CFO will need to log in to pull reports or wait for AP staff to manually export and forward them, reintroducing the human dependency the buyer is trying to eliminate. …

Requirement evaluated: Custom field mapping between the AP platform and Intacct

For this multi-location services company running 2 Sage Intacct entities, Medius handles dimension-level field mapping through its 'Coding String' framework: an admin-configurable layer where each company's coding row is assembled from named dimensions (GL account plus additional coding positions such as Department, Location, Project, or custom ERP dimensions). …

Limitations: Because the Intacct connector is partner-delivered (Acuity Solutions), not Medius-managed, there is no direct Medius help-center documentation confirming that user-defined fields, custom segments, or non-standard Intacct dimensions are supported at the same depth Medius provides for its natively managed ERP connectors; …

Requirement evaluated: Custom field mapping between the AP platform and Intacct

For a $120M services company running two Sage Intacct entities, Ottimate addresses custom field mapping through its 'Enhanced Dimensions' module, which is explicitly listed as supported for Intacct. <cite index="25-1,25-3,25-4">Enhanced Dimensions allow the buyer to configure the AP platform with all the dimensions the ERP supports, with rules for automated coding at the line-item level, and the ability to set dimensions at either the invoice header or line-item level.</cite> On the Intacct-specific side, <cite index="1-1,1-2">Ottimate directly confirms it supports mapping across customized dimensions and metadata fields configured within Sage Intacct entities.</cite> A dedicated Ottimate he …

Limitations: The publicly documented custom field setup (for URL-type link-back fields) walks through steps inside Intacct's Platform Services menu, suggesting initial configuration for non-standard custom segments may require Ottimate implementation support rather than being fully self-serve through an Ottimate admin UI. …

Requirement evaluated: Automatic extraction of: vendor name, invoice number, date, PO number, line items, amounts, tax, and payment terms

For a 3-person AP team at a $120M services company currently keying 1,800 invoices per month by hand into Sage Intacct, Medius addresses Stage 1 of the pre-processing journey (legitimacy and data capture) through a dedicated module called Medius Capture. The module combines OCR, AI, and ML to extract structured data from paper, PDF, XML, EDI, and email-based invoices without requiring manual templates for each new vendor layout. …

Limitations: No public help-center documentation enumerates every extractable field by name with a confirmed mapping to Sage Intacct field IDs, so the buyer should validate during a structured proof-of-concept that PO number and payment terms pass through to Intacct at full fidelity, not just as captured text. …

Requirement evaluated: Automatic extraction of: vendor name, invoice number, date, PO number, line items, amounts, tax, and payment terms

For a $120M multi-location services company currently keying 1,800 invoices per month manually into Sage Intacct, Ottimate's Instant Capture module addresses Stage 1 (legitimacy/capture) of the pre-processing journey directly. Invoices arriving by email or mail are ingested and processed by Ottimate's AI, which combines OCR with deep learning to extract both header-level fields and line-by-line detail. …

Limitations: No publicly documented enumeration of every extracted field (e.g., explicit confirmation that payment terms are extracted as a discrete structured field, not just read as free text) was found in help center documentation; the help.ottimate.com site did not return results in search. …

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

For a multi-location services company with subcontractor, facilities, and professional-services POs, Medius operates at pre-processing stages 2 and 5 (PO match and cost allocation) and explicitly supports 2-way matching as a configurable match type for service-based purchases. The Medius glossary directly answers the buyer's scenario: 'Can invoice matching be tailored for service-based purchases without a goods receipt? Yes. …

Limitations: The product definition documentation confirming the 2-way matching policy is drawn from MediusFlow/D365 integration specs dated 2017-2018; configuration options for the current Sage Intacct connector should be verified with Medius directly to confirm that the 2-way match policy is available and configurable at the PO-t …

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

For a multi-location services company processing subcontractor, facilities, and professional services invoices against service POs where no goods receipt exists, Ottimate's PO Match module directly addresses this scenario. The platform explicitly offers both match modes as selectable options: <cite index="1-3,1-4">Ottimate gives you flexibility with two types of purchase order verification: 2-way matching to connect POs with invoices, or 3-way matching to reconcile invoices, receipts, and POs.</cite> The 2-way path operates at the pre-processing stage 2 level (PO match), validating price and quantity at the line-item level against the service PO without requiring any goods receipt or warehou …

Limitations: No publicly documented evidence confirms that the 2-way vs. 3-way match mode can be automatically assigned per PO line type or vendor category (i.e., that service POs are routed to 2-way and goods POs to 3-way without manual selection per invoice); the multi-workflow release note is the closest evidence but stops short …

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 self-service portal: new vendor registration, W-9/W-8 submission, banking detail entry, invoice submission, payment status inquiry

For your 3-person AP team processing 1,800 invoices/month, Ottimate addresses several vendor-facing needs through a combination of point-specific tools rather than a single unified self-service portal. Banking detail entry works via an AP-initiated email invitation: once your AP team flags a vendor for ACH in the Vendors module, the vendor receives a secure link, completes their banking fields, and creates a login at vendor.plateiq.com, with micro-deposit verification taking 1-3 business days (Ottimate Help Center: 'Vendor ACH Verification', 'How do I Invite Vendors to Accept ACH Transfers'). …

Limitations: W-9 and W-8 collection is not present in Ottimate's documented capabilities at any tier or price point, which means your team would need a separate process (email, PDF, or a third-party tool) to collect and store tax compliance documents for new vendors — a direct gap against your critical requirement. …

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: SOC 2 Type II certification (current, not in-progress)

For a $120M services company treating SOC 2 Type II as a critical procurement gate, Ottimate meets the credential on its face. Ottimate's dedicated AP security and compliance page states directly that the platform is SOC 2 Type I and Type 2 certified, covering the operational control-effectiveness standard the buyer requires. The audit was conducted by A-LIGN, an AICPA-accredited licensed CPA firm and one of the most widely recognized SOC 2 auditors in the market, confirming this is Ottimate's own application-layer report and not inherited from a cloud infrastructure provider. …

Limitations: Ottimate's public pages do not disclose the coverage period, report end date, or recertification cycle for the current Type II report, so the buyer cannot confirm 'currency' from public sources alone. …