How Diffa works

Diffa is an integration engine between the platforms you sell through and your accounting software. Each platform has its own integration in. Everything after that happens in one engine that books sales, VAT and fees the same way whatever the source and shows every month that it matches.

The Diffa engine

Reads the payout with every line

Turns the lines into common events

Books them to your approved accounts

Works out VAT, OSS and currency

Reconciles against the payout

Each platform has its own integration into the Diffa engine. The engine reads the payout, turns the lines into common events, books them, works out VAT and currency, reconciles and sends the voucher to your accounting software.

From platform to event

How Diffa brings in the money from each platform.

One integration per platform, one engine for all

Every platform reports its payouts in its own way. Stripe lists every payment and fee included in the payout. Klarna sends a settlement report. PayPal has a statement. Shopify has the orders in one place and the money in another.

That is why Diffa has its own integration for each platform. The integration reads the platform’s records and turns them into the same kinds of events whatever the source: sale, fee, refund, payout, reserve and exchange difference. The engine that books only sees the events. A sale with OSS VAT is therefore booked the same way whether the money came through Stripe, Klarna or Shopify.

It is also why Diffa can take on many platforms. A new platform is a new integration that translates its records. VAT rules, accounts and reconciliation are already in the engine and do not need to be rebuilt.

Several sources in one company

A Shopify store often takes payment in several ways: Shopify Payments for cards, Klarna for invoices and PayPal for those who want it. If the company also sells subscriptions through Stripe, that is four platforms paying out to the same bank account, each with its own fees and schedule.

All four are connected to the same company and the same accounting software. Each source gets its own receivable and its own fee accounts so you always see what each platform owes you. The reconciliation is shown per source and for all of them together.

How many sources you can connect depends on the plan: Bas one source, Plus up to three sources and Volym unlimited sources.

Fetching

Diffa fetches transactions and payouts from the platform twice a day at 07:00 and 19:00. It also fetches straight away when the platform sends a signal. Every payout is fetched with its lines: payments, refunds, disputes and fees. The raw data is always kept so every voucher can be traced back to what the platform actually said. The same event is never booked twice even if it arrives both by signal and by fetch.

From event to voucher

How every line gets its account, VAT and rate.

Booking to accounts

Every line gets an account according to the rules you approved: gross sales on the revenue account, fees on their account and VAT on its own. The net goes to the receivable from the platform, 1686 by default, until you book the deposit in your accounting software. Each sales day becomes a voucher against the receivable and the payout is then reconciled against what is already booked. For a source you can instead choose one voucher per payout or per transaction. Diffa never reads bank accounts and never books bank lines.

VAT

Swedish VAT on Swedish sales. Reverse charge on fees from foreign platforms. OSS VAT on sales to consumers in other EU countries at the right country’s rate. Where the platform sells in its own name your sale is booked as a service to the platform company without Swedish VAT. Stripe Tax codes are read where they exist so goods and services land right per line.

Currency

Amounts in other currencies are converted at the Riksbank’s rate on the transaction date for 29 currencies. The difference from what the platform actually paid out is booked as an exchange difference on its own account, never hidden in the sales.

When the engine cannot decide

Diffa does not guess. An event that cannot be booked safely is parked with an explanation: a payment that mixes goods and services without the platform reporting the lines, a fee without VAT information, a currency the Riksbank does not publish. You or your accountant decide in Diffa and the event is booked straight away. Until then it shows in the reconciliation as not booked.

Control and delivery

How you see that it matches and decide what is sent.

Reconciliation

Every month, per source and for all of them together, Diffa compares the sum of the platform’s payouts with the sum of Diffa’s vouchers and lists the events not yet booked. The month’s report can be printed or saved as a PDF for your accountant’s file.

Read about the reports you get.

Your AI assistant via MCP

At launch Diffa gets an MCP server. MCP is the open protocol that AI assistants such as Claude and ChatGPT use to fetch information from other services. The assistant can then answer questions about your company in Diffa or be part of an automated flow you build yourself.

You connect the assistant with OAuth: you log in to Diffa, choose the company and approve. No passwords or keys leave Diffa and you remove the connection under Settings whenever you like. The assistant reads; it books nothing.

You decide when it is sent

The vouchers are created in Diffa first. They are sent to your accounting software once you turn on automatic booking. You can turn it off again. Nothing is booked twice, nothing is booked in a locked period and nothing is booked before the start date you chose. Anything not sent can be downloaded as a SIE 4 file.

Want to know when Diffa opens?

Leave your email and we will be in touch. No newsletter, just one email when it is time.

We will be in touch when we open.