Microsoft Dynamics GP and Wise integration

What moves between them

Approved payables flow from Dynamics GP to Wise. ml-connector polls Dynamics GP on your payment schedule for approved invoices, groups them by vendor, creates or reuses Wise recipients for each vendor, executes a quote to lock the exchange rate, and posts the transfer. Vendor bank details are stored encrypted in ml-connector; Dynamics GP holds no bank account information. Once posted to Wise, transfers are tracked back into Dynamics GP's audit log so your month-end reconciliation sees both the GP invoice and the corresponding Wise payout reference.

How ml-connector handles it

ml-connector presents your Windows domain credentials to authenticate against Dynamics GP's SBA or SOAP endpoint, using the exact tenant and company names you provide. It polls at your chosen interval for open invoices by status or ModifiedDate, respecting Dynamics GP's requirement to keep requests to 2-5 concurrent and avoid closed fiscal periods. For each approved invoice, ml-connector looks up or creates a Wise recipient using the vendor's bank details, requests a fresh Wise quote to lock the exchange rate at payment time (quotes expire, so a new one is generated for each batch), and posts the transfer. Wise OAuth tokens refresh automatically when they expire, and 429 rate limit responses trigger exponential backoff. Dynamics GP's Windows authentication and requirement for an active domain account is handled once at setup; Wise credentials are stored encrypted. Every payment carries a trace ID linking the Dynamics GP invoice number to the Wise transfer reference for audit and reconciliation.

A real-world example

A mid-sized manufacturing company runs Dynamics GP for accounting and has suppliers across Europe and Asia. Before the integration, the AP team approved invoices in GP, exported them manually, entered bank details and currency conversions in their banking portal, and then recorded the payment in GP after settlement. Exchange rates drifted between approval and execution, currency conversions had to be verified by hand, and reconciling invoices to payments took days. With Dynamics GP and Wise connected, each approved invoice in GP flows directly to Wise with the vendor's bank details already on file, the exchange rate is locked at the moment of payment, and the Wise transfer reference automatically records back into GP's payment history. Month-end reconciliation now matches invoices to settlements instantly.

What you can do

• •Poll Dynamics GP on a schedule you control for approved vendor invoices, handling Windows domain authentication and GP's on-premises SBA or SOAP endpoints.
• •Create or reuse Wise recipients for each vendor, storing bank account details encrypted and updating them when vendor records change in GP.
• •Execute a fresh Wise quote for each payment batch to lock the exchange rate at payment time, then post the transfer with automatic currency conversion.
• •Track every transfer from Dynamics GP through Wise execution and settlement, with a full audit trail and transfer reference recorded back in GP.
• •Handle Wise rate limits with backoff, token refresh, and recipient validation so international payments execute reliably without manual intervention.

Questions

How does ml-connector authenticate to Dynamics GP if it is on-premises and requires Windows domain credentials?

ml-connector uses your Windows domain account credentials (Kerberos or NTLM) to authenticate against your Dynamics GP SBA or SOAP endpoint. The account must be created in your Active Directory and mapped to a Dynamics GP user with appropriate GL and Payables permissions. ml-connector stores these credentials encrypted and presents them on every poll, ensuring it respects your GP user's role-based access controls.

Does ml-connector handle the 4-step transfer sequence that Wise requires?

Yes. ml-connector automates the full sequence: it retrieves or creates a Wise recipient for the vendor, requests a fresh quote to lock the exchange rate (quotes expire, so a new one is generated for each payment batch), creates the transfer order with the locked rate, and funds the payment. If a quote expires before funding or a rate limit is hit, ml-connector backs off and retries with a fresh quote.

What happens if a vendor's bank details in Dynamics GP change after a payment has been posted to Wise?

ml-connector compares vendor records from Dynamics GP on each poll against previously synced recipients. If the bank account or currency has changed, it marks the old recipient for review and creates a new one on the next payment run. This ensures future payments go to the correct account while maintaining an audit trail of the change and the invoices affected by the prior account.