BILL (Bill.com) vs Mekorma

Requirement evaluated: Approval delegation with automatic expiration (e.g., delegate to backup for 5 business days while on PTO)

For your 6-location services company with a 3-person AP team, BILL's approval workflow does support multi-level routing and the use of approval groups, where any member of a designated group can act on a pending bill. As documented in BILL's help center, approval groups let you assign a pool of approvers to a policy, and once any one member approves, the bill moves to the next stage. This provides coverage continuity when a named approver is unavailable. …

Limitations: For this buyer's audit and separation-of-duties needs across 2 Sage Intacct entities, the approval group workaround removes named-delegate accountability: the audit trail shows which group member acted, but not that they were acting as a bounded substitute for a specific absent approver, and there is no automatic rever …

Requirement evaluated: Approval delegation with automatic expiration (e.g., delegate to backup for 5 business days while on PTO)

Your team runs Sage Intacct, and that is the threshold issue: Mekorma is built to run natively inside Microsoft Dynamics GP, Dynamics 365 Business Central, and Acumatica. <cite index="2af73af2-5de8-4f3a-9f4f-d3e9f098300c">Mekorma is an embedded accounts payable automation solution designed for Microsoft Dynamics 365 Business Central, with continued support for Dynamics GP and Acumatica.</cite> Sage Intacct is not a supported platform, so none of Mekorma's capabilities, including its delegation feature, are accessible to your organization without replacing your ERP. …

Limitations: Mekorma has no integration with Sage Intacct; deploying it would require migrating away from your ERP, making it a non-starter for your 2-entity Sage Intacct environment. …

Requirement evaluated: The system must provide a self-service vendor portal where suppliers can submit invoices directly, check payment status, and respond to queries from AP, reducing inbound email volume and giving AP a single structured intake channel. For the buyer's three-entity structure, the portal must allow vendors to indicate or confirm which legal entity the invoice is addressed to at submission time, so that entity-level routing can begin without manual AP triage.

For a buyer running three D365 Finance legal entities, BILL does offer a vendor network where suppliers can create accounts, submit invoices, and track payment status without emailing AP directly. BILL's own learning content confirms that vendors can 'submit invoices and track approval and payment status at their convenience' and that 'vendors can access all the critical information they need without having to reach out directly to your team.' However, the entity-routing requirement exposes a structural gap: BILL's multi-entity architecture creates a separate BILL company account per legal entity, and a vendor in the BILL Network connects to a specific company account. …

Limitations: BILL's multi-entity portal architecture assigns vendors to separate company accounts per entity rather than providing a single intake portal with an entity selector, so entity-level routing at submission time cannot be achieved without vendor-side knowledge of which account to use or post-submission AP triage. …

Requirement evaluated: The system must provide a self-service vendor portal where suppliers can submit invoices directly, check payment status, and respond to queries from AP, reducing inbound email volume and giving AP a single structured intake channel. For the buyer's three-entity structure, the portal must allow vendors to indicate or confirm which legal entity the invoice is addressed to at submission time, so that entity-level routing can begin without manual AP triage.

The buyer runs three legal entities on Dynamics 365 Finance and needs a self-service supplier portal where vendors submit invoices directly, check payment status, and select the target legal entity at intake so entity-level routing begins without AP triage. Mekorma does not offer this capability. Its invoice intake mechanism is an email-based channel: vendors email invoices to a dedicated AP inbox, Microsoft AI Builder extracts header-level data (invoice number, date, amount, due date), and a Power Automate flow pushes records into the ERP for AP staff review — a workflow documented on the Dynamics GP Invoice Capture feature page and confirmed across multiple help-center builds. …

Limitations: Mekorma has no supplier-facing portal for invoice submission, payment status, or entity routing at any tier of its product line, and its documented ERP coverage does not include Dynamics 365 Finance, making this requirement entirely unaddressed by Mekorma regardless of configuration or add-on selection.

Requirement evaluated: The system must capture and pass D365 Finance financial dimensions (business unit, department, cost center, project, and any custom dimensions configured in the buyer's D365 instance) at the invoice line level, not just the header, so that cost allocation across the three legal entities is encoded during AP processing rather than corrected post-posting. This addresses stage 5 of the pre-processing journey, where budget owners and cost centers must be identified before the invoice reaches the ERP.

This buyer runs D365 Finance across three legal entities and needs invoice line-level financial dimension coding (business unit, department, cost center, project, custom dimensions) resolved during AP pre-processing before posting, which is stage 5 of the pre-processing journey. BILL's entire Microsoft Dynamics integration footprint is built for Dynamics 365 Business Central, a separate product with a different API surface than D365 Finance (F&O). Every Microsoft Dynamics help article on BILL's help center is titled 'Microsoft Dynamics 365 Business Central'; no documentation for a D365 Finance connector exists. …

Limitations: BILL has no documented D365 Finance (F&O) integration; its Microsoft Dynamics connector covers Business Central only, which is a fundamentally different ERP product. …

Requirement evaluated: The system must capture and pass D365 Finance financial dimensions (business unit, department, cost center, project, and any custom dimensions configured in the buyer's D365 instance) at the invoice line level, not just the header, so that cost allocation across the three legal entities is encoded during AP processing rather than corrected post-posting. This addresses stage 5 of the pre-processing journey, where budget owners and cost centers must be identified before the invoice reaches the ERP.

This buyer runs D365 Finance across three legal entities and needs line-level financial dimension mapping (business unit, department, cost center, project, and custom dimensions) resolved during AP pre-processing, before the invoice posts. That is stage 5 of the pre-processing journey. Mekorma cannot address this requirement because it does not run on D365 Finance. …

Limitations: Mekorma has no documented D365 Finance compatibility; deploying it would require the buyer to first replace their ERP with Business Central or Dynamics GP, which is outside the scope of an AP automation evaluation. There is no workaround or add-on that bridges this gap within the Mekorma product family.

Requirement evaluated: The AP automation layer must integrate with Dynamics 365 Finance at full data model depth, replicating every financial dimension, legal entity structure, tax configuration, and custom segment that D365 Finance supports across all three legal entities, with no field-level truncation or mapping loss. This is the buyer's stated top-priority criterion; any gap here limits how much of the D365 Finance investment is actually usable through the AP layer.

This buyer runs Dynamics 365 Finance across three legal entities and requires an AP automation layer that replicates D365 Finance's full data model: financial dimensions, legal entity structure, tax configuration, and custom segments. BILL's published integration documentation and help center articles confirm that its Microsoft Dynamics integration covers only Dynamics 365 Business Central and the legacy Dynamics GP. The official BILL integration page states that 'BILL Accounts Payable and BILL Accounts Receivable sync with Microsoft Dynamics 365 Business Central,' with no mention of D365 Finance (F&O) anywhere in BILL's documentation. …

Limitations: BILL has no integration with Dynamics 365 Finance at any depth: the ceiling is not a field-mapping gap but a product absence. For a three-legal-entity D365 Finance organization requiring full financial dimension replication and tax configuration passthrough, BILL is structurally incompatible with the buyer's top-priori …

Requirement evaluated: The AP automation layer must integrate with Dynamics 365 Finance at full data model depth, replicating every financial dimension, legal entity structure, tax configuration, and custom segment that D365 Finance supports across all three legal entities, with no field-level truncation or mapping loss. This is the buyer's stated top-priority criterion; any gap here limits how much of the D365 Finance investment is actually usable through the AP layer.

This buyer runs Dynamics 365 Finance across three legal entities and needs an AP automation layer that integrates at full data model depth: financial dimensions, legal entity structure, tax configuration, and custom segments. Mekorma cannot deliver this because it does not integrate with Dynamics 365 Finance at all. Every product Mekorma ships is scoped to a different set of ERP platforms. …

Limitations: Mekorma has no integration with Dynamics 365 Finance; this is a complete platform mismatch, not a depth or fidelity gap. Deploying Mekorma would require the buyer to replace D365 Finance with Business Central, which is a full ERP migration, not an AP automation project.

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

For a $120M multi-location services company running 1,800 invoices per month across two Sage Intacct entities, BILL offers a native analytics layer called BILL Insights, launched in early 2024. The feature delivers out-of-the-box dashboards covering AP-level metrics. Per BILL's own press release, the documented metrics include top vendors by amount paid, average days to pay, and aging summary. A separate Bill Approval Audit report (a named help-center article confirmed at help.bill.com) captures approval-level activity. However, the five KPIs this buyer requires (average days to approve at the approval-stage level, touchless rate, cost per invoice, exception rate, and discount capture rate) …

Limitations: At least four of the five requested KPIs (touchless rate, cost per invoice, exception rate, discount capture rate) are not documented as native labeled metrics in BILL Insights, and would require manual derivation from exported transaction data, which is not a viable self-service workflow for a 3-person AP team. …

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

Your team needs a native AP KPI dashboard tracking five specific operational metrics: average days to approve, touchless rate, cost per invoice, exception rate, and discount capture rate. This requirement is doubly disqualified for Mekorma. First, Mekorma is built exclusively for Microsoft Dynamics 365 Business Central, Dynamics GP, and Acumatica; it has no integration with Sage Intacct, the ERP your organization runs. Second, even within the ERPs it does support, Mekorma offers no native KPI analytics dashboard of this kind. …

Limitations: No pre-built metrics for days to approve, touchless rate, cost per invoice, exception rate, or discount capture rate exist anywhere in Mekorma's product; and the platform does not connect to Sage Intacct at all, making this vendor inapplicable to the buyer's environment regardless of analytics capability.

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

For a $120M services company processing 1,800 invoices/month across 2 Sage Intacct entities, BILL's exception handling works as follows: invoices arrive in BILL's document Inbox, where the platform surfaces a count of unprocessed items. When a PO-linked bill has a discrepancy, BILL holds it without allowing payment until the mismatch is resolved. BILL confirms that Sage Intacct customers have access to both 2-way and 3-way PO matching that 'automatically syncs back into Sage Intacct to prevent errors and overpayments,' and BILL's blog documentation states that discrepant invoices are held 'without being paid until rectified.' At the individual bill level, BILL flags duplicate invoice numbers …

Limitations: BILL does not document a dedicated exception triage workbench with aging buckets and priority indicators; its documented exception surface is per-invoice hold status and an Inbox item count, which forces the buyer's AP team to open individual records to discover stalled items rather than triaging from an aggregate view …

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

Your team runs Sage Intacct across two entities and needs a live dashboard surfacing every unmatched or flagged invoice with aging and priority indicators so your three-person AP team can triage exceptions without manually opening each record. Mekorma cannot serve this need for two distinct reasons. First, Mekorma is designed exclusively for Microsoft Dynamics 365 Business Central, Dynamics GP, and Acumatica; it carries no documented integration with Sage Intacct, so the platform incompatibility alone removes it from consideration. …

Limitations: Mekorma has no integration path to Sage Intacct, which disqualifies it entirely for this buyer's environment. Even setting aside the ERP mismatch, no Mekorma module provides an aggregated exception dashboard with aging timers or priority scoring for unmatched invoices; that pre-payment exception visibility layer is abs …

Requirement evaluated: The system must maintain a complete, timestamped audit trail covering every action in the pre-processing journey: invoice receipt, OCR extraction, dimension coding, tax code assignment, approval decisions (including who approved, from which interface, Teams or portal), delegation events, escalations, and ERP posting confirmation, with records tied to the specific legal entity and financial dimensions on each transaction. This audit record must be exportable and must satisfy both internal controls and external audit requirements across all three legal entities without manual log reconstruction.

This buyer runs Microsoft Dynamics 365 Finance across three legal entities and needs an audit trail tied to D365 Finance financial dimensions, legal entity context, tax codes, Teams-based approvals, and ERP posting confirmation. BILL does maintain a timestamped, unalterable audit trail covering AP activity: approvals, payments, review notes, and remittance details per transaction. However, the foundational integration problem renders this capability irrelevant for the buyer's context: BILL's Microsoft Dynamics integration is scoped exclusively to Dynamics 365 Business Central and Dynamics GP, two mid-market products. …

Limitations: BILL's Dynamics integration is limited to Business Central and GP; no integration with D365 Finance exists, which means the audit trail cannot be anchored to D365 Finance financial dimensions, legal entities, tax codes, or ERP posting events as this buyer requires. …

Requirement evaluated: The system must maintain a complete, timestamped audit trail covering every action in the pre-processing journey: invoice receipt, OCR extraction, dimension coding, tax code assignment, approval decisions (including who approved, from which interface, Teams or portal), delegation events, escalations, and ERP posting confirmation, with records tied to the specific legal entity and financial dimensions on each transaction. This audit record must be exportable and must satisfy both internal controls and external audit requirements across all three legal entities without manual log reconstruction.

This buyer runs Dynamics 365 Finance across three legal entities and requires a complete, exportable, entity-scoped audit trail covering the full pre-processing journey. The foundational barrier is platform compatibility: <cite index="eb651e1d-97c4-4df6-b5b7-e5147f483910">Mekorma is an embedded AP automation solution designed for Microsoft Dynamics 365 Business Central, with continued support for Dynamics GP and Acumatica</cite>. Dynamics 365 Finance (the enterprise F&O product the buyer operates) is not a supported platform. …

Limitations: Mekorma is not available for Dynamics 365 Finance; the platform incompatibility alone eliminates it from consideration before any audit trail capability question can be evaluated. …

Requirement evaluated: Data encryption at rest and in transit

For a $120M multi-location services company processing invoices and payments across two Sage Intacct entities, BILL addresses data encryption at the infrastructure and transport layers. On the at-rest side, BILL's security documentation states that 'BILL Accounts Payable and BILL Accounts Receivable ensures customer data is protected at rest with encryption' and applies 'an additional level of encryption to protect access to sensitive customer data from malicious applications.' The production environment runs on AWS across three physically separate availability zones, with continuous data backups to a secondary region, providing the encrypted storage substrate for all invoice documents, vend …

Limitations: BILL's public-facing security pages document encryption at rest and TLS in transit but do not explicitly name the cipher strength for at-rest storage (e.g., AES-256) or the specific TLS version enforced (1.2 vs. …

Requirement evaluated: Data encryption at rest and in transit

For a $120M multi-location services company running Sage Intacct, Mekorma presents a foundational compatibility problem before encryption can even be evaluated: Mekorma is purpose-built for Microsoft Dynamics 365 Business Central, Dynamics GP, and Acumatica, and does not support Sage Intacct. On the encryption question itself, Mekorma's own published documentation does not include a trust center, security whitepaper, or product page that states specific cryptographic standards for the platform as a whole. …

Limitations: Mekorma does not support Sage Intacct, making it incompatible with this buyer's ERP environment entirely. Even setting that aside, Mekorma publishes no accessible trust center, SOC 2 report, or security architecture document that would allow a buyer to verify AES-256 encryption at rest or TLS 1.2/1.3 in transit for the …

Requirement evaluated: AI/OCR-powered extraction from PDF, image, and email-embedded invoices with 95%+ accuracy on header and line-item data

For a 3-person AP team processing 1,800 invoices per month across two Sage Intacct entities, BILL's invoice capture stack works as follows. Vendors email invoices to a dedicated BILL inbox address (e.g., companyname@bill.com); <cite index="12-17">a unique inbox email address is generated, which can be provided to vendors so they can email bills directly into the account for processing.</cite> Once documents arrive, <cite index="11-7">the Intelligent Virtual Assistant (IVA) …

Limitations: Two material ceilings exist for this buyer. First, the Invoice Coding Agent's line-item coding predictions are documented to cover amounts, descriptions, and six specific coding fields; raw line-item fields needed for PO-line-level 3-way matching (quantity, unit price, item code) …

Requirement evaluated: AI/OCR-powered extraction from PDF, image, and email-embedded invoices with 95%+ accuracy on header and line-item data

Your team runs on Sage Intacct, and this is the threshold issue: Mekorma does not integrate with Sage Intacct. The vendor's own positioning explicitly scopes the product to Microsoft Dynamics 365 Business Central, Dynamics GP, and Acumatica. No Sage Intacct connector, marketplace listing, or certified integration exists. Setting the platform mismatch aside, Mekorma does have an Invoice Capture feature for Dynamics GP users, but it is powered by Microsoft Power Platform and AI Builder and extracts only four header-level fields: Invoice Number, Invoice Date, Amount, and Due Date. Line-item data extraction is not part of the documented mechanism. …

Limitations: Mekorma cannot be deployed in a Sage Intacct environment at all: the product has no documented integration with Sage Intacct and does not appear on the Sage Intacct Marketplace. …

Requirement evaluated: The system must support multi-legal-entity coding and data isolation across the buyer's three legal entities, enabling AP staff to code invoices to any of the three entities with entity-level permission controls that prevent one entity's approvers or coders from viewing or acting on another entity's invoices. This is an intra-system segregation requirement, not a multi-instance requirement: all three entities must be manageable from a single centralized AP workspace while maintaining strict per-entity data boundaries.

This buyer operates three D365 Finance legal entities and needs a single centralized AP workspace where coders and approvers are system-enforced to see only their permitted entity's invoices, with cross-entity visibility available only to designated AP administrators. BILL does offer a multi-entity capability, but its architecture is built as separate BILL accounts per entity navigated via a single-login switcher: <cite index="43-9,43-10,43-11">with one secure login, users can access and manage the financials for all subsidiaries and switch between entity contexts without signing out.</cite> This is an entity-context-switching model, not a unified AP queue with row-level data isolation; a us …

Limitations: BILL's multi-entity model achieves isolation through separate per-entity accounts rather than enforced row-level access control within a unified workspace, which structurally breaks the buyer's requirement for a single centralized AP queue where all three entities are simultaneously manageable. …

Requirement evaluated: The system must support multi-legal-entity coding and data isolation across the buyer's three legal entities, enabling AP staff to code invoices to any of the three entities with entity-level permission controls that prevent one entity's approvers or coders from viewing or acting on another entity's invoices. This is an intra-system segregation requirement, not a multi-instance requirement: all three entities must be manageable from a single centralized AP workspace while maintaining strict per-entity data boundaries.

This buyer runs Dynamics 365 Finance across three legal entities and needs enforced, per-entity invoice coding and access control inside a single centralized AP workspace. Mekorma cannot address this requirement for two compounding reasons. First, and most fundamentally, Mekorma is purpose-built for Dynamics 365 Business Central, Dynamics GP, and Acumatica; the vendor's own footer, fact sheet, and product announcements confirm this scope explicitly, and there is no documented Mekorma product for D365 Finance. The buyer's ERP is outside Mekorma's supported platform set entirely. …

Limitations: Mekorma has no product for Dynamics 365 Finance; its entire solution set targets Business Central, Dynamics GP, and Acumatica. Even setting aside the ERP mismatch, Mekorma's multi-entity isolation mechanism is ERP-session-delegated access control, not an independent AP-platform RBAC layer, which means it cannot deliver …

Requirement evaluated: The system must support tax configuration pass-through to D365 Finance, meaning that tax codes, tax groups, and item tax groups configured in the buyer's D365 instance are available for selection or auto-assignment during AP processing, and are written back to the D365 transaction record without manual re-entry or override. This covers stage 3 of the pre-processing journey, ensuring that tax terms verified during AP processing survive the handoff to the ERP intact.

This buyer runs Microsoft Dynamics 365 Finance across three legal entities and requires that D365 tax codes, tax groups, and item tax groups be surfaced in the AP processing UI and written back to D365 transaction records intact. That capability depends entirely on a functioning D365 Finance connector. BILL's documented Microsoft Dynamics integration covers only Dynamics 365 Business Central and Dynamics GP: the BILL help center publishes a dedicated sync matrix, setup guide, payments guide, and error guide for Business Central, with no parallel documentation for D365 Finance (F&O) anywhere in its help center. …

Limitations: BILL does not offer a D365 Finance (F&O) integration at all; the product integrates with D365 Business Central and Dynamics GP only. Any attempt to connect BILL to D365 Finance would require custom middleware with no documented tax field mapping, making tax configuration pass-through structurally absent rather than mer …

Requirement evaluated: The system must support tax configuration pass-through to D365 Finance, meaning that tax codes, tax groups, and item tax groups configured in the buyer's D365 instance are available for selection or auto-assignment during AP processing, and are written back to the D365 transaction record without manual re-entry or override. This covers stage 3 of the pre-processing journey, ensuring that tax terms verified during AP processing survive the handoff to the ERP intact.

This buyer runs Dynamics 365 Finance across three legal entities, a platform where tax codes, tax groups, and item tax groups are configured at the legal-entity level and must survive the handoff from AP processing to the posted vendor invoice record intact (stage 3 of the pre-processing journey). Mekorma cannot fulfill this requirement because it does not connect to Dynamics 365 Finance at all. …

Limitations: The limitation is not a feature gap within D365 Finance; it is an absent ERP connection. Mekorma's entire embedded architecture operates within Business Central's AL extension model, which is incompatible with the X++ and OData-based extension model of D365 Finance. …

Requirement evaluated: Automatic combination of multiple approved invoices to the same vendor into a single payment, with the matching criteria used for combination clearly stated

For a 3-person AP team processing 1,800 invoices per month across two Sage Intacct entities, BILL's payment consolidation works as follows: administrators enable the feature globally under Payables Preferences, then activate it per vendor by checking 'Combine payments' under Payment Processing on each vendor record. Once enabled, BILL automatically combines multiple approved bills to the same vendor into a single check or ACH (ePayment) disbursement. …

Limitations: BILL can combine a maximum of 35 bills per single consolidated payment; vendors with more than 35 open approved invoices in a payment run will require a second payment. Card payments (virtual card, BILL Divvy Card) …

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 …

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

For a $120M company running 2 Sage Intacct entities, BILL provides a pre-built, native Sage Intacct connector with a documented self-service setup process: the buyer creates a Web Services sync user in Intacct at the top/root level, assigns full module permissions, and configures the two-way sync for vendors, chart of accounts, departments, locations, and bills. …

Limitations: For this buyer's specific scenario, a 2-entity Sage Intacct environment, the evidence consistently indicates that hands-on integration setup assistance beyond self-service documentation is separately scoped and priced rather than bundled into the standard implementation fee; the buyer should require explicit written co …

Requirement evaluated: Native, pre-built, bidirectional integration with Sage Intacct (not middleware-dependent)

Your organization runs two ERP entities in Sage Intacct, and the requirement is a native, pre-built, bidirectional connector to that system. Mekorma does not offer this. Every documented integration Mekorma publishes targets Microsoft Dynamics 365 Business Central, Microsoft Dynamics GP, and Acumatica: those are the three platforms named in Mekorma's own user guide selector, their partner directory listings, and their product marketing. Sage Intacct does not appear in any Mekorma platform list, help article, or marketplace listing found across multiple searches. …

Limitations: Mekorma cannot connect to Sage Intacct at all: not natively, not via a paid add-on, and not via a documented third-party bridge. Selecting Mekorma would require your organization to replace Sage Intacct with a Microsoft Dynamics ERP, which is a full ERP migration, not an AP automation project.