Let an AI assistant do the books, with a person still approving every action.

Copperline's customers ask Claude or ChatGPT to pay bills, categorize spend, chase invoices and post journal entries. The assistant reads their ledger through the Apideck MCP server and queues each change. Nothing writes until someone approves it in Copperline.

AI assistant · Copperline

What should we get done?

This assistant is connected to Copperline. It can read the books and queue work, but nothing writes until someone approves it in Copperline.

Any MCP client works the same way: Claude, ChatGPT, Cursor or your own agent. The tables are MCP Apps the server returns with its results.

Copperline · Tidewater Studio

Approvals

Nothing waiting

Ask the assistant for something. Whatever it wants to change lands here first.

AI assistant access

Connected

Set in Copperline. The assistant can read everything and queue only what's ticked.

Read accounts, bills, expenses and invoicesQueue: pay billsQueue: categorize transactionsQueue: send invoice remindersQueue: post journal entries

Approval rules

Auto-approve categorizations at ≥ 90% confidenceAuto-approve payments under $500Four-eyes approval on payments ≥ $2,000

The policy the team already follows, applied to the assistant. Flagged items never auto-approve; everything else waits for a tap.

How it fits together

AI assistant

Claude, ChatGPT, any MCP client. Reads and asks.

Copperline

Permissions, approval rules and the queue. Holds every write.

Apideck

MCP server and unified Accounting API. One integration.

The customer's ledger

QuickBooks, QuickBooks Desktop, Sage Business Cloud Accounting, Sage Intacct and 38 more

Reads pass straight through. A write the assistant asks for is held by Copperline, not run, and goes to the ledger only once a person, or a rule they set, approves it. The guardrail lives in the server the assistant calls, not in its prompt, so the assistant can't be talked past it.