cogny clifinancefirst 15 calls free

fortnox queried from Bash.

Read invoices, supplier invoices, vouchers, accounts, customers and financial years from your Fortnox books — from the shell over the Fortnox MCP. Pull the ledger as JSON for revenue, AR aging, and reconciliation, no login.

1. sign up, free for the first calls (uses your git email)npx @cogny/cli init --agent claude-code
2. see every Fortnox toolcogny tools list
3. call any tool from bash, no MCP wiringcogny tools call mcp__Fortnox__list_invoices --input '{…}'

Start free @cogny/cli on npm

01two paths

you're a person

Checking AR aging or reconciling spend against the books means clicking through Fortnox screens and exporting. The CLI returns invoices, payments, and vouchers as JSON you can pipe into a reporting step. Connect Fortnox once in Cogny Solo and let your coding agent, or a scheduled loop, do the querying for you.

Start Solo

you're an agent

Sign yourself up with one command. The CLI issues a key, wires nothing, and exposes every Fortnox tool over JSON-RPC. The first 15 calls are free.

npx @cogny/cli init --agent claude-code

02tools call

real Fortnox tools.

Tool names as the Fortnox MCP serves them. Send --input JSON, get JSON back. The payloads are illustrative.

mcp__Fortnox__list_invoices

List customer invoices, filtered (e.g. unpaid).

cogny tools call mcp__Fortnox__list_invoices \ --input '{"filter":"unpaid","limit":2,"sortby":"duedate","sortorder":"ascending"}'

example response

{
  "Invoices": [
    {
      "DocumentNumber": "1142",
      "CustomerName": "Acme AB",
      "Total": 18750,
      "Balance": 18750,
      "DueDate": "2026-05-30",
      "Currency": "SEK"
    },
    {
      "DocumentNumber": "1147",
      "CustomerName": "Beta HB",
      "Total": 9200,
      "Balance": 9200,
      "DueDate": "2026-06-10",
      "Currency": "SEK"
    }
  ]
}

mcp__Fortnox__get_invoice

Read a single invoice with line rows.

cogny tools call mcp__Fortnox__get_invoice \ --input '{"document_number":"1142"}'

example response

{
  "DocumentNumber": "1142",
  "CustomerName": "Acme AB",
  "Total": 18750,
  "Balance": 18750,
  "Booked": true,
  "InvoiceRows": [
    {
      "Description": "Consulting May",
      "Price": 1500,
      "DeliveredQuantity": "12.5"
    }
  ]
}

mcp__Fortnox__list_vouchers

List accounting vouchers for a financial year.

cogny tools call mcp__Fortnox__list_vouchers \ --input '{"financialyear":5,"limit":2}'

example response

{
  "Vouchers": [
    {
      "VoucherSeries": "A",
      "VoucherNumber": 412,
      "TransactionDate": "2026-06-14",
      "Description": "Customer payment 1138"
    },
    {
      "VoucherSeries": "A",
      "VoucherNumber": 411,
      "TransactionDate": "2026-06-13",
      "Description": "Supplier invoice 9921"
    }
  ]
}

03tools list

the rest of the surface.

A sample of the other Fortnox tools. Run cogny tools list --json for every tool and its input schema.

mcp__Fortnox__get_company_information
mcp__Fortnox__list_customers
mcp__Fortnox__get_customer
mcp__Fortnox__list_supplier_invoices
mcp__Fortnox__list_invoice_payments
mcp__Fortnox__get_voucher
mcp__Fortnox__list_accounts
mcp__Fortnox__list_financial_years
mcp__Fortnox__list_orders

04then a verdict

calls from a script. verdicts from cogny.

Every write is logged with who authorised it. Launches your agent makes (a new campaign, a new ad) become measured tickets automatically; for other changes, your agent offers to register them. Cogny measures each in your own data, three days later for ads and seven for content and SEO, and closes it as worked, partial, didn't work or inconclusive.

worked
Moved the number. Every measured win has a share card.
partial
Some of it did.
didn't work
On the record anyway, so it isn't proposed again.
inconclusive
Not enough data to call.

How the loop works

05questions

questions.

Is this an official Fortnox CLI?: No — it is the Cogny CLI calling the Fortnox MCP over the cogny-mcp-proxy. You connect Fortnox once in Cogny, then read the ledger from Bash. Fortnox AB is not affiliated.
Can it modify the books?: No — this MCP is read-only by design. Fortnox OAuth scopes are coarse-grained and cannot enforce read-only at the token level, so write tools (create/update/bookkeep invoices and vouchers) are intentionally not registered. You can only query.
What can I build on it?: Revenue-vs-baseline reports, AR aging from `list_invoices` (unpaid filter), and reconciling ad/supplier spend against `list_supplier_invoices` and `list_vouchers` — all as scheduled JSON pulls.

06related

Building an agent? The full tool map for every server is one fetch: /cli/llms.txt

fortnox, then a verdict.

Start free All CLIs