Basware vs Medius vs Vic.ai for AP Automation

For a 3-person AP team where the same individuals currently enter, approve, and initiate payments, Basware enforces segregation of duties through a combination of role-based access controls and workflow task assignment in its AP Automation platform. Control Objective 10 of Basware's documented AP Automation application controls states that 'logical access into AP Automation system is restricted to authorized personnel only and that the user roles are adequately segregated,' and the platform's approval workflow architecture explicitly requires that 'each invoice must be reviewed and approved by a separate person.' Roles are configured in P2P Administration as distinct permission sets (invoice entry/processing, review, approval, transfer to accounting), so a user holding only the Invoice Processor right cannot hold the Approver right simultaneously; the workflow routes tasks only to users whose role grants them that specific action at that stage. Payment release is a separate downstream stage: once an invoice clears approval, it enters a 'Ready for Transfer' state that is acted on by AP/finance users configured for accounting transfer, creating a hard functional boundary between the approver identity and the payment-release identity.

For a 3-person AP team at a multi-location services company, Medius enforces all three legs of segregation of duties through distinct, system-level mechanisms rather than policy-only controls. First, the `AllowInspectAndAttest` system parameter controls whether the user who reviewed and coded an invoice can also approve it: setting this to 'No' means that a person who has reviewed a coding row can never approve the same row. Second, Medius includes a configurable Four Eyes Principle (4EP) that seamlessly forces documents to be handled by at least two different users, with an admin page allowing company-specific 4EP settings; it can be applied to non-PO invoices for a limited set of suppliers above a dollar threshold, and the invoice history is stamped that the invoice was routed for additional approval due to Four Eyes Principle. Third, the payment step is protected by a dedicated Pay Approver Role: Medius explicitly documents 'full control and compliance with the Pay Approver Role, ensuring clear separation of duties and secure authorisation,' with the process requiring a separate CFO or Financial Controller to approve a payment batch before payments are processed. Taken together, these three mechanisms enforce the buyer's complete chain: the coder cannot approve their own coded rows, approval requires at least a second authenticated user, and payment release requires a separate role entirely. Medius's options for segregation of duties and a four-eyes principle are described as keeping everyone on task verifying information before any payment is made.

For a 3-person AP team moving from manual email-chain approvals to a system-enforced control environment, Vic.ai's role architecture creates the three-stage separation your policy requires. The platform distinguishes an Accountant role (invoice entry, AI-prediction review, and coding on the Invoices tab) from a separately designated Approver role, and from payment execution permissions managed through VicPay. The Approvals product page documents 'Permission guardrails: Define parameters for approval limits and editing permissions by role or user,' and the FAQ confirms 'Vic.ai enforces controls through configurable workflows, role-based permissions, and audit tracking.' Practically, the AI ingests and codes the invoice (acting as a distinct first-stage actor), the Accountant reviews and validates those predictions, and the workflow then routes to a named Approver who is a different user identity; once approved, VicPay payment execution is controlled through a separately permissioned layer with 'centralized control: manage user permissions across entities and teams.' Every action — approval, rejection, edit, and payment — is time-stamped and user-attributed in a full audit trail, covering stages 1 through 5 of the pre-processing journey (legitimacy, PO match, terms, receipt, and cost allocation routing) before the invoice posts to your Sage Intacct entities.

Your AP team currently generates international wire instructions manually outside Sage Intacct for 8 overseas vendors. With Medius Payments (the vendor's payment execution module, priced separately from core AP automation), once an invoice completes the Medius approval workflow, a wire payment is formatted within Medius using the vendor's stored SWIFT/BIC code or IBAN, then transmitted via secure FTP directly to your financial institution's wire desk for settlement — no manual Sage Intacct export or separate bank login required. Medius documents support for over 180 currencies by default, with additional currencies addable manually or synced from your ERP, and clients have full control to enable international wire as a payment method per supplier. For buyers with European banking needs, Medius Payments in Europe is delivered in partnership with Nomentia, which connects to over 10,800 banks globally via host-to-host, SWIFT, and local rails. The June 2025 'Straight Through Payments' capability removes ERP file uploads entirely, routing payments through the buyer's existing bank accounts from within Medius.

For a $120M services company paying 8 overseas vendors, Basware handles the invoice processing side of multi-currency AP: the platform captures invoices in foreign currencies, maintains exchange rate data via a dedicated ExchangeRates API, and flags currency discrepancies before posting through its AP Protect module. Basware also claims coverage across 190+ countries for its e-invoicing and compliance network. However, Basware's own documentation describes the standard payment flow as transferring approved invoices to the ERP or accounting system for payment execution, and its blog explicitly positions payment automation as a separate integration that 'creates a better link between your P2P system and your payments solution.' This means the actual disbursement of international wire transfers in local currencies to your overseas vendors would likely depend on Sage Intacct's own payment rails or a connected third-party payments provider, not a native Basware wire-execution engine with SWIFT routing and FX conversion at the time of disbursement.

For a $120M services company needing to pay 8 overseas vendors in multiple currencies, Vic.ai's VicPay module does list international wires as a supported payment method alongside check, ACH, and virtual card, all within the same platform workflow after invoice approval. Once an invoice completes the approval stage, a Payment Initiator assembles a payment batch, selects the pay-from bank account, and submits for a Payment Approver to release; the payment data then syncs back to the connected Sage Intacct entities via a reconciliation API. Vic.ai also confirms that outbound payments from the US can be sent in the vendor's local currency, supporting multi-currency disbursement for overseas payees. However, a confirmed user-reported limitation surfaces here: payment batches are restricted to one currency per batch, meaning each currency requires a separate batch run rather than a single consolidated multi-currency run; a material operational friction for any buyer managing international vendors across payment cycles.

For a $120M services company managing 1,800 invoices per month across two Sage Intacct entities, Basware delivers cash flow forecasting through its Basware Insights analytics layer, specifically via the Committed Spend Dashboard. This dashboard aggregates all open commitments spanning payment plans, purchase orders, and invoices at every stage of the pipeline, including both invoices still in the approval workflow and those already approved, into a unified forward-looking view. As documented on the Basware Insights product and committed spend analytics pages, the dashboard surfaces expected due dates for all open commitments on a single timeline, showing committed spend by due date, and assigns commitment levels graded 1 to 3 to reflect the probability of spend materializing based on where each document sits in the process flow. The predictive analytics layer, also documented on the Basware AI/ML capabilities page, identifies invoices at risk of late payment to support proactive cash position management. Basware Insights Pro extends this with generative AI natural language querying, allowing finance team members to ask plain-language questions and receive immediate visualizations of payables obligations, while Insights Essentials provides the baseline real-time operational dashboards; both tiers are available as part of the Basware platform, with Pro priced at a higher tier.

For a $120M multi-location services company currently flying blind on payables timing, Medius delivers a dedicated Cashflow Dashboard within its Medius Analytics module, listed as a named pre-built dashboard in the Medius help center documentation alongside the Overview, Capture Insights, and Straight Through Processing dashboards. The mechanism works because Medius sits in the pre-processing layer: every invoice, whether still in an approval queue or fully approved and awaiting payment, lives in the Medius pipeline with its due date, payment terms, and workflow status tracked in real time. This means the cashflow view draws from the full liability picture, including invoices that have not yet been posted to Sage Intacct, which is exactly the gap in any ERP-native report. The platform's product page explicitly describes the goal as keeping finance teams 'on top of costs, forecasts and cashflow with a full, real-time view into supplier invoices through pre-defined reports, dashboards and KPIs,' and the homepage extends this to knowing 'precisely what's pending and what's paid, building trust in forecasts and eliminating surprise expenses.' Beyond the Cashflow Dashboard, the payments module supports monitoring of 'payment statuses, identify pending or overdue payments, and generate reports for better financial oversight,' providing a complementary view of scheduled outflows. One customer quote on the Medius Analytics page captures the outcome directly: 'Before Medius, AP was reactive. Now, it's predictive. We forecast cash flow with precision and make smarter payment decisions.'

For a 3-person AP team currently flying blind on cash timing, Vic.ai's VicAnalytics module and VicAgents layer offer the closest match to this requirement. VicAnalytics explicitly lists 'trustworthy accruals and forecasting' as a feature, framed as financial planning built on 'real, up-to-date AP data for better cash flow management' — and because Vic.ai captures invoice due dates at the header level during processing (before posting to Sage Intacct), that data pool includes invoices still moving through the approval queue, not just posted transactions. The CFO-facing product page reinforces this: 'Vic.ai continuously analyzes financial activity across all entities, giving you real-time control over spending, forecasting, and liquidity management.' VicAgents extend this further, with an explicit capability to 'forecast cash flow and surface risks before they impact your bottom line.' The material gap is in specificity: no documented source describes a due-date distribution view that buckets approved-but-unpaid invoices separately from invoices still in workflow, nor is there evidence of a configurable time-horizon histogram (e.g., 0-30, 31-60, 61-90 days outstanding) segmented by approval status. The analytics press release references 'invoice age on platform,' which tracks how long an invoice has been in the system — a process-performance metric — rather than a forward-looking payment-date distribution. What is documented is cash flow and accruals framing anchored to AP pipeline data; what is not documented is the specific status-segregated, due-date-bucketed forecast view the buyer describes.