A Fortnox integration built for your flow
Invoice data, accruals, customer records and journal entries that go straight into the books. Built by people who run an accounting practice themselves and know what happens when the source data is wrong.
A Fortnox integration is easy to describe and easy to do badly. Pushing an invoice line across is not enough. The customer number has to match, the VAT code has to be right, the accrual has to land in the correct month, and an interrupted run must not leave half the data in the system and half in the books.
We are an integration partner with Fortnox and build a dedicated link for each flow rather than forcing you into a template. That means we start from how you invoice: as you go, in advance, per subscription, per hour, per booking, or all of those at once. The data is created where the business happens, checked by a person where that matters, and then sent across.
Because we also run an accounting practice, we see the other side of that link every month. It shows in the details: reconciliations with evidence and a comment, traceability from a line in the books back to the contract, and clear failures when something does not go through instead of a silent row nobody notices until year end.
What you get
- Invoice data created where the business happens and sent to Fortnox with no manual entry.
- Accruals and index uprating handled in the flow, not in a spreadsheet on the side.
- Customer records kept in step both ways, so the same customer does not exist in two versions.
- VAT codes and exceptions set by your rules rather than a generic template.
- Supplier invoices and journal entries tied to the right contract, project or cost centre.
- Clear failures with a queue and a retry, so a failed transfer never becomes a silent gap.
When it fits
We spend two days a month moving invoice data by hand and it still comes out wrong.
Our system can export a file, but somebody always has to correct it before it enters the books.
We do not know whether every contract was actually invoiced this month, we just hope so.
Two ways to own it
You decide how you pay for what we build. Both routes give you the same system.
You own the solution
One fixed price, paid once. The code is yours, we hand over the source and you can take it anywhere, with us or without us. A good fit if you want control and an investment that becomes a real asset on your books.
We own the code
A low monthly fee and no upfront investment. We handle hosting, updates and continuous improvements. A good fit if you want to get going quickly without tying up capital, and would rather have a cost you can switch off than an investment you have to write down.
Not sure which one? We will talk it through with you, free of charge.
Common questions
- What do you need from us to get started?
- Someone who can explain how you invoice today, and access to your Fortnox environment. We build and test against a contained environment first, run in parallel for a period and only go live once the figures match.
- What happens if Fortnox is down when you send?
- The transfer is queued and retried automatically. Nothing is lost, and if something does get stuck the system alerts us straight away instead of leaving the row sitting quietly.
- Can you connect more than invoices?
- Yes. Customers, articles, supplier invoices, journal entries and payment status are the most common. If you need something the standard flow does not cover, we build it against the API.
Sound familiar?
Describe the problem, not the solution. We reply within one working day.