Medius vs Zip

Requirement evaluated: Batch approval capability for recurring invoices from the same vendor (e.g., monthly telecom bills across 6 locations)

For a buyer processing monthly telecom bills across 6 locations, Medius provides two complementary mechanisms that address this requirement at different points in the pre-processing journey. First, the Medius AP inbox includes a 'Bulk Operation' (also called 'Batch approval' in MediusGo) feature: when an approver has multiple invoices in the same workflow step, selecting them activates the Bulk Operation button, allowing simultaneous approval of a set of invoices rather than opening each one individually. This is documented in Medius's own customer success guidance as commonly used for Final Approval scenarios with invoice backlogs. …

Limitations: The Bulk Operation button groups invoices by workflow step, not necessarily by vendor, so the approver must filter or sort by supplier to isolate the 6 telecom invoices before batch-selecting them; this is a minor UX step rather than a structural gap. …

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 telecom bills across 6 offices, Zip's closest mechanism is its dynamic, rule-based approval workflow engine rather than a true batch approval queue. <cite index="8-1,8-2">Zip offers highly flexible and customizable approval workflows that can be tailored to specific business needs, allowing for complex, multi-level approvals based on criteria such as amount, department, or vendor.</cite> In practice, this means Zip can be configured to route all invoices from a known recurring vendor (e.g., the telecom provider) …

Limitations: Without a native batch/bulk approval UI or vendor-grouped invoice queue, an approver handling 6 monthly telecom invoices across locations still performs 6 individual approval actions; the workflow automation reduces friction per action but does not collapse the 6 approvals into one. …

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 their inboxes, Zip's Spend Insights module offers the closest match. Zip's product page states users can 'easily build custom reports and automate delivery to stakeholders at a regular cadence to keep everyone in the loop,' and the vendor's spend management blog confirms the platform supports 'repeatable exports and scheduled email deliveries' for data manipulation and stakeholder sharing. The module tracks invoices, purchase requests, POs, and spend by department, category, vendor, or GL account, which covers some of the data this buyer's Controller and CFO would want. …

Limitations: Zip's reporting data model is built around procurement orchestration metrics (spend by vendor, request cycle times, savings tracking), not AP financial reporting; the Controller and CFO may find the delivered reports lack the AP-specific detail they need, such as aging buckets, payment method breakdowns, or accrual dat …

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 services company processing 1,800 invoices per month from email and mail, the early payment discount detection requirement demands: OCR extraction of discount terms (e.g., 2/10 net 30) from unstructured PDFs, a deadline calculator that counts down from the invoice date, and a time-sensitive AP alert before the 10-day window closes. Zip's AI OCR layer does capture 'payment terms' as a structured field during invoice ingestion — the platform documents that it captures 'details like invoice numbers, line items, and payment terms with a high degree of accuracy.' The Procure-to-Pay product page confirms that Zip AI 'flags discrepancies and enforces policy' and supports conditional wor …

Limitations: No documented discount-deadline alerting mechanism exists in Zip's current product: the 10-day window in a 2/10 net 30 term leaves almost no margin for a workflow that depends on custom-configured rules rather than a native discount-detection engine. The buyer's invoice mix (email and mail PDFs from 6 locations) …

Requirement evaluated: Approved POs push to NetSuite automatically; payment status syncs back

For a $250M technology company currently creating POs manually in NetSuite, Medius replaces that manual workflow through its 'Built for NetSuite' certified SuiteApp, which extends NetSuite's existing procure-to-pay functionality rather than replacing it. Approved POs created in Medius Procurement flow directly into NetSuite via a cloud-managed connector that Medius maintains; no custom coding or file uploads are required. The integration is bi-directional: vendor master data, PO lines, and goods receipt data sync from NetSuite into Medius, and once an invoice clears the Medius approval and matching workflow, the posting (preliminary, cancel, and final) writes back to NetSuite automatically. …

Limitations: The depth of PO-line data flowing into the connector depends on the NetSuite integration package version in use; buyers should verify that the connector imports PO lines before goods receipts are confirmed, which is a configuration requirement Medius documents for its goods-receipt deviation routing feature. …

Requirement evaluated: Approved POs push to NetSuite automatically; payment status syncs back

For a $250M tech company currently creating POs manually in NetSuite, Zip operates as the front-end intake and approval layer: employees submit purchase requests through Zip's intake form, and those requests route automatically across finance, legal, IT, and security teams for approval. Upon connection, Zip executes a daily master data sync that pulls vendors, GL segments, subsidiaries, custom fields, tax codes, and amortization schedules from NetSuite into Zip so PO fields are pre-populated accurately. …

Limitations: The payment status sync-back direction is documented at the architecture level (AP status visibility described as real-time) but published technical documentation does not specify the exact NetSuite bill-payment fields or polling frequency that flow back into Zip; the buyer should validate during a technical demo wheth …

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

For a $250M technology company with 35% maverick spend and a pressing need for policy compliance reporting, Medius delivers meaningful but AP-execution-centric visibility. On the AP side, the platform logs every invoice, approval, and workflow step digitally, and its dashboard/gadgets layer (documented in the Medius Success Portal) exposes configurable metrics including the ratio of invoices routed manually vs. automatically, invoice status proportions, and touchless-processing rates. …

Limitations: For this buyer's CFO, who needs discrete, auditable percentage metrics such as spend-through-approved-channels rate and approval policy adherence score, Medius's documented reporting centers on AP operational metrics (touchless rate, invoice status, manual routing ratio) …

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

For a $250M technology company currently tracking 35% maverick spend with no procurement system, Zip's intake-orchestration architecture is the core mechanism: every purchase request must enter through a single front door, creating a real-time numerator for spend-under-management percentage that can be compared against total spend pulled from NetSuite. Zip's Spend Insights capability page documents dashboards that track purchase requests, POs, and invoices by department, category, vendor, and GL account, while also monitoring approver SLA adherence and surfacing bottlenecks in the approval cycle — directly producing the 'approval policy adherence' metric the buyer needs. …

Limitations: Contract compliance rate reporting specifically — the precise mechanism for how Zip computes and surfaces on-contract vs. off-contract spend as a percentage — is documented at the KPI and blog level but not in granular product documentation found in this search; buyers should confirm in a demo how Zip's contract manage …

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 multi-location services company running 2 Sage Intacct entities, Zip's connector addresses cost-allocation field passthrough (pre-processing stage 5) primarily through a daily sync of standard Intacct reference data into Zip's intake layer. <cite index="22-3">Upon connecting Zip and Sage Intacct, Zip initiates a daily sync process to pull Entities, Locations, Segments, and the existing vendor list from Sage Intacct into Zip</cite>, making those standard objects selectable on request forms and invoice coding screens. …

Limitations: Zip's Intacct connector is designed around procurement intake: it syncs standard Intacct objects (entities, locations, segments, vendors) into Zip's forms, but there is no documented admin-configurable mapping layer for Intacct UDFs or custom segments. …

Requirement evaluated: Automated three-way matching: PO to receipt to invoice with configurable tolerance (2% price, 5% quantity)

For a $250M technology company coming from a fully manual, email-based process, Medius delivers automated three-way matching as a core capability of its AP Automation module. When an invoice arrives, Medius's AI-powered capture extracts line-item data (vendor name, PO number, quantities, unit prices) and automatically connects it to the corresponding purchase order and goods receipt (GDR) already synced from NetSuite. …

Limitations: Medius relies on goods receipt data being registered and synced from NetSuite into Medius for the third leg of the match; since this buyer currently has no receiving process or system discipline, the ops team will need to establish a goods receipt confirmation workflow in NetSuite before three-way matching can operate …

Requirement evaluated: Automated three-way matching: PO to receipt to invoice with configurable tolerance (2% price, 5% quantity)

For a $250M technology company moving off email-based approvals, Zip's AP automation suite covers the downstream matching stages through its AI-driven Invoice Review Agent. When a vendor invoice arrives, Zip's AP Inbox Agent captures it from email or other sources, extracts line-item data via OCR and AI, and the Invoice Review Agent then runs three-way matching against the PO and contract data already stored in Zip, surfacing 'purchase order tolerance breaches' and flagging discrepancies before the invoice reaches an approver (ziphq.com/blog/introducing-ai-automation-p2p). …

Limitations: No Zip-authored documentation found explicitly confirms that price-% tolerance and quantity-% tolerance are independently configurable as two distinct thresholds; the buyer's specific requirement for separate 2% price and 5% quantity bands may require implementation-time configuration or custom exception rules to appro …

Requirement evaluated: The AP automation solution must integrate bi-directionally with NetSuite as the system of record, writing back fully coded bills, vendor records, payment status, and GL entries with full NetSuite field fidelity, including custom segments, classes, departments, and locations, so that no manual re-keying into NetSuite is required at any stage of the invoice lifecycle.

For an entertainment business running NetSuite as system of record, Medius delivers bi-directional integration through its own dedicated cloud connector: a certified 'Built for NetSuite' hybrid SuiteApp (covering AP Automation and Pay) that Medius manages directly, with no third-party middleware involved. On the inbound leg, Medius imports coding dimensions directly from Oracle NetSuite, and its May 2025 product definition document explicitly states that 'the structure of coding dimensions - including both standard and custom dimensions - is determined during the data gathering phase' and that Medius pulls those dimensions from NetSuite's own schema. …

Limitations: While Medius's May 2025 product definition confirms that both standard and custom coding dimensions are imported from NetSuite and that approved invoices post back to NetSuite, the documentation does not provide field-level specificity on how payment status records (e.g., bill payment clearance, open-bill reconciliatio …

Requirement evaluated: Approved purchase orders and requisitions must write commitment records back to Sage Intacct in real time (or near-real time) so that the encumbrance balance visible to other requesters in req_3 reflects all open commitments, not just paid invoices. Without this writeback, two requesters in the same department can simultaneously consume budget that appears available because neither commitment has yet posted as an actual.

Your scenario involves two concurrent department requesters who could both consume the same available budget because Zip's Intacct integration does not demonstrably write commitment records back as encumbrance transactions at the moment of PO/requisition approval. Zip's accounting solutions page claims that <cite index="24-2,24-3">approved transactions sync bi-directionally in real time, so your GL reflects committed spend as it happens</cite> — but the authoritative Sage Intacct Marketplace listing tells a narrower story: <cite index="15-2,15-3">the Zip integration with Sage Intacct automates vendor creation and keeps Zip in sync with the vendor record; upon connecting Zip and Sage Intacct, …

Limitations: The documented Zip-Intacct integration is limited to daily master-data pull sync and vendor record creation; no source confirms that approved PO or requisition records write back to Intacct as encumbrance or commitment document types that decrement available budget in real time. …

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: Centralized vendor master synchronized bidirectionally with Sage Intacct

For your 2-entity Sage Intacct environment, Zip establishes a connection with Intacct at the point where vendor master data must stay consistent across both your procurement layer and your ERP. On the inbound side, once the connector is configured, Zip runs a daily scheduled pull from Sage Intacct that brings Entities, Locations, Segments, and your existing vendor list into Zip, giving requesters the correct vendor data when they initiate purchase requests. On the outbound side, when a Zip user submits a purchase request referencing a net-new vendor and that vendor clears Zip's onboarding and approval workflow, Zip creates the new vendor record in Sage Intacct automatically. …

Limitations: The sync as documented operates on a daily schedule for the Intacct-to-Zip direction and triggers only on new vendor creation for the Zip-to-Intacct direction; updates to existing vendor records in either system (e.g., a banking detail or payment terms change entered in Intacct, or a W-9 collected through Zip's supplie …

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 ingestion from our shared AP email inbox; no manual downloading or sorting

For a team currently downloading invoices from a shared AP email inbox and manually keying them into Sage Intacct, Zip's AP Automation module addresses this at the very first stage of the pre-processing journey (legitimacy and capture). Zip provides a dedicated AP Inbox Agent that actively monitors incoming vendor mail, extracts invoice attachments, and organizes them into the processing queue without any human download or sort step. …

Limitations: The specific technical integration method for connecting the buyer's existing shared Office 365 or Google Workspace AP mailbox (IMAP, OAuth connector, or forwarding rule) …

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: Per-vendor duplicate sensitivity configuration for vendors that legitimately reuse invoice numbers (e.g., recurring rent or utility billing)

For a multi-location services company with recurring vendors like landlords and utility providers that legitimately reuse invoice numbers monthly, this requirement asks whether Zip can be configured to suppress or tune duplicate flags at the individual vendor level. Zip's Invoice Review Agent does surface duplicate invoices before they reach an approver: <cite index="10-5">the Invoice Review Agent surfaces duplicates, purchase order tolerance breaches, and contract mismatches before anything reaches an approver, with three-way matching running against contract data already in Zip.</cite> Additionally, <cite index="6-1,6-2">Zip catches duplicates, overages, and contract mismatches before invo …

Limitations: For this buyer's 45% non-PO invoice volume (utilities, subscriptions, recurring rent), vendors that legitimately reissue the same invoice number each billing cycle would generate recurring false-positive duplicate flags with no documented per-vendor suppression or sensitivity tuning mechanism. …

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 Sage Intacct / Adaptive Planning buyer who needs a queryable override audit trail, Zip captures structured event records per request as it moves through its orchestration workflow. The platform's persistent audit log records date, user, action, and target for every customer action, and every request, approval, PO, invoice, and payment is timestamped and traceable without manual reconstruction. When a budget-exceeding request triggers a soft-stop reroute, the workflow engine flags the overage and routes it to finance approvers like a CFO, with approvers shown real-time remaining budget at the moment of decision. …

Limitations: The buyer's requirement calls for four structured fields per override event: requester identity, budget dimension breached, overage amount at time of override, and authorizing approver. …

Requirement evaluated: Blanket PO support for contract-based spending with release tracking against the total commitment

For a $250M technology company that currently has no procurement system and 35% maverick spend, Medius offers two overlapping mechanisms that partially address blanket PO needs. First, the Medius I2P platform includes a 'Supplier Contract' document type that supports contract-based invoice matching: incoming invoices can be matched against a stored supplier contract rather than only a standard PO, and the MediusFlow product has included 'Contract Management functionality for 4-way match and real-time follow-up on invoice transactions and invoice plan' since at least 2014. …

Limitations: The specific release-tracking mechanism this buyer needs (each release drawing down a running balance against the parent commitment ceiling, with enforcement before a release is approved) …

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

For a $250M technology company replacing ad hoc email and Slack approvals, Zip covers the full PO lifecycle natively within its procure-to-pay platform. Once a purchase request clears the approval workflow, Zip automatically generates a PO and delivers it to the supplier through its Vendor App portal — this is the 'approved through acknowledged' handoff, where the supplier receives the PO directly in Zip's portal rather than via email. …

Limitations: Help-center documentation confirms that the supplier portal delivers POs and enables vendor-side interaction, but does not explicitly document a distinct 'acknowledged' status label that is updated by a supplier confirmation action separate from PO delivery — the acknowledged stage is effectively PO delivery to the Ven …

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: Mandatory IT security review for all software/SaaS purchases regardless of amount

For a $250M technology company like this buyer, whose 35% maverick spend includes shadow SaaS purchases at any dollar level, Zip's Intake-to-Procure workflow engine directly addresses the requirement. Every purchase request enters through a single intake portal where the request type and vendor category are captured upfront; the no-code workflow engine then evaluates those attributes and automatically routes the request to the designated IT security reviewer as a required approval step before any PO or contract can proceed. This category-based trigger is independent of spend amount: Zip's rules engine routes on request type (software, SaaS, subscription) …

Limitations: The non-bypassability of the IT security step depends on correct workflow configuration during implementation: an admin must define the software/SaaS category condition and assign IT security as a required (not optional) reviewer, so initial setup rigor is essential. …

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)

As a $120M multi-location services company with sensitive procurement data flowing through Sage Intacct, your security review team will want a completed, operational-controls audit rather than a point-in-time snapshot. Zip's official Trust page confirms that <cite index="10-1,10-2">Zip has undergone a Service Organization Controls audit (SOC 2 Type 2), and prospects can contact their account manager or Zip's Security Resource Center to request the most recent report.</cite> The audit runs on an annual cycle: <cite index="11-3">Zip is annually audited for SOC 2 Type 2 compliance on select trust service principles.</cite> Zip's product pages also list SOC 2 Type 2 alongside SOC 1 Type 2, ISO 2 …

Limitations: The report covers 'select trust service principles' rather than all five AICPA Trust Services Criteria, so your security team should confirm which criteria (Security, Availability, Processing Integrity, Confidentiality, Privacy) are in scope when requesting the report. …

Requirement evaluated: Spend dashboards: real-time spend by vendor, category, department, location, and period

For a $250M technology company currently flying blind on 35% of its spend, Medius delivers this requirement through its dedicated Medius Analytics module, a separately licensed product that sits alongside AP Automation and Procurement. <cite index="32-1">The module provides "a full, real-time view into how money is spent across your organization delivered through pre-defined reports, dashboards and KPIs,"</cite> with named sub-sections in the product documentation covering AP Insights, Invoice Process Insights, User Insights, and a Procurement Dashboard. …

Limitations: Some dashboard gadgets in Medius Spend Management rely on a scheduled ETL job rather than a live data feed, meaning <cite index="13-4">"displayed data is based on ETL reporting data"</cite> for those panels, which introduces a batch-refresh lag rather than truly instantaneous data. …

Requirement evaluated: Maverick spend tracking: flag all invoices that arrive without a matching PO

For a company with 35% maverick spend and no systematic PO enforcement, Zip addresses this requirement through two layers that operate end-to-end. First, at the intake stage, Zip forces every purchase request through a structured workflow that automatically generates a PO before any vendor is engaged: the intake-to-pay product page states that 'Zip ensures all requests go through intake and automatically generates POs, so you can drive PO adoption effortlessly.' Second, at the invoice stage, Zip's AP automation module pulls invoices from the AP inbox, applies AI-driven matching against the corresponding PO record, and explicitly 'prevents exceptions at intake, catches the rest with AI matchi …

Limitations: Zip's exception-catching mechanism operates on invoices that enter Zip's AP inbox or intake workflow; invoices submitted directly into NetSuite by the ops team, bypassing Zip entirely, will not be caught by Zip's matching engine unless the buyer fully routes all AP intake through Zip. …