Action Packs: Connect AI to Your ERP, Banks and AS400
Ready-made Actions that let Claude, ChatGPT and Copilot work in NetSuite, Business Central, Acumatica, AS400, your banks and Stripe, with approvals built in.
Every finance team has a list of systems it still works around by hand.
The bank portal that hands over yesterday's transactions only if someone logs in and clicks download. The ERP that needs a consultant, a custom role and a token before anything can touch it. The green-screen system where orders get re-keyed into the new ERP line by line.
These systems run the business. They're also the hardest to reach, so the work around them lands on a lean team with a lot of tabs open.
A few weeks ago, we launched Actions, so the AI your team already uses can do real work in those systems, with a person approving anything that changes the books. Today we're launching Action Packs: ready-made Actions for the systems finance runs on, and a format your coding agent can use to build a Pack for any system that doesn't have one yet. The first Packs cover NetSuite, Microsoft Dynamics 365 Business Central, Acumatica, AS400, J.P. Morgan, Wells Fargo and Stripe, and work with Claude, ChatGPT and Microsoft Copilot.
A Monday morning in accounts payable
Ava runs accounts payable at Harbor, the demo company from our Actions launch. Harbor runs on Microsoft Dynamics 365 Business Central, still runs its warehouse on an AS400, gets paid through Stripe and banks across several accounts.
At 8:05, she asks Claude three things:
- "What's our cash position across every bank account this morning?"
- "Match Friday's Stripe payouts to the deposits and show me what doesn't tie."
- "Draft the accrual for last week's warehouse receipts that haven't been invoiced in Dynamics yet. Send it to Connie before it posts."
Here's what comes back:
- Her cash position in one table, pulled from every bank, with no portal logins.
- The payouts that tie are matched. The ones that don't are listed with the backup attached.
- The accrual is drafted and on hold until Connie, the controller, approves it.
Those three requests draw on four Packs: Banks, Stripe, AS400 and Dynamics. Ava gets her answers in one conversation, with no exports, no re-keying, and nothing changing the books until Connie approves it.
What is an Action Pack?
An Action is a typed function, something like netsuite.create_journal_entry, that does one thing in one system. A month-end close is dozens of those things. That's where Action Packs come in.
An Action Pack is a ready-made set of Actions for one system: the ones your team will use in the first week, plus the connection they run on.
Authentication happens through CoPlane. Sign in to the system from the CoPlane app. CoPlane holds the credentials. IT approves the Connection once, and the people, workflows and assistants using it never see the keys.
The Actions your team needs first. Each Pack covers the work your team does most in that system, sorted by effect:
- Read: balances, transactions, open items.
- Write: entries, invoices and vouchers, drafted and staged for review.
- Post: only after the right person approves.
The controls you already have. Every Action in a Pack runs through the same executor and the same policy file as the Actions you write yourself. Same permission check, review before anything posts, and a record of every call, including the refused ones.
Action Packs available today
These Packs are already running in production with customers, across ERP, legacy systems, banking and payments. They cover the systems finance teams depend on every day and have the hardest time connecting.
| Action Pack | Category | Once connected, your team can |
|---|---|---|
| AS400 (IBM i) | ERP (legacy) | Pull orders, invoices and payables off green-screen systems and stage them in your ERP, without re-keying |
| NetSuite | ERP | Pull GL detail and saved searches, draft journal entries and invoices, post them once approved |
| Acumatica | ERP | Look up accounts and balances, draft journal entries, post or hold them for release |
| Microsoft Dynamics 365 Business Central | ERP | Pull open AP and GL activity, stage entries and vouchers, post them at period end |
| J.P. Morgan | Banking | Pull daily transactions and balances across every account, without logging in to a portal |
| Wells Fargo | Banking | Pull daily transactions and balances across every account, without logging in to a portal |
| Stripe | Payments | Pull payouts, fees and disputes, and line them up against what landed in the bank |
Don't see your system? Build the Pack
Every Pack in the table above started the same way: point a coding agent at the system's API docs and CoPlane's docs, and it writes most of the Pack, including the connection, the Actions sorted by read, write and post, and the policy that governs them. Your team reviews the code and deploys. In-house systems work the same way.
Packs you build run through the same executor, policy file and approval flow as the ones we ship, so there's no second-class tier.
Combine Packs for work that spans systems
A Pack works the same way wherever it's used: in Copilot, ChatGPT or Claude, in a workflow, or by an agent that runs overnight. That makes it easy to combine Packs for work that crosses systems, which accounts for most of what finance does every week.
| Workflow | Packs | What changes |
|---|---|---|
| Cash reconciliation | Banks, Stripe, any ERP | Bank activity and Stripe payouts are pulled daily and matched to the ledger. A deposit that hit the bank but never posted shows up the next morning rather than at month-end. |
| Intercompany reconciliation | NetSuite and Acumatica, or any two ERPs | Both entities' balances and entries are pulled side by side, so an invoice one booked in September and the other in October gets caught before cutoff instead of in an email chain. |
| Legacy to modern ERP | AS400, any ERP | Orders, receipts and invoices move from the AS400 to the new ERP every day, so nobody re-types them while both systems run side by side during a migration. |
| Period-end accruals | Dynamics, NetSuite or Acumatica | Goods received but not yet invoiced are pulled at cutoff. The accrual entry is drafted for review, but doesn't get posted until the controller approves. |
What your IT team gets
Each system gets one Connection, and IT approves it once. Every use case after that reuses the same reviewed Actions under the same policy, so you aren't issuing a new service account for each bot.
Packs are code you can manage. Each Pack lives in your repository like any Action you wrote, so you can read every function, extend it, and choose where each Action appears: in an assistant, in a workflow, or nowhere at all. For more on how the controls work, read how CoPlane's hybrid architecture eliminates vendor risk.
Start with one Pack
Pick the system your team copies data out of most, connect it, and see what your copilot does once it can reach it. Get started
Next up is Processes, for the work you want done the same way every time, built from the Actions in your Packs.
Frequently asked questions
Which AI assistants work with Action Packs?
Claude, ChatGPT for Work, Microsoft Copilot and Copilot Studio agents can all call the same Actions over the Model Context Protocol (MCP), under the same policy. Workflows and overnight agents use them too.
Can an AI assistant post entries to our ERP on its own?
No. Actions are sorted into read, write and post. Assistants can read data and draft entries, but posting waits for the person your policy names, such as the controller.
Who holds the credentials for our ERP and bank accounts?
CoPlane does. You sign in to each system once from the CoPlane app, IT approves the Connection, and the people, workflows and assistants using it never see the keys.
What if our system doesn't have a Pack yet?
Point a coding agent at the system's API docs and CoPlane's docs. It writes most of the Pack, and your team reviews and deploys it like any other code. In-house systems work the same way.
Be the first to see Processes
Get product launches and CoPlane's perspectives on AI in finance operations in your inbox.
By submitting, you agree to our privacy policy.
Written by Chris Sperandio
All perspectives
