Mekorma vs Ottimate vs Ariba for AP Automation

For a 3-person AP team at a multi-location services company, Ottimate supports segregation of duties across three distinct, separately permissioned stages: invoice capture, invoice approval, and payment execution. Administrators configure these stages through separate policy types: 'Invoice Approval Policies' and 'Payments Approval Policies' are distinct configuration objects in Admin Settings, and the 'Approve Invoices' permission is a separately grantable role capability from capture/entry access. Invoice Approval Policies and Payments Approval Policies are created separately in Admin Settings, and role-based approval policies allow any user from a specific role to serve as approver, with roles assigned explicitly by the administrator. At the payment stage, the 'Expedite Check' and 'Approve Payment' permissions are separated, requiring explicit access to each, and a 2025 platform update further tightened this to prevent unintended payment actions. The standalone Payments page is visible only to users with Admin or General Manager roles, and bulk payment export actions are restricted to those same roles. Additionally, a 'Force Approve' capability exists for administrators or roles with that permission enabled, with an added verification step required. The segregation is enforced through role configuration: an admin assigns entry-only roles to AP clerks, approval roles to managers, and payment roles to controllers, keeping these non-overlapping across the team.

For your 3-person AP team on Sage Intacct, SAP Ariba Buying and Invoicing enforces two of the three SoD legs natively within its own platform. First, invoice entry and invoice approval are controlled by distinct user groups: AP staff who key invoices belong to entry-level system groups, while approvers are configured separately with approval permissions, and the system prevents the same user from holding both roles simultaneously. Second, a configurable approval-flow rule called 'Prevent Self-Approval Under Delegation' blocks a delegatee from approving their own documents, and a filter rule action explicitly 'removes the requester from the approval flow if the requester was added as a separate approver' (SAP Learning: Discovering Additional Approval Rule Types). These controls cover the entry-cannot-approve leg across both your PO-based and non-PO invoice populations. The third leg, approver-cannot-process-payment, is where Ariba's native control stops: once the invoice reconciliation is fully approved, Ariba generates an OK2PAY file and sends it to Sage Intacct, where the payment run is actually executed. 'Buyers can submit payments using the ERP system or using Ariba Pay on the Ariba Network' (SAP Learning: Understanding Invoicing Basics). Because payment release happens inside Sage Intacct under Sage's own role-based permission model, Ariba cannot enforce that the Ariba approver is excluded from the Sage Intacct payment release role. The buyer must configure that third-leg control separately in Sage Intacct's AP payment approval settings.

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. Within its supported platforms, Mekorma does offer a documented Task-Based Security model that assigns distinct roles to AP clerks, approvers, and payment processors, and its Secure Approval Workflow gates payment batches so they cannot be processed until the appropriate approver signs off — release notes confirm that the first approver in a two-approver chain is blocked from approving a batch a second time. The company also explicitly advocates keeping invoice approval and payment approval separate with different authorizers as a segregation-of-duties best practice. But every element of this architecture operates inside Dynamics GP or Business Central. Because Mekorma cannot be deployed into your Sage Intacct environment at any price or configuration, none of its SOD controls are available to your AP team.

For your 3-person AP team processing 1,800 invoices/month, Ottimate addresses several vendor-facing needs through a combination of point-specific tools rather than a single unified self-service portal. Banking detail entry works via an AP-initiated email invitation: once your AP team flags a vendor for ACH in the Vendors module, the vendor receives a secure link, completes their banking fields, and creates a login at vendor.plateiq.com, with micro-deposit verification taking 1-3 business days (Ottimate Help Center: 'Vendor ACH Verification', 'How do I Invite Vendors to Accept ACH Transfers'). Invoice submission is handled through a vendor-specific email address that routes invoices directly into Ottimate's ingestion queue, reducing your team's data entry workload (ottimate.com/feature/invoice-automation). Payment status inquiry is addressed by Ottimate's Invoice Status Tracker, launched June 2026, which lets suppliers enter an invoice number, date, and amount in a browser to see a three-step status (received, under review, payment initiated) with no account or login required (ottimate.com/feature/supplier-invoice-tracker, ottimate.com/blog/supplier-invoice-tracker). However, new vendor self-registration is not a vendor-initiated flow: vendors cannot discover and onboard themselves; your AP team must set up the vendor record first and then trigger the ACH invite. Most critically, no W-9 or W-8 collection mechanism appears anywhere in Ottimate's documented feature set; tax document collection is absent from the platform's help center, product pages, and marketing materials.

For a $120M multi-location services company on Sage Intacct, SAP Ariba delivers vendor self-service through two complementary layers. First, the SAP Business Network (formerly Ariba Network) provides supplier self-registration at supplier.ariba.com: suppliers receive an email invitation, click a unique registration link, and complete a guided wizard that collects company name, address, contact credentials, and business profile data. Second, the Supplier Lifecycle and Performance (SLP) module extends that registration into structured onboarding questionnaires where suppliers self-enter tax IDs (with country-specific validation), bank account details including account holder name, account number, and ABA routing number (via structured Bank Account question types with built-in syntax validation), certifications, and compliance documents. For invoice submission, suppliers on SAP Business Network can submit PO-based invoices via PO flip, non-PO invoices via web form, or PDF upload; both PO and non-PO invoice types are supported through the supplier-facing network portal. For payment status, SAP Business Network offers a dedicated Invoice Status Portal described as 'a self-service solution that allows suppliers to view their invoice and payment status at anytime, reducing the need to contact their customers.' However, two mechanism-level shortfalls apply to this buyer. First, SAP's own help documentation explicitly states that SAP Ariba does not support collecting sensitive personal information for individuals, including social security numbers and bank information for individuals, in supplier management questionnaires; this means W-9 collection for sole proprietors and individual subcontractors (a common vendor type in a services company) is not covered by the SLP questionnaire mechanism. Second, the Invoice Status Portal requires SAP Cloud Integration Gateway for SAP ERP systems or cXML integration for non-SAP ERP systems; because this buyer uses Sage Intacct rather than an SAP ERP, connecting invoice status data to the portal requires a cXML or middleware integration, not a pre-built native Sage Intacct connector, adding implementation complexity at the payment-status step of the journey.

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) is operated entirely by your AP team inside the ERP; suppliers do not log in, register, or submit documents themselves. Its Remote Payment Services (RPS) add-on delegates vendor enrollment and banking-detail maintenance to a third-party payment partner (Corpay), whose own portal allows enrolled vendors to select a payment method and view Corpay-processed payments, but that is Corpay's portal, not a Mekorma-built interface, and it covers only payment-method selection and payment inquiry for Corpay-routed payments rather than new vendor registration, W-9/W-8 collection, or invoice submission. No Mekorma-owned product, module, or add-on provides vendor self-registration, supplier-initiated W-9/W-8 upload, supplier-entered banking credentials, supplier invoice submission, or a supplier-accessible payment status dashboard.

For a $120M services company running two Sage Intacct entities, Ottimate connects via its own API platform directly to Sage Intacct's Web Services, with no third-party middleware required. Ottimate is listed on the Sage Intacct Marketplace under the Direct Integrations category, which Sage defines as connections built by partners using Web Services to connect to Sage Intacct. On the data flow side, Ottimate explicitly states that 'invoices, corporate cards, and vendor payments' are kept 'up-to-date in both directions,' covering the core bidirectional sync this buyer requires. The integration reaches across all major Sage Intacct modules, including AP, AR, GL, and Purchasing, and it carries Intacct's standard dimensions as well as any customized dimensions and metadata fields configured within Sage Intacct entities, so your location, department, and entity coding structure in Intacct is available for line-level invoice coding inside Ottimate. The Sage Intacct integration is included in the standard Ottimate subscription at no additional charge and supports Sage Intacct versions 8.31 and higher for cloud-based subscriptions.

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. There is no Mekorma entry in the Sage Intacct Marketplace, no connector documentation for Intacct's XML Web Services or REST API, and no support for Intacct-specific constructs such as dimensions, locations, or multi-entity books. Mekorma's Payment Hub is structurally embedded inside Microsoft ERP environments; it has no integration layer for Intacct at any price or packaging tier.

For this $120M, 2-entity Sage Intacct company, SAP Ariba does not offer a native, pre-built, bidirectional connector to Sage Intacct built into its own platform. SAP Ariba's documented integration architecture, the Cloud Integration Gateway (CIG) and SAP Integration Suite, is designed exclusively for SAP ERP and SAP S/4HANA backends: the SAP help portal states that the managed gateway 'allows you to easily integrate SAP ERP and SAP S/4HANA backend system with your trading partners and SAP Ariba solutions,' with no Sage Intacct path documented. The next-generation SAP Ariba Invoicing product page confirms its compatible backends as 'SAP S/4HANA Cloud Public Edition, SAP S/4HANA Cloud Private Edition, SAP S/4HANA (2022 support pack 1 or later), and SAP ERP Central Component,' and explicitly notes that 'compatibility with third-party ERP systems will be added in future releases' — meaning Sage Intacct is not supported today. For non-SAP ERPs, Ariba's own training documentation states that 'enterprise integration is provided by the SAP Cloud Integration Gateway, SAP Ariba Integration Toolkit or other middleware,' and an SAP Community thread asking about a Sage ERP integration with Ariba was answered directly: 'You will have to use CIG integration in Mediated Connectivity i.e via a middleware.' The only documented Ariba-to-Sage Intacct connection in the market is provided by APIWORX, a third-party managed integration provider — not a connector built into and maintained by Ariba itself.