/
/
Get every active GP vendor into Intacct, once
For payables teams after a Sage Intacct cutover who want missing Dynamics GP vendors created there, by asking their AI assistant.
On this page
Connector
Connect Microsoft Dynamics GP, pick your AI tool and paste the prompt.
The problem
Missing vendors block bills after cutover
After a Dynamics GP to Sage Intacct cutover, vendors that did not migrate block bill entry and payments. Adding them by hand risks a second record for a vendor that came across under a new ID, and payment terms Intacct rejects.
Without PopdockAI
- Compare vendor lists from GP and Intacct
- Search Intacct by name for vendors under a new ID
- Work out which payment terms Intacct will accept
- Re-enter addresses and holds by hand
With PopdockAI
- Each active GP vendor is checked in Intacct by ID, then by name
- Possible migrations under another ID are never created
- Payment terms are proposed once you confirm the mapping
- GP holds are kept, addresses listed, and each vendor is read back
The prompt
Use this prompt
Copy it into any AI tool connected to PopdockAI. Swap the values in braces for your own.
**Objective:** Create in Intacct the active GP vendors that are missing there, optionally only GP vendor class `{vendor-class}`, after the user confirms the list.
**Step 1: GP vendors**
Call `dynamics-gp-get-pm-vendor` (`vendor-class-id` = `{vendor-class}` when given). Keep active vendors only (`vendor-status`, using the codes the tool lists) and note which are on `hold`.
**Step 2: Check Intacct**
For each GP vendor call `intacct-get-vendor` with `vendor-id`. If there is no match, call it again with `vendor-name`. A name match under a different id means "possibly migrated under a new id": list it and never create it.
**Step 3: Propose**
For each missing vendor propose:
* `vendor-id`: the GP `vendor-id`.
* `name` and `print-as`: the GP `vendor-name`.
* `email`: `primary-email-address`; `phone`: `phone-number-1`.
* `payment-term`: only if the user confirms the Intacct term name that matches GP `payment-terms-id` (Intacct rejects unknown terms). Ask once for the mapping of the GP term ids you found.
* `status`: active.
The create tool takes no address. List each vendor's GP `address-1`, `city`, `state` and `zip-code` in the proposal as "not carried, enter separately".
Show the proposal and ask the user to confirm, edit or drop rows.
**Step 4: Create**
Only after confirmation, call `intacct-create-vendor` once per confirmed vendor. For a created vendor that is on hold in GP, call `intacct-update-vendor` with `on-hold` = true, once. Stop on the first failure, report it, and ask whether to continue.
**Step 5: Confirm**
Re-read each created vendor with `intacct-get-vendor` and report: created, placed on hold, failed (with the error), skipped, and possible duplicates from Step 2.
**Rules & Guidelines:**
* Tools prefixed dynamics-gp- are on the dynamics-gp MCP server. Tools prefixed intacct- are on the intacct MCP server. Both servers must be connected; if a tool from either is missing, say which server is not connected and stop.
* Pass `{gp-company}` as `company` on every dynamics-gp- call and `{intacct-company}` as `company` on every intacct- call. Leave either empty to use that server's default company, and name the companies you used in the report.
* Set `max-records` high (5000) on every list read. If a read returns exactly that many rows, say the result may be truncated and narrow the filter (per account, per vendor, per customer or per item) instead of reporting totals from it.
* The only writes allowed are `intacct-create-vendor` per confirmed vendor and `intacct-update-vendor` to set a hold. Never write to GP: do NOT call `dynamics-gp-pm-vendor-add` or `dynamics-gp-pm-vendor-update`.
* Propose at most 25 vendors per confirmation; offer the next batch.
**Validation:**
* If every active GP vendor is already in Intacct, say so and stop.
* Never create a vendor whose name already exists in Intacct.Who it's for
One answer, three teams that use it
Accounts payable
Enter bills for every vendor
Vendors that did not come across are created, so bills stop failing on a missing vendor.
Which Dynamics GP vendors are missing from Sage Intacct? I need to enter bills for them.
Migration leads
Finish the vendor migration safely
Vendors that may have migrated under a new ID are listed for review, so no supplier ends up with two records.
Find GP vendors in class FREIGHT that did not come across to Intacct and create them after I review.
Treasury teams
Keep held vendors on hold
Vendors on hold in GP stay on hold in Intacct, so payments do not go out to suppliers you had stopped.
Migrate missing Dynamics GP vendors to Intacct and make sure any on hold stay on hold.
How it works
What PopdockAI does when you ask
You optionally pick a vendor class, and your AI assistant finds Dynamics GP vendors missing from Sage Intacct. Only the vendors you confirm are created, up to 25 at a time.
01
Ask
You optionally pick a Dynamics GP vendor class.
02
Check
It looks up each active vendor in Sage Intacct by ID, then by name.
03
Confirm
You review the proposed details and payment term mapping, up to 25 at a time.
04
Create
It creates them, keeps GP holds, and reads each one back.
What PopdockAI provides
The tools behind the answer
Ready made tools for Microsoft Dynamics GP and one secure connection to your AI tool. No code, no exports.
microsoft-dynamics-gp-get-pm-vendor
sage-intacct-get-vendor
sage-intacct-create-vendor
sage-intacct-update-vendor
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
Every active vendor in Intacct, once
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)
