Ramp vs Zip

Requirement evaluated: The system must support configurable approval routing for requisitions that exceed a soft-stop threshold, routing the override request to a designated budget owner or finance approver for the relevant department or dimension before the commitment proceeds. This is implied by the soft-stop model the buyer described: a soft stop without a structured approval path is just a dismissible warning, not a control.

For a mid-market company on Sage Intacct with budgets imported from Workday Adaptive Planning, Ramp converts soft-stop budget thresholds into structured gating approvals through its dedicated 'Budget-based approval workflows' feature. Once the buyer's Adaptive budgets are uploaded into Ramp Budgets (file upload replaces the active budget), admins configure budget-aware conditions that trigger a mandatory approval step when a purchase request exceeds a defined percentage of remaining budget: <cite index="21-3">conditions such as 'If a purchase exceeds 80% of remaining budget' automatically involve budget owners in the approval chain, adjust approval paths based on real-time budget data, and d …

Limitations: Budget-aware threshold conditions (percentage of remaining budget) require the buyer's Adaptive Planning budgets to be actively loaded into Ramp Budgets as the live tracking source; <cite index="22-20,22-21">only one budget version can be active at a time, so scenario budgets must be managed outside Ramp and the desire …

Requirement evaluated: The system must support configurable approval routing for requisitions that exceed a soft-stop threshold, routing the override request to a designated budget owner or finance approver for the relevant department or dimension before the commitment proceeds. This is implied by the soft-stop model the buyer described: a soft stop without a structured approval path is just a dismissible warning, not a control.

For a mid-market buyer whose budgets live in Workday Adaptive Planning and whose spend problem is enforcement at the moment of commitment, Zip's workflow engine is purpose-built for this control model. When a requester submits a purchase request through Zip's intake portal, <cite index="22-4,22-5,22-6">the platform collects all relevant information upfront, including what is being purchased, from which vendor, for how much, and which budget it affects, before any commitment is made.</cite> The soft-stop-to-structured-approval chain is handled through Zip's no-code conditional logic layer: <cite index="2-2">the workflow engine uses preset spending limits and rules to determine whether a reque …

Limitations: The depth to which live budget-consumption data from Workday Adaptive Planning (as opposed to a static dollar threshold configured in Zip) can serve as the conditional trigger in a workflow rule is not explicitly documented; the buyer should confirm during implementation that the Adaptive-to-Zip budget sync feeds a rea …

Requirement evaluated: SOC 2 Type II certification for the platform

For your CFO and audit committee, Ramp holds a current SOC 2 Type 2 report covering the period ending October 2024, issued through its annual independent audit cycle. The report is available for download from Ramp's public Trust Center at trust.ramp.com (powered by SafeBase): a prospective customer submits an access request, signs an NDA electronically within the portal, and can then view and download the full report. …

Limitations: The report is gated behind an NDA, which is standard practice but means your legal team must execute that agreement before your auditors can review the document. The audit period runs through October each year, so if your own audit cycle falls in the spring, you may be working from a report that is 5-6 months old at th …

Requirement evaluated: SOC 2 Type II certification for the platform

For a $250M technology company whose CFO and audit committee need documented evidence of sustained security controls, Zip holds a current SOC 2 Type 2 certification issued by an independent auditor. Zip's public compliance page states it is <cite index="2-5">"annually audited for SOC 2 Type 2 compliance on select trust service principles."</cite> The report is available upon request: <cite index="1-7,1-8">Zip has undergone a SOC 2 Type 2 audit and customers can contact their account manager or Zip's Security Resource Center to request the most recent report.</cite> Zip's contractual Information Security Policy reinforces this: <cite index="6-4,6-5">Zip will make copies of third-party audit r …

Limitations: The SOC 2 Type 2 report covers "select trust service principles" rather than all five trust service criteria; the buyer should request the current report to confirm which principles (security, availability, processing integrity, confidentiality, privacy) are in scope before finalizing vendor diligence. …

Requirement evaluated: Partial receipt support: PO for 100 units, receive 60, match against invoice for 60

For a $250M technology company receiving 60 of 100 ordered units, Ramp handles this through its native item receipt and three-way match workflow in Ramp Procurement. Once 3-way match is enabled on a Spend Program, a 'Receive' button appears on approved POs; the receiving team creates an item receipt recording the quantity actually delivered (e.g., 60 units), and the PO moves to 'Partially received' status: meaning item receipts exist but not every line has been fully received. …

Limitations: Quantity-level partial receiving (tracking 60 of 100 units) is only available on item-coded line items; expense-coded lines (which cover the buyer's indirect spend categories like SaaS, facilities, and professional services) support only binary received/not-received status, not unit-quantity tracking. …

Requirement evaluated: Partial receipt support: PO for 100 units, receive 60, match against invoice for 60

For a buyer receiving 60 of 100 ordered units and needing to match an invoice for exactly 60, Zip's documented AP automation centers on PO-to-invoice matching rather than a structured goods-receipt-driven three-way match. The Zip Intake-to-Pay launch documentation specifies that Zip AP Automation provides 'automated two-way matching,' with stakeholders able to 'acknowledge any goods and services have been received' inside an approval workflow step — this is a workflow acknowledgment, not a goods receipt note (GRN) that tracks quantity against an open PO line. …

Limitations: Zip's native AP automation is documented as two-way PO-to-invoice matching with a workflow acknowledgment step for receipt confirmation; no Zip help center documentation describes a structured GRN module with per-line open-quantity tracking that would enforce a partial receipt match (60 of 100 units) …

Requirement evaluated: Mandatory IT security review for all software/SaaS purchases regardless of amount

For a $250M technology company trying to enforce mandatory IT security review on every software and SaaS purchase, Ramp Procurement's primary mechanism is the dedicated Spend Program: admins create a category-specific 'Software purchase request' program that carries its own mandatory approval chain, and every step in that chain executes regardless of dollar amount. …

Limitations: The 'mandatory regardless of amount' goal is achievable within a dedicated Software Spend Program, but Ramp provides no automatic cross-channel intercept: an employee who routes a SaaS purchase through a general procurement program, or buys a SaaS subscription directly on a corporate card, can complete the transaction …

Requirement evaluated: Mandatory IT security review for all software/SaaS purchases regardless of amount

For a $250M technology company where any department can purchase SaaS tools and 35% of spend currently bypasses any approval gate, Zip's architecture directly addresses this requirement at the intake stage: the mechanism is a no-code conditional workflow engine that fires before a PO is ever created. When an employee submits a purchase request through Zip's single intake portal, the intake form captures what is being purchased and from which vendor; if the request is classified as software or SaaS by category or vendor type, Zip's workflow engine automatically injects an IT security review step into the approval path regardless of dollar amount. …

Limitations: Configuration of the category-based trigger depends on accurate intake form classification; if a requester deliberately miscategorizes a software purchase as 'general services,' the IT security step would not fire, so the buyer should map intake form answer choices carefully to close that gap during implementation. …

Requirement evaluated: The procurement tool must import approved budgets directly from Workday Adaptive Planning on a scheduled or on-demand basis, mapping them to Sage Intacct dimensions and department structures without requiring manual re-entry. This integration is the foundation of enforcement: if the imported budget does not reflect the Adaptive-composed version with full dimensional fidelity, every downstream control is operating on stale or incomplete data.

For a buyer who builds budgets in Workday Adaptive Planning and needs them live in a procurement tool without manual re-entry, Ramp's mechanism falls meaningfully short of the stated requirement. Ramp does support budget ingestion: <cite index="10-9,10-10,10-11">Ramp Budgets is designed to provide real-time visibility into spending, tracking plan versus actuals and connecting financial approval workflows to evaluate purchases against available budget</cite>, and <cite index="21-4,21-5,21-6,21-7">the process requires filling out a Ramp-provided CSV template, saving it, uploading it to Ramp, and then using a mapping interface to match fields to Ramp's dimensions.</cite> Dimensional budget line …

Limitations: There is no native, scheduled, or on-demand API integration between Ramp's budget module and Workday Adaptive Planning; every refresh of Adaptive-composed budgets requires a manual CSV export and re-upload, creating the exact re-entry risk and staleness gap the buyer flagged as critical. …

Requirement evaluated: The procurement tool must import approved budgets directly from Workday Adaptive Planning on a scheduled or on-demand basis, mapping them to Sage Intacct dimensions and department structures without requiring manual re-entry. This integration is the foundation of enforcement: if the imported budget does not reflect the Adaptive-composed version with full dimensional fidelity, every downstream control is operating on stale or incomplete data.

For a buyer composing budgets in Workday Adaptive Planning and enforcing them against Sage Intacct dimensions, Zip offers a named, shipping integration with Workday Adaptive Planning launched in 2024. <cite index="1-1,1-5">Zip's strategic budgets integration with Workday Adaptive Planning delivers real-time budget visibility within Zip's platform, giving finance and procurement teams a clear view of actual spend, approved spend, and pending spend against budgets in one place.</cite> <cite index="35-6,35-11">Described as a strategic integration providing real-time budget visibility within Zip's interface, it is designed to enhance spend control, improve financial predictability, and facilitat …

Limitations: The Adaptive Planning integration is confirmed as providing real-time budget visibility inside Zip, but no publicly available help center documentation describes how Zip maps Adaptive Planning budget lines to Sage Intacct's specific dimension values (department, location, class, project) or confirms scheduled vs. …

Requirement evaluated: PO change order workflow: amendments require re-approval if they exceed original amount by more than 10% or $5,000

For a $250M technology company that needs PO amendments to trigger re-approval only when they cross specific thresholds, Ramp's Procurement module includes a dedicated Change Orders feature that allows authorized users (the PO request owner, approvers, AP, and Admin roles) to submit amendment requests against any approved PO. Admins can configure a separate change order approval workflow within the relevant Spend Program, and that workflow supports conditional routing: the help documentation explicitly states that 'amount changes above a threshold could require VP approval,' meaning the workflow engine can branch based on the dollar magnitude of the change. …

Limitations: For this buyer's specific policy (re-approval only when the amendment exceeds 10% OR $5,000, no re-approval below both thresholds), Ramp's documented conditional routing confirms amount-threshold-based escalation but does not confirm that sub-threshold change orders can be fully exempted from re-approval rather than si …

Requirement evaluated: PO change order workflow: amendments require re-approval if they exceed original amount by more than 10% or $5,000

For a $250M technology company replacing ad-hoc email/Slack approvals, Zip's PO Management module handles change orders as a distinct, configurable workflow step within its Procure-to-Pay product. Zip's official admin training course, 'Procure-to-Pay Admin Fundamentals,' lists 'Configure the approval workflows for PO change orders' as a core learning objective, and the platform's Intake-to-Pay capability explicitly includes the ability to 'manage change orders with the right approvals' alongside syncing PO data back to the ERP. …

Limitations: The buyer's specific requirement calls for re-approval when an amendment exceeds either 10% or $5,000 (whichever is triggered first), a dual-condition OR logic applied to the change delta. …

Requirement evaluated: Supplier performance scorecards: on-time delivery rate, quality issues, invoice accuracy, responsiveness

For a $250M technology company needing to track on-time delivery rates, quality issues, invoice accuracy, and responsiveness across 800+ active vendors, Ramp offers no native supplier performance scorecard mechanism. Ramp's own blog on supplier scorecards states explicitly: "While Ramp doesn't create supplier scorecards, our procurement software complements your evaluation efforts by automating key purchasing workflows, centralizing vendor data, and ensuring policy compliance." Ramp's vendor management module, per its help documentation, surfaces data such as total spend, tax details, contract dates, and recent bill or card transactions per vendor profile; it does not collect or aggregate op …

Limitations: Ramp has no mechanism to calculate or display on-time delivery rate, quality issue counts, or responsiveness scores for this buyer's 800+ vendor base; the platform's data model stops at payment and spend, so none of the four scorecard dimensions the buyer requires can be generated natively. …

Requirement evaluated: Supplier performance scorecards: on-time delivery rate, quality issues, invoice accuracy, responsiveness

For a $250M technology company that needs to track on-time delivery, quality issues, invoice accuracy, and responsiveness across 800+ active vendors it is consolidating, Zip's approach combines two modules rather than a single scorecard engine. The Vendor Management module centralizes vendor data in a unified record, while the Spend Insights module allows tracking of 'purchase requests, POs, and invoices... by department, category, vendor, or GL account' and surfaces SLA compliance for approvers. …

Limitations: No product capabilities page documents a native, auto-populated scorecard that pulls on-time delivery rates from PO-vs-receipt timestamps, quality flags from receiving records, or responsiveness scores from request logs as continuously scored dimensions. …

Requirement evaluated: Before a requester submits a requisition, the system must display their real-time remaining budget for the relevant dimension and department, calculated against all open commitments, approved purchase orders, and actuals already posted to Sage Intacct. The buyer explicitly called this out: requesters must see their true available balance before they commit, not after.

This buyer needs requesters to see a true available balance, calculated against open commitments, approved POs, and Sage Intacct actuals, before submitting a requisition. Ramp Budgets does provide real-time budget visibility: the module unifies spend data across cards, reimbursements, Bill Pay, and POs into a single budget dashboard, and the budget-based approval workflow feature explicitly documents 'Informed decisions: Display current budget status at the time of approval request.' Budget owners receive live dashboards and can see remaining budget against actuals tracked within Ramp. However, the balance Ramp calculates is sourced entirely from Ramp-native activity. …

Limitations: The buyer's true available balance requirement depends on actuals already posted to Sage Intacct being reflected in the pre-submission display; Ramp's budget balance is calculated only from Ramp-originated spend (cards, Bill Pay, reimbursements, Ramp POs), so any Sage Intacct actuals that did not flow through Ramp will …

Requirement evaluated: Before a requester submits a requisition, the system must display their real-time remaining budget for the relevant dimension and department, calculated against all open commitments, approved purchase orders, and actuals already posted to Sage Intacct. The buyer explicitly called this out: requesters must see their true available balance before they commit, not after.

This buyer runs budgets in Workday Adaptive Planning and actuals in Sage Intacct, and needs requesters to see a true available balance before submitting. Zip has a named, strategic integration with Workday Adaptive Planning, launched in 2024, that surfaces real-time budget visibility directly inside Zip's platform interface. As documented in Zip's official product launch announcement, <cite index="30-3,30-4,30-5">the integration delivers real-time budget visibility right within Zip, empowering teams to make informed purchasing decisions with visibility into budgets, while tracking actual spend, approved spend, and pending spend all in one place.</cite> At the request stage, <cite index="11-1 …

Limitations: The Workday Adaptive Planning budget integration is well-documented and directly matches this buyer's budget source; however, the Sage Intacct integration is documented as a daily master-data sync, not a real-time actuals pull, so the available balance shown to requesters may not include invoices posted to Sage Intacct …

Requirement evaluated: Hosted catalog for frequently purchased items with pre-negotiated pricing (office supplies, IT peripherals, standard software)

For a $250M tech company looking to channel 450 employees toward pre-approved items with locked pricing, Ramp's mechanism operates at the intake and approval stage rather than the catalog-browsing stage. Through Ramp Procurement (a separately licensed module available on Ramp Plus), admins create Spend Programs: templated intake forms for specific spend categories such as 'Software Purchase Request' or 'IT Peripherals.' When an employee needs to buy, they select the relevant Spend Program, fill in the vendor name, description, and amount manually, and the request routes through a configured approval workflow before a PO is generated. …

Limitations: Ramp's procurement intake is form-driven rather than catalog-driven: employees specify vendor, item, and price manually rather than browsing a curated item list with pre-loaded contract rates, so the system cannot enforce pre-negotiated unit pricing at the point of selection for office supplies, IT peripherals, or stan …

Requirement evaluated: Hosted catalog for frequently purchased items with pre-negotiated pricing (office supplies, IT peripherals, standard software)

For a $250M technology company trying to reduce 35% maverick spend by channeling purchases toward pre-negotiated vendor relationships, Zip operates at the intake stage: every purchase request originates inside Zip, and the platform steers employees toward contracted suppliers before a free-form request can proceed. Zip's documented mechanism has two layers. First, during intake, AI supplier search automatically surfaces contracted and preferred vendors for the requester, discouraging new or off-contract supplier creation. …

Limitations: The buyer requires a procurement-team-managed internal item list with fixed per-item contract prices for categories like office supplies, IT peripherals, and standard software; Zip's documented catalog mechanism leans on supplier catalog connections and AI-driven preferred-supplier steering rather than a natively hoste …

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

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 mid-market company on Sage Intacct that authors budgets exclusively in Workday Adaptive Planning, Zip's posture is encouraging but incompletely evidenced at the enforcement layer. Zip functions as a pure enforcer, not a composer: <cite index="1-17,1-18">Zip creates a single digital checkpoint where all purchase requests must start, connecting to existing financial software rather than replacing it, acting as the front door that enforces purchasing rules companies already have.</cite> Critically, Zip has a documented integration with the buyer's exact planning tool: <cite index="41-6,41-11">the budget integration with Workday Adaptive Planning provides real-time budget visibility within …

Limitations: The Workday Adaptive Planning integration is confirmed as a real-time budget visibility layer within Zip's interface, but published documentation does not specify whether hard stops (blocking submission) or soft stops (requiring override justification with audit trail) …

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: 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: 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: Approval bottleneck analysis: which approvers are slowest, which invoice types take longest

For a $120M services company currently routing approvals through email chains with zero visibility into who is holding things up, Zip's Spend Insights module directly addresses this gap. The module tracks each request as it moves through Zip's multi-step approval workflow, logging time spent at every stage and by every approver. Zip's capability page states that the platform 'analyzes your cycle times to identify opportunities for optimizing workflows and moving requesters and approvers through the process faster,' and the Enterprise dashboard surface offers 'real-time visibility into spend volume, approver productivity, and savings.' SLA compliance is a named use case: Zip explicitly positi …

Limitations: Some users reviewing Zip's reporting suite note that the standard dashboards cover core cycle-time and approver-productivity metrics well, but teams requiring highly complex, multidimensional procurement analytics (beyond bottleneck identification) may need to export data to an external BI tool for deeper slicing. …

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: Early payment discount detection: auto-flag invoices with discount terms (2/10 net 30) and alert AP when deadline approaches

For your AP team processing 1,800 invoices per month across 6 locations, early payment discount detection requires three connected steps: extracting discount notation (such as '2/10 net 30') from invoice text, calculating the deadline date, and alerting AP before the window expires. Zip's AI invoice processing does capture payment terms as a data field during document extraction, per Zip's own blog content on AI invoice processing. …

Limitations: No help center article, product page, or technical documentation found for Zip confirms a discount-deadline calculation and AP notification feature; the gap between capturing a 'payment terms' text field and auto-flagging an expiring 2/10 window with a deadline-driven alert is material for a buyer whose team is current …

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: Custom field mapping between the AP platform and Intacct

For a $120M multi-location services company running two Intacct entities, Zip's Sage Intacct integration operates primarily as a procurement intake and vendor management layer rather than a deep AP bill coding connector. The Sage Intacct Marketplace listing for Zip documents a daily pull sync that brings Entities, Locations, Segments, and the existing vendor list from Intacct into Zip — giving the platform the structural Intacct objects it needs to route procurement requests and create new vendor records. …

Limitations: The specific requirement — mapping custom or user-defined Intacct fields (such as UDDs on AP Bills, contract codes, or supplemental vendor tags) between the two platforms — has no documented mechanism in any Zip-authored source; the integration as publicly described stops at standard Entities, Locations, Segments, and …

Requirement evaluated: SOC 2 Type II certification (current, not in-progress)

For a $120M multi-location services company with two Sage Intacct entities, SOC 2 Type II compliance is a non-negotiable prerequisite before placing financial data in any third-party AP platform. Ramp maintains a completed, current SOC 2 Type 2 audit: its public Trust Center at trust.ramp.com lists the SOC 2 Type 2 report for the period ending October 2025, available for download, alongside a SOC 1 Type 2 report, ISO 27001:2022 certification, and PCI DSS Attestation of Compliance for the same cycle. …

Limitations: The most recent publicly listed report covers the period ending October 2025; as of September 2026 that report is approximately 11 months old, within the standard 12-month validity window, but buyers should confirm the October 2026 renewal cycle report is available before contract execution if timing is tight. …

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: Clear exception categories: price variance, quantity variance, missing PO, missing receipt, duplicate, vendor mismatch

For a multi-location services company processing 1,800 invoices per month with 55% PO-based spend across two Sage Intacct entities, Ramp addresses several of the six required exception categories but not all with equal depth. Price variance and quantity variance are handled through Ramp's Overbilling Protection module, which operates at the line-item level: admins configure separate thresholds for 'Unexpectedly high unit rates' (a rate percent threshold and a rate amount threshold) …

Limitations: The buyer's requirement calls for six discrete, named exception categories that an AP clerk can triage by type; Ramp's documented model consolidates price, quantity, PO, and vendor signals into a single 'Review recommended' flag at the approval stage, which means clerks must open each flagged bill to investigate the ro …

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