What you can do with the AI connector

No need to memorize anything: ask in your own words and in your own language. The assistant translates your question into the queries it needs. If you haven't connected it yet, start with Connect your assistant.

A good first step, especially if you have access to more than one account (group, subsidiaries, or a client portfolio if you're an accounting firm):

"What B2Brouter accounts do I have?"

The assistant lists the accounts where your user is a member, with name and tax IDs. From there, you can refer to them naturally ("the Client SA account").

Who it's useful for

If you handle invoicing, to unblock rejected invoices and figure out how to invoice a new customer.
If you're an advisor or accounting firm, to review the tax status of your clients' accounts and translate the authorities' rejections.
If you're a developer, so your coding agent can diagnose your test invoices without leaving the editor.
If you're a manager or finance lead, to get business figures from chat, without entering the web app.

Everything this page describes is available to every profile, within the permissions each user already has.

1. Search and list invoices

This is the starting point for most queries: which invoices meet a condition.

"What invoices do I have with errors?" "What invoices have been rejected this week?" "List my overdue invoices, from largest to smallest" "Find invoice FC-2026/0089 and tell me what status it's in"

The assistant lists the invoices that match, by status (with error, rejected, unpaid...), by number or series, by period, and from the list you can request the detail of any of them.

2. Inspect and validate an invoice

From the summary to the full detail:

"Show me invoice 2026/0142"

The assistant returns the full content: parties, lines, amounts, taxes, payment terms. And the key question when something fails:

"Why did 2026/0142 fail?" "Will this invoice pass validation before I send it?"

The assistant gets the exact validation errors and explains them: what each error means, which field it affects and what needs to change. You make the correction in the web app (the connector doesn't touch anything) and then you can verify again: "is it fine now?".

The invoice body is returned in the exact format of the REST API response, and validation is the same battery as the validation endpoint: XSD + Schematron + model rules. This means your coding agent can cross-reference the error directly with the JSON your integrator sends and propose the fix to your payload. The recommended workflow for integrations: (1) consult the developer guides on this portal ("how do I create an invoice via API and send it over Peppol?", "how does the sandbox work?"); (2) create test invoices via API (the connector doesn't create anything); (3) diagnose via the connector without leaving the editor ("which invoices from the test batch have ended up in error?", "invoice 123 doesn't validate, what do I need to change in my JSON?"); (4) for format mapping, use the JSON→Facturae, FatturaPA, UBL BIS3, CII and KSeF FA-3 mapping guides.

3. Track tax reports

If your country has electronic invoice declaration or registration (Verifactu, SII or TicketBAI in Spain, DGFiP in France, KSeF in Poland, ZATCA in Saudi Arabia, MyInvois in Malaysia...), each invoice generates a tax report with its own lifecycle before the authority. The connector tracks it:

"What tax reports do I have in error or rejected?" "What did the tax authority reject on the Client SA account this week?" "Was the report for invoice FC-0089 registered correctly?"

And for every rejection, the full diagnosis:

"Give me the detail of the first one" → status, amounts and the authority's literal rejection message. "What does this error mean and how do I fix it?" → the assistant interprets the code and, if it can read web pages, cross-references it with B2Brouter's guide for each authority to tell you the affected field and the fix.

It works for any of the supported authorities, and you can ask about codes on their own: "what does this Verifactu error 1210 mean?", "what does this KSeF rejection code mean?".

4. Business figures

These are the same figures as the B2Brouter dashboard; there aren't two truths:

"How have we done this quarter?" → revenue, expenses and net result for the period. "What do we have pending to collect? How much is overdue?" → amounts pending collection and payment, split between on time and overdue, with invoice count and amount. "Who are our top customers this year? And suppliers?" → ranking by invoiced volume. "How has cash flow evolved month by month?" → revenue, expenses, difference and cumulative by month.

And free-form composition:

"Put together a summary for the meeting with the bank: yearly billing, monthly evolution, notable pending and overdue amounts"

Practical details:

Periods: this month/quarter/year, previous ones, or any specific range ("from January 1st to March 15th").
Taxes: ask for the figures with or without VAT, as you prefer.
Currencies: each summary is for a single currency (by default, the account's). If you invoice in more than one, ask for them separately ("and now in dollars").

5. How to reach a company with documents

A new client asks you for an electronic invoice and you don't know where to start. Give the assistant the client's tax ID (the NIF in Spain, the SIRET in France, the Partita IVA in Italy, the NIP in Poland, the VAT number elsewhere in the EU):

"Can I send electronic invoices to NIF B51115943? How?" "How do I send invoices to SIRET 13002526500013?" "Does this German client with VAT DE811907980 receive over Peppol?"

The assistant queries the B2Brouter directory and tells you which channel this company receives documents on (Peppol, FACe, Chorus Pro, SDI...), which document types it accepts and which codes you'll need: the DIR3 codes for a Spanish public administration, the SIRET and service code for Chorus Pro, the Codice Destinatario for the Italian SDI, the Peppol identifier for international clients...

If the company is on the Peppol network, but the data is still syncing, the assistant will tell you and retry.
If there's no way to send it documents electronically, it will tell you clearly, and can explain the alternatives.

The search is by exact tax ID and has a daily limit (see Usage limits).

6. Questions about how B2Brouter works

Ask as you would ask support:

"How do I create a credit note?"
"How do I set up TicketBAI?" · "What do I need to do to comply with French electronic invoicing?" · "How does KSeF work?"
"What is the DIR3 code and where do I put it?" · "What is the Peppol identifier?"

For these questions, the connector points the assistant to where B2Brouter's official documentation lives: this very portal. If the assistant can read web pages, it consults it and answers with the current content; if not, it gives you the link.

Chaining it all together

The value of the connector is that these six pieces combine naturally within a conversation. Some complete flows:

Unblocking the day's work: "what invoices do I have with errors?" → "why did the first one fail?" → "what does this error mean?" → you fix it in the panel → "is it fine now?".
The morning tax review (accounting firms): "what did the AEAT reject on the Client SA account this week?" → rejection detail → translation using the authority's guide. To review the whole portfolio: "review all my accounts and tell me which ones have rejected reports". It works, but with dozens of clients it's slow (one query per account); for day-to-day work it's usually faster per specific client.
From the overview to the detail: "what's overdue?" → "list them by amount" → "show me the biggest one".
Integration (developers): API guide → create via API in the sandbox → diagnose errors via the connector → fix the payload.

Remember: the assistant only reads. Creating, correcting, sending and collecting is done in the panel or via API, as always. The work it saves you is searching, cross-referencing and understanding.

To see the functions behind each example, see the Tools reference.