Expensify vs Spendesk vs Medius for AP Automation

For a $120M multi-location services company running 1,800 invoices per month across two Sage Intacct entities, this requirement sits entirely outside the pre-processing journey and operates as a post-processing visibility layer for finance leadership. Medius delivers this through three complementary mechanisms: (1) a one-click Excel export button available directly from any report view, which opens the report output directly in Microsoft Excel and, when coding rows are included, transfers line-level coding detail for each invoice into the spreadsheet; (2) a native report scheduling feature embedded in the business reporting module, where the reporting options provide rich, configurable reporting across a number of sources, with in-report grouping, totaling, and filtering with drill-down to the underlying document, along with report scheduling and the ability to pull report data via OData; and (3) an OData feed that allows the Controller or CFO to connect a live, auto-refreshing Excel workbook directly to the Medius reporting database, eliminating the need for manual export entirely. Medius AP Automation is deployed with preconfigured dashboards to get users started, alongside a configurable gadget library for building custom dashboards. The gadget layer explicitly supports exporting results into an Excel file from any dashboard view. One operational caveat: report data shows a timestamp indicating when it was last updated, because Medius uses a separate reporting database, meaning there is a delay between an invoice hitting the transactional workflow and it becoming available for inclusion in reports.

This buyer needs automated, scheduled delivery of AP invoice reports (aging, unpaid bills, payment runs across 1,800 invoices/month) to a Controller and CFO in Excel format. Expensify's Insights dashboard and Reports page support manual CSV and XLS export: a Workspace Admin selects expenses or reports, clicks 'Export To,' and chooses CSV, XLS, or a custom template built under Settings > Export Formats. Custom reports triggered from the Insights page are emailed to the requesting user rather than being automatically downloaded or pushed to named recipients on a schedule. No help center documentation confirms a native scheduled delivery mechanism that sends AP data exports to configurable recipients (Controller, CFO) on a recurring cadence; the 'Scheduled Submit' feature governs employee expense submission timing, not outbound analytics distribution. Critically, Expensify's reporting data model is built around employee expense reports and T&E spend, not AP invoice lifecycle data (vendor bills, payment status, aging), which is the core reporting need for this buyer's three-person AP team processing 1,800 invoices monthly across two Sage Intacct entities.

For a $120M services company whose Controller and CFO need regular AP data in Excel, Spendesk covers the export half of this requirement but not the scheduled delivery half. The Spend Trends dashboard and Control dashboard both support manual, on-demand export: a user selects a date range, clicks the download icon, and chooses a preferred export format such as CSV or PDF. The Bookkeep module extends this further, with custom export templates that allow users to adjust columns, naming, file structure, and date/decimal formats before downloading payment and payable data. For budget data specifically, clicking the download icon initiates a background export, after which the user receives an email containing a link to download the exported spreadsheet; but this is a link-delivery mechanism triggered manually, not a scheduled push to named recipients. Across all of Spendesk's documented reporting surfaces, including the Spend Trends dashboard, the Control dashboard, and the Bookkeep export module, no scheduled report delivery feature, report subscription, or recurring email cadence to configured recipients such as Controller or CFO appears in any help center documentation.

This multi-location services company needs to generate a Bank of America-formatted positive pay file after each bi-weekly check run, listing issued check numbers, amounts, and payee data so BofA can match and reject unauthorized items. Positive pay file generation is not a documented Expensify capability. Expensify's bill pay module routes vendor payments through ACH, credit/debit card, or Venmo — all electronic rails that Expensify controls directly — and does not execute employer-controlled paper check runs, which are the prerequisite transaction type that positive pay files document. The only bank-specific file export Expensify documents is an ABA batch file for Australian employee reimbursements, a different format serving a different purpose. No help center article, product page, or marketing claim references positive pay file generation for any bank.

This $120M multi-location services company runs bi-weekly check runs through Bank of America and needs a positive pay file in BofA's exact format submitted after each run to prevent check fraud. Spendesk's payment architecture does not support this workflow at any layer. Spendesk's US payment services cover payment accounts, debit cards, and wire transfers, delivered through its partner Sutton Bank. On the invoice payment side, Spendesk enables batch payment execution by generating bank-ready export files in CSV and SEPA formats for approved invoices. The payment export options are XML SEPA file download or CSV, both of which the company must manually upload to its own bank; Spendesk does not execute the transfer. Critically, the XML SEPA payment option is available to EEA-based companies only, meaning the SEPA rail is not available for a US entity at all. While Spendesk does offer a custom export builder, the default export is a purchase journal; columns, delimiters, and structure can be customized, but bank journals cannot be edited. None of these exports are check registers, and none produce a structured fixed-width or bank-specific file listing issued check numbers and amounts: the data object (a US paper check) does not exist in Spendesk's disbursement model, making positive pay file generation structurally impossible within this platform.

This $120M services company runs bi-weekly check runs and needs to upload a Bank of America-formatted positive pay file after each run so BofA can match and reject unauthorized checks. Positive pay file generation is not a documented feature in Medius's platform. Medius's US check payment model operates as a managed, outsourced service: the buyer keeps their own checking account, but checks are printed at Medius's secure off-site facility, where data is merged with an electronic forms design and sent to a laser printer. Because Medius owns the physical check output step rather than returning a check register to the buyer for bank upload, the buyer cannot generate the structured, BofA-formatted issued-check file that positive pay requires. Medius's documented fraud prevention is entirely internal: a hub called 'Fire Station' tracks outstanding and handled risk factors across transactions, and Medius performs a twofold duplicate check across companies and stops flagged invoices from being processed further. These are AP-side pre-payment controls, not the bank-side positive pay mechanism (a formatted file listing issued check numbers, amounts, and payees submitted to BofA after the check run). No help center article, product page, or documentation on success.medius.com references positive pay file generation, configurable bank file format templates, or Bank of America-specific export.

For a $120M multi-location services company whose AP team currently chases vendors by email for banking details and tax documents, Medius provides a purpose-built, two-module supplier portal architecture. The buyer's AP team creates onboarding forms in Medius Supplier Onboarding; those forms are then pushed to the Medius Supplier Portal, a dedicated external-facing environment where vendors self-register, record, and update their details in a single cloud-based location. A dedicated self-serve portal gives suppliers the flexibility to respond to onboarding forms in one place; on submission, authorized users can review and approve supplier responses in Supplier Onboarding. The Supplier Registration Form (SRF) supports PII field masking, supplier attestation workflows, and configurable questionnaires that can capture regulatory documentation. Selected SRF fields can be marked as PII with role-based visibility controls, and the system supports the ability to complete registration forms on behalf of the supplier when needed. For banking detail entry, suppliers can be onboarded via the Medius Supplier Portal, and if given access, vendors can use the portal to manage their banking and contact information themselves. For invoice submission, the portal resolves the problem of AP staff tied up responding to supplier inquiries on PO and invoice payment status, and provides a centralized entry point for suppliers to exchange invoices and other documents. For payment status visibility, Medius makes it easy to get suppliers set up and onboarded through the Vendor Marketplace, and with digital payments, suppliers get clear visibility into the payments process through the Medius supplier portal. The W-9/W-8 gap is where this falls short of full coverage: Medius's onboarding questionnaire is configurable and captures key vendor details based on vendor type, including thorough questionnaires and detailing regulatory requirements, to ensure master supplier data remains compliant. However, no Medius documentation explicitly describes a purpose-built W-9/W-8 collection engine with IRS TIN matching, 1099 preparation support, or FATCA compliance routing. The SRF can accommodate document uploads and custom fields that could include W-9/W-8 attachments, but this is a configurable workaround rather than a native tax-compliance automation layer.

For a $120M services company with a 3-person AP team processing 1,800 invoices/month, the vendor self-service portal requirement covers five discrete sub-capabilities: new vendor registration, W-9/W-8 collection, banking detail entry, vendor-initiated invoice submission, and payment status inquiry. Expensify's documented mechanism for vendor invoice intake is an email-inbox model: the buyer shares a dedicated billing address (domain.com@expensify.cash) with vendors, vendors email their invoices to that address, and SmartScan automatically creates a bill inside Expensify for internal AP review. This digitizes the receipt step but replicates email intake rather than replacing it with a structured portal. No help.expensify.com documentation found describes a dedicated external vendor portal with unique vendor login credentials, a self-registration workflow, embedded W-9/W-8 tax form collection and TIN validation, vendor-entered ACH banking details, or a vendor-facing payment status dashboard. The 'vendor' concept in Expensify's documentation refers either to vendor bill records within accounting integrations (e.g., Sage Intacct, NetSuite) or to travel supplier programs, neither of which addresses external self-service onboarding. Payment status is also internally restricted: bills route only to the primary domain contact and only internal AP staff can view and action them.

For a $120M US multi-location services company needing a persistent external portal where vendors can self-register, submit W-9/W-8 tax documents, enter ACH banking details, submit invoices, and check payment status, Spendesk does not deliver this capability end to end. Spendesk does have a Vendor Portal feature, but it is scoped narrowly: it activates only when a procurement request is in flight, sends the vendor a one-time emailed link, and collects custom onboarding form fields (IT surveys, compliance certificates, tax information fields). Once that procurement request closes, the portal session ends. There is no persistent, always-available external login where a vendor can independently take action. Invoice submission is exclusively internal: per Spendesk's help center, 'Account Owners and any member with a Requester role can submit supplier invoices on Spendesk through the Requests tab,' and suppliers who email invoices to a dedicated Spendesk address only create internal drafts that an AP user must then process. Banking detail entry is also internal: Spendesk's own documentation notes that banking details collected via the vendor portal 'are not sent automatically from Procurement Request to Account Payable Supplier,' and instructs controllers to 'Go to Spendesk Account Payable to input manually these supplier/banking details.' Payment status is visible only to internal Spendesk users in the Requests and Payments tabs; proof of payment is downloaded by finance and emailed to suppliers manually. W-9/W-8 collection is not a native capability: the platform's compliance framework is European (SEPA, XML, VAT, GDPR, PSD2), with no IRS TIN matching, no W-9/W-8 form engine, and no 1099 workflow anywhere in the documented help center.