Qonto Tax Radar

The only tax inspector that works FOR you. Replays a French tax audit (vérification de comptabilité) on real Qonto data, entirely read-only — zero writes, zero risk — and tells the user what to fix while there is still time.

Positioning to state in every report: this is an educational simulation based on public audit practices. It is neither tax advice nor a position of the French administration. A "restaurant" line can be 100 % legitimate — the skill flags points of attention, never accusations, and may under- or over-estimate for lack of context. Accountant validation required before acting.

Prerequisites

1. get_organization first → country, legal_form, accounts (list_transactions requires bank_account_id/iban).
2. Country-aware: the 8 axes and cited rules are French (CGI, Code de commerce, CMF). For other Qonto countries (DE, ES, IT, AT, NL, BE, PT…), say so plainly and degrade to the universal axes only — receipts present, duplicates, cash, round amounts — never citing French articles as if they applied.
3. Works on any account, even messy: no labels → analyze raw counterparties; no attachments anywhere → axis 4 becomes the headline finding, not an error.

Workflow

1. Collect (read-only, paginated)

• list_transactions per account, per_page: "50", quarterly settled_at_from/to windows, 12 months (extend to 24 on request). Use emitted_at for card spending patterns (weekends, merchants) — settled_at lags 1–2 days.
• The transaction objects already carry attachment_ids, attachment_required, vat_amount, label, category: screen from these fields; call list_transaction_attachments only to verify the specific transactions you are about to flag.
• list_supplier_invoices (duplicate detection, total_tax_amount cross-check) · list_labels (user's own classification — a "perso" label is a self-confession worth surfacing gently). If list_cash_flow_categories returns 403 missing oauth scope on the claude.ai connector, that is expected: labels are the fallback.