JAGGAER vs Ramp

Requirement evaluated: Approval bottleneck analysis: which approvers are slowest, which invoice types take longest

For a $120M services company routing 1,800 invoices per month through a 3-person AP team, JAGGAER Invoicing provides built-in dashboards that track invoice status, cycle times, and exceptions in real time. The JAGGAER Invoicing product brief explicitly names 'cycle times' and 'exceptions' as monitored metrics, and the Digital Mailroom datasheet confirms that reports track 'exception trends, approval times, supplier opportunities, and many other metrics.' The JAI AI layer adds a conversational 'Deep Research' capability through which finance analysts and AP managers can query bottleneck answers and diagnose invoice backlogs with prioritized recommendations — explicitly named use cases on JAGG …

Limitations: Your AP team's core ask — a ranked view of the slowest individual approvers and longest invoice categories — is most clearly delivered through JAGGAER's JAI Deep Research conversational AI layer, which may require a premium tier and a willingness to query results on demand rather than reading a persistent dashboard. …

Requirement evaluated: Approval bottleneck analysis: which approvers are slowest, which invoice types take longest

For your 3-person AP team processing 1,800 invoices monthly across two Sage Intacct entities, Ramp provides two overlapping but incomplete answers to the bottleneck question. First, every bill carries a per-bill activity log: Ramp documents that 'every bill has an approval history' accessible via the activity tab, capturing who approved what and when as a timestamped audit trail on each individual record. Second, the Bill Pay 'Approvals' tab gives AP administrators a real-time queue view of all bills currently awaiting approval, filterable by vendor, amount, and status, so the team can see which invoices are stalled right now. Ramp's Insights/Reports module (available on Ramp Plus) …

Limitations: Ramp does not surface a native approval bottleneck dashboard that ranks approvers by average cycle time or segments invoice processing time by type (PO vs. non-PO, utilities vs. professional services). …

Requirement evaluated: Real-time or near-real-time sync of: chart of accounts, dimensions, vendor master, PO data, and GL postings

For a $120M services company running two Sage Intacct entities, JAGGAER's invoicing module claims pre-built integrations with 'Sage' among 30+ ERPs, and its Connect infrastructure states that 'real-time syncing via JAGGAER Link and APIs' supports master-data sync and real-time GL posting writeback once an approved invoice is processed. However, JAGGAER's own Connect solutions page explicitly names only Oracle, SAP, NetSuite, and Ellucian as ERPs with ready-to-use prebuilt connectors; Sage Intacct is absent from that named-connector list. …

Limitations: The absence of a named prebuilt Sage Intacct connector means integration depth for Intacct-specific constructs (user-defined dimensions, valid-combination enforcement, entity-level vs. top-level posting) …

Requirement evaluated: Real-time or near-real-time sync of: chart of accounts, dimensions, vendor master, PO data, and GL postings

For a multi-entity Sage Intacct environment like yours, Ramp connects via Sage Intacct's Web Services API and operates as a native, two-way integration rather than a flat-file or middleware layer. The integration syncs continuously in real time, automatically keeping charts of accounts, vendors, dimensions, and transactions aligned between both systems with no manual imports or CSV uploads. Ramp pulls all Intacct dimensions, including entities, locations, departments, classes, and projects, along with any custom fields and User-Defined Dimensions (UDDs), and enforces those dimensions at the line level when posting transactions. …

Limitations: One configuration note specific to PO-matched bills: GL accounts are not coded directly in Ramp for PO-matched flows; instead, Sage Intacct maps inventory items to GL accounts via the vendor invoice transaction definition when the invoice posts to AP. …

Requirement evaluated: Automatic escalation: if approver has not acted within 48 hours, escalate to their manager with notification

For a $120M multi-location services company moving off manual email-chain approvals, JAGGAER's configurable approval workflow engine handles this requirement within its Invoicing and eProcurement modules. JAGGAER explicitly documents that escalation for stalled approvals is supported alongside delegation, parallel routing, and sequential routing: when an approver has not acted within a defined period, the system automatically escalates and notifies the appropriate next-level approver. …

Limitations: No publicly documented specification for a minimum-configurable timeout interval (e.g., whether 48 hours is a supported threshold or whether the platform enforces a coarser granularity such as 1-day or 2-day increments) was found; the buyer should confirm 48-hour precision during a demo or contract negotiation. …

Requirement evaluated: Automatic escalation: if approver has not acted within 48 hours, escalate to their manager with notification

For a multi-location services company running 1,800 invoices per month and requiring automatic escalation to an approver's manager after 48 hours of inaction, Ramp's Bill Pay approval system delivers automated reminders on a time-based cadence but does not natively re-route or escalate the approval to a different person after a deadline. Specifically, Ramp's documented behavior is a 2-day (48-hour) reminder: a direct message is sent to the vendor owner and designated approver via Slack if no action has been taken, and daily auto-reminders continue Monday through Friday thereafter. …

Limitations: For this buyer's critical requirement, the gap is material: Ramp sends a 2-day reminder to the same approver (and daily reminders thereafter) but does not automatically remove, bypass, or reassign the approval to the approver's manager on a timeout. …

Requirement evaluated: Learning capability: accuracy should improve over time on our specific vendor invoice formats

Your team currently hand-keys 1,800 invoices per month with no feedback loop; JAGGAER's Digital Capture module addresses the first stage of pre-processing (legitimacy and initial data extraction) by combining OCR with machine learning and, in the 25.1 release, computer vision and deep learning to automate field extraction from emailed and scanned invoices. …

Limitations: For a $120M services company with a stable vendor base of facilities, subcontractors, and professional services suppliers, the critical ask is per-vendor extraction learning: that correcting a misread field on a utility invoice trains the system not to repeat that error on the next bill from that same utility. …

Requirement evaluated: Learning capability: accuracy should improve over time on our specific vendor invoice formats

For a 6-location services company currently doing all extraction manually, Ramp's 'Smart OCR' module directly addresses the per-vendor learning requirement. When an invoice arrives (via email forwarding to a dedicated AP inbox or direct upload), Smart OCR identifies the vendor, then references that vendor's historical invoices already processed in Ramp and applies any saved custom instructions to extract fields more accurately on each successive invoice. …

Limitations: Smart OCR and the auto-coding learning agent require Ramp Plus (a paid upgrade from Ramp's base plan); the base plan provides standard OCR without the historical-pattern learning layer. …

Requirement evaluated: Payment approval workflow: all payment batches require CFO or Controller electronic approval before release

For a $120M services company currently executing bi-weekly check runs and monthly ACH batches with no system-enforced payment authorization, JAGGAER Pay (JAGGAER's native payments module, available as part of the JAGGAER One platform) operates as a discrete payment execution layer downstream of invoice approval. JAGGAER Pay's documented mechanism allows payable invoices to be automatically batched and scheduled based on due dates or discount dates, with approvals 'systematically implemented using robust, auditable rules' before any batch is submitted for processing. …

Limitations: The buyer's requirement is that ALL batches require CFO or Controller sign-off, with no amount threshold below which the gate is bypassed; JAGGAER's payment approval documentation confirms rules-based batch approval but does not explicitly demonstrate a universal mandatory executive gate configuration, leaving open the …

Requirement evaluated: Payment approval workflow: all payment batches require CFO or Controller electronic approval before release

For a $120M multi-location services company running bi-weekly check runs and monthly ACH batches through Ramp Bill Pay, the relevant mechanism is Ramp's Payment Step Approvals (Payment Release) combined with Payment Runs. Once enabled in Bill Pay settings, a designated Payer must explicitly release each payment before any funds are transmitted: no payment moves to ACH, check, or wire without that act. AP staff prepare a payment run grouping all due bills, and the Payer then reviews and releases the entire run at once. This directly mirrors the buyer's requirement that every payment batch require a CFO or Controller electronic sign-off before release. …

Limitations: The Finance Admin role, which Ramp's own documentation designates as the CFO/Controller role, is not currently eligible to be assigned as a Payer for payment release; the buyer's CFO or Controller would need full Admin access to serve as the mandatory payment releaser, granting them broader platform permissions than th …

Requirement evaluated: Automated PO distribution to vendors via email or vendor portal

For a $250M technology company currently routing POs manually through NetSuite, JAGGAER's eProcurement module automates PO distribution at the point of approval. Once a requisition clears configured approval workflows, JAGGAER generates a purchase order and transmits it directly to the supplier without manual intervention (JAGGAER eProcurement page: 'once approved, the system generates a purchase order and transmits it to the supplier for fulfillment'). Transmission supports multiple channels: email notification, cXML electronic document exchange, EDI, and API, giving the buyer flexibility across its 800+ vendor base regardless of supplier technical sophistication. …

Limitations: Suppliers who resist portal registration will receive POs via email only, with no structured acknowledgment mechanism back to the buyer. For the buyer's 800+ vendor base, onboarding suppliers to the portal varies by supplier willingness and technical capacity, and cXML enablement for high-volume suppliers requires a se …

Requirement evaluated: Automated PO distribution to vendors via email or vendor portal

For a $250M technology company currently routing POs entirely through manual email and NetSuite, Ramp Procurement represents a meaningful step forward but stops short of fully automated outbound delivery. When a request is fully approved, Ramp creates the PO automatically, eliminating the ops team's current manual PO-creation step in NetSuite. However, admins, approvers, and PO owners can download Ramp purchase orders into a PDF or send them directly to the vendor contact's email inbox by clicking the "More" option on a purchase order and choosing either "Send to vendor" or "Download PDF" — meaning the outbound dispatch to the vendor is a user-initiated click, not a trigger that fires automa …

Limitations: The documented "Send to vendor" flow requires a human to open each PO and click send after approval; there is no documented auto-dispatch trigger that pushes the PO PDF to the vendor's email the moment an approval chain completes, which means the ops team must still take a manual action per PO. …

Requirement evaluated: Tail spend analysis: identify high-transaction-count, low-dollar vendors for consolidation

For a $250M technology company sitting on fragmented NetSuite spend data and 800+ active vendors with no analytics layer, JAGGAER's dedicated Spend Analytics module (part of JAGGAER ONE) directly addresses this requirement. The module ingests spend data from NetSuite and any other source via REST API or SFTP feeds, then runs it through IntelliClass, which uses nine NLP and ML algorithms to classify transactions, normalize supplier records, and continuously retrain on the buyer's own data, reaching 95%+ classification accuracy. …

Limitations: The Spend Analytics module is a separately licensed component within the JAGGAER ONE suite and is priced as an add-on; the buyer should confirm it is included in any deal scope. …

Requirement evaluated: Tail spend analysis: identify high-transaction-count, low-dollar vendors for consolidation

For a $250M technology company trying to rationalize 800+ active vendors, Ramp offers two relevant mechanisms. First, its Savings Insights feature, accessible via the Insights tab, automatically analyzes transactions and proactively surfaces recommendations such as redundant subscriptions, duplicate spend, and SaaS pricing opportunities; the documented examples focus on finding redundant subscriptions, advising on better SaaS pricing, and canceling unused solutions. …

Limitations: Ramp's insights are strongest on card-based spend and SaaS subscriptions; the buyer's $30M in direct materials and significant PO/invoice-based indirect spend flowing through NetSuite (not through Ramp cards) …

Requirement evaluated: Self-service request portal where any employee can submit a purchase request without training; must be simpler than email

For a 450-person technology company currently routing purchases through email and Slack, JAGGAER's eProcurement module delivers a consumer-grade self-service intake experience via two complementary paths. First, punchout catalogs give buyers a familiar, consumer-grade shopping experience: they browse the supplier's live website, see real-time pricing and inventory, build a cart, and return it to JAGGAER for approval and PO generation, with no manual re-keying and all purchasing governance staying inside the platform. …

Limitations: For the large volume of off-contract and professional services spend that characterizes this buyer's current maverick spend problem, non-catalog requests still require the employee to manually enter item descriptions and pricing derived from a supplier quote; the system has no price for those items and places that burd …

Requirement evaluated: Self-service request portal where any employee can submit a purchase request without training; must be simpler than email

For a $250M technology company where 35% of spend currently bypasses any PO and approvals happen ad hoc over Slack and email, Ramp Procurement's self-service intake directly addresses the root friction. The mechanism has two complementary entry points, both designed for employees with zero procurement knowledge. First, 'AI Intake' lets any employee describe what they need to buy in plain language: AI Intake lets employees describe what they need in plain language, Ramp builds the request and routes it to the right approver automatically, and there are no forms to memorize and no guesswork about where to submit. …

Limitations: The intake experience requires admins to publish at least one Spend Program before employees can submit requests; if no relevant program exists, employees are directed to ask their Ramp Admin which program to use or whether one needs to be published for their purchase type, which is a light but real setup dependency. …

Requirement evaluated: Non-PO invoice routing: automatic GL coding suggestions based on vendor history and invoice description

For a $120M multi-location services company where 45% of invoices arrive without a PO, JAGGAER's native Invoice Automation module addresses this requirement directly. It recommends account codes at both header and line level for non-PO invoices, and invoices are scored against historical approval data, with configurable thresholds that determine when human review is required. The AI assistant JAI drives this: JAI scores invoices against historical approval decisions, performs intelligent PO matching, flags anomalies and high-risk lines, and assists AP staff in resolving exceptions. …

Limitations: JAGGAER's native invoicing page documents coding suggestions based on 'historical approval data' but does not explicitly describe invoice-description NLP analysis as a separate input signal; buyers should confirm during demo whether JAI's native model reads line-item description text directly or whether that capability …

Requirement evaluated: Per-vendor duplicate sensitivity configuration for vendors that legitimately reuse invoice numbers (e.g., recurring rent or utility billing)

For a 3-person AP team processing about 1,800 invoices a month, with recurring rent and utility vendors billing under repeated invoice numbers, Ramp Bill Pay's duplicate check sits at the invoice-intake step (stage 1, legitimacy). Ramp's help center says it flags a potential duplicate when the vendor name and invoice number match an existing bill (Bill Pay AP email forwarding). Its AP agents also treat a potential duplicate as a reason not to auto-create a bill, so the bill goes to manual review (AP Agents available in Ramp Bill Pay; fact sheet claim 79ed14dd on two- and three-way matching). For recurring charges, Ramp's recurring-bill templates auto-suffix invoice numbers (-2, -3) …

Limitations: I found no per-vendor duplicate-sensitivity setting in Ramp's help center, so landlords and utilities that reuse invoice numbers will be flagged on every bill and must be cleared each time. …

Requirement evaluated: Vendor performance visibility: on-time payment rate, average payment cycle, dispute frequency

For a $120M multi-location services company running 1,800 invoices per month across two Sage Intacct entities, JAGGAER's relevant mechanism spans three modules rather than a single AP-side vendor performance dashboard. The Spend Analytics module offers the closest match to on-time payment monitoring: 65+ pre-built Tableau dashboards cover spend, savings, supplier, and category performance, and the module explicitly tracks payment-term adherence and off-contract leakage. …

Limitations: No documented mechanism delivers all three buyer-required metrics (on-time payment rate, average payment cycle, dispute frequency) as calculated, per-vendor historical analytics in a single AP-oriented view; the closest capabilities are spread across Spend Analytics (payment-term adherence), JAGGAER Pay (real-time paym …

Requirement evaluated: 1099 preparation: automated classification, threshold tracking, and electronic filing

For your 45% non-PO spend (professional services, subcontractors, insurance) and the PO-based subcontractors across 2 Sage Intacct entities, Ramp runs 1099 prep in the vendor and payment layer, ahead of ERP posting. Ramp states that it applies a Bill Pay spend threshold by tax year when automatically determining 1099 eligibility: at least $600 for tax years through 2025 or at least $2,000 for tax year 2026. GL accounts map to 1099 boxes through rules you create in settings (Add Box, choose GL accounts, map them to a 1099 box), and the fact sheet says bill pay spend is mapped to 1099-NEC and 1099-MISC boxes and can be filed directly with the IRS and eligible states. …

Limitations: Sage Intacct 1099 status is documented as only syncing from Sage to Ramp, so your Intacct vendor flags must be kept accurate in Intacct, and Ramp-side changes will not write back. Filing is limited to 1099-NEC and 1099-MISC for Bill Pay customers. …

Requirement evaluated: SOC 2 Type II certification for the platform

For a $250M technology company with CFO-level compliance scrutiny, JAGGAER meets the SOC 2 Type II bar at the platform level. JAGGAER's own solutions and Procure-to-Pay pages explicitly list 'SOC 2 Type II audited' as a security credential alongside ISO 27001, applying to the JAGGAER One suite. Their dedicated certifications page confirms the SOC 2 report evaluates controls across Security, Availability, and Confidentiality using the AICPA's Trust Services Criteria, and that the report is available on request to prospects who sign an NDA and to existing customers under their agreements. …

Limitations: The publicly available documentation does not enumerate which specific modules are in scope for each SOC 2 audit period; buyers should request the current report under NDA during due diligence to confirm that the procurement modules they intend to deploy (e.g., eProcurement, Supplier Management, Invoicing) …

Requirement evaluated: Configurable retention policies aligned with our 7-year record retention requirement

For a $250M technology company needing to enforce a 7-year procurement record retention schedule, Ramp's approach is primarily passive storage rather than configurable policy enforcement. Ramp's Audit History help center confirms that 'all your transaction data and receipts are securely stored as long as you remain an active customer,' and the platform captures a full audit trail covering receipts, approvals, coding decisions, and payment records that can be exported at any time filtered by date range, department, vendor, or cost center. …

Limitations: Ramp's retention guarantee is tied to active customer status with no documented configurable minimum-floor policy, meaning there is no in-platform control that prevents premature deletion or enforces a 7-year window per record type; the buyer's compliance obligation would rest on NetSuite or an external archive rather …

Requirement evaluated: SSO integration with Microsoft Azure AD

For a multi-location services company whose AP team and internal approvers authenticate via Microsoft Azure AD, JAGGAER ONE supports federated SSO by accepting Azure AD (Microsoft Entra ID) as an external identity provider. JAGGAER ONE allows organizations to integrate their own identity provider via standardized authentication protocols: SAML or OpenID Connect, for seamless single sign-on to the JAGGAER solution. At the configuration level, the buyer's IT administrator registers JAGGAER as an enterprise application in Azure AD and exchanges metadata; JAGGAER then acts as the SAML/OIDC service provider (SP), deferring all credential validation to Azure AD. …

Limitations: Only SP-initiated SSO is supported, meaning users must navigate to the JAGGAER URL first rather than launching it from the Azure AD MyApps portal tile, which is a minor UX gap but does not affect centralized identity governance. …

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: Automatic match-and-pass for invoices within tolerance, reducing AP workload to exceptions-only review

For a $250M technology company moving from email-and-Slack approvals to systematic AP automation, JAGGAER's Invoicing module (part of the JAGGAER One platform) delivers the full three-way matching and auto-pass workflow this buyer needs. Invoices arrive via portal, EDI, cXML, OCR, or PEPPOL and are standardized into structured fields; the system then compares each invoice against its PO and goods receipt using 2-way, 3-way, or n-way matching with configurable price and quantity tolerance bands set by the organization. …

Limitations: Tolerance band configuration and invoicing workflow setup are performed during implementation by JAGGAER's team rather than being fully self-service for the buyer's admin; changes to matching rules typically require coordination with JAGGAER support or a project manager, which may slow iteration as the buyer's process …

Requirement evaluated: Service receipt: time-based or milestone-based confirmation for professional services engagements

For a $250M technology company with significant professional services spend, Ramp's coverage stops at 2-way matching for services. Ramp's own Quick Start Guide explicitly positions its matching options as: 2-way match (invoice amount against PO, vendor) for software and services, and 3-way match for physical goods only — the 3-way match mechanism is built around quantity-based item receipts tied to inventory line items, not service delivery confirmation. …

Limitations: For the buyer's professional services engagements (consulting, marketing agency, outsourced development), Ramp provides no dedicated service receipt mechanism: an approver's manual checklist checkbox is the only available proxy for delivery confirmation, and it carries no structural link to the time period billed or th …

Requirement evaluated: Centralized supplier database with self-service onboarding portal: vendors enter their own info, upload W-9, insurance, banking

For a $250M technology company moving away from email-based purchasing and managing 800+ active vendors, JAGGAER's Supplier Management module provides exactly the centralized supplier database and self-service onboarding portal the buyer requires. Vendors receive an invitation and self-register through a dedicated supplier portal: they enter company information, provide tax details, and upload compliance documents without buyer-side manual data entry. …

Limitations: The supplier portal is free to suppliers, but the full Supplier Management and onboarding workflow capabilities sit within JAGGAER's broader source-to-pay platform, so the buyer will need to confirm which specific tier or module covers their required onboarding configuration depth (e.g., custom questionnaires, insuranc …

Requirement evaluated: Contract repository: store agreements, track renewal dates, alert stakeholders 90/60/30 days before expiration

For a $250M technology company currently tracking contracts in email and shared folders, Ramp's dedicated Contracts & Renewals module provides a native repository inside the procurement workflow. It gives customers a single place to create, upload, import, and manage contracts; monitor key dates like contract end and last date to action; and take follow-up actions such as requesting a renewal, requesting an expansion, or marking a contract as renewed or not renewed. …

Limitations: An older Ramp help article on vendor documents describes standard reminders as only 30 and 60 days to the Vendor Owner; the newer Contracts & Renewals module explicitly supports 90-day configuration, so buyers should confirm they are on the current Procurement add-on module and not the legacy vendor document workflow. …

No public documentation covering this requirement was found on the documentation sources this vendor publishes. That is a limit of the public evidence, not a finding about the product.

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

For your move from email and Slack approvals plus manual PO keying in NetSuite, JAGGAER eProcurement uses prebuilt connectors in JAGGAER Link, which JAGGAER says lets approved purchases write back to your ERP, with NetSuite on the named connector list. Under the hood, JAGGAER's integration documentation lists a Purchase Order Export (including PO changes) to the client ERP system, plus a Purchase Order Status import for closed or canceled orders. For payment status, the JAGGAER Indirect API includes a method that imports updated invoice payment status (In Process, Payable, Paid, or Cancelled) and payment details. …

Limitations: The public material does not give a NetSuite-specific field map or confirm whether the NetSuite connector uses the same export and status-import calls as the generic API document. …

Requirement evaluated: Budget data pulled from NetSuite for real-time budget enforcement

For a $250M technology company running NetSuite, Ramp's native integration pulls NetSuite's structural dimension data (accounts, departments, classes, locations, custom segments) into Ramp and uses those as the foundation for its Budgets module. Ramp pulls in every account, department, class, location, and custom segment from NetSuite, so budget lines can be mapped to the same dimensional hierarchy the buyer already uses in their ERP. Ramp Budgets tracks plan vs. …

Limitations: The buyer's requirement is for budget data pulled from NetSuite to drive enforcement; Ramp's Budgets module uses NetSuite's dimensional structure (departments, GL accounts) …

No public documentation covering this requirement was found on the documentation sources this vendor publishes. That is a limit of the public evidence, not a finding about the product.

Requirement evaluated: Category-based shopping with visual interface; not just a search box

For a $250M technology company looking to move its 450 employees away from email-based purchasing, JAGGAER ONE eProcurement presents requesters with a configurable Shopping Home Page that goes well beyond a search box. The homepage features a 'Showcase' section displaying visual supplier and catalog tiles, allowing employees to click directly into punchout or hosted catalog experiences without needing to know a supplier name or item number. The Shop area lets users enter goods or services via the search bar, or click on the supplier tiles in the Featured Suppliers section to browse products from catalogs with pre-negotiated pricing. …

Limitations: The primary visual layer in JAGGAER's shopping homepage centers on supplier-logo tiles ('Featured Suppliers') rather than pure spend-category tiles (e.g., 'IT > Hardware > Laptops'); buyers who want a consumer-app-style category drill-down independent of supplier identity may need to configure product taxonomies carefu …

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 …