How to Use the Koncile MCP for Ambient Accounts-Payable Automation (Accountants)

A firm doing accounts payable for 12 small-business clients ships maybe 800 invoices a month through some combination of QuickBooks, Bill.com, and a partner email inbox. Of those 800, somewhere north of 600 are completely routine — same vendor, same category, same approval pattern as last month. The bookkeeper still touches every one.

Koncile is one of the AP-extraction tools that the Accounting Today and CPA Trendlines 2026 outlooks point at as a category. The pitch isn't a new dashboard — it's a doc-to-GL pipeline with claimed >99% accuracy on structured invoices. The MCP version is what makes it agentic: the bookkeeper doesn't run Koncile; Koncile runs while the bookkeeper is doing the planning memo, surfacing only the invoices that need a decision.

💡 The stack. Koncile MCP extracts the data. The Accountant AI Cowork Vault is the agentic layer that codes it to your COA, drafts the approval message, and flags the boundary calls. Always-on practice-boundary + data-privacy guards. $19 one-time — both Claude and Microsoft 365 Copilot plugins included.

What the Koncile MCP actually does

Koncile's product is structured data extraction from financial documents — PDFs of invoices, bills, statements, receipts. The MCP wraps three core endpoints:

• extract — given a document URL (S3, Dropbox, Drive), returns the structured fields: vendor, vendor address, invoice number, line items with descriptions and amounts, totals, tax, due date, terms
• classify — given an extracted invoice, predicts the most likely expense category based on prior vendor history (per-firm, not cross-tenant)
• anomaly_flag — given an extracted invoice, flags items that look out of pattern: unusual amount, new vendor, duplicate invoice number, line item that doesn't match prior coding

Conspicuously absent: GL posting. Koncile returns data; your system posts. That's intentional — they're not trying to be QuickBooks.

Pre-flight

• Claude Cowork (desktop) or Claude Code
• A Koncile account with API access — their developer tier is free up to 100 docs/month, which is enough to pilot
• The Accountant AI Cowork Vault installed in your Cowork Project
• A folder Claude can read where invoices land — could be a watched email inbox, a Drive folder, or a Dropbox shared folder

Configure the MCP server

{
  "mcpServers": {
    "koncile": {
      "command": "npx",
      "args": ["-y", "@koncile/mcp-server"],
      "env": {
        "KONCILE_API_KEY": "your-api-key-here",
        "KONCILE_FIRM_ID": "your-firm-id"
      }
    }
  }
}

Restart Claude. The Koncile server should appear in your connectors list.

The ambient flow: invoice arrives, decision queued

Here's what the loop looks like in practice. The bookkeeper isn't watching this happen — it runs while they're doing actual practitioner work.

Trigger: invoice lands in the firm's inbox

A vendor emails an invoice to bills@firmname.com. The watched inbox forwards to a Drive folder Claude can read. The Cowork Project has a recurring task set to fire when the folder changes.

Step 1: Koncile extracts

Claude calls the Koncile MCP extract endpoint with the new PDF URL. Koncile returns the structured fields. Claude logs the extraction.

Step 2: Vault skill codes it

Claude calls the vault skill /ap-invoice-code:

/ap-invoice-code
Client: [Client]
Invoice data: [from Koncile extract]
Prior coding for this vendor: [the vault's memory of how this vendor was coded last 3 invoices]
Client COA: [loaded from setup wizard]

The vault matches the vendor + line item against the client's chart of accounts, returns a coded entry: "Office Supplies — Staples — $147.42." The skill is conservative: if the vendor is new (no prior coding to match), it returns the coded entry tagged [NEW VENDOR — confirm].

Step 3: Anomaly check

Claude calls the Koncile MCP anomaly_flag endpoint. If anything's weird (amount 3× prior monthly average, duplicate invoice number, vendor not seen before), the flag fires.

Step 4: Decision queued (not auto-posted)

The vault produces a single-line summary in the partner's queue:

✅ Staples — $147.42 — Office Supplies (matches prior coding for this vendor) ⚠️ NewCo Marketing — $4,200 — UNCATEGORIZED (new vendor; no prior coding)

The partner sees the queue when they open the project. Two-second triage on the ✅; thirty-second decision on the ⚠️. Total time spent: ~90 seconds for an invoice batch that would have been 30 minutes of manual review.

What this is NOT

It's not autoposting to QBO. The vault deliberately stops at the queue. The partner clicks through to QBO (or Sage Intacct, or NetSuite) to post — partly because some clients require human approval for AP, partly because the integration risk on auto-post outweighs the time savings.

It's not crossing the CPA boundary. The vault's practice-boundary-guard fires if a draft drifts into tax-advice or audit-defense territory. AP coding is bookkeeping; the boundary holds.

It's not a substitute for vendor verification. New vendors should still get a 60-second sniff test before payment. The vault includes a /new-vendor-verification skill that builds an EIN/W-9/state-registration check; Koncile doesn't do that part.

Chain it with the month-end close

Once the AP queue is processed for the month, the same Koncile-extracted data feeds month-end:

/month-end-variance-commentary
Client: [Client]
Period: April 2026
Categorized AP: [from this month's Koncile + vault queue]
Prior month: [from last month's coded entries]
Anomalies flagged this month: [from anomaly_flag fires]

Out comes a variance-commentary draft. The partner reviews, edits, sends to the client.

Common failure modes

• Koncile misreads a line item. Happens on handwritten receipts and on multi-line POs with split categories. The vault skill returns flagged items as [verify]; don't post them without eyeballing.
• New-vendor floodgate. If you onboard a client mid-year, every vendor is "new" for the first month. The anomaly flag will fire on each. Suppress the alert for net-new-client onboardings; re-enable after a 30-day baseline.
• Charity / pro-bono coding ambiguity. Vendor invoices for charitable contributions are routinely miscategorized. The vault's /pro-bono-coding-rules skill handles the firm's standing rule; if you don't have one, write it before the first run.

When you'd skip this stack

• Sub-50-invoices/month firms. Manual is faster than the setup time. Revisit when you cross 100/month.
• Heavily intercompany clients. Koncile is excellent at vendor invoices; intercompany journal entries and equity transactions need a different tool. The vault has /intercompany-allocation for those.
• No client-side discipline on document arrival. If clients dump 80 receipts into a Google Drive folder named "stuff" the night before tax filing, no MCP will save you. Fix the intake process first.

Sources

• Koncile: Developer API documentation (vendor primary)
• Anthropic: Model Context Protocol (MCP) introduction
• Accounting Today: A big year for AI in accounting (2026 outlook)
• AICPA: Statements on Standards for Tax Services