Cogny Cloud · Fortnox

Bookkeeping that connects to the rest of your stack.

Cogny reads Fortnox through the MCP, joins your bookkeeping to ad spend and revenue, and creates tickets for invoice drafts, voucher postings and reconciliation. Approve in tickets — Cogny executes through the Fortnox MCP.

❯ book a Cloud demo see how it replaces the manual flow →

❯

cogny --replaces

FLOW

Same outcome. Two very different processes.

How you do it today

Open Fortnox. Draft invoices for new customers by hand.
Match supplier invoices against the right account by memory.
Reconcile vouchers row by row.
Cross-check totals against Stripe / Shopify in a spreadsheet.

How Cogny Cloud does it

Cogny connects to Fortnox + Stripe / Shopify via MCP — one-time.
Pulls customers, articles, invoices, supplier invoices and vouchers on a schedule.
Finds insights: missing invoices, miscategorized supplier invoices, voucher drift.
Creates a ticket per proposed action.
You approve in tickets.
Cogny executes through the Fortnox MCP — drafts invoices, posts vouchers, updates customers.
Tracks which tickets actually closed the bookkeeping gap. Smarter every period.

❯

cogny --tickets

read + write

Cogny creates tickets AND executes the approved ones through the MCP. Each insight becomes one ticket — here are the kinds Cogny creates from Fortnox:

Invoice-draft ticketNew Stripe customer without a matching Fortnox invoice — Cogny drafts it.

Voucher-post ticketBookkeeping entries ready to post after end-of-month reconciliation.

Supplier-invoice ticketSupplier invoices waiting for approval / bookkeep flagged for review.

ExecutionCogny can create customers / articles / invoices / vouchers and post bookkeeping entries through the Fortnox MCP after approval. Posted invoices and vouchers cannot be undone — credit notes are used instead, also via Fortnox.

LearnsCogny learns your chart-of-accounts conventions over time — which voucher series and which accounts you actually use — so proposals match house style without manual fix-ups.

❯

cogny --reads

DATA

The reports Cogny pulls on schedule for Fortnox insights

FortnoxCustomers, Invoices, Vouchers, Articles

StripeRevenue + invoice source

ShopifyOrder + product data

Cogny memoryOrg context across weeks

❯

cogny --book

DEMO

Tell us your use case. Then book a 15-min Cloud demo.

❯

cogny --faq

ASK

The questions we usually get on the demo call

Does Cogny replace Fortnox?

No. Cogny connects to Fortnox and adds an AI analyst on top — you keep using Fortnox for everything you do today.

Does Cogny make changes automatically?

No — Cogny creates a ticket for every proposed action, you approve in tickets, then Cogny executes the approved ticket through the Fortnox MCP. Nothing ships without you signing off.

Does Cogny write copy or creative?

No. Cogny does not write ad copy, email bodies, post content, image creative or rewrite existing copy. Cogny’s execution is limited to structural changes — segments, tags, metadata, internal links, redirects, scheduling assets you’ve already drafted, status changes (pause/resume/archive), and code-level PRs via Cogny Code.

Does Cogny actually get smarter over time?

Yes. Every approval and rejection is a signal. Cogny tracks the outcome of each executed ticket (did the deal close, did the ranking recover, did the segment lift revenue) and tunes its proposals to your business — so noisy or irrelevant tickets fall off and the high-signal ones become the default.

❯