Ramp vs Stampli vs Concur for AP Automation

For a company running 2 Sage Intacct entities today and planning to add a third, Ramp operates through a single Ramp instance connected to one Sage Intacct accounting connection. Each legal entity is configured inside Ramp's Company > Entities settings, where it receives its own subsidiary mapping to the corresponding Intacct entity, its own bank account for bill payments and reimbursements, and its own coding rules and sync settings. Ramp allows customers to add all business entities within a single instance; each entity can have its own subsidiary mapping, payment settings, and sync settings, with statement payments generated individually per entity and a single batch sync covering transactions and reimbursements across all entities. Adding the planned third entity is self-service: existing customers can access bulk entity creation at any time from Company > Entities > Bulk Add, and if Sage Intacct is already connected, Ramp imports subsidiary entities automatically for selection. At the field level, Ramp pulls in custom fields from the Sage Intacct configuration and any UDDs, so entity-specific coding dimensions are available within Ramp. The Sage Intacct Marketplace listing confirms transaction splitting and real-time sync across multiple entities with support for unlimited subsidiaries. Each entity can also maintain a separate chart of accounts: each Ramp entity maps to a corresponding entity or subsidiary within the ERP, each entity/subsidiary can use its own chart of accounts and coding structure, and transactions sync to the correct accounting system using entity-specific account mappings. This multi-entity capability is available on Ramp Plus and Ramp Enterprise (not the free tier).

For a company operating 2 Sage Intacct entities today and planning a third, Concur's Sage Intacct integration via its Financial Integration Service (FIS) connects a single Concur company to multiple Intacct entities without requiring separate Concur accounts per entity. The official SAP Concur listing on the Sage Intacct Marketplace documents that customers can sync at the Intacct Top Level or connect up to 10 entities to one SAP Concur company, well above the buyer's current and planned scope. During setup, Concur automatically pulls account codes, dimension lists, and vendors directly from Sage Intacct, and approved invoices post back to the Intacct Accounts Payable module in near real-time with posting confirmation fed back to Concur. A recent help.sap.com release note titled 'Top Level Disabled When Reconnecting to Sage Intacct' confirms that when reconnecting a multi-entity Intacct environment through FIS, the connection operates at the entity level rather than the top level, meaning each entity's books remain correctly segregated during posting.

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.

For your 2 Intacct entities (with a third coming), Stampli connects once to Intacct through a Web Services user and syncs both the top-level organization and entity data, including vendors, GL accounts, locations and POs, into a single Stampli account. Stampli uses a Web Service User to automatically sync top level organization and entity data into Stampli. Stampli mirrors Intacct's multi-entity hierarchy in one unified platform and imports and enforces the same entity-level user restrictions configured in Intacct. Invoices can be routed to the right entity at intake by emailing an entity-specific alias, and when entity keys change or new ones are added, you simply use the new key in the alias. Stampli also states that coding structures, approval workflows and vendor lists can be configured per entity, and that its ERP integration syncs new entities along with their vendor lists, coding practices, and approval workflows. That means a third entity is added in Intacct and then synced, not re-implemented. This covers pre-processing stage 5 (entity and cost allocation) and approval routing, which can route on subsidiary, among up to five conditions (vendor, GL account, subsidiary, department, location, amount). On payments, Stampli Direct Pay for Intacct multi-entity customers adds a required Paying Location selector that drives the available bank accounts and payment methods (Stampli help center, Multi-location payments for Sage Intacct). The 15,000 entities across Stampli's customer base and the 71-location Advance Financial example show the model works at scale.

For your AP team of three processing 1,800 invoices/month across two Intacct entities, Ramp's reporting covers part of the KPI set but leaves material gaps on several of the five metrics you named. On the coverage side: Ramp's Reporting module (under Insights > Reports) lets you build and save custom reports organized into dashboards, tracking spend across Cards, Reimbursements, and Bills. Bill payments are also surfaced in the Accounting and Insights tabs. The Bill Pay approval workflow logs a detailed audit trail so you can monitor who approved what and when, and you can view a bill's individual approval history via the Activity tab on each bill. The bill-level CSV export includes invoice date, due date, payment scheduled date, entity, vendor, and status fields, alongside accounting category, project ID, department, and sync codes, which means approval cycle time could be reconstructed externally by computing the delta between invoice date and payment date. For accounting-firm advisor users specifically, the Advisor Console's Reporting tab includes an Efficiency section showing time to approval and completion across Ramp tasks, and an AP Reporting section covering AP aging, outstanding bills, and AP spend stats -- however this panel is scoped to the advisor console experience and is not documented as a direct-customer-facing KPI dashboard. On the gaps: touchless rate (the share of invoices that flow through without human touch) is not a documented native bill-level metric; the closest analogue is the Policy Agent dashboard, which tracks accepted approval recommendations and agent alignment under Insights > Reports > Policy, but that applies to card/expense policy enforcement, not invoice AP workflows. Cost per invoice is not computed by Ramp at all -- no staffing cost inputs exist in the platform. Most critically for your requirement, Ramp does not currently support configuring structured early payment discount terms on vendor profiles or bills; net payment terms set the due date but do not include a discount component, which means discount capture rate cannot be tracked natively.

For your 3-person AP team running about 1,800 invoices a month across 2 Intacct entities (soon 3), Stampli's Dashboards & Reports area is the in-product place to track KPIs, and it sits in the pre-processing stage between invoice arrival and ERP export. The Invoice Lifecycle Dashboard shows average lifecycle time, average time at each stage (Coding & Routing, Invoice Approvals, authorized for payment), and rejected and canceled invoices with top rejection reasons. The User Productivity Dashboard shows average approval time per approver and trends, and the In Process Dashboard shows invoices pending approval by number of days (Stampli help center, Invoice Lifecycle, User Productivity and In Process dashboard articles). Every KPI can be filtered by Source, Entity (Company or Subsidiary) and Vendor, so your Intacct entities can be viewed separately or together, and results can be downloaded as CSV or XLSX (Stampli help center, Identify Approval Delays). On discounts, Stampli applies vendor credits and early-payment discounts at payment creation, but the documentation I found does not show a discount capture rate KPI. Stampli lists 12 pre-built reports and interactive dashboards as included.

For your 3-person AP team handling 1,800 invoices a month across 2 Intacct entities, Concur's KPI tracking runs through Intelligence, its embedded reporting tool. Intelligence is described as a fully customizable reporting tool embedded within the Concur platform, with editable or custom reports plus scheduled report and dashboard distribution. Approval timing is covered by prebuilt content: an Invoice Cycle Time Segments report showing the average time an invoice spends at each stage of the payment lifecycle, and Workflow Cycle Time reports (Invoice > Workflow Cycle Time Details) that identify bottlenecks. The Top 10 Longest to Approve report ranks the slowest approvers by name, and an Invoice Spend Management Overview dashboard shows metrics for the invoice process. Concur operates at stages 2 to 4 of the pre-processing journey; its matching compares invoices to purchase orders and goods receipts and displays exceptions. Intacct sync relies on partner connectors such as Wipfli's InvoiceConnect, which accommodates multi-currency, multi-entity and inter-company. A separate Intacct marketplace listing says customers can sync at the Top Level or up to 10 entities to one SAP Concur company, so a third entity is not a problem. The fact sheet's own claims are broad (spend visibility tools to automate AP end to end) and name none of your five KPIs.

For your 3-person AP team keying about 1,800 invoices a month into Sage Intacct, Stampli handles card spend in the same workspace as invoices. When a Stampli Card transaction is authorized and settled, an invoice is created automatically for it. It carries the cardholder as owner, the merchant, the amount, and any predefined coding. Billy then suggests the vendor, and the cardholder uploads or matches the receipt (Stampli help center: Process Stampli Card Transaction as Invoices). Stampli's documentation says AP can process card transactions with the same workflow as invoices. It adds configurable approval levels (up to three, with multiple approvers per level) and pre-coded cards. It also syncs the transactions to the ERP with the same frequency as invoice data, typically within 24 hours (Stampli help center: Stampli Card in Procurement). Where Intacct coding needs more than a standard expense layout, Stampli directs those cards to be set up as AP cards so they follow the standard invoice workflow (Stampli help center: Expense Approval Workflow, Roles, and User Properties). This covers cost allocation (stage 5) and approval of card spend, with the same audit trail. Stampli lists Sage Intacct among its supported ERPs, and the vendor says approval and accounting context carries through payment.

For your 1,800 invoices a month across 2 Intacct entities (a third planned), Ramp puts cards and AP in one platform, so card spend is not a separate system. Card transactions are coded, with Ramp suggesting coding from past activity and accounting rules, and are then reviewed and synced from the Accounting tab. Ramp can suggest transaction coding based on your accounting setup and past activity. Pre-coded cards apply the same coding to every transaction on a card, and accounting rules apply coding based on merchant, amount, department, or employee. Invoices use Ramp's AP agent, which learns from past invoices and applies that logic across hundreds of line items. In Intacct, card transactions sync as credit card transactions, and Ramp infers the subsidiary from the transaction's location. Bills sync as AP bills with payments linked back to them. Multiple entities can be added in a single instance, and one batch sync can cover several entities. On approvals, card transactions go through in-platform transaction review, and you can filter the Accounting tab to sync only fully approved charges. Bills are routed to approvers through the AP workflow (every bill is routed to the right approver). Ramp also keeps an audit trail with a transaction log. In pre-processing terms, this covers cost allocation (stage 5) and approval for cards. For invoices it also covers PO matching, with two and three-way matching.

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.

For your team of 3 handling about 1,800 invoices a month into Sage Intacct, Concur would run card spend and vendor invoices as two separate products on one platform. Card transactions are loaded into the cardholder's Available Expenses and added to expense reports in Concur Expense (once a card is assigned, transactions upload automatically into Available Expenses to be added to expense reports). Each expense report carries its own audit trail (recording everything done to the report from submission until payment). Vendor invoices go through Concur Invoice, which covers capture, OCR, PO matching and approval routing (pre-processing stages 1, 2, 4 and 5; fact sheet claims a155834a, a1fc30c6, 7d2bf853). The two modules share user profiles, approval workflows, and financial integrations, but manage vendor invoices separately from employee expenses. Concur's own community documentation describes the two as separate paths on the same underlying infrastructure. In Sage Intacct, card transactions can be posted as either credit card or bill transactions, and Account Codes, dimension lists and vendors are pulled directly from Sage Intacct.