Microsoft Dynamics GP Accounts Payable Automation Compared

Short answer: Microsoft Dynamics GP already has native accounts payable approval workflow, so unlike every other ERP in this series the thing you are actually buying from a third party is invoice capture, not routing. That changes the shortlist and it changes what you should pay. It also runs against a clock: Microsoft ends Dynamics GP product support on 31 December 2029 and stops issuing security patches on 30 April 2031, and not one vendor selling AP automation for GP mentions either date on its product page.

The deadline that changes the math

Microsoft announced the end of Dynamics GP in September 2024 and confirmed the dates on Microsoft Learn. Product enhancements, regulatory tax updates and technical support end on 31 December 2029. Microsoft moved that date back from an earlier 30 September 2029 target specifically so payroll customers would not be caught mid fiscal year. Security updates and patches, if needed, remain available until 30 April 2031.

Older GP versions ran on the Fixed Lifecycle Policy and several have already fallen off it. Here is where each version stands as of September 2026.

If you are running GP 2016, extended support ended two months ago. That is worth surfacing to whoever owns your IT general controls, because an AP system sitting on an unsupported database platform is the kind of finding that turns up in an audit rather than in a status meeting. Teams that formally track control obligations tend to catch this early, and if yours does not have a system for mapping obligations to the controls that satisfy them, an end-of-support date on a financial system is a good reason to start.

Microsoft's own recommended path is Dynamics 365 Business Central, which it names explicitly in the lifecycle documentation. That matters for this decision: if you are likely to migrate to Business Central inside the next three years, buying a GP-only AP tool with a long implementation and a multi-year contract is money you spend twice. Our breakdown of AP automation for Business Central covers what the connectors look like on the other side.

Perpetual license sales for GP have also ended, and Dynamics partners report new subscription license sales closed in April 2026. Microsoft's lifecycle page does not list those dates, so treat them as partner-reported rather than confirmed, but the direction is not in question.

What Dynamics GP already does natively for AP

This is the section that saves most GP shops money, because the vendor marketing for this category is written for ERPs that cannot do what GP can.

GP handles accounts payable through Payables Management. Vendor records, invoice entry, batch processing, check runs and EFT all live there, and that part is unremarkable. The interesting piece is Workflow 2.0, which Microsoft introduced in GP 2013 R2 and which runs entirely inside Dynamics GP rather than depending on SharePoint the way the earlier workflow module did. GP 2015 R2 then added Payables Management invoice approval, so individual invoices can be submitted for approval rather than only whole batches.

In practice that means GP can already route an invoice to a named approver based on criteria you configure, including dollar thresholds. The approver can approve, reject or delegate from the Payables Transaction Entry window, from the automatically generated email notification, or through the PM Batch Approval workflow, and comments are tracked as part of the approval record.

Read a Dynamics GP AP automation product page and you will see "automated approval workflows" sold as a headline benefit. For GP specifically, a large part of that is a feature you already own and may simply have never configured. Before you buy anything, have your partner turn on Workflow 2.0 payables approval in a test company and see how much of your problem disappears.

What Dynamics GP does not do

What GP has never done is get the invoice into the system in the first place. There is no native OCR, no invoice capture, no email intake and no automatic line-level coding. Somebody keys the invoice, and that keying is where the hours and the errors live. Every credible third-party product for GP is, at its core, solving that one problem, and the approval features are packaging.

So the honest buying question for a GP shop is narrow: what is the best way to stop keying invoices, on a platform with a known end date?

The AP automation options built for Dynamics GP

Several vendors publish GP-specific pages. The three worth serious evaluation differ less on feature checklists than on architecture, and architecture is what determines whether the project survives a GP upgrade or a migration.

Mekorma

Mekorma is the one that is genuinely different. It positions itself as "Mekorma Ease, Embedded in your ERP", and it means it literally: these are add-ons that install into Dynamics GP rather than a separate cloud application that talks to GP. Its invoice capture uses AI to "read and transfer invoices into Dynamics GP, without human intervention". Mobile approval works outside GP, letting approvers view payables transactions and vendor entries awaiting approval and approve in bulk. On the payment side it automates payment batch building and processing, prints checks with electronic signatures, and supports remote approval from a mobile device or browser. It also does vendor validation.

Embedded architecture has a real advantage and a real risk. The advantage is that there is no sync to break, because the data never leaves GP. The risk is that your AP automation is tied to the life of GP itself, which now has a date on it. Mekorma does not publish pricing and routes to a discovery call or quote request.

Rillion

Rillion runs the more conventional model: capture, code and route invoices in Rillion, then post to GP. It states that "approved header and line data are sent to Microsoft Dynamics GP for posting in Payables Management", and that payment outcomes and remittance information are reflected back into Rillion for centralized archiving. Its own summary of the arrangement is that "you continue reporting and balancing in GP while Rillion removes manual data entry", which is a fair description of what you are actually buying.

It carries a cascading PO-matching engine supporting both two-way matching of invoice to PO and three-way matching of invoice, PO and goods receipt. Unlimited users are included at no extra cost, which is unusual enough in this category to be worth noting when you compare against per-seat vendors. Rillion does not publish pricing on its GP integration page and directs you to book a demo.

One thing Rillion does not state anywhere on that page is the integration mechanism. It describes what moves and in which direction, but never says whether it is a live API, a scheduled sync or a connector service. That gap has mattered in every one of these ERP comparisons we have run, so ask before you sign.

AvidXchange

AvidXchange sells AvidSuite for Microsoft and describes an API integration with automatic syncing between its platform and Dynamics GP, a fully paperless process, multiple payment methods, and configurable two-way and three-way PO matching. It is the option that also gives you a payment rail, which matters if writing checks in-house is part of what you are trying to stop doing. AvidXchange does not publish list pricing. Note also that on AvidPay Direct, AvidXchange charges the supplier a per-transaction fee whose rate is set in each individual Supplier Services Agreement rather than published, so third-party quotes of a specific percentage are not AvidXchange rates.

Beyond those three, CoreIntegrator has worked in the GP AP space for over twenty years, MetaViewer sells a paperless AP product across GP and Dynamics 365, Stampli publishes a Dynamics GP connector, and Quadient publishes a GP-specific buyer guide. None of them publish pricing either.

Integration mechanism, side by side

This is the table to actually use, because it is the part that decides implementation risk.

Across this series we have now found four genuinely different integration architectures for the same category: file export, live API, a bridge service, and Mekorma's embedded model. Never assume a vendor's integration quality carries across its own portfolio, and never assume a competitor's model is the same as the one you are looking at.

How to choose, given the end date

Work backwards from your migration plan rather than forwards from a feature list.

If you expect to stay on GP through 2029 and then move, buy the shortest commitment you can get and prioritize a product whose data you can extract cleanly. An embedded product that lives inside GP is efficient right up until the moment GP goes away, at which point your invoice history and coding rules are a migration problem rather than a portable asset.

If you are already planning a Business Central migration inside two years, the calculation is different again. Do not sign a long GP-specific contract. Either solve capture with something platform-neutral that can follow you across, or wait and buy once on the new system.

And if the real pain is simply that three people key four hundred invoices a month, test how far native Workflow 2.0 approval plus a capture-only tool gets you before committing to a full enterprise AP suite with an implementation project attached.

Frequently asked questions

When does Microsoft Dynamics GP support end?

Microsoft ends Dynamics GP support on 31 December 2029 for product enhancements, regulatory tax updates and technical support. Security updates and patches remain available until 30 April 2031. Microsoft moved the first date back from 30 September 2029 so payroll customers could complete a full fiscal year, and recommends transitioning to Dynamics 365 Business Central.

Does Dynamics GP have built-in accounts payable approval workflow?

Yes. Workflow 2.0 arrived in GP 2013 R2 and runs entirely inside Dynamics GP with no SharePoint dependency. GP 2015 R2 added Payables Management invoice approval for individual invoices. Approvers can approve, reject or delegate from the Payables Transaction Entry window, from an emailed notification, or via PM Batch Approval, and comments are retained in the approval record.

Does Dynamics GP do OCR or invoice capture?

No. Dynamics GP has no native OCR, no invoice capture, no email intake and no automatic line-level coding. Invoices are keyed into Payables Management manually. This is the specific gap every third-party AP automation product for GP is built to close, and it is the capability worth paying for.

Should I buy AP automation for GP if support ends in 2029?

It depends on your migration timeline, not on the calendar alone. Three years is long enough for capture automation to pay back several times over at meaningful invoice volume. The risk is contract length and data portability, not the purchase itself. Buy short terms, confirm you can export invoice images and coding history, and avoid multi-year commitments to a product that cannot follow you to your next ERP.

What is the best AP automation for Microsoft Dynamics GP?

There is no single answer, because the three serious options solve different shapes of the problem. Mekorma suits shops that want everything to stay inside GP and that need check printing and payment batch control. Rillion suits shops whose main pain is PO matching at volume and who have many occasional approvers, since users are unlimited. AvidXchange suits shops that also want to stop handling payments in-house. None publish pricing, so budget for a sales cycle on all three.

How much does AP automation for Dynamics GP cost?

None of the GP-specific vendors publish list pricing, so any number you see online is a third-party estimate rather than a vendor rate. Expect a quote driven by invoice volume, module scope and whether payments are included. Our AP automation pricing guide collects which vendors in the wider category publish real figures and which route you to sales, which is a useful anchor before a GP quote conversation.

Where AutoPayables fits, and where it does not

We are not a Dynamics GP product and we will not pretend to be. We have no GP connector, and an accounting sync is on our roadmap rather than in the product today. What we do is the capture half: AI extraction of vendor, invoice number, PO number, dates, currency, subtotal, tax, discount, shipping, total and line items from an upload or an email, with a confidence score stored on every field, and line-level GL coding where each individual invoice line carries its own GL account. There is a REST API on the Scale plan, and pricing is published: free for 20 invoices a month, $49 for 200, $149 for unlimited.

What we do not do: two-way or three-way PO matching, duplicate invoice detection, multi-level or role-based approval routing, any payment rail, and any direct sync to GP or any other ERP. If your GP project needs matching or payments, one of the three vendors above is the right call. If what you need is to stop keying invoices and get clean coded line data you can move across an ERP migration, that is the narrow job we built for, and you can test it on a real invoice without a demo booking. Our comparison of AP automation software and our page on ERP AP modules versus standalone AP software both go deeper on that trade-off.

Last updated September 2026. Lifecycle dates verified against Microsoft Learn and the Microsoft Dynamics 365 blog on 8 September 2026. Vendor claims quoted from rillion.com, mekorma.com and avidxchange.com on the same date. No vendor in this category publishes list pricing; we re-verify on a recurring schedule and correct this page when that changes.