Basware vs Mekorma

Requirement evaluated: Exception dashboard showing all unmatched/flagged items with aging and priority indicators

For a 3-person AP team processing 1,800 invoices per month across two Sage Intacct entities, with 55% PO-based volume, Basware delivers exception visibility through two complementary surfaces. First, the AP dashboard acts as the central command center where AP professionals can track all invoices in real time, route them through workflows, and resolve exceptions in one place (G2 Basware product listing). Within that dashboard, the dedicated Matching Queue (part of Basware Match Orders) …

Limitations: The documented exception queue explicitly shows a short error message per invoice, and invoices with multiple simultaneous errors display only 'Many' rather than a full enumerated error list inline, which may require opening individual records to see all failure reasons at once. …

Requirement evaluated: Exception dashboard showing all unmatched/flagged items with aging and priority indicators

Your team runs on Sage Intacct, and Mekorma's entire product line is built exclusively for Microsoft Dynamics 365 Business Central, Dynamics GP, and Acumatica. There is no Sage Intacct integration, which means Mekorma cannot participate in your AP pre-processing journey at any stage. Setting aside the ERP mismatch, Mekorma's closest analog to an exception surface is the Invoice Capture Validation Window, a worklist of AI-extracted invoices inside Dynamics GP where a yellow alert icon flags items that cannot be batch-processed; users click the icon to review issues individually. …

Limitations: Mekorma does not connect to Sage Intacct under any configuration, so it cannot be deployed in this buyer's environment at all. Even if the ERP were compatible, no Mekorma product documents a matching-exception dashboard with aging and priority indicators: the validation worklist surfaces individual invoice flags but la …

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

For a $120M multi-location services company running Sage Intacct, 1099 preparation requires automated vendor classification, IRS threshold tracking, and year-end electronic filing: none of which appear anywhere in Basware's documented product. Three targeted searches of basware.com and docs.basware.com returned zero results for 1099, W-9, TIN validation, or IRS e-file. The one Basware compliance page located confirms their tax compliance engine is built around <a href='https://www.basware.com/en/compliance/invoicing-and-tax-compliance/'>global e-invoice formats and VAT in 100+ countries</a>, consistent with the platform's European enterprise heritage. …

Limitations: Basware has no native 1099 module for this US-based buyer; the entire requirement falls outside the product's documented scope and must be managed via Sage Intacct's native functionality plus a separate e-filing tool, which creates a data integrity dependency between Basware's payment records and Intacct's 1099 trackin …

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

This buyer runs Sage Intacct as their ERP, and that is the disqualifying structural barrier. Mekorma is explicitly built as an embedded AP automation solution for Microsoft Dynamics 365 Business Central, Dynamics GP, and Acumatica; there is no documented integration with Sage Intacct and no evidence one exists. The 1099-adjacent capability Mekorma does offer is its Vendor Validation module, which automates TIN matching and OFAC screening inside Business Central and GP before payment runs. However, this is a pre-payment compliance check focused on vendor data accuracy, not a 1099 preparation system: it does not perform automated vendor classification by 1099 type (MISC vs. …

Limitations: Mekorma has no Sage Intacct integration, making it inapplicable to this buyer's entire AP environment regardless of the specific requirement. Even within its supported ERP platforms, Mekorma does not offer a 1099 preparation module covering automated classification, $600 threshold monitoring, or IRS e-file; those funct …

Requirement evaluated: Integration setup assistance included in implementation; not a separate SOW or additional cost

For a $120M services company processing 1,800 invoices per month across 2 Sage Intacct entities, Basware does offer professional services support for implementation. Basware's own services page describes two delivery models: 'Plug-in' for rapid deployment and 'Blueprint' for more complex, phased rollouts, and states that its Professional Services and Customer Success Teams 'will provide extensive support to ensure a faster time to value.' However, the critical issue for this buyer's requirement is whether Sage Intacct integration setup assistance is included in the base implementation engagement or is a separately scoped and separately priced deliverable. …

Limitations: No evidence was found that Basware bundles Sage Intacct integration setup into its standard implementation at no additional cost; all available pricing and services commentary indicates implementation and integration work is scoped and billed separately through Basware Professional Services, directly contradicting this …

Requirement evaluated: Integration setup assistance included in implementation; not a separate SOW or additional cost

This buyer runs two Sage Intacct entities and needs an AP automation vendor whose implementation team can configure the Sage Intacct connection as part of standard onboarding. Mekorma cannot satisfy this requirement at any level because Sage Intacct is not a supported platform. Every product Mekorma publishes is built exclusively for Microsoft Dynamics 365 Business Central, Dynamics GP, and Acumatica. The vendor's own documentation, about page, user guides, and partner announcements consistently list these three ERPs and no others; Sage Intacct does not appear anywhere in Mekorma's product catalog or integration support materials. …

Limitations: Mekorma is architecturally incompatible with Sage Intacct. The buyer would need to evaluate a different vendor entirely; this is not a pricing or packaging gap that can be resolved by purchasing an add-on module.

Requirement evaluated: Role-based access control with entity-level restrictions

For your two-entity Sage Intacct environment, Basware AP Automation manages access through a company/organization hierarchy built directly into the platform. Administrators import an organization structure into Basware AP Automation via the 'organizations' API or the Basware Admin UI, and users are then assigned to specific company nodes within that hierarchy. Once assigned, a user can access only the invoices and business documents belonging to the organization (and its subsidiaries) they were added to, preventing an AP clerk in Entity 1 from viewing or acting on Entity 2's invoices. …

Limitations: The documented mechanism confirms organization-scoped user assignment and row-level advancedPermissions, but explicit documentation of how a single user account holds different roles across two entities simultaneously (e.g., read-only in Entity 1, full AP clerk in Entity 2) …

Requirement evaluated: Role-based access control with entity-level restrictions

For this buyer's 2-entity Sage Intacct environment, Mekorma's role-based access control is inaccessible because Mekorma does not integrate with or support Sage Intacct. All of Mekorma's security and entity-restriction capabilities are built directly on top of the Microsoft Dynamics GP and Business Central security frameworks: administrators assign users to specific companies and AP task roles through the Dynamics GP User Security window, and Mekorma layers its own AP-specific role IDs (e.g., MEKORMA_APPROVER_LEVEL_1) on top of the underlying Dynamics permission model. …

Limitations: Mekorma's entire product, including its access control model, is embedded within the Microsoft Dynamics ecosystem; a buyer running Sage Intacct cannot deploy Mekorma at all, making every capability in this evaluation moot for this buyer's scenario.

Requirement evaluated: Our specific routing rules: under $2,500 manager, $2,500-$10K director, $10K-$50K VP, over $50K CFO

For a multi-location services company replacing email-chain approvals, Basware's AP Automation platform handles threshold-based routing through its rules-based approval workflow engine, operating at stage 5 of the pre-processing journey (cost allocation and authority verification). The system reads invoice data fields including invoice total and automatically determines the correct approval recipient without manual intervention: <cite index="5-1,5-2">Basware's smart routing functionality ensures that invoices are automatically sent to the appointed approval workflow, and based on the invoice data, the AP automation system automatically determines the recipient and sends the invoice along for …

Limitations: Web search did not surface a specific Basware help-center article showing the exact UI configuration screen for a four-tier dollar-threshold matrix, so the precise steps to build and maintain the authority table (e.g., whether tiers are configured as an approval matrix, a visual flow builder, or script-based conditions …

Requirement evaluated: Our specific routing rules: under $2,500 manager, $2,500-$10K director, $10K-$50K VP, over $50K CFO

This buyer runs Sage Intacct across 2 entities and needs a 4-tier dollar-amount approval chain (manager under $2,500, director $2,500-$10K, VP $10K-$50K, CFO over $50K). Mekorma's threshold-based approval mechanism, called 'Threshold IDs,' does exist in documented form for its supported platforms: each Threshold ID configures multiple dollar-amount ranges mapped to named security levels (MEKORMA_APROVER_LEVEL_1, _2, _3, etc.), and transactions are automatically routed, and batches split, so that each tier can be approved independently without holding up lower-value payments. …

Limitations: Mekorma has no Sage Intacct integration; the product cannot be installed or configured in this buyer's ERP environment. The threshold routing capability, while technically well-developed for Dynamics platforms, is entirely inaccessible to a Sage Intacct shop.

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

For a 3-person AP team currently keying 1,800 invoices per month from email and physical mail, Basware covers Stage 1 of the pre-processing journey (legitimacy and data capture) through a three-channel ingestion architecture. PDF invoices arriving by email are routed to SmartPDF, which uses deep learning, text extraction, and AI vision to convert each PDF into a structured e-invoice without OCR, capturing both header and line-level data fields including vendor name, invoice number, date, PO number, line items, amounts, tax, and payment terms. …

Limitations: Physical mail invoices require a scanning step before SmartPDF's AI-driven extraction takes over; Basware's CloudScan (the paper/OCR channel) is described by Basware itself as 'highly manual,' meaning the buyer's estimated mail-delivered invoices will need a process decision on who scans them and how exceptions are val …

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

This buyer runs Sage Intacct across 2 entities and needs automatic extraction of 8 invoice fields including line items, PO number, tax, and payment terms. Mekorma's entire product line is built exclusively for Microsoft Dynamics 365 Business Central, Dynamics GP, and Acumatica; there is no Sage Intacct integration or compatibility of any kind. <cite index="252e91d1-4404-4c8c-8ba0-2d4c22817ae7">Mekorma is designed for Microsoft Dynamics 365 Business Central, with continued support for Dynamics GP and Acumatica</cite> — Sage Intacct is not a supported platform. …

Limitations: Mekorma has no Sage Intacct support, making its invoice capture capabilities entirely unavailable to this buyer. Even within its supported ERP ecosystem, its native GP Invoice Capture extracts only 4 of the buyer's 8 required fields and does not reach line-item, PO number, tax, or payment terms extraction.

Requirement evaluated: Export to Excel and scheduled report delivery to Controller and CFO

For a 3-person AP team at a $120M multi-location company running two Sage Intacct entities, Basware covers this requirement across two layers of its own platform. In the core AP product, invoice list data and coding rows are exported directly in .xlsx format, and accrual reports generate an email notification to named recipients with an Excel download link and no row-count cap, meaning your Controller and CFO can receive the file without manually pulling it. The Basware Reporting tool adds a self-service layer where reports can be generated, downloaded, scheduled, and shared without raising a support request. The separately licensed Basware Analytics (also marketed as Basware Insights) …

Limitations: Scheduled dashboard delivery and CFO-level KPI views require the Basware Analytics or Basware Insights add-on, which carries a separate license fee beyond the base AP automation subscription; confirm whether this module is included in the proposed contract scope. …

Requirement evaluated: KPI tracking: average days to approve, touchless rate, cost per invoice, exception rate, discount capture rate

Your team runs Sage Intacct, and Mekorma's product line is built exclusively as a native extension inside Microsoft Dynamics 365 Business Central and Dynamics GP. Mekorma does not appear in the Sage Intacct Marketplace, and no Sage Intacct integration is documented anywhere in Mekorma's product materials or third-party review sources. Even setting aside the ERP mismatch, the reporting capabilities documented in Mekorma's own help center are limited to payment-execution audit tools: a payment history audit log, a batch inquiry screen, and a Remote Payment Services reporting tool. …

Limitations: Mekorma has no integration with Sage Intacct, making the entire product line inaccessible to this buyer without replacing their ERP. Even on its supported platforms (Business Central and Dynamics GP), Mekorma's reporting scope covers payment batch and audit log history, not AP lifecycle performance metrics.

Requirement evaluated: Virtual card program with rebate revenue; we want to shift 30%+ of spend to virtual card

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

Limitations: Basware's primary buyer-revenue mechanism in its current marketing is early payment discounts (dynamic discounting funded by the buyer's own cash), which is structurally different from virtual card interchange rebates; a buyer focused on virtual card rebate revenue as a financial goal should confirm with Basware direct …

Requirement evaluated: Automatic remittance advice sent to vendors upon payment

This buyer runs Sage Intacct across 2 entities. Mekorma is built exclusively for Microsoft Dynamics 365 Business Central, Dynamics GP, and Acumatica; it has no product, module, or certified integration for Sage Intacct. Within its supported ERP platforms, Mekorma does offer automated EFT remittance delivery: the system generates a PDF remittance and emails it to the vendor's address on file at the time of payment processing, and its Remote Payment Services (RPS) module sends remittance emails automatically for ACH and virtual card payments. However, none of this mechanism is accessible to a Sage Intacct environment. …

Limitations: Mekorma is not deployable on Sage Intacct at any price or tier; the platform incompatibility is absolute. For remittance automation on Sage Intacct, the buyer should evaluate solutions certified in the Sage Intacct Marketplace, where Sage Intacct itself provides native vendor payment notification functionality as a sta …