Microsoft Dynamics GP

Microsoft Dynamics GP, formerly Great Plains, is Microsoft’s ERP for accounting, inventory, and operations, deployed on-premise or through partner hosting on Windows and SQL Server. Many long-established warranty and service contract programs still run their financial operations on it. For ProPay, Dynamics GP is downstream of a decision already made, the system ProPay writes approved contractor and supplier payment records into. Nothing reaches Dynamics GP until ProPay has validated the invoice against the authorization record that approved the work.

What ProPay sends to Dynamics GP

ProPay validates contractor and supplier invoices against the authorization decision that approved the repair or parts order, the same decision that carried a confidence level and a documented reason at the time it was made. Only invoices that pass that check reach Dynamics GP.

Every payment instruction ProPay sends to Dynamics GP traces back to a specific claim: a validated invoice, an authorization decision made at a known confidence level, and, where a homeowner was involved, the SMS conversation that confirmed the work was done.

That’s what Dynamics GP receives: a payment instruction with the underlying claim, invoice, and authorization already reconciled, not a raw invoice needing separate review.

How the Dynamics GP connection works

Dynamics GP runs on Microsoft SQL Server and supports integration through eConnect and its web services layer, which is where ProPay writes payment and invoice records.

Because Dynamics GP deployments vary widely in age and customization, a Forward Deployed Engineer maps ProPay’s payment records to your specific chart of accounts and approval structure during deployment, so what lands in Dynamics GP fits how your finance team already reconciles spend.

What stays in Dynamics GP

Dynamics GP continues to own the actual disbursement, reconciliation, and financial reporting exactly as it does today. ProPay supplies validated payment instructions; Dynamics GP remains the system of record for the money itself.

Data handling and security

Payment data written into Dynamics GP comes from a company-specific ProPay instance, one client’s financial data is never accessible to another. ProPay is SOC 2 compliant, with both Type I and Type II audits complete.

Every payment ProPay sends to Dynamics GP is logged alongside the authorization decision and confidence level behind it, so any payment landing in Dynamics GP is traceable back to the claim that generated it.

Deploying the integration

A dedicated Forward Deployed Engineer sets up the Dynamics GP connection to match your chart of accounts and payment approval structure before any live payments flow through it, accounting for the specific version and customization your instance runs.

Frequently asked questions about ProPay and Microsoft Dynamics GP

Does ProPay execute payments directly, or does Dynamics GP still control disbursement?

Dynamics GP remains the system of record for actual disbursement and reconciliation; ProPay supplies validated payment instructions once its own authorization check has passed.

How does ProPay connect to Dynamics GP?

Dynamics GP runs on Microsoft SQL Server and supports integration through eConnect and its web services layer. A Forward Deployed Engineer maps the connection to your specific deployment during setup.

Can a payment reach Dynamics GP without authorization?

No. Every invoice is validated against the authorization record before it’s written to Dynamics GP, recommendations outside configured thresholds route to a person first.