Microsoft Dynamics GP and PayPal integration

What moves between them

PayPal order capture and refund events flow into Microsoft Dynamics GP as receivables transactions. When a capture webhook fires, ml-connector reads the order details and creates a customer receivable in GP with the payment amount, customer reference, and posting date. Refund events create offsetting credit memos. Customer records are synchronized from PayPal into GP so that new PayPal customers are available for selection when entering receivables. Receivables in GP are read-only from PayPal's perspective; ml-connector never writes back to PayPal.

How ml-connector handles it

ml-connector stores both credential sets encrypted: the Windows domain account credentials are used to authenticate against the Microsoft Dynamics GP SBA endpoint, while the PayPal Client ID and Secret are exchanged for an OAuth 2.0 bearer token cached for reuse. PayPal webhooks arrive over HTTPS and are verified using RSA-SHA256 signature validation before processing. Each webhook payload is mapped to a GL Journal Entry template or customer receivable template in GP, then posted to the appropriate fiscal period. Because Microsoft Dynamics GP requires posted transactions to be immutable, ml-connector validates that the fiscal period is open before attempting to create a receivable; if the period is closed it queues the transaction for later processing. Every record includes the original PayPal order ID so reversals and corrections can be traced back to the source payment. On failure, ml-connector retries with exponential backoff and surfaces the error in the audit log.

A real-world example

A mid-market e-commerce company operates Microsoft Dynamics GP for accounting and uses PayPal for direct customer payments on their web storefront. The finance team previously exported PayPal transaction reports daily and manually entered each order as a customer receivable in GP, then reconciled the two systems at month end. With Microsoft Dynamics GP and PayPal connected, each PayPal capture automatically creates a receivable in GP on the same day it settles. The finance team runs month-end close knowing that receivables are complete and PayPal revenue is already recorded in the GL, eliminating the daily manual entry step and reducing reconciliation time from several days to minutes.

What you can do

• •Sync PayPal order captures into Microsoft Dynamics GP as customer receivables with the payment amount and original order reference.
• •Map PayPal customers to existing Dynamics GP customer records and create new customers as needed.
• •Post customer receivables to the correct fiscal period in Microsoft Dynamics GP with automatic validation and queuing for closed periods.
• •Verify PayPal webhook signatures using RSA-SHA256 and bridge Windows domain authentication to PayPal OAuth 2.0.
• •Maintain a complete audit trail of every payment, with full error replay and retry on network failures.

Questions

Which direction does data flow between PayPal and Microsoft Dynamics GP?

PayPal orders and captures flow into Microsoft Dynamics GP as customer receivables. PayPal refunds create offsetting credit memos in GP. Customer records are synced from PayPal into GP so new customers are available for selection. Microsoft Dynamics GP receivables are read-only from PayPal's perspective, so ml-connector does not write financial transactions back to PayPal.

How does ml-connector handle the Windows domain authentication that Microsoft Dynamics GP requires?

ml-connector stores encrypted Windows domain account credentials and uses them to authenticate against the Microsoft Dynamics GP SBA endpoint on every request. The account must be created by the customer's IT team as an Active Directory user with appropriate GP security roles. This isolates the domain credentials from PayPal and keeps each system's authentication independent.

What happens if a receivable is created for a fiscal period that is already closed in Microsoft Dynamics GP?

Microsoft Dynamics GP only allows new transactions to be posted to open fiscal periods. ml-connector validates that the period is open before creating a receivable; if the period is closed it queues the transaction in the audit log for manual processing by the finance team, who can then reopen the period or correct the posting date as policy requires.