Medius vs Stampli vs Basware for AP Automation

For a two-entity Sage Intacct environment growing to three, Stampli operates within a single platform account that mirrors Intacct's entity hierarchy directly. At invoice ingestion, entities are assigned automatically: AP staff email invoices to a dedicated alias that encodes the Intacct entity key (e.g., companyID+Entity-KEY@mystampli.com), and Stampli pre-populates the working entity on the invoice record before any human touches it (Stampli Help Center, 'Email Address for Auto Assigning Invoices to Entities'). Entity-level permissions, chart of accounts, dimensions, and vendor lists for each entity sync from Intacct automatically, so each entity's GL structure stays isolated without manual remapping (stampli.com/erp/sage-intacct: Stampli 'mirrors Intacct's multi-entity hierarchy exactly in one unified platform' and 'entity-level permissions travel automatically from Intacct'). Approval routing is entity-aware: rules can fire based on entity as an invoice attribute alongside amount, department, vendor, and GL account, so approvers for Entity A never see Entity B invoices unless explicitly granted access (stampli.com/resources/approval-workflows-in-accounts-payable). At payment, the multi-location Direct Pay feature presents a paying-location dropdown that locks each payment to one entity's bank accounts and posts the payment record back to that specific Intacct entity (Stampli Help Center, 'Multi-location payments for Sage Intacct', updated 2026-01-14). Adding a third entity requires updating the email alias to include the new entity key, which the help documentation describes as self-service with no re-implementation (Help Center, 'Email Address for Auto Assigning Invoices to Entities': 'If entity keys change or new ones are added, just simply use the new or updated entity key in the email alias'). Stampli publicly states it supports unlimited entities and has 15,000 entities represented across its customer base, with a documented case of a single customer running 400-plus entities through the Sage Intacct integration.

As a $120M multi-location services company operating 2 Sage Intacct entities with a third planned, you need an AP layer that can route invoices to the right entity-scoped workflow, post to the correct entity's GL, and scale to a third entity without re-implementation. Medius's own platform supports multi-entity environments through a 'company' construct with entity-scoped accounting templates, entity-aware approval routing, and virtual-company-level analytics visible from a single login, as documented in the Medius Success Portal. However, the connection to Sage Intacct specifically is delivered as a pre-packaged integration built in partnership with Acuity Solutions, a third-party implementation partner, rather than a Medius-native, directly maintained connector. Medius's blog and enterprise marketing pages confirm the platform centralizes AP workflows and reporting across multiple entities and ERP systems, with configurable entity-level workflows and approval hierarchies; but no public documentation from Medius or Acuity specifies whether that partner-delivered Intacct connector carries entity-level GL posting, Intacct's custom dimensions, or per-entity vendor master synchronization at the depth this buyer's multi-entity Intacct configuration requires.

Your scenario involves 2 active Sage Intacct entities with a third planned, all processed through a centralized 3-person AP team. Basware's platform is built around an organizational structure that accommodates multiple companies or entities within a single AP processing environment: its developer XML integration guide instructs customers to submit one master data file per ERP system and notes that 'the organization structure created in Basware AP Automation affects how data is loaded,' with company codes used as prefixes in external record identifiers (e.g., [companyCode]_[AccountCode]). Its ERP integrations page commits to '100% of invoices across every entity, ERP, and geography' from a single centralized interface. At the architectural level, Basware can ingest invoices, apply entity-level GL coding, and route approval workflows per organizational unit. However, no pre-built, certified connector between Basware and Sage Intacct is listed on the Sage Intacct Marketplace, and Basware's documented certified integrations are primarily with SAP (BTP-certified), Oracle, and Microsoft Dynamics. For Sage Intacct specifically, integration would be delivered through Basware's general API or XML framework, requiring custom configuration to map each Intacct entity ID, chart of accounts, and dimensions. The depth of that custom integration — including whether entity-level posting (posting bills directly to Entity 1 vs. Entity 2 in Intacct, not just tagged records in Basware) is validated — is not documented for this specific ERP pairing.

For a $120M multi-location services company handling invoice data, vendor credentials, and payment information across two Sage Intacct entities, Medius provides encryption controls at both the storage and transmission layers. On the storage side, Medius explicitly documents AES-256 encryption across its infrastructure, which is hosted in Microsoft Azure data centers with customer data separated into unique SQL databases per customer. On the transmission side, Medius's Trust Center confirms that Transport Layer Security (TLS) protects all user access over the internet, and a Medius case study references 'full end to end encryption of all integration files as well as the integration communication channels.' These controls are independently audited: Medius holds ISO 27001:2022, SOC 1 Type 2, and SOC 2 Type 2 certifications, and its public SafeBase Trust Center shows a Qualys SSL Labs rating of A+, which confirms strong TLS configuration. The full security documentation package, including SOC 2 Type 2 report and PCI DSS report, is available upon request at trust.medius.com.

For a multi-location services company moving from manual email-and-spreadsheet AP to an automated platform, data protection must cover every touchpoint: invoice ingestion, in-platform processing, ERP sync to Sage Intacct, and payment execution. Stampli addresses all of these on its published Security Policy and Practices page. All data sent to or from Stampli is encrypted in transit using 256-bit encryption. API and application endpoints are TLS/SSL only, using only strong cipher suites. Data at rest is encrypted using an industry-standard AES-256 encryption algorithm. For the highest-sensitivity fields your AP team handles, including vendor bank accounts and tax identification numbers, protection goes a layer deeper: more sensitive data fields such as external system tokens, bank accounts, and Social Security numbers are further encrypted using AES-256 with a separate private key. The HIPAA documentation independently confirms that TLS encryption applies to inbound email uploads (the path by which your team currently receives invoices) and that outbound notifications enforce TLS as well, with delivery blocked if the recipient system does not support it. Stampli maintains SOC 2 Type 2 certification, which provides independent third-party audit attestation that these encryption controls are not only designed but operationally effective over time.

For a $120M services company routing 1,800 invoices per month through Basware into Sage Intacct, all invoice data, vendor credentials, and payment information are protected at both storage and transmission layers. Basware's own published legal documentation explicitly states that 'network traffic over public Internet is encrypted and customer data in storage is encrypted,' with encryption key management handled using Hardware Security Modules (HSMs) in accordance with industry best practices. This covers both the data-at-rest requirement (invoice documents and financial records stored in Basware's cloud environment) and the data-in-transit requirement (API calls between Basware and Sage Intacct, supplier portal sessions, and outbound payment rails). Basware's security posture is independently attested through a triple certification stack: ISO 27001 (information security management), ISO 27017 (cloud-specific security controls), and ISO 27018 (protection of personal data in public clouds), plus product-specific SOC 2 / ISAE 3000 reports available to customers and prospects under NDA.

For a US-based multi-location services company aiming to convert 30%+ of AP spend to virtual card, Medius delivers this through Medius Payments (their own payment module, priced separately from the core AP automation product). Once invoices are approved in the AP workflow, Medius Payments routes each payment to the optimal method: virtual card, ACH, wire, or check. For virtual card transactions, Medius issues a unique, single-use card number tied to a specific invoice and dollar amount; after the supplier processes it, the card self-destructs, closing the payment loop back to the ERP. The rebate structure is documented as 1%+ cashback paid monthly with no spend thresholds and no transaction fees on vCards, turning AP spend into a direct revenue stream. Supplier enrollment is handled by Medius's own dedicated onboarding team, which conducts outreach to the buyer's vendor base to maximize card acceptance, forecasts rebate potential, and auto-imports card reconciliation reporting into the ERP.

For a $120M multi-location services company looking to shift 30%+ of spend to virtual card, Stampli offers two complementary native mechanisms within Stampli Direct Pay. The first is Stampli Card: when an invoice is approved, the AP team can pay the vendor using a single-use virtual card generated per transaction; the vendor receives card details via the Stampli Vendor Portal or a secure link and processes it to collect funds. Vendor Managers can invite vendors to accept card payments in bulk from the Vendor Management screen. The second mechanism is Stampli E-Payments, powered by the Paymode network (operated by Bottomline): for vendors already enrolled in Paymode, Stampli automatically sets E-payment as the default payment method in the Select to Pay queue; the buyer pays no per-transaction fee, and a portion of the network fee paid by the vendor is shared with the buyer as a rebate on qualifying transactions. Both paths generate rebate revenue: Stampli documents up to 1% cashback on eligible purchases, paid quarterly via ACH to the buyer's designated bank account. To maximize virtual card adoption, Stampli displays a green rebate badge on eligible invoices and an orange missed-rebate badge when an eligible invoice is routed to a non-E-payment method, creating an active prompt for AP to recapture the rebate opportunity before confirming a payment batch. All card transactions sync to Sage Intacct through the same Direct Pay integration and appear in Stampli as invoice-like records processed through the standard coding and approval workflow.

For a $120M services company running two Sage Intacct entities and targeting 30%+ of spend on virtual card, Basware does offer virtual card as one of four payment rails within its payment module (check, ACH, virtual card, and wire from a single application), and its launch documentation explicitly states that clients can 'generate rebates on their spend' through this payment capability. The CorPay technology partner page on Basware's current website confirms an ongoing relationship with a commercial card infrastructure provider, which is the typical mechanism for sourcing virtual card issuance and rebate revenue share. However, the detailed documentation on Basware's virtual card rebate program dates to its 2018 NetworkPay launch; there is no current (2024-2026) Basware product page or help center article that confirms the buyer-rebate virtual card program is actively available to US mid-market customers, outlines rebate tiers, or documents a supplier enrollment program designed to drive adoption toward a target like 30% of spend. Critically, Basware's ePayments documentation lists its pre-built ERP integrations as Oracle, SAP, Unit4, and several UK-market ERPs, without listing Sage Intacct; no certified Sage Intacct marketplace listing for Basware's payment module was found, which creates a material uncertainty about whether virtual card payments would loop back to Sage Intacct automatically or require manual reconciliation steps.