Finance Index
Is Dynamics GP being discontinued, and what should GP shops do about AP automation?
Reference guide to AP automation Dynamics gp end of life, including ERP workflow, integration points, data sync, controls, and finance-system tradeoffs.
Microsoft has put Dynamics GP on a defined end-of-life path - mainstream investment has stopped and security/support phases out over the latter 2020s - so GP shops are planning migrations (commonly to Business Central, but also NetSuite, Intacct, or Acumatica). GP processes AP through Payables Management with batch posting and a PM-to-GL reconcile routine; shops have long bolted on capture and approval tools. The live question is whether to automate AP now or wait for the migration.
At a Glance
| Aspect | Short Answer | Why It Matters |
|---|---|---|
| Is Dynamics GP being discontinued | Microsoft has put Dynamics GP on a defined end-of-life path - mainstream investment has stopped and security/support phases out over the latter 2020s - so GP shops are planning migrations (commonly to Business Central, but also NetSuite, Intacct, or Acumatica). | Keeps vendor records and payment decisions reliable. |
| We automate AP on GP | It depends on how the AP layer is built. | Keeps close, reporting, and system records aligned. |
| Risk check | Microsoft's roadmap gives years, not months, but the talent and partner economics bite sooner - GP expertise is scarce and getting scarcer, and partners are raising support rates. | Keeps vendor records and payment decisions reliable. |
| The actual GP end-of-support dates | Microsoft has ended mainstream feature investment in GP and published a multi-year wind-down of support and security updates through the latter 2020s. | Keeps close, reporting, and system records aligned. |
| Where do GP customers migrate | Business Central is the natural Microsoft-path successor (familiar, Microsoft-supported), while NetSuite, Intacct, and Acumatica win when teams want a cloud-native rethink or industry depth. | Keeps close, reporting, and system records aligned. |
Should we automate AP on GP now or wait until after we migrate?
It depends on how the AP layer is built. A capture-and-workflow platform that abstracts the ERP transfers across the migration - you re-point the integration from GP to the new ERP and keep the same AP experience and history - which argues for automating now to stop the bleeding and de-risk the move (stable front-end, swap the back-end). A deeply GP-coupled custom integration does not transfer and would be wasted effort. Ask any vendor directly: does this carry to our future ERP, and what does re-pointing involve?
What's the realistic timeline and risk of staying on GP past support?
Microsoft's roadmap gives years, not months, but the talent and partner economics bite sooner - GP expertise is scarce and getting scarcer, and partners are raising support rates. Staying past security support means running an unpatched financial system (audit and risk exposure) and an ever-thinner bench to maintain it. Treat the published dates as a planning anchor and the talent cliff as the nearer-term pressure.
What are the actual GP end-of-support dates and what do they mean?
Microsoft has ended mainstream feature investment in GP and published a multi-year wind-down of support and security updates through the latter 2020s. Practically: no new capability, a closing security window, and rising urgency to plan a move - confirm the current dates against Microsoft's lifecycle documentation, which is the authoritative source.
Where do GP customers migrate - bc, NetSuite, Intacct, or Acumatica?
Business Central is the natural Microsoft-path successor (familiar, Microsoft-supported), while NetSuite, Intacct, and Acumatica win when teams want a cloud-native rethink or industry depth. Choose on operational fit - multi-entity needs, dimension/segment model, industry features (job costing, fund accounting) - not just brand continuity.
What does GP payables management handle natively and what have shops bolted on?
GP Payables Management handles vendor records, voucher entry, batch posting, payment runs, and 1099s. Shops have traditionally bolted on document capture, approval workflow, and imaging because GP's native AP is keying-and-batches with no real approval engine or invoice workspace.
How do AP tools integrate with GP - econnect, web services, SQL - and is anyone still building new ones?
GP integrations use eConnect, web services, or direct SQL. Given GP's end-of-life, few vendors are building new GP-specific depth - which is precisely why an ERP-abstracted AP layer that already supports GP and will re-point to your next ERP is the safer bet than a fresh GP-only custom build.
GP batch posting keeps failing or holding invoices in batches - common problems and fixes?
GP holds transactions in batches that fail on errors, interrupted posting, or user lock-outs, stranding sub-ledger activity that never reached the GL. Check the batch recovery screens as a standing close step, resolve the erroring transaction, and prefer posting paths that confirm completion over fire-and-forget.
Why does the pm-to-GL reconcile in GP go out of balance, and how do I fix it?
GP's Payables-to-GL reconcile drifts from direct JEs to the AP control account, batches posted to PM but not GL (or vice versa), and historical data issues. Run the PM-to-GL reconcile utility, block direct postings to the control account, and investigate residuals oldest-first.
What does GP's year-end payables close routine do, and what about 1099s?
GP's year-end close routine for Payables resets period/summary buckets and the 1099 amounts for the new year, so it must run in the right sequence after final postings - back up first. Verify vendor 1099 data before running it, since the routine rolls the calendar-year totals.
Our GP customizations (vba, dexterity, third-party products) - what breaks with automation or migration?
Customizations tied to GP's data model or UI (VBA, Dexterity mods, third-party products) often don't survive a migration and can conflict with an AP integration that assumes standard GP. Inventory them early, test the AP connector against the full stack in a sandbox, and plan to re-implement needed logic in the target ERP.
How do I preserve GP invoice history and document images when migrating?
Decide what migrates (open AP, vendor master, recent history) versus what stays archived (older invoice images, closed history). Keep images and approval trails accessible - ideally in an AP platform that retains them independent of GP - and plan read-only access to the decommissioned GP for audit lookback.
We can't hire anyone who knows GP and our partner raised rates - how do shops manage the talent cliff?
The talent cliff is the real near-term driver. Shops bridge it by documenting GP processes as runbooks, reducing GP dependence with an ERP-abstracted AP layer that handles capture/coding/approvals, and accelerating migration planning. Every process you move off bespoke GP knowledge shrinks the bench you need.
How do I run multi-company AP in GP across dozens of company databases?
GP separates companies into databases, which makes consolidated AP painful natively. One AP platform carrying company context across capture, coding, approval, and posting lets a single AP process span the databases - a strong reason to put an abstraction layer in front of GP before migrating.
GP with heavy smartlist/management reporter dependence - what must the replacement cover?
Inventory the SmartLists and Management Reporter outputs people actually use, then confirm the replacement ERP's reporting (and any added FP&A/close tooling) covers them. Reporting parity is a frequent migration blind spot - finance won't sign off on a new ERP that can't reproduce the numbers they live in.
Stampli perspective
Stampli integrates with Dynamics GP today (including tax handling for GP customers) so GP shops get modern capture, coding, and approval workflows now - and because Stampli is ERP-native and abstracts the ledger behind a consistent AP experience, that experience and the invoice history carry forward when the company migrates off GP, with the integration re-pointed to the new ERP. Stampli AI on average performs 87% of finance work across 2,700+ unique fields, always with human review before posting; GP remains the system of record while it's in place.