/
/
Shrink the Stripe to Dynamics GP receivables reconciliation
For receivables teams who want every Stripe invoice found in Dynamics GP and the real exceptions surfaced by their AI assistant.
On this page
Connector
Connect Stripe, pick your AI tool and paste the prompt.
The problem
The invoices that matter are buried in rows that agree
Reconciling Stripe invoices with Dynamics GP means hunting each invoice by number, then PO number, then customer and amount when it was keyed differently. The ones that matter, paid in Stripe but open in GP, are buried among hundreds of rows that agree.
Without PopdockAI
- Search GP for each Stripe invoice number
- Try the PO number, then customer and amount
- Compare totals and balances row by row
- Lose the important ones among hundreds that agree
With PopdockAI
- Every finalized Stripe invoice is read for the range
- GP is searched by number, then PO, then customer, date and amount
- Fallback matches count only when unique, labelled probable
- Paid-but-open invoices are grouped, and nothing is changed
The prompt
Use this prompt
Copy it into any AI tool connected to PopdockAI. Swap the values in braces for your own.
**Objective:** Reconcile every Stripe invoice created from `{start-date}` to `{end-date}` against Dynamics GP receivables in company `{company}` (leave empty for the default company), and report each invoice as matched, mismatched, or missing from GP.
**Step 1: Read the Stripe invoices**
Call `stripe-get-invoice` with `created-date.from` = `{start-date}` and `created-date.to` = the day after `{end-date}` (Stripe date filters can leave out the end date itself). Drop any invoice created after `{end-date}` and any with status `draft` or `void`. Keep `number`, `customer-name`, `customer-email`, `total`, `amount-paid`, `amount-remaining`, `status`, `created-date` and `currency`.
**Step 2: Find each invoice in Dynamics GP**
For each Stripe invoice, call `dynamics-gp-get-rm-trx` with `document-number` = the Stripe `number` and `company` = `{company}`. If nothing comes back, try again with that number in the `customer-po-number` filter of `dynamics-gp-get-rm-sales-trx`, because some teams key Stripe numbers as the customer PO. If both return nothing, call `dynamics-gp-get-rm-trx` filtered by `customer-name.contains` (the Stripe `customer-name`), `document-date.from` and `document-date.to` set to the Stripe created date plus or minus 3 days, and `document-amount.min` / `document-amount.max` both equal to the Stripe `total`. Count that as a match only if exactly one record comes back, and flag it as a probable match.
**Step 3: Compare**
For each matched pair compare the Stripe `total` with GP `document-amount`, and the Stripe `amount-remaining` with GP `current-transaction-amount` (GP's outstanding balance).
**Step 4: Report**
A summary line first: invoices read, matched, probable matches, mismatched, missing from GP. Then one table per group with columns Stripe number, customer, Stripe total, GP document number, GP amount, Stripe remaining, GP remaining, and a Note saying what differs. List the invoices that are paid in Stripe but still open in GP, and the reverse, as their own group, because those are the ones someone has to act on.
**Rules & Guidelines:**
* `stripe-get-invoice` is on the stripe server. `dynamics-gp-get-rm-trx` and `dynamics-gp-get-rm-sales-trx` are on the dynamics-gp server.
* This prompt is read-only. Do not call `dynamics-gp-rm-trx-add`, `dynamics-gp-rm-trx-note` or any other dynamics-gp tool whose name does not start with dynamics-gp-get-.
* Match on the invoice number first. Fall back to customer, date and amount only when the number finds nothing, and never match two Stripe invoices to one GP document.
**Validation:**
* If Stripe returns no invoices in the range, say so and stop.
* If GP returns an error about the company, report it and stop rather than reading from a different company.
* If a Stripe amount is exactly 100 times the GP amount, report it as a units problem, not an amount difference.
* If the currencies differ, report the pair as a currency mismatch and do not compare amounts.Who it's for
One answer, three teams that use it
Accounts receivable
Apply payments GP is missing
Invoices paid in Stripe but open in GP get their own group, ready to apply.
Reconcile October's Stripe invoices with Dynamics GP receivables.
Controllers
Shrink the month-end reconciliation
Rows that agree drop away, leaving only the invoices someone needs to act on.
Which Stripe invoices from last month disagree with Dynamics GP?
Billing specialists
Catch keying errors
Amounts out by a factor of 100 and currency mismatches are flagged separately.
Find Stripe invoices this quarter where the GP amount looks keyed wrong.
How it works
What PopdockAI does when you ask
You give a date range, and your AI assistant matches Stripe invoices to Dynamics GP receivables. It only reads and calls out currency mismatches and amounts out by a factor of 100.
01
Ask
You give a date range.
02
Read
It reads every finalized Stripe invoice in the range.
03
Match
It looks in GP by invoice number, then PO number, then customer, date and amount.
04
Report
You get mismatches grouped, probable matches labelled and nothing changed.
What PopdockAI provides
The tools behind the answer
Ready made tools for Stripe and one secure connection to your AI tool. No code, no exports.
stripe-get-invoice
microsoft-dynamics-gp-get-rm-trx
microsoft-dynamics-gp-get-rm-sales-trx
This report is built from Get data tools only. PopdockAI applies the row, field and parameter rules your admin sets, and every query is written to the audit trail.
The outcome
A short list of invoices that need action
Related use cases
More ways to put this data to work
One prompt template with infinite possibilities.
Your AI assistant adapts its approach, tone, and capabilities to match each unique context while you maintain a single, manageable workflow.
Join forward-thinking companies that are transforming their operations with intelligent, secure AI automation.

.webp)
