Last updated: October 15, 2026
A Dynamics GP and BILL integration moves approved invoices and payment results between the two systems so nobody re-keys them. BILL handles approval and payment. GP stays the system of record for the books.
TL;DR. Payment platforms like BILL, formerly Bill.com, sit outside your financial system, so the connection between them has to be built. It doesn’t come standard. A working integration lets your team enter and pay invoices in BILL while GP records everything in the ledger. What it automates depends on the method behind it, the mapping rules you set, and who maintains it. Ask your vendor which method it supports today.
A request we hear often goes like this. “People are fighting new ways to process their AP… I need some help to tie that data back to my accounting system.” The payables process changed, and the ledger didn’t catch up. If that sounds familiar, you’re in the right place. It’s one of the most common requests we get on our Dynamics GP support and optimization work, and the answer is rarely “buy another system.”
What the integration moves
Three things matter. Invoices that were approved in the payment platform. Payments that went out, with their dates and amounts. And the general ledger entries that follow from both.
Stephen Tanner, our founder, describes the finished result this way. “Once it’s running, you can enter your invoices at bill.com, pay them at bill.com, and have GP record them in your system of record for financial recording.” Your team works in one place. GP quietly keeps the books.
That’s the goal. Getting there takes a few decisions.
Why it isn’t out of the box
Payment platforms are built to do one job well, which is getting a vendor approved and paid, and they weren’t built around the structure of your general ledger, so they don’t know your chart of accounts the way GP does and the connection has to be designed rather than switched on.
“Whether it’s a bill.com … or any other third party cloud solution for payment automation… [those] systems are silos, meaning they don’t integrate directly to anything,” Stephen says. “But they can give you a report, or an export file, or an API connector that allows you to connect those payment transactions to an invoice in GP.”
Those three options are the whole menu. A report someone runs and loads. A file that gets exported and imported on a schedule. Or an API connector that passes data back and forth. Each one needs integration tooling on the GP side.
Then there’s translation. “Generally there’s some logic that has to go into the translation of what a bill.com thinks it should be versus what GP believes it needs to be,” Stephen explains. “So that’s where the integration settings come from.” In practice, that means deciding how a BILL vendor maps to a GP vendor ID, how an expense line maps to a GL account segment, and what happens when the two disagree about an amount.
Which tools GP gives you to build it
Microsoft’s developer documentation for GP names three integration tools, with Integration Manager moving data without custom programming, Web Services described as the preferred tool for integrating data, and eConnect serving as the fallback when a Web Services object isn’t available. Microsoft’s own page adds that it isn’t actively fixing issues in the eConnect shipping product because of the product’s life cycle.
That last point matters if you’re planning a build today. Plan for it. A connection built on tools Microsoft is no longer improving needs a partner who knows how to maintain it, which is the kind of work our Dynamics GP support team does every week. We’d rather you ask about that before the project starts than after it breaks.
Fair warning. Whether a payment vendor offers a native connector to GP has changed over the years. BILL announced a two-way sync with Dynamics GP and Business Central in April 2021. Always ask the vendor in writing which method it supports today, and what it will cost you to keep running.
What still needs a human
Integration removes re-keying. It doesn’t remove judgment. Someone still decides who approves a $40,000 equipment invoice. Someone still resolves the vendor that exists twice under two names. And someone owns the mapping table when you add a new GL segment.
Good integrations make those jobs visible. Bad ones hide them until month-end.
What it’s worth
Manual invoice handling is expensive. The Ardent Partners 2025 State of ePayables report, which Bottomline sponsored, found an average cost of $9.84 per invoice and 8.2 days to process, against $2.65 and 2.9 days for best-in-class teams. That’s a vendor-sponsored study. Your numbers will differ. But the gap shows where the hours go.
Payment method matters too. An Association for Financial Professionals survey from 2022, as reported by Nacha, put the median cost to issue a check at $2.01 to $4.00 and an ACH payment at $0.26 to $0.50. GP can already generate ACH files out of the box, with 10 standard formats that follow NACHA requirements according to Microsoft, which means a team can stop writing checks without buying anything new. “A lot of clients have been used to using checks,” Stephen says. Habit is hard to move. Moving them is a process change as much as a software one.
We’ve seen this work. One client’s accounts payable team cut data entry by 95% using scheduled integrations from their expense management system into GP. Nothing was replaced. The pieces they already owned just started talking.
Questions finance teams ask about connecting GP to BILL
Does BILL connect to Dynamics GP on its own?
BILL once announced a two-way sync with Dynamics GP, but connection methods change, so confirm in writing what your vendor supports today. Either way, someone still has to configure the mapping between BILL and your GP records. It isn’t plug and play.
Do we need custom development to make it work?
Often some, because the method decides how much build work you need, and a file-based approach can lean on Integration Manager while an API connector usually takes more. Ask for the scope in writing before you commit.
Is paying vendors through BILL cheaper than GP’s own ACH?
GP already generates ACH files for North American banks out of the box, so you may not need a third-party platform just to stop writing checks. In our experience, the gain from a platform shows up in invoice capture and approvals, not in the payment rail itself. We’d look at your volume first, because the right answer for a team paying 200 vendors a month isn’t the same as for one paying 2,000.
What happens to the integration if we move to Business Central later?
The payment platform stays, but the connection to the ledger gets rebuilt or reconfigured for Business Central’s structure, because the mapping logic is specific to the system on the other side. Budget for that early, and see our Business Central migration page for how we plan it.
How do we tell a good integration from a fragile one?
Ask who maintains it, what tool it’s built on, and what happens when GP is updated. A good build is documented, and the answers come back in minutes, not days.
Want it connected without replacing anything?
If your AP team is re-keying invoices into GP, tell us how the work flows today. We’ll show you what an integration could remove and what it would take to maintain. Start with a Free Business Assessment, or call (626) 403-9744.