Dynamics GP integration for SaaS companies
Many of your prospective customers still run Microsoft Dynamics GP. Unity connects your product to it, syncing customers, invoices and cash receipts through GP's own modules, under your brand, managed by our team.
- Customers
- Invoices
- Payments
- Orders
- GP 2015 and later
- On-premises or hosted
- Multiple companies
- GP 18.x supported
Dynamics GP runs on the customer's own servers, so an integration needs a secure way in and a way to create transactions that GP's posting rules accept. Unity installs a lightweight agent inside your customer's network and connects to GP through its own REST connection, with no reliance on SmartConnect or Integration Manager. Our team builds the integration, delivers it under your brand and keeps it running through GP upgrades.
Dynamics GP records Unity maps for SaaS products
Each map uses GP's own modules and documents, so transactions land in the batches and accounts your customer's finance team expects.
| Dynamics GP record | Typical direction | What it's used for |
|---|---|---|
| Customers and addresses | Both ways | The companies your app bills or serves, with their bill-to and ship-to addresses |
| Inventory items | From GP | Products, SKUs and price levels your app quotes or sells against |
| Sales Order Processing documents | To GP | Orders and invoices captured in your app, created in GP's Sales Order Processing module |
| Receivables transactions | Both ways | Open invoices, credit memos and balances in Receivables Management |
| Cash receipts | To GP | Payments collected in your app, applied against the right open documents |
| Vendors and payables transactions | Both ways | Suppliers and bills for AP, spend and procurement platforms |
| General ledger transactions | To GP | Journal entries posted to the right account segments |
On-premises access without the old add-ons
Most GP customers run it on their own servers or with a hosting partner. Unity reaches it securely and works the way GP expects.
An agent inside the customer's network
A lightweight Intelligrate agent runs next to GP and runs scheduled processes every few minutes. No inbound firewall ports are opened.
No SmartConnect or Integration Manager
Unity connects to GP 2015 and later through its own REST connection. Your customer doesn't need to buy, license or maintain a separate integration add-on.
Every company database
GP customers often run several company databases. Unity connects to each one the customer chooses, with each company's data kept separate.
Built for GP's own posting rules
Transactions are created in GP's own modules and batches, so they follow the same validation and posting rules as documents entered by your customer's finance team.
Is it still worth integrating with Dynamics GP?
Yes, for now. Microsoft supports Dynamics GP with product enhancements, tax updates and technical support until December 31, 2029, and security updates until April 30, 2031. Many companies will keep running GP for years, and they need the same integrations as everyone else.
| Milestone | Date | What it means for your integration |
|---|---|---|
| End of enhancements, tax updates and support | December 31, 2029 | GP stays stable, so integrations built now keep working without chasing new releases |
| End of security updates | April 30, 2031 | The last date Microsoft patches GP, so customers plan their next ERP before then |
Dynamics GP problems we've already solved
These are the issues that stall do-it-yourself GP integrations, and how Unity handles each one.
Transactions sit in batches nobody posts
GP groups transactions into batches that must be posted before they reach the ledger. Unity posts batches automatically or leaves them for review, depending on each customer's preference.
Posting into a closed fiscal period
GP rejects transactions dated in a closed period. Unity raises a case with GP's own message, so finance can reopen the period or change the date.
An invoice arrives before its customer exists
GP won't accept a document for a customer ID it doesn't know. Unity's dependent maps create the customer first, then the document.
Integrations that need extra GP products
Many GP integrations depend on add-ons like SmartConnect or Integration Manager, each with its own licenses and upgrades. Unity's own REST connection removes that dependency.
Which SaaS products connect to Dynamics GP?
Payments and accounts receivable
Pull open receivables into your platform, collect payment, and create cash receipts in GP applied to the right invoices.
Transportation management (TMS)
Send sales orders from GP to your TMS for load planning, then return carriers, tracking numbers and actual freight costs so invoices carry the real shipping charge.
AP automation and spend management
Sync vendors, push approved payables transactions to GP, and return payment status to your app.
Ecommerce, CPQ and order management
Read items and price levels from GP, then create Sales Order Processing documents the moment a customer buys.
Field service and support
Keep customer records aligned, and send billable work back to GP for invoicing.
Unity is a managed integration service for SaaS companies, built on the Intelligrate iPaaS. We build your Dynamics GP integration, put your brand on it, monitor it, fix errors and handle upgrades. Integration updates can even flow into your own help desk. See how Unity works for SaaS.
Dynamics GP integration questions
Which Dynamics GP versions does Unity support?
Dynamics GP 2015 (version 14.0) and later, including the current 18.x releases, whether GP runs on the customer's own servers or with a hosting partner.
Do our customers need SmartConnect, Integration Manager or another add-on?
No. Unity connects to GP through its own REST connection and a lightweight agent inside the customer's network, so there's no extra GP integration product to buy or maintain.
How does Unity reach a GP server behind the customer's firewall?
Through a lightweight Intelligrate agent installed inside the customer's network. The agent connects out, so no inbound firewall ports are opened.
What if a customer later moves to Business Central?
Business Central is a different system with different records and processes, so it needs its own integration. Unity has a separate Business Central integration that we build and manage the same way.
Should we still build a Dynamics GP integration if GP support is ending?
Microsoft supports GP until December 31, 2029, with security updates until April 30, 2031, and many companies still run it. Integrating through Unity lets you sell to those customers now, without your team building and maintaining a GP integration in-house.
Are transactions posted automatically?
Either way. Unity can post GP batches automatically or leave them for finance to review, depending on each customer's preference.
How long does a Dynamics GP integration take?
A first Dynamics GP integration typically goes live in eight to twelve weeks. Each new customer after that is mostly configuration, since the maps are already built.
Your customers run other ERPs too
- All Unity integrations for SaaS
- SAP Business One
- All Microsoft Dynamics integrations
- Microsoft Dynamics 365 Business Central
- Microsoft Dynamics 365 Finance & Supply Chain
- Epicor Prophet 21
- All Epicor integrations
- Epicor Kinetic
- Infor SyteLine / CloudSuite Industrial
- All Infor integrations
- Infor VISUAL
- Infor LN
- Infor M3
- Infor SX.e
- Infor XA
- NetSuite
- Acumatica