How Mekorma works

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

This buyer operates two Sage Intacct entities, but Mekorma is documented exclusively as an embedded solution for Microsoft Dynamics 365 Business Central, Dynamics GP, and Acumatica. No Sage Intacct integration exists in any Mekorma product documentation, help center, or web search result, so the product cannot be deployed in this buyer's environment at all. Setting aside the ERP compatibility gap: Mekorma's central interface, the Action Board, is a payment batch processing and approvals hub, not an exception triage dashboard. …

Limitations: Mekorma cannot be deployed in this buyer's Sage Intacct environment: the product is architecturally scoped to Dynamics BC, Dynamics GP, and Acumatica only. Even on a compatible ERP, Mekorma offers no documented exception dashboard with aging timers or priority scoring for unmatched or flagged invoices; exception visibi …

Requirement evaluated: Automated three-way matching: invoice to PO to goods receipt, with configurable tolerance (2% price, 5% quantity)

Your AP team runs 1,800 invoices per month across two Sage Intacct entities, with 55% PO-based invoices that require three-way matching against POs and goods receipts with 2% price and 5% quantity tolerances. Mekorma's documented product scope covers payment execution (Payment Hub, Remote Payment Services), approval routing (Power Approvals, Mobile Workflows), and vendor validation (TIN matching, OFAC screening), all built natively inside Microsoft Dynamics 365 Business Central, Dynamics GP, and Acumatica. …

Limitations: Mekorma does not support Sage Intacct and does not offer any PO-to-invoice-to-receipt matching engine or percentage-based tolerance configuration at any price point or tier. …

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: 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: Centralized vendor master synchronized bidirectionally with Sage Intacct

Your business runs two ERP entities in Sage Intacct, so any AP automation vendor must have a working Sage Intacct integration as its foundation before vendor master synchronization can even be considered. Mekorma does not have that foundation: every product in its portfolio, including Payment Hub, Remote Payment Services, and Shared Services, is built exclusively for Microsoft Dynamics 365 Business Central and Dynamics GP. …

Limitations: Mekorma has no Sage Intacct integration of any kind. A buyer on Sage Intacct who implements Mekorma would have two completely disconnected systems, with no mechanism to synchronize vendor master data, post invoices, or close the payment loop back into Sage Intacct.

Requirement evaluated: Vendor self-service portal: new vendor registration, W-9/W-8 submission, banking detail entry, invoice submission, payment status inquiry

For your $120M multi-location services company on Sage Intacct, Mekorma cannot deliver the vendor self-service portal this requirement describes, for two compounding reasons. First, Mekorma is built exclusively for Microsoft Dynamics 365 Business Central, Dynamics GP, and Acumatica; it has no integration with Sage Intacct, so no Mekorma capability is available to your AP environment at all. Second, even setting aside the ERP mismatch, Mekorma does not offer a supplier-facing self-service portal with any of the five components your requirement specifies. Its Vendor Validation module (TIN matching, OFAC screening, address verification) …

Limitations: Mekorma is not compatible with Sage Intacct at any price point, which is a threshold disqualifier for this buyer before vendor portal functionality is even evaluated. …

Requirement evaluated: Vendor performance visibility: on-time payment rate, average payment cycle, dispute frequency

For a $120M services company on Sage Intacct, Mekorma is not a viable candidate for this requirement on two distinct grounds. First, the ERP fit is absent entirely: Mekorma is built exclusively for Microsoft Dynamics 365 Business Central, Dynamics GP, and Acumatica; it has no integration with Sage Intacct and cannot be deployed in this buyer's environment. Second, even setting aside the ERP mismatch, Mekorma offers no documented mechanism for vendor performance analytics of the kind requested. …

Limitations: Mekorma has no Sage Intacct integration, making it incompatible with this buyer's ERP stack regardless of feature set. Even on its native ERPs, no documented vendor performance scorecard, on-time payment rate calculation, average days-to-pay by vendor, or dispute frequency tracking exists in Mekorma's product.

Requirement evaluated: Vendor performance visibility: on-time payment rate, average payment cycle, dispute frequency

Your company runs Sage Intacct as its ERP, and this is the first disqualifying factor: Mekorma is built natively for Microsoft Dynamics 365 Business Central, Dynamics GP, and Acumatica exclusively. Mekorma's own documentation states it is 'an embedded accounts payable automation solution designed for Microsoft Dynamics 365 Business Central, with continued support for Dynamics GP and Acumatica,' and Mekorma does not appear in the Sage Intacct Marketplace among its 350+ certified integration partners. …

Limitations: Mekorma cannot be deployed against a Sage Intacct environment, which removes it from consideration for this buyer entirely. Separately, even within its supported ERP environments, Mekorma has no documented mechanism for aggregating historical payment timing data into vendor-level performance metrics or dispute frequenc …

Requirement evaluated: Segregation of duties enforcement: person who enters cannot approve, person who approves cannot process payment

Your team runs on Sage Intacct, and Mekorma is built exclusively inside Microsoft Dynamics 365 Business Central and Dynamics GP (with Acumatica support). Mekorma's own positioning confirms it is 'an embedded accounts payable automation solution designed for Microsoft Dynamics 365 Business Central, with continued support for Dynamics GP and Acumatica' — Sage Intacct is not on that list, and a search of the Sage Intacct Marketplace returns no Mekorma listing. …

Limitations: Mekorma has no integration with Sage Intacct and cannot be deployed in a Sage Intacct environment; the platform incompatibility is total, making the SOD requirement undeliverable for this buyer regardless of any other capability Mekorma offers.

Requirement evaluated: Dual approval requirement for all capital expenditures regardless of amount

Your company runs Sage Intacct, and this is the foundational incompatibility with Mekorma. Mekorma's Payment Hub is built natively inside Microsoft Dynamics 365 Business Central and Dynamics GP; it is not designed to connect to or operate within Sage Intacct. Setting ERP compatibility aside entirely, Mekorma's documented approval routing logic operates on two triggers: dollar-value threshold ranges (called Threshold Levels) and Vendor Classes. Your dual-approval CapEx requirement calls for a third trigger: GL account type classification, where any invoice coded to a capital expenditure account automatically routes to two approvers, independent of dollar amount. …

Limitations: Mekorma has no Sage Intacct integration at any price point; it runs exclusively inside Microsoft Dynamics GP, Business Central, and Acumatica. Even on its native ERPs, its approval routing is bounded by dollar-value thresholds and vendor class, not by GL account type, so the CapEx-triggers-dual-approval-regardless-of-a …

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: Approval delegation with automatic expiration (e.g., delegate to backup for 5 business days while on PTO)

For a multi-location services company managing AP approvals across 3 staff members and 6 locations, Mekorma does offer a documented out-of-office approval delegation mechanism within its Dynamics GP product. <cite index="1-4">Mekorma Payment Hub allows approvers to delegate their approval responsibilities while out-of-office.</cite> The approver self-configures the delegation directly in the Mekorma User Preferences window: <cite index="1-9,1-10">they check the box 'Enable Out-of-Office Re-Route of Approval' and use the look-up to select the desired delegate.</cite> Critically for the buyer's requirement, <cite index="10-4,10-5">the approver chooses the date range for which they would like t …

Limitations: Mekorma does not integrate with Sage Intacct; the out-of-office delegation feature documented in Mekorma's own help articles is specific to Dynamics GP, so this buyer cannot use this capability without replacing their ERP. …

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: Spend analytics: top vendors, spend by GL category, month-over-month trending

For a $120M services company running Sage Intacct, Mekorma cannot deliver this requirement for two independent reasons. First, Mekorma is built exclusively for Microsoft Dynamics 365 Business Central, Dynamics GP, and Acumatica: its documentation and product pages make no reference to Sage Intacct as a supported ERP, and Mekorma does not appear in the Sage Intacct Marketplace. The product cannot be deployed in this buyer's environment. Second, even on its native platforms, Mekorma has no documented spend analytics capability of the kind requested. …

Limitations: Mekorma does not integrate with Sage Intacct, making it incompatible with this buyer's ERP environment entirely. On its native platforms, Mekorma offers no documented mechanism for spend analytics by GL category, top-vendor ranking, or month-over-month trending; any such reporting would have to be sourced from the unde …

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: Spend analytics: top vendors, spend by GL category, month-over-month trending

For a $120M services company running 1,800 invoices per month across two Sage Intacct entities, Mekorma cannot address this requirement on two compounding grounds. First, Mekorma is purpose-built for Microsoft Dynamics 365 Business Central, Dynamics GP, and Acumatica; its fact sheet explicitly describes it as 'built natively into Microsoft Dynamics environments' with no Sage Intacct integration documented anywhere in the product. Second, within the ERP environments it does support, Mekorma's documented capabilities cover payment execution, check and ACH processing, batch approval workflows, vendor validation, and MICR printing. …

Limitations: Mekorma has no integration with Sage Intacct and no native spend analytics layer; the buyer would need to rely entirely on Sage Intacct's own built-in reporting tools (which are capable but require no AP automation vendor to surface) …

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.

Requirement evaluated: Multi-entity support within the integration; we operate 2 entities in Intacct and plan to add a third

Your business runs 2 Sage Intacct entities today and plans to add a third; this requirement asks whether an AP automation layer can connect to those entities, preserve entity-level data isolation, and route invoices to the correct Intacct books. Mekorma cannot satisfy this requirement because it has no Sage Intacct integration at any tier. Mekorma is built exclusively as an embedded solution inside Microsoft Dynamics 365 Business Central, Dynamics GP, and Acumatica: every capability in the product, including its multi-company payment consolidation and approval workflows, operates within those Microsoft Dynamics environments only. …

Limitations: Mekorma does not offer a Sage Intacct connector at any price point or packaging tier; this is a platform boundary, not a missing add-on. A buyer on Sage Intacct would need to evaluate a different vendor entirely.

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

Your company runs Sage Intacct across 2 entities, and the integration setup requirement is predicated on Mekorma connecting to that ERP. Mekorma does not offer a Sage Intacct integration. Every Mekorma product, including the Payment Hub, Remote Payment Services, and its invoice capture tools, is built exclusively for Microsoft Dynamics GP, Microsoft Dynamics 365 Business Central, and Acumatica. The vendor's own user guide library lists supported platforms as 'Microsoft D365 Business Central, GP and Acumatica Cloud ERP' with no mention of Sage Intacct anywhere in their documentation or product catalog. …

Limitations: Mekorma is a Microsoft Dynamics-native vendor; adopting it would require your organization to migrate off Sage Intacct, which is a foundational ERP change, not an AP automation decision. This disqualifies Mekorma for any buyer whose ERP of record is Sage Intacct.

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: Complete audit trail: every action timestamped with user ID, viewable by invoice or by user

Your company runs Sage Intacct across two ERP entities, and Mekorma is purpose-built exclusively for Microsoft Dynamics 365 Business Central, Dynamics GP, and Acumatica. There is no Mekorma integration with Sage Intacct, which means the product cannot be deployed in your environment at any price or configuration. Within the Microsoft Dynamics environments it does support, Mekorma provides an Audit Log Report (accessible at Mekorma Area Page > Inquiry > System > Audit Log) that records posted check and EFT batch details including the approvers and authorizers of each batch, filterable by Checkbook ID, Batch ID, or Posting Date, with drill-down to batch-level detail. …

Limitations: Mekorma has no Sage Intacct integration and cannot be implemented in your environment; this alone makes the capability unavailable to you. For buyers on compatible Microsoft Dynamics platforms, the audit trail covers posted payment batches only, lacks a per-user activity view, and does not capture pre-payment invoice l …

Requirement evaluated: SOC 2 Type II certification (current, not in-progress)

Your team's requirement is for a current, dated SOC 2 Type II attestation report from a licensed CPA firm, confirming that Mekorma's own controls operated effectively over a minimum six-month audit period. Three targeted searches, including a direct search of mekorma.com's security and terms-of-use pages, returned no trust center, no SOC 2 report (Type I or Type II), no compliance badge from platforms such as Vanta or Drata, and no in-progress audit statement of any kind. …

Limitations: No evidence of a current SOC 2 Type II report, trust center, or third-party audit attestation was found on Mekorma's website or in any external index after exhaustive search; the buyer should request this documentation directly from Mekorma before proceeding, as its absence from all public-facing channels is a material …

Requirement evaluated: AI-powered anomaly detection for unusual invoice patterns (spike in amount, new bank account, unusual vendor behavior)

Your team processes 1,800 invoices monthly across two Sage Intacct entities and needs a system that can proactively flag unusual patterns, such as an invoice amount spiking beyond a vendor's historical baseline, a new bank account appearing on a known vendor record, or a dormant vendor suddenly reactivating. Mekorma's documented security capabilities operate at the payment-execution stage and address a different problem: the Vendor Validation module runs automated TIN matching against IRS records, OFAC sanctions screening, and Google address verification before a payment is released, and can block payments when those checks fail (Mekorma Vendor Validation page, mekorma.com/solutions/vendor-v …

Limitations: Mekorma's security model is built on point-in-time compliance checks (OFAC list, TIN validity, address format) and human-oversight controls (dual approval, segregation of duties). …

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: Learning capability: accuracy should improve over time on our specific vendor invoice formats

Your team runs Sage Intacct as its ERP. Mekorma's Invoice Capture product, which is the only mechanism the vendor offers for invoice data extraction and AI reading, is documented exclusively for Microsoft Dynamics GP, with a separate Business Central path delivered through a partner (SignUp Software). No Mekorma invoice capture product for Sage Intacct exists in any documentation found across the vendor's product pages, user guides, or help center. …

Limitations: Mekorma Invoice Capture is a Dynamics GP and Dynamics 365 BC product; there is no version for Sage Intacct, which makes the entire invoice capture and learning capability unavailable to this buyer without replacing their ERP. …

Requirement evaluated: Learning capability: accuracy should improve over time on our specific vendor invoice formats

For a $120M services company running Sage Intacct, this requirement cannot be met by Mekorma. Mekorma's Invoice Capture product is built exclusively for Microsoft Dynamics GP, using Microsoft Power Platform and AI Builder to receive invoices by email, extract data, and push records into Dynamics GP. For Business Central users, Mekorma redirects to a partnership with SignUp Software. There is no Mekorma invoice capture product for Sage Intacct, meaning the prerequisite mechanism for any learning capability simply does not exist for this buyer's environment. …

Limitations: Mekorma's Invoice Capture is a Dynamics GP-only product with no documented Sage Intacct integration, making it unavailable to this buyer entirely. The AI learning model it relies on (Microsoft AI Builder) …

Requirement evaluated: Confidence scoring on extracted data so AP clerks know which fields to verify vs. which are high-confidence

For your 3-person AP team at a $120M Sage Intacct shop, Mekorma's invoice capture capability has two compounding problems. First, Mekorma's Invoice Capture product is built exclusively for Microsoft Dynamics GP and, via a partnership with SignUp Software, for Dynamics 365 Business Central. There is no Mekorma invoice capture module designed for or integrated with Sage Intacct, which is your ERP of record. …

Limitations: Mekorma Invoice Capture is incompatible with your Sage Intacct environment at the platform level; it requires Dynamics GP or Business Central. Even setting aside the ERP mismatch, the product extracts only four header-level fields and presents them in a flat validation queue with no confidence differentiation, which me …

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: 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: Payment approval workflow: all payment batches require CFO or Controller electronic approval before release

This buyer runs on Sage Intacct. Mekorma's payment approval workflow is a well-documented, genuinely capable mechanism: within its supported ERPs, the Payment Hub enforces a hard separation between the Requestor (who builds batches) and the Approver (who must electronically authorize before any batch can print or release), with named role levels such as MEKORMA_APPROVER_LEVEL_1 and MEKORMA_APPROVER_LEVEL_2 that can be assigned to specific executives like a CFO or Controller, and threshold-based rules that require progressively higher-level sign-off on larger batches. …

Limitations: Mekorma has no Sage Intacct integration; the buyer's ERP is outside Mekorma's supported platform set, making every Mekorma capability, including its payment batch approval controls, unavailable to this buyer without an ERP migration. This is a foundational compatibility failure, not a feature gap.

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