aistack
Book consultation →
← All articles
Finance · CRM

CRM reports for the finance team: how much money is coming before the invoice exists

Sales sees open deals in the CRM, finance only sees invoices once they are issued. When Claude reads both with one person's permissions, the revenue estimate for the next few months stops being a guess.

October 2026·7 min read·Milan Janoštík·
ClaudeMCPFinance
Infographic: a funnel of sales opportunities on the left passes through a blue bridge with Claude and a lock, and becomes a bar chart of expected monthly income on the right.

Looking for CRM reports for your finance team? Usually the need is not another Excel export. Finance wants to see what sales is negotiating before it turns into an invoice. In most companies there is a gap between the CRM and the accounting system, and the revenue estimate for the next three months falls right into it.

The work nobody wants

End of the month. The finance lead needs a cash flow estimate, so she emails sales. A salesperson exports opportunities from the CRM into a spreadsheet. The columns are named differently from last time, and half the deals have sat in “proposal sent” for six months. Finance then matches CRM companies to customers in accounting by hand, crosses out dead deals and recalculates the probabilities.

The result is a spreadsheet nobody fully trusts. Sales feels finance is lowballing their numbers. Finance feels sales is padding them. By the time it gets sorted out, the data is a week old and the whole round starts again.

“Could you send that export one more time, but with the signing date this time?”

— Quarterly planning, abridged

What connected actually means

Claude gets access to both sides: sales opportunities in the CRM, and issued and paid invoices in accounting. Not through a copy of the data, and not through a shared admin account. Through small MCP servers, one for the CRM and one for accounting. Think of MCP as a standard connector: an agreement on how AI asks a system a question and what it is allowed to get back.

Every request carries the identity of the person asking. The finance lead sees the whole pipeline, because she already sees it in the CRM today. The head of one sales team sees only that team. Claude reads the data at the moment of the question, keeps it in no database of its own, and builds the answer from the current state.

The bridge rule
Claude never sees more than the person asking
Permissions are not set up again for AI. They are inherited from the CRM and the accounting system, exactly as the company has them today. If a salesperson has no access to invoices in Pohoda, they will not get them through Claude either.
CRM opportunities cross a bridge carrying your identity and arrive as an income estimate by month

Concretely: Raynet and Pohoda

A typical Czech company: sales works in a CRM such as Raynet or Pipedrive, accounting works in Pohoda. Both systems stay. Nothing is migrated and nobody learns a new tool. A bridge is added. For a company with twenty salespeople and a few hundred open opportunities, setup is typically a matter of days, not months (an illustrative estimate).

  • matches a CRM company to a customer in Pohoda by IČO, the Czech company ID, rather than by a name spelled differently in each system
  • reads the stage, amount and expected close date of every open opportunity
  • compares them with history: how long each customer usually takes from signature to invoice, and from invoice to payment
  • flags deals that have not moved in a long time and never counts them silently
  • builds a monthly view in three layers: certain (invoiced), probable (signed), possible (in negotiation)

To illustrate: a manufacturing firm in Brno, eight salespeople, one finance lead. On Monday morning she asks Claude: “How much money will likely come in during July and August, and which three deals move that number the most?” The answer links to specific opportunities in the CRM and invoices in Pohoda, so she can open any figure and check it.

What an AI report from your CRM will not do, and why that is good

Claude does not decide whether a deal will close. It does not know that the customer's director left last week, or that a salesperson promised a discount on the phone. The estimate is only as good as the data in the CRM. If salespeople do not update their stages, Claude can show that clearly, but it cannot fix the habit for them.

It posts nothing to accounting, issues no invoices and changes no probabilities in the CRM. It reads, calculates and explains. Decisions about budget, credit lines or who to call about a late payment stay with a person. That is exactly why it can be trusted: every number has a trail back to its source, and nothing in your systems changes without people knowing.

3–5 h
less manual export matching each month
1 day
instead of a week for the estimate to reach management
0
new copies of data outside your infrastructure

What it would take

It starts with a short conversation: which CRM you use, which accounting system, and who should have access to what. Then we build two small MCP servers and deploy them on your own cloud, with your sign-in and a single audit trail showing who asked what. Once finance has a report it likes, we save it to the skills library, so next month anyone with the right permissions can run it. No year-long project, no new data platform.

A question from finance→Identity and permissions→MCP: CRM and Pohoda→Claude joins the data→Estimate by month

What's left

The model is not what companies are missing. Claude can calculate a weighted pipeline and explain why the estimate moved since last month. What it lacks is access to the data you already have, at the right scope. That gap is what we close.

Write to us. A short call is enough to find out whether your CRM and accounting can be connected, and how much work it would take off your finance team.