Airbase vs Ramp

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

For your scenario of approving monthly telecom bills across 6 locations, Airbase offers two relevant but incomplete mechanisms. First, the platform supports recurring bill creation: you can make recurring payments to a vendor on Airbase, and this option will create bills on a recurring basis for that vendor, which automates bill generation on a schedule so your 6 telecom invoices arrive without manual data entry each month. Second, bills are routed automatically to the right approvers and observers based on subsidiary, department, vendor, and amount, meaning approval policy rules can target a specific vendor and send all its bills to the same approver. …

Limitations: The buyer's AP team will still open and action each of the 6 location-level telecom bills one at a time at the approval stage; the recurring creation and vendor-based routing rules reduce setup friction but do not compress the approval touchpoints into a single action the way a documented bulk-approve-bills mechanism w …

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 recurring telecom bills from the same vendor across 6 sites, Ramp's Bill Pay module supports batch approval through two complementary mechanisms. First, the 'For approval' queue supports a checkbox multi-select UI: approvers can approve multiple bills at once by selecting the check box to the left of the bills on the Bill Pay > For approval tab, enabling a single approver action to clear all pending telecom bills in one step rather than opening each individually. …

Limitations: Only bills formally set up as a recurring series appear in the Recurring Bills panel; Ramp does not automatically detect recurring payment patterns from individually created bills, so telecom invoices arriving as separate PDFs across 6 locations will appear as individual bills unless deliberately configured as a series …

Requirement evaluated: Real-time AP dashboard: invoice aging, approval queue depth, processing cycle time, spend by vendor/category/entity

For your 3-person AP team handling about 1,800 invoices a month across 2 Sage Intacct entities, Airbase's reporting sits on top of Bill Payments, after invoice capture and before the Intacct sync. Airbase says its unified platform delivers real-time visibility into spend. In Bill Payments, a Pending Bills report lists bills waiting for approval, and it names the pending approvers. The same help article lists Export Pending Bills, Export All Bills, Export Aging Reports and Export Unpaid Bills. …

Limitations: The documented AP aging, unpaid and pending views are export-based reports. The Pending Bills export is still labeled beta. I found no help-center documentation of a live AP dashboard with aging buckets, approval queue depth, or processing cycle time (receipt to approval to payment), so the buyer would need to confirm …

Requirement evaluated: Real-time AP dashboard: invoice aging, approval queue depth, processing cycle time, spend by vendor/category/entity

For your 3-person AP team handling about 1,800 invoices a month across 2 Sage Intacct entities, Ramp Bill Pay gives you live status views and a report builder. These sit after invoice capture and approval routing (pre-processing stages 1 to 5) and before posting and payment. Bill Pay opens on an Overview that organizes bills by status, with tabs for Overview, Drafts, For approval, Payment required, In-flight, and History. An "Awaiting approvals" status filter shows bills in the approval flow, and vendor and vendor-owner filters are also available. That gives you a working approval-queue view, but it is a filtered list rather than a documented queue-depth metric. …

Limitations: I found no documented bill-level cycle-time or time-in-stage report, so measuring invoice-received-to-paid or approver bottlenecks will likely need an export or a custom report you build and validate in a demo. The AP aging report is generated as a download (ZIP or CSV) …

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

For your 3-person AP team paying subcontractors, landlords and professional-services vendors out of two Sage Intacct entities, Airbase covers the intake end of 1099 work. It does not cover classification, threshold tracking or filing. In the vendor portal, vendors upload a tax form such as a W-9 and the system scans it and auto-fills legal name and tax ID. The help article also says the system validates the Tax ID with government records to support reporting requirements such as 1099. Airbase's AP page describes AI-powered W-9 collection and validation that make 1099 reporting more efficient. That covers the vendor-legitimacy and tax-data step before invoices are posted. …

Limitations: Airbase's documented 1099 support stops at W-9 collection and TIN validation. Classification, threshold tracking and e-filing across your two entities would still run in Sage Intacct or a separate filing service, so your team would not get a single in-tool 1099 workflow. …

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

For your 3-person AP team filing 1099s across 2 Sage Intacct entities, Ramp covers the full chain inside Bill Pay. A vendor is automatically marked 1099 eligible when bill payments reach the threshold ($600 for tax years through 2025, $2,000 for 2026) and the federal tax classification is not a corporation, international or other excluded type. Bills paid by card are excluded, and bills paid manually outside Ramp are included. AP can manually override the toggle on a vendor profile, and once overridden Ramp stops auto-updating it. …

Limitations: Threshold tracking is based on Bill Pay spend, so check runs and ACH batches paid outside Ramp only count if recorded as manually paid bills, and card-paid bills are excluded. The Sage Intacct 1099 eligibility sync is one-way from Sage, so you need to decide which system owns the 1099 flag. …

Requirement evaluated: Payment reconciliation with automatic journal entries back to Sage Intacct

For a 3-person AP team moving 1,800 invoices per month across two Sage Intacct entities, Airbase handles payment reconciliation through a documented bi-directional sync architecture. When a bill payment is executed in Airbase (ACH, check, or virtual card), Airbase writes the payment back to Sage Intacct as a paired Bill plus Payment record, automatically clearing the open payable in the AP subledger and posting the corresponding cash or clearing account entry without manual re-keying. …

Limitations: The full body of the 'Sync Bill Payments to Sage Intacct' help article was not rendered by search, so the precise field mapping (payment date, reference number, clearing account designation) …

Requirement evaluated: Payment reconciliation with automatic journal entries back to Sage Intacct

For your two-entity Sage Intacct environment, Ramp Bill Pay creates the AP bill directly in Sage Intacct when an invoice is processed, then automatically syncs a bill payment record back to Sage Intacct once the payment is executed; no manual re-keying is required. Per Ramp's Bill Pay accounting documentation, 'Ramp automatically syncs bill payments to your accounting software once the bill has been paid,' with the payment date tied to when funds leave your bank account. Each Sage Intacct entity gets its own configured cash account mapping in Ramp, so the debit to the cash account and the credit clearing the AP liability post to the correct subsidiary ledger automatically. …

Limitations: For payments initiated entirely outside Ramp's payment rails (for example, checks your team prints and mails through your bank without using Ramp), the automatic payment sync depends on the two-way status sync detecting the change in Sage Intacct, which runs on a scheduled refresh cycle rather than in real time; ACH, w …

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

For a services company processing 1,800 invoices per month across recurring vendor categories like rent and utilities, Airbase provides system-level duplicate invoice detection: the platform automatically flags potential duplicate invoices by comparing attributes including invoice number, vendor, and amount at the time of bill creation. This operates during the pre-processing legitimacy check (Stage 1 of the pre-processing journey) before a bill is posted to Sage Intacct. …

Limitations: For this buyer's 45% non-PO invoice mix, which includes utilities, subscriptions, and insurance policies that commonly reuse invoice numbers on a recurring cycle, Airbase's uniform duplicate detection will generate false-positive flags on legitimate invoices with no documented per-vendor override or sensitivity configu …

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: Board-ready spend reports: quarterly spend summary by category with trend lines and vendor concentration metrics

For a $250M technology company currently flying blind with 35% maverick spend, Airbase's dedicated Spend Analytics module (launched June 2024) aggregates data across all three spend channels: accounts payable, corporate cards, and employee expenses, giving it the full spend footprint needed to reflect reality rather than just PO-backed transactions. The module surfaces spend broken down by department, vendor, subsidiary, and category with trend visualization across time periods, and users can filter by custom date ranges including quarterly windows. …

Limitations: For this buyer's CFO and board audience, the material gap is in the final presentation layer: Airbase does not appear to produce natively formatted, board-ready quarterly packages (PDF or slide-ready export with branded formatting and concentration metrics pre-calculated); finance staff will likely need to export raw d …

Requirement evaluated: Board-ready spend reports: quarterly spend summary by category with trend lines and vendor concentration metrics

For a $250M technology company moving off email-and-Slack approvals with 35% maverick spend, Ramp addresses this requirement through two interconnected reporting layers. First, its real-time reporting module lets finance admins build saved reports, organize them into custom dashboards, and track spend across Cards, Reimbursements, and Bills, with the ability to reuse saved reports, share individual reports with teammates, and export report data. Critically, this covers the full spend universe that matters here: card spend, AP/bill pay, and reimbursements, so maverick card spend is not excluded from category roll-ups. …

Limitations: The buyer's CFO will need to manually assemble individual CSV report exports into a board-formatted deck, since Ramp does not document dashboard-level PDF/PPT export or scheduled quarterly delivery of a packaged board summary to named recipients; the concentration and trend data is present in the system, but the final …

Requirement evaluated: Support for Sage Intacct dimensions: Location, Department, Class, Project, Customer, and custom dimensions

For your two-entity Sage Intacct environment, Airbase codes invoices (bills) using a system of Line Level Tags and Transaction Level Tags that map to Sage Intacct's dimension fields. The bill export documentation explicitly lists Department and Location as Sage Intacct-specific dimension fields carried on bill transactions, and a separate help article confirms that Sage Intacct users can set Project as a GL line-level tag, meaning Project coding can be applied per invoice line to support split allocations across your 6 locations and subcontractor projects. …

Limitations: Airbase's documented Sage Intacct dimension coverage is limited to Department, Location, and Project; Class, Customer, and any user-defined/custom dimensions the buyer has configured in Sage Intacct are not documented as supported in the bill coding or sync workflow, meaning those dimensions would require manual coding …

Requirement evaluated: Support for Sage Intacct dimensions: Location, Department, Class, Project, Customer, and custom dimensions

For a $120M multi-location services company running 2 Sage Intacct entities, Ramp Bill Pay connects to Sage Intacct via a direct API integration and pulls the buyer's own dimension schema into Ramp's coding interface at setup. The Sage Intacct overview in Ramp's help center states that the dimensions displayed in the Ramp Accounting screen are determined by the buyer's Sage Intacct configuration, meaning Location, Department, Class, Project, and Customer are all surfaced if they exist in the connected instance. Beyond those standard dimensions, Ramp explicitly pulls user-defined dimensions (UDDs) …

Limitations: One minor constraint: any Sage Intacct custom field named 'restricted' cannot be pulled because 'restricted' is a reserved word in Sage, though this is unlikely to affect standard AP configurations. …

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

For a $120M multi-location services company evaluating security posture before committing to an AP automation platform, Airbase (now operating under Paylocity following acquisition) maintains an annually renewed SOC 2 Type II attestation conducted by independent, reputable CPA firms. The official Airbase security policy page states that audits cover controls related to financial reporting, security, confidentiality, and availability, with each control tested for both design appropriateness and operating effectiveness. …

Limitations: Because Airbase was acquired by Paylocity relatively recently, buyers should confirm during the sales process that the SOC 2 Type II report scope explicitly covers the Airbase spend management modules (AP automation, bill pay, guided procurement) …

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

For a $120M multi-location services company handing sensitive vendor and payment data across two Sage Intacct entities, SOC 2 Type II certification is a threshold security requirement before any AP automation vendor is considered. Ramp holds a current, completed SOC 2 Type 2 audit: the trust center at trust.ramp.com publishes a SOC 2 Type 2 report with an audit period ending October 2024, available for download after an NDA is signed via the SafeBase-powered portal. …

Limitations: The SOC 2 Type 2 report covers the audit period ending October 2024; the buyer should confirm at contracting time that a refreshed report covering the current period is available, and should request the report scope documentation to verify that the Bill Pay and AP workflow modules are within the audit boundary (not jus …

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

For a $250M technology company currently tracking zero contracts systematically, Airbase's Vendor Management module provides a meaningful starting point. Each vendor profile stores contracts, insurance certificates, and tax documentation centrally, and the platform's dedicated 'renewals' feature provides automated renewal planning with stakeholder notifications. A third-party review of the module documents that automated alerts fire at 30, 60, and 90 days before contract or document lapse, matching the buyer's required cadence. …

Limitations: The buyer's requirement for a true contract repository (searchable by metadata, with lifecycle status, expiration-date fields, and configurable multi-stakeholder alert rules) …

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

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

For a $250M technology company that currently has no system-enforced record preservation, Airbase does automatically capture and store a comprehensive audit trail for every spend event: purchase requests, PO approvals, invoice activity, card transactions, and reimbursements. According to Airbase's own audit trail feature page, the platform captures transaction details as they happen and records them to 'an easily retrievable audit trail,' covering all purchase transaction elements regardless of payment method. The audit trail also syncs bidirectionally to the connected ERP (NetSuite in this buyer's case), so the general ledger receives a complete, audit-ready record of each event. …

Limitations: The buyer's requirement is not just record creation but enforced, configurable retention: a guarantee that POs, invoices, and approval logs cannot be deleted or become unavailable before 7 years have elapsed. …

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: Service receipt: time-based or milestone-based confirmation for professional services engagements

For a $250M technology company processing significant professional services spend, Airbase approaches service receipt confirmation through two layered mechanisms rather than a dedicated service receipt document type. First, the Guided Procurement module allows admins to configure milestone-based approval checkpoints across the procurement lifecycle: admins set milestones per spend category, and milestone completion triggers stakeholder notifications and sign-off requirements before the process advances. …

Limitations: The milestone system in Guided Procurement is primarily an intake and pre-purchase approval control; Airbase does not document a purpose-built service receipt document type that natively slots into the receipt leg of 3-way match for professional services, nor a time-based (e.g., monthly period attestation) …

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: Budget data pulled from NetSuite for real-time budget enforcement

For a $250M tech company replacing email-and-Slack approvals with a formal procurement system, Airbase offers genuine pre-approval spend controls through its Spend Controls module: finance administrators configure hard-block and soft-warning policies, spending limits by role and expense type, and card-level limits on virtual and physical cards, all of which fire at the point of requisition submission or card use. The NetSuite integration is deep and bi-directional for GL coding: Airbase pulls chart-of-accounts dimensions (departments, classes, custom segments) …

Limitations: The budget enforcement mechanism in Airbase is configured within Airbase, not pulled live from NetSuite's budget records, so the buyer cannot use NetSuite as the single source of truth for budget limits. …

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: Confidence scoring on extracted data so AP clerks know which fields to verify vs. which are high-confidence

For your 3-person AP team processing 1,800 invoices per month, the relevant question is whether Airbase surfaces per-field confidence scores so clerks know exactly which extracted values to verify rather than checking every field on every invoice. Airbase's bill capture module uses AI-powered OCR and machine learning to auto-fill key invoice fields such as vendor name, invoice date, amount, and line items, and applies ML-based predictive GL coding that learns from past coding corrections. …

Limitations: No evidence was found in Airbase's help center, product documentation, or any third-party review that Airbase presents per-field confidence percentages or visual confidence indicators to AP clerks during invoice review; clerks would need to rely on their own judgment to determine which auto-extracted fields require ver …

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

For a multi-location services company forwarding emailed invoices and uploading scanned mail, Ramp Bill Pay's OCR engine automatically ingests documents via an AP forwarding email address or direct drag-and-drop upload, then parses and pre-fills a draft bill within roughly 30 to 60 seconds. At the base OCR tier, the system extracts vendor name, invoice number, due date, payment account details, and line items. The Smart OCR tier (available on Ramp Plus) …

Limitations: Payment terms are not extracted from the invoice as a structured term string (e.g., '2/10 Net 30' with an early-pay discount trigger); instead, Ramp captures the due date via OCR and stores net day terms on the vendor profile, so early-payment discount terms printed on the invoice face would not be parsed into actionab …

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

For a finance team that wants PO amendments to go back for approval only when they grow more than 10% or $5,000 over the original, Airbase has approval rules but nothing documented that works on the size of the change. Airbase Approval Policy rules combine conditions (for example, department and a spend amount such as 'greater than or equal to USD 500') with an ordered list of approvers. POs created in Airbase can go through the approval cycle if the Approval Policy dictates it, and requests go to approvers in the order listed in the rule. Policies for purchase orders can be specific to a department, spend threshold, or expense category. Airbase works at the PO request and approval stage, then bill matching and receipts. Receipts are created against POs, and PO and receipt details sync to NetSuite every 6 hours. I found no public help article describing a change-order or amendment flow that compares the amended total to the original PO and re-triggers approval on a percentage or dollar variance.

Limitations: Approval thresholds are set on a spend amount. The public documentation does not show a condition for 'amended total exceeds original by more than 10% or $5,000', so the buyer would likely need a workaround. That could be a threshold on the new total, or a manual re-request or Workflow Builder process. The documentation also does not say what happens to approval status when an already-approved PO is edited.

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: Link request to existing contract when applicable (e.g., ordering under a blanket PO or master agreement)

For your $250M technology company trying to eliminate maverick spend and ensure purchases reference existing agreements, Airbase's Guided Procurement module operates at the intake stage but does not offer a native contract repository that auto-surfaces existing blanket POs or master agreements when a requester selects a known vendor. What Airbase does provide is a configurable, no-code intake form that can collect and route contract documents: the Guided Procurement overview sheet states that 'requirements for each business group, like SOC attestations, tax information, or contracts flow automatically to stakeholder systems,' meaning an admin can build a custom intake field prompting the req …

Limitations: Airbase has no native contract repository, so there is no mechanism to automatically surface an existing blanket PO or master agreement when a requester picks a vendor during intake: a requester must manually know an agreement exists and attach it themselves, which does not reliably prevent off-contract ordering. …

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: Mandatory legal review routing for all software and professional services purchases over $25K

For a $250M technology company routing software and professional services purchases over $25K to legal, Airbase delivers this through two complementary modules: Advanced Approvals and Guided Procurement. In Advanced Approvals, admins build conditional 'When...then...' rules where the trigger conditions can combine spend type (e.g., software, professional services) and dollar amount, automatically routing to a named Legal approver or Legal approval group before the request advances. …

Limitations: Airbase's documentation describes the enforcement model as policy-configured rather than system-hardened: whether legal approval can be administratively overridden or delegated away by a super-admin is not explicitly addressed in the available documentation, so the buyer should confirm during a demo that the legal node …

Requirement evaluated: Complete audit trail meeting SOX-adjacent control requirements for our IPO preparation

For a $250M company preparing for an IPO, Ramp offers a multi-layered audit infrastructure that covers most SOX-adjacent controls but has documented gaps in completeness. The central mechanism is a dedicated Audit Log in company settings: it is described as "a consolidated place to track all actions made by Ramp and fellow teammates across Ramp," explicitly framed to help companies "Stay SOX Compliant" and "keep track of key changes such as changes made to bank account information, vendor information, etc." The log covers a canonical catalog of approximately 200 tracked actions (e.g., "Sign in," "Request revision," "Reimbursement paid") with event-specific metadata including actor vs. …

Limitations: The audit log has a documented coverage gap: "not all admin actions are currently tracked in the audit log, including some integration setup events and older administrative behaviors," and Ramp instructs users to assume untracked actions simply are not captured. …