/
/
Post Stripe invoices to Dynamics GP without duplicates
For receivables teams who want finalized Stripe invoices added to a Dynamics GP batch by asking their AI assistant, with no invoice keyed twice.
On this page
Connector
Connect Stripe, pick your AI tool and paste the prompt.
The problem
Keying Stripe invoices into GP twice or to the wrong customer
Getting Stripe invoices into Dynamics GP receivables means exporting from Stripe, checking each number against GP and finding the right GP customer. Pick the wrong customer or miss one already keyed and the receivables ledger is wrong until someone spots it.
Without PopdockAI
- Export finalized invoices from Stripe
- Check each number against GP
- Find the right GP customer for each
- Key them into a batch by hand
With PopdockAI
- Invoices whose number GP already holds are skipped
- Each is matched to one clear GP customer by name and email
- Unclear matches, other currencies and long numbers are held back
- You approve the table, and each invoice is added to the batch once
The prompt
Use this prompt
Copy it into any AI tool connected to PopdockAI. Swap the values in braces for your own.
**Objective:** Find the finalized Stripe invoices created from `{start-date}` to `{end-date}` that have no receivables document in Dynamics GP, and add the ones the user confirms to GP batch `{batch-number}` in company `{company}` (empty means the default company).
**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}`. Keep invoices with status `open`, `paid` or `uncollectible`, and drop any created after `{end-date}`.
**Step 2: Skip the ones GP already has**
For each invoice, call `dynamics-gp-get-rm-trx` with `document-number` = the Stripe `number`. If a record comes back, skip the invoice.
**Step 3: Map the customer**
For each remaining invoice, call `dynamics-gp-get-rm-customer` with `customer-name.contains` = the Stripe `customer-name`, and accept the GP customer whose `main-email-address` equals the Stripe `customer-email`, ignoring case. If none matches, or more than one does, mark the invoice as unmapped. Do not post it.
**Step 4: Propose and confirm**
Show a table: Stripe number, created date, due date, customer, GP customer ID, total, status. Show the unmapped invoices separately and suggest `backfill-stripe-customers`. Then stop and wait. Post nothing until the user confirms, and post only the rows they confirm.
**Step 5: Post**
For each confirmed invoice, call `dynamics-gp-rm-trx-add` once with `document-type` = the code the tool lists for an invoice, `document-number` = the Stripe `number`, `customer-id` = the GP customer ID, `document-date` = the Stripe created date, `due-date` = the Stripe due date, `document-amount` and `sales-amount` = the Stripe `total`, `batch-number` = `{batch-number}`, `description` = "Stripe " followed by the Stripe number, `create-distributions` = 1 and `company` = `{company}`. Stripe totals include tax, so do not also set `tax-amount`.
**Step 6: Report**
A table of what was posted, what failed (with the error) and what was skipped, and a closing line saying the batch still has to be posted in Dynamics GP.
**Rules & Guidelines:**
* `stripe-get-invoice` is on the stripe server. The dynamics-gp tools are on the dynamics-gp server.
* The only write tool this prompt may call is `dynamics-gp-rm-trx-add`, once per confirmed invoice. Do not call `dynamics-gp-rm-sales-trx-add`, `dynamics-gp-rm-customer-add`, `dynamics-gp-gl-bank-deposit-add` or any other dynamics-gp write tool. The stripe server has no write tools.
* Payments are not posted here. A paid Stripe invoice goes in as an invoice only.
**Validation:**
* If every Stripe invoice is already in GP, say so and stop.
* If a Stripe number is longer than 21 characters, GP cannot hold it. Report it and do not post it.
* If a post fails, report the error, do not retry it, and continue with the next invoice.
* If the invoice currency is not the GP company's functional currency, do not post it. Report it instead.Who it's for
One answer, three teams that use it
Accounts receivable
Load Stripe invoices without rekeying
Invoices go into your batch ready to post, with duplicates already removed.
Post finalized Stripe invoices from October to Dynamics GP batch STRIPE1031.
Controllers
Keep the receivables ledger right
Invoices without a single clear customer are held back rather than guessed.
Which Stripe invoices from last week could not be matched to a GP customer?
Billing specialists
See what will be posted first
A table of every invoice lets you check before anything enters GP.
Show me the Stripe invoices from 1 to 15 November that would go into GP batch STRIPEMID.
How it works
What PopdockAI does when you ask
You give a date range and a batch, and your AI assistant prepares Stripe invoices for Dynamics GP. Nothing is written until you confirm, and posting the batch stays with you.
01
Ask
You give a date range and a GP batch.
02
Check
It skips Stripe invoices whose number Dynamics GP already holds.
03
Match
It finds one clear GP customer by name and email, holding back the rest.
04
Confirm
You approve the table, then each invoice is added to the batch once.
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-customer
microsoft-dynamics-gp-rm-trx-add
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
Stripe billing in GP, with no duplicates
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)
