dynamics GP integration
5 min read

Utility Billing Software With Dynamics GP Integration

How utility billing software integrates with Microsoft Dynamics GP: what to post, GL mapping, file vs API, and what to ask a vendor.

See a 10-minute demo

For US Utilities serving 3,000-100,000 meters and for operations team, billing team and utility managers. For Heads of Billing who own collections accuracy and revenue leakage.

Written by
Sewanti Lahiri
Published on
November 3, 2026
Updated on
November 12, 2026

Utility billing software with Dynamics GP integration sends the results of each bill run, payment batch, and receivables update into Microsoft Dynamics GP automatically, so the finance team stops re-keying billing totals into the general ledger. A utility billing platform built this way keeps GP as the accounting system of record and handles billing, meter data, and customer accounts on its own side. This guide covers what should move between the two systems, how to map it to the GP chart of accounts, and what to ask a vendor before you sign.

Why Utilities Keep Dynamics GP When They Replace Billing

Many small and mid-size utilities run Microsoft Dynamics GP, long known as Great Plains, for accounting, and a separate system for billing and customer information. When the billing system reaches the end of its life, the finance side often does not want to move at the same time. Replacing billing and accounting together doubles the risk in a single project.

A utility usually keeps GP because it already holds:

  • The general ledger and the chart of accounts the auditors know
  • Accounts payable and vendor history
  • Payroll, where the utility runs payroll in GP
  • Fixed assets and depreciation schedules
  • Budgets and board reporting built on GP data

That makes the integration the deciding question. A new billing platform has to fit the accounting system the utility already trusts, without forcing a change to how the books are closed.

What Moves Between Billing and Dynamics GP

A billing-to-GP integration carries four kinds of data. Most of it flows from billing into GP, because billing is where the activity happens and GP is where it is recorded.

DataDirectionWhat GP uses it forWhat breaks if it is missing
GL journal entriesBilling to GPRevenue by service and fundRevenue is re-keyed by hand and month-end slips
Payments and cash receiptsBilling to GPCash and bank reconciliationDeposits in GP do not match payments in billing
AR balancesBilling to GPReceivables control accountThe AR control account drifts from customer balances
Payroll dataAs configuredPayroll in GPField and office hours are entered twice

The first three are the core of the integration. If revenue, cash, and receivables reach GP correctly every cycle, the finance team can close the month from GP without opening the billing system.

What a Dynamics GP Integration Should Do

Will your finance team still export a spreadsheet after every bill run?

If the answer is yes, the integration is a file hand-off, not an integration. A billing system that works properly with GP should:

  • Post summarized journal entries after each bill run, mapped to the correct GL accounts
  • Post payments and cash receipts by deposit, so bank reconciliation in GP matches
  • Send AR balances so the GP control account ties to customer balances in billing
  • Keep separate funds separate, for example water and sewer as distinct enterprise funds
  • Record which bill run or batch each entry came from, so auditors can trace it back
  • Flag a failed posting the same day instead of leaving a gap for month-end

The traceability point matters at audit time. Every journal entry in GP should point to a specific bill run or payment batch in billing, so a reviewer can follow a number from the ledger back to the customer accounts behind it.

Mapping Billing Activity to the GP Chart of Accounts

The integration is only as good as its GL mapping. Before go-live, every billing event needs a home in the GP chart of accounts. The same discipline applies to any ERP, as the guide to automating utility bill integration with ERP solutions explains, but GP utilities often carry years of account structure that the mapping has to respect.

Billing eventTypical GL entryWatch for
Bill runDebit AR, credit revenue by serviceRevenue split by fund, not lumped together
Payment receivedDebit cash, credit ARPayments posted to the right bank account
Penalty or late feeDebit AR, credit penalty revenueFees kept apart from service revenue
Customer depositDebit cash, credit deposits heldDeposits held as a liability, not revenue
Adjustment or creditDebit revenue, credit ARReason codes that auditors can read
RefundDebit AR or deposits, credit cashRefunds tied to the original payment

Walk this table with the finance director before configuration starts. The entries themselves are standard accounting. The work is agreeing on which GP accounts each one uses, and how funds and services are split.

File Exports vs API Integration With Dynamics GP

There are two common ways to connect billing to GP. Both can work. They differ in how quickly GP reflects billing activity and how failures show up. Payment platforms face the same choice, as the Paymentus payment processing integration guide shows.

DimensionFile exportAPI integration
How it worksBilling writes a file; staff or a scheduled job imports it into GPBilling sends entries to GP through an API on a schedule or as events happen
TimingBatch, usually daily or per bill runPer bill run, per batch, or near real time
Staff effortSomeone runs, checks, and imports each fileRuns without a manual step once mapped
Failure visibilityA missed file is found when totals do not matchFailed postings are flagged at the time they fail
Audit trailDepends on keeping the filesEach entry can carry its source batch reference
Best fitLow volume, simple chart of accountsMultiple funds, frequent bill runs, lean finance team

For a small team, the staff-effort row usually decides it. A file that someone has to remember to import is a task that slips during busy months.

How to Integrate Utility Billing With Dynamics GP

Who owns the GL mapping: billing, finance, or the vendor?

Settle that first. The steps below assume finance owns the chart of accounts and billing owns the source data.

  1. Inventory what GP holds today. List the funds, GL accounts, bank accounts, and any payroll data the billing system will touch.
  2. Agree the GL mapping. Map every billing event in the table above to a GP account, split by fund and service.
  3. Choose the connection method. Decide between file export and API based on volume, number of funds, and staff time.
  4. Set the posting schedule. Decide when journal entries, payments, and AR balances post, and make sure posting finishes before month-end close.
  5. Test with a parallel cycle. Run one full billing cycle in both systems and compare revenue, cash, and AR totals in GP to the old process.
  6. Assign daily monitoring. Name the person who checks for failed postings, and decide how fast a failure must be fixed.

The parallel cycle in step 5 is the protection that matters most. If GP totals match the old process for a full cycle, the integration is ready for go-live.

Questions to Ask a Billing Vendor About Dynamics GP

Can you show the Dynamics GP integration working in a test environment with our chart of accounts?

A slide is not evidence. Ask to see entries post, and ask the questions below in writing. The broader guide to choosing a utility billing system covers the rest of the evaluation.

  • Method: Is the GP connection built on an API, a file export, or a custom script?
  • Scope: Which of journal entries, payments, AR balances, and payroll does it cover?
  • Funds: How does it keep water, sewer, and other enterprise funds separate?
  • Failures: What happens when a posting fails, and who is told?
  • Cost and time: Is the GP connection included, or priced and scheduled as a custom project?

Ask the last question early. Some vendors treat an ERP connection as a separate services engagement, which changes both the cost and the go-live date.

Planning Around Dynamics GP's End of Support

Keeping GP is a sound choice today, but Microsoft ends product support and updates for Dynamics GP on December 31, 2029, so pick a billing platform whose GL mapping and API can point at a new ERP later without a rebuild. When the accounting move comes, the guide to Microsoft Dynamics GP migration for utilities covers it.

Where SMART360 Fits

SMART360 is the billing and customer information side of this picture, not the accounting system. Dynamics GP stays the book of record. SMART360 connects to GP through its REST API and sends the billing activity GP needs.

Integration needHow SMART360 handles it
GL journal entriesSent to GP through the REST API, mapped to the utility's GL accounts
Payments and cash receiptsSent to GP so deposits match payments in billing
AR balancesSent to GP so the control account ties to customer balances
PayrollConnected where the utility runs payroll in GP
Fund separationGL mapping keeps each service and fund distinct
Future ERP moveThe same API and mapping approach can point at a new ERP later

SMART360 includes 25+ pre-built integrations, and new custom API connections typically take 2 to 4 weeks. It is built for utilities serving 3,000 to 100,000 connections, with billing, meter data, service orders, and the customer portal on one platform.

Frequently Asked Questions

What is utility billing software with Dynamics GP integration?

It is a billing and customer information system that sends its financial results into Microsoft Dynamics GP automatically. After each bill run and payment batch, it posts journal entries, cash receipts, and receivables balances to the right GL accounts, so the finance team closes the month in GP without re-keying billing totals by hand.

Can a utility replace its billing system and keep Dynamics GP?

Yes. Many utilities replace billing first and keep GP as the accounting system of record. The new billing platform has to post to the existing GP chart of accounts, keep funds separate, and match GP's month-end close. Replacing billing and accounting in separate projects lowers the risk of each one.

What data should move from billing to Dynamics GP?

At minimum, journal entries for billed revenue by service and fund, payments and cash receipts by deposit, and AR balances for the receivables control account. Utilities that run payroll in GP may also connect payroll data. Each entry should carry a reference to the bill run or payment batch it came from.

Is an API or a file export better for connecting billing to Dynamics GP?

A file export is simpler to set up but depends on someone running and checking each file. An API integration posts entries without a manual step and flags failures when they happen. For utilities with several funds, frequent bill runs, or a small finance team, an API integration is usually the better fit.

Does SMART360 integrate with Dynamics GP?

Yes. SMART360 connects to Microsoft Dynamics GP through its REST API. It sends GL journal entries, payments and cash receipts, and AR balances to GP, and connects payroll data where the utility runs payroll in GP. Dynamics GP remains the accounting system of record.

Choosing Billing That Fits Your Accounting

The right billing platform for a GP utility is one that leaves the accounting system alone and feeds it cleanly. Agree the GL mapping with finance, choose a connection method that does not depend on someone remembering to import a file, test a full parallel cycle, and plan for the day the utility moves off GP. The utility billing software implementation guide covers the rest of the project plan. To see how SMART360 posts billing activity to Dynamics GP, book a demo.

About Two Cta Image

Ready to see how SMART360 fits your utility?

Book a personalized demo with the SMART360 team and see how SMART360 fits your utility?

Related Post From This Category