Automate Supplier Invoices Into Fortnox
By CodexierPublished 6 min read
Supplier invoices are the most repetitive flow in a small Swedish company: an email arrives, someone downloads a PDF, types the amount into Fortnox, matches it to a cost account and asks the owner to approve. Every step can be automated, and two of them should stay with a person. This guide walks the invoice from inbox to attested booking and shows where the line goes.
The short answer
This is one of the flows we build most often in a workflow automation project, so the steps below are the ones that survive contact with real bookkeeping, not a demo.
Map today's invoice journey
Before touching a tool, write down what happens to one invoice now. Who receives it, where it waits, who decides the account, who approves, and when it is paid. Most companies find that an invoice passes through three inboxes and one spreadsheet before it reaches Fortnox, and that the delay sits in approval, not in typing.
| Step | Usually done by | Automate? |
|---|---|---|
| Receive the invoice | Whoever's inbox it lands in | Yes: route every invoice to one channel |
| Read amount, date, VAT, OCR number | Bookkeeper, by hand | Yes: interpretation with a confidence check |
| Choose account and cost centre | Bookkeeper | Mostly: rules for known suppliers, human for the rest |
| Approve for payment | Owner or manager | No: automate the reminder only |
| Register and pay in Fortnox | Bookkeeper | Yes: API or built-in flow |
Capture: email, scanning and Peppol
The capture step decides how much cleaning the rest of the flow needs. A Peppol e-invoice arrives as structured data: amounts, VAT lines and due date are fields, not pixels. Ask every supplier that can send Peppol to do so; Fortnox has a Peppol address for your company, and public-sector suppliers already use it. Fortnox's own supplier invoice inbox handles PDF and scanned invoices with interpretation, and is the right second choice. Parsing emails yourself with an automation tool is the last resort, because attachments come in every format and the interpretation is on you.
- Give suppliers one address: a dedicated invoice mailbox or your Peppol ID, never a person's email.
- Forward that mailbox automatically to the Fortnox inbox so nothing waits in a personal account.
- Keep the original file. The Bookkeeping Act requires the invoice in the form it was received, so a PDF stays a PDF.
- Set a confidence threshold: an interpreted amount below full confidence goes to a person, not into the ledger.
Coding and approval rules
Coding is where rules pay off. Most suppliers always land on the same account: the phone operator on telecom, the landlord on rent, the fuel card on vehicle costs. A rule set of supplier, amount range and a keyword on the invoice line covers most volume. Everything that does not match a rule is queued for a bookkeeper with a suggested account, not silently booked to a catch-all.
Approval is the step we advise clients to keep human, and to make fast instead. The automation's job is to send the approver a message with the supplier, amount and a link, remind after two days, and escalate after five. The decision stays with a person because approval is also fraud control: fake invoices that mimic a real supplier are the most common attack on small companies, and a rule cannot spot a changed bank giro number the way an attentive owner can.
Fortnox connection options
Built into Fortnox
Supplier invoice inbox, interpretation and attest flow are included in the higher plans. Zero integration work; least flexible rules.
Marketplace app
Pre-built invoice management apps connect through Fortnox's app store. Good rules and approval flows; a monthly fee per company and sometimes per user.
Zapier, Make or n8n
Fine for routing and reminders, weaker at interpretation. Use with the Fortnox inbox rather than instead of it.
Custom integration via the Fortnox API
When coding rules depend on your own systems, such as a project number from a job system. Full control, needs an owner.
Decision rule: fewer than fifty invoices a month, use what is built into Fortnox. More, or invoices that must be matched to projects or purchase orders, use a marketplace app or a custom flow. If you are choosing between the automation platforms, our Zapier, Make and n8n comparison covers pricing and EU hosting.
What to keep manual
Not every company should buy this. If you receive a handful of invoices a month, Fortnox's inbox and a fixed Friday routine are enough, and an automation project would cost more than a year of the typing it removes. Keep three things manual regardless of volume: the approval itself, any invoice from a new supplier or with changed bank details, and the monthly reconciliation where a person confirms that what was booked matches what was paid.
If you are past fifty invoices a month, or the approvals are what slows payments, book a call and bring last month's invoice list. We will show you which steps a rule can take and quote a fixed price from our price list.
Frequently asked questions
Does automating invoices satisfy the Swedish Bookkeeping Act?
Yes, provided the original is preserved in the form it arrived, every booking can be traced back to it, and the material is kept for seven years. Fortnox stores the attached file with the voucher, which meets the archiving requirement as long as the file you attach is the one the supplier sent.
Can the flow handle invoices in other currencies and reverse-charge VAT?
It can, but these are exactly the cases to route to a person. Foreign supplier invoices often need reverse-charge VAT coding and the correct exchange rate on the invoice date. A rule can flag them; a bookkeeper should confirm the coding until the pattern is stable.
What happens when interpretation reads the wrong amount?
A well-built flow compares the interpreted total with the sum of the lines and the VAT, and sends anything that does not add up to a review queue. Nothing is booked automatically below a confidence threshold. Expect a small share of invoices to need a human look; that share drops as suppliers move to Peppol.
How long does it take to set up?
Using Fortnox's built-in inbox, an afternoon. A marketplace app with coding rules and an approval flow, a few days including testing on last month's invoices. A custom API integration depends on the systems it must talk to and is scoped on a call.
Want your invoices to stop waiting in inboxes?
Bring last month's supplier invoice list. In fifteen minutes we map which steps rules can take, where approval should stay human, and what a fixed-price setup would cost.
Book a free 15-minute call