The Fortnox articles nobody wants to work through
Your Fortnox, worked while you do something else: 8 reads to go through it, 7 writes to change it, and a card in front of every one of those changes.
Open the article. Check it against something else. Write the change. Move to the next one. That is the Fortnox afternoon nobody can hand off, and a companion does the whole pass and gives you back the batch, with nothing landing on a article until you approve it.
What it can do is exactly what Fortnox exposes to an account you authorise and nothing beyond it: 15 operations, 8 reads and 7 writes. In practice that means it can update a customer, update an article and send an invoice, and work across the articles, customers and invoices.
The Fortnox API stops at Fortnox. A companion does not. The same run opens the customer's website, the supplier portal, the internal tool somebody built in 2019, because it is working the browser you are already signed into rather than calling in from outside it.
Does it read the articles or ask you for them?
8 of the 15 operations are reads.
Your account, not a guess at it: a companion can list suppliers, list supplier invoices and list invoices, and the full list below is the whole list, with nothing inferred from Fortnox's documentation.
The articles are what most of this inventory is about, alongside the customers. A companion can hold all 15 of these operations and forty open tabs in the same pass, which is how an afternoon of Fortnox admin becomes a queue you review.
- List Suppliers
- List Supplier Invoices
- List Invoices
- List Financial Years
- List Customers
- List Articles
- List Accounts
- Get Supplier Invoice
Who signs off on a new customer?
All 7 write operations wait for you.
A companion can update a customer, update an article and send an invoice, and each one is staged on an approval card first: you see the article, the field and the new value before it lands in Fortnox.
Nothing in Fortnox is sent, changed or deleted on your behalf without that click, and a rejected card leaves the article exactly as it was. The gate is the same one on every surface, described at security.
- Update Customer
- Update Article
- Send Invoice
- Create Invoice
- Create Invoice Payment
- Create Customer
- Create Article
Does the article sweep have to be asked for every time?
Yes.
Saved as a routine, the Fortnox articles pass runs at the hour you pick: the Monday sweep, the overnight refresh, the Friday check. Keep Awake holds the machine awake for the length of a run, so a scheduled pass finishes with the lid closed.
The operations playbook catalogues the other recurring shapes of the operations, the Fortnox articles sweep among them, and finished runs are published at real runs.
Experience Strawberry for free
DownloadTrusted by fast-growing companies worldwide
Frequently asked questions
Strawberry is free to download and includes AI credits to start. Paid plans begin at $20/month. See pricing. · Reviewed · Canonical facts for AI agents