Claude Connector Coming soon

Billyou in Claude.
Conversational.

Connect Billyou to Claude once, then ask about invoices, clients, and SPV status in plain language. The assistant sees your data, scoped to one organization, and only on request.

AI assistant, on accounting terms

Claude sees your data on terms an accountant would accept. Per-org isolation, no writes at launch, full log of every action.

1
org per connector
strict isolation
Read
only at launch
no writes, no deletes
90
days audit log
auto-deleted after
OAuth
2.0 with PKCE
via Kinde

How it works

Four steps. Set it up once, ask every day.

01

Add Billyou in Claude

Add Billyou as a connector inside Claude (claude.ai, Claude Desktop, or Claude API). One click. No plugin to install.

02

Authorize one organization

Sign in with your Billyou account. The connector binds to the organization you pick, via OAuth 2.0 with PKCE. No back-channel, no global access.

03

Ask in plain language

Ask Claude for unpaid invoices, last month's revenue, or the SPV status of a specific invoice. The answer uses real data from your account.

04

Verify at the source

Claude returns data straight from your account. For any accounting, tax, or audit decision, open Billyou and check at the source. The assistant doesn't replace the accountant.

What you can ask

Concrete questions, real answers from your Billyou account.

Question

How much do my clients owe me this week?

How Claude answers

Claude calls the unpaid-invoices tool, aggregates the total, and returns the sum with a per-client breakdown.

Question

Which January invoice was rejected by ANAF?

How Claude answers

Claude searches January invoices with non-confirmed SPV status and shows the ANAF error code and description.

Question

Send me the expense breakdown by category for April.

How Claude answers

Claude calls the expense report tool for April and formats the response as a table directly in the conversation.

Question

Who are my clients with the most unpaid invoices?

How Claude answers

Claude groups invoices by client, sorts by outstanding count, and returns the top five.

mcp-tool-call.json
// The call Claude makes when you ask
// "How much do my clients owe me this week?"
{
  "tool": "list_unpaid_invoices",
  "params": {
    "organizationId": "org_billyou_demo",
    "dateFrom": "2026-04-27",
    "dateTo": "2026-05-04"
  },
  "auth": "oauth2_pkce",
  "trace": "trc_a2f81…"
}

How it's built

Model Context Protocol (MCP)

The connector uses the open MCP standard to expose specific tools (list invoices, find client, e-invoice status). Claude only calls the tools it needs to answer your prompt.

Single-org scope

The OAuth grant binds to one Billyou organization at the moment of authorization. To use data from a second company, you connect a second time with that company's credentials.

Anthropic's policies apply

How data is handled after it reaches Claude, including whether it's used for training and how long it's retained, depends on your Anthropic plan (Free, Pro, Team, Enterprise, API) and your account settings. On business plans, Anthropic publicly states that customer data is not used for training by default. Check Anthropic's official privacy policy for the exact terms.

Audit log per action

Every call is logged with the tool name, parsed parameters (with secrets redacted), duration, and outcome. Last 50 actions visible in Settings, MCP Activity.

Ready to connect Billyou to Claude?

Account in 30 seconds. Connection in 30 more. No credit card required.

Try free

Questions about the Claude connector

Only what's needed to answer your specific prompt, scoped to the organization you authorized. Asking about invoices returns invoice fields. Expenses don't come along unless you ask. The connector exposes specific tools, not a full database mirror.
It depends on your Anthropic plan and your Claude account settings. On Team, Enterprise, and Claude API, Anthropic states that customer data is not used for training by default. On consumer plans (Free, Pro), there are settings you can review in your account. The official policy is Anthropic's. Billyou only sends data to Claude when you prompt for it and does not control what Anthropic does with the data once it leaves our server.
Yes, but each connection binds Claude to a single organization. To use a second company, add the connector a second time and authorize with that company's credentials. Cross-organization access is impossible by construction.
Not at launch. The connector is read-only. It can search, list, and summarize, but cannot issue, edit, or send invoices. Write capabilities will be opt-in per organization, behind a paid-tier flag, with explicit confirmation required for destructive operations.
Two options. In Claude, remove the Billyou connector from your assistant settings; the OAuth refresh token is invalidated immediately. In Billyou (Settings, Active Sessions, MCP), revoke the session at the source. After revocation, Claude must be re-authorized to make any further calls.
Billyou is built together with AxACont, an accounting firm with over 25 years of experience in Romanian accounting. The product and connector are built by developers; what data is sensible to expose to AI assistants and under what conditions is validated by accountants who file with ANAF every day. More at axacont.ro.

Your data, in Claude.
With the lines an accountant would draw.

Read-only at launch. Full audit log. Strict single-org isolation.