Ramp

Named systems throughout, with the workflow acting across them: the procurement page states the security team approves in Jira, legal reviews in Ironclad and the workflow keeps moving in Ramp with no one switching systems, and its FAQ names accounting sync to QuickBooks Online and NetSuite, contract and eSignature tools Ironclad, DocuSign, Linksquares and Spotdraft, ticketing in Jira, Asana and Linear, and third party risk platforms Vanta and LogicGate; the pricing page's integration tiers add Xero, Sage Intacct, Acumatica, Microsoft Dynamics, Workday and Oracle Fusion Cloud plus continuous HRIS sync, and agents.ramp.com documents agents paying by card, ACH, wire, check or agent native rails with accounting context attached as money moves.

SourceRamp, ramp.com/procurement, ramp.com/pricing and agents.ramp.comread 2026-09-07

Workflow Orchestration is the procurement page's own section heading, and the surface is customer composed: a no-code workflow builder routes approvals in parallel, rules are set on budget, department, vendor type, GL code and payment type, agents are embedded inside the approval workflows the admin builds, and the run goes end to end from plain language intake through vendor research, stakeholder review, PO generation, three way match and payment. The customer composes the orchestration rather than running a fixed vendor pipeline.

SourceRamp, ramp.com/procurementread 2026-09-07

A maintained corpus that persists past any run and is queried per event: price intelligence is a named platform feature on the pricing page's vendor management tier, the procurement page has AI surfacing pricing benchmarks and contract details ahead of every renewal and delivering negotiation briefings with recommendations to extend, renegotiate or cancel, and the underlying corpus is the vendor's anonymized pricing and vendor data from millions of transactions, tailored to each customer's size and industry.

Contracts are additionally tracked from creation with terms extracted and kept on the vendor profile for audits. The benchmark corpus outlives any run and answers each new negotiation.

SourceRamp, ramp.com/procurement and ramp.com/pricingread 2026-09-07

Customers configure and operate the gates on money movement themselves, on Ramp's own surface.

On agents.ramp.com, every agent carries a human owner, a budget, merchant restrictions and an approval threshold before money moves, illustrated as approval required for payments over five hundred dollars, with only approved payment methods and funding sources usable.

Across the platform, admins build approval workflows in a no code builder with parallel stakeholder review, no spend slips through without sign off, nothing renews without sign off, and payment release approvals are a named plan feature.

SourceRamp, agents.ramp.com, ramp.com/procurement and ramp.com/pricingread 2026-09-07

Ramp's security page states that it undergoes annual SOC 2 Type II audits and abides by PCI standards, with a trust portal at trust.ramp.com linked in the site navigation. The same page documents SSO for Okta, Google and Microsoft Azure with mandatory MFA for every user, and the pricing page's user management tier names SCIM, SSO and SAML logins, custom user roles, multi entity visibility restrictions and an audit log.

SourceRamp, ramp.com/security and ramp.com/pricingread 2026-09-07

A runtime record of agent actions with attribution, on the vendor's own agent surface: agents.ramp.com states every payment and accounting sync is recorded as the agent works, every financial action stays attributed from request through reconciliation, and the illustrated ledger attributes a transaction to an agent acting on behalf of a named owner. The audit trail is a per agent property alongside identity, policy and capabilities, and an audit log is a named plan feature on the pricing page. This reconstructs what an agent did and on whose authority.

SourceRamp, agents.ramp.com and ramp.com/pricingread 2026-09-07

Neither a memory layer with a stated scope and lifetime (per agent, per user or per workflow) nor session or preference recall is documented for the agents. The durable thing on the agent surface is identity: a durable name, owner, budget and permissions per agent, which is governance and stays attributed through reconciliation, and the transaction and audit history is the application's financial record. The benchmark corpus that improves each negotiation is reference knowledge rather than agent memory.

SourceRamp, agents.ramp.com, ramp.com/procurement and ramp.com/pricingread 2026-09-07

No deployment option, hosting region or residency control is documented. Ramp is described as one cloud product, and its global tier covers card issuing, local currency payments and reimbursements, which is payment geography rather than data hosting. The privacy policy at ramp.com/legal/privacy-policy could not be read.

SourceRamp, ramp.com/security, ramp.com/procurement, ramp.com/pricing, agents.ramp.com, legal tier unreadableread 2026-09-07

Named agent families a customer adopts, each doing its own job: AP Agents are named plan features on the pricing page carrying automated fraud checks, approval recommendations and line item auto coding; Procurement Agents are AI assistants built into approval workflows handling vendor research, contract review and compliance checks, fully customizable with the customer defining the review criteria; and per agent identity on agents.ramp.com gives each its own owner, budget and permissions. The AP agents and procurement agents are each whole, shipped in different plan tiers, and adopting one does not require the other.

SourceRamp, ramp.com/pricing, ramp.com/procurement and agents.ramp.comread 2026-09-07

Several documented trigger classes. Request events: agents complete contract reviews, security assessments and compliance checks before the request hits an approver's inbox. Date events: every agreement is tracked with reminders before renewal deadlines and negotiation briefings delivered ahead of them.

Document and transaction events: invoices are two and three way matched on arrival with discrepancies flagged, card transactions are captured and matched to purchase orders automatically, and cards auto lock when required receipts are not submitted on time. Proactive flags: agreements worth renegotiating are surfaced without being asked. Requests, dates, documents and transactions together cover how work reaches the agents.

SourceRamp, ramp.com/procurement and ramp.com/pricingread 2026-09-07

Ramp's own agents run on models it does not name, and no customer or admin choice of model or routing is documented. AI Token Spend Management tracks the customer's own spend across model providers, which describes the customer's AI vendors rather than Ramp's stack, and the agent surface names outside assistants as callers of Ramp rather than models Ramp runs.

SourceRamp, ramp.com/procurement, ramp.com/pricing and agents.ramp.comread 2026-09-07

The platform is callable from outside through documented interfaces: agents.ramp.com offers connection to Ramp by API, MCP and CLI, with connection guides at agents.ramp.com/docs and payment, identity and connecting guides linked from the page, and API documentation for the platform sits at docs.ramp.com in the site wide navigation. The direction is inbound, an outside agent or customer system driving Ramp, illustrated by a third party assistant transacting on behalf of a named owner under the customer's policies.

SourceRamp, agents.ramp.com and ramp.com site navigation to docs.ramp.comread 2026-09-07

A live metric on operations that the team reads to tune the workflow: the reporting suite tracks approval efficiency, cycle times and bottlenecks in the process, purchasing data is queryable in plain language for instant answers on cycle times and PO status, and every PO is tracked against budget to improve forecasting. Nothing puts a change to the agents themselves under test; no harness, scored test set, release gate or controlled optimization loop for agent behavior is documented, and AI driven vendor compliance reviews evaluate the customer's counterparties, not the agent.

SourceRamp, ramp.com/procurement and ramp.com/pricingread 2026-09-07

Agents research each case at run time, by a mechanism Ramp does not describe: when a purchase request arrives, agents automatically research the vendor, check its compliance and security posture, and complete any evaluation the customer defines before the request reaches an approver, and Zero Touch Sourcing has the agent research vendor options against the open market and score responses.

That is per case research over sources the vendor does not control. No browser, desktop or computer control mechanism is documented, how the research is performed is not described, and no interface operation is documented.

SourceRamp, ramp.com/procurementread 2026-09-07