Accounting machine for small Norwegian companies
Macct posts the vouchers, sends the invoices, runs payroll, calculates VAT, depreciates the assets, closes the year and files with the Norwegian authorities. AI reads your documents and proposes the entry. You approve. The machine does the rest — at three in the morning, in July, on a Sunday.
NOK 250 per calendar month you actually use it 30 days free No lock-in Norwegian standard chart of accounts (NS 4102)
One machine
The same machine carries a document from the moment it lands in your inbox to the moment the tax return is filed. Nothing is exported to somewhere else halfway through, and nothing is typed in twice.
Documents→Bookkeeping→Invoicing→Payroll→Bank→VAT→Fixed assets→Year-end→Tax return→Annual accounts→filed
Drag and drop, photo from the phone, EHF file — or forward the invoice to the address your company gets in Macct.
Double entry on the NS 4102 chart, VAT code per line, cost centre and project if you use them. Posted vouchers cannot be edited afterwards.
Invoice as PDF or EHF/Peppol XML, KID and bank account filled in, customer and supplier ledgers, reminders and statutory late-payment interest.
Gross to net with the tax card, employer contribution per zone, holiday pay, payslips and the monthly A-melding. Hours from the time-tracking module flow straight in.
Upload the statement from your online bank — Macct knows the formats from most Norwegian banks — and matches it against what is already posted.
The term is calculated from the vouchers, the settlement entry is proposed, and the return can be validated against the Tax Administration without submitting anything.
Declining-balance depreciation per tax group, with the small-balance rule applied for the year in question — not for today.
NRS 8 check, tax calculation, result to equity, periods locked, and the opening balance for next year generated — one voucher per ledger partner.
Ledger balances mapped to the official fields, validated against the Tax Administration, and submitted — after four separate approval steps that cannot be skipped.
Full annual accounts with notes for a small AS, signed via Altinn and filed with the Register of Company Accounts.
Time tracking, travel expenses, shareholder register, SAF-T export and the full report pack are in the same machine, at the same price. Accounting firms get a client view on top of it.
AI, in practice
AI in Macct is not a chatbot in the corner. It is the part that reads the crumpled receipt and proposes the entry — and it is deliberately never the part that decides.
Drag it in, photograph it, or forward the email. Every company gets its own intake address, and the machine works out what it received: a bank statement goes to reconciliation, a supplier invoice to the invoice queue, your own outgoing invoice is stopped rather than booked as a cost.
The image or PDF is read by Claude Vision: amount, date, supplier, VAT, currency. A receipt in euros is not quietly turned into kroner — the currency is kept, and the rate from Norges Bank for that date is used.
The account comes from the NS 4102 chart, the VAT code from the document. The supplier is matched against what you have posted for that supplier before — your own history outranks everything else. When the AI service does not answer, 198 rule patterns take over instead of leaving you with a blank form.
Probable duplicate. Foreign VAT that cannot be deducted in Norway. An amount that does not add up against the VAT on the document. A ledger entry without a customer or supplier. Each of these is a named warning on the line itself — and a flagged document never posts itself.
Nothing enters your ledger until you accept it. And the database itself refuses any voucher where debit does not equal credit — that is a trigger in Postgres, not a good intention in the code. Once posted, the voucher cannot be edited; a correction is a new, traceable entry.
What the machine deliberately does not do: guess whether a purchase was private. A cafe buys groceries legitimately, and a false accusation is worse than silence. It tells you what it is unsure about instead.
The rules
Any accounting system can write on its website that it follows the Bookkeeping Act. The difference is whether the rules are prose on a page, or code that refuses your voucher when it is wrong.
NS 4102, filled in and ready on day one — not a blank chart you have to build yourself. VAT codes follow the SAF-T standard, output VAT is split by rate the way an auditor expects to find it, and input VAT sits on the asset side where it belongs.
Debit must equal credit — enforced by the database itself, not only by the application, so no path in or around the system can leave an unbalanced entry behind. The period must be open. A VAT term that has been filed cannot be altered underneath the filing. At year-end, equity has to add up before anything is posted.
A posted voucher cannot be edited. A correction is a new, visible voucher that points at the old one — the way the Bookkeeping Act requires and an auditor expects. Nothing is quietly rewritten, and the change log says who did what, and when.
Rates and thresholds are dated, not constants: the small-balance limit is 15 000 up to and including the 2023 income year and 30 000 from 2024, and a calculation for 2023 uses the 2023 figure. Every statutory paragraph we cite in the interface is registered with its heading from Lovdata, and a job checks them every Monday — if a law is amended underneath a reference that was correct when it was written, we get an email about it.
A complete SAF-T Financial v1.30 export, the format the Tax Administration requires when it asks to see the accounts. Plus your own full export whenever you want it — the accounts are yours, and leaving is not something you have to negotiate.
The night shift
In most systems the answer is nobody, until somebody notices something on Monday. Here is the actual schedule, in UTC, every night — 23 scheduled jobs inside the application and 22 more on the server around it.
None of them wait for somebody to remember them. When one of them finds something, it sends an email — and by then the night pipeline has usually already started looking into it.
People are wonderful.
But they are terrible cron jobs.
A person has to remember to run the test, read the log, check the job, notice the deviation, take the backup and follow it up. People get sick, take holidays, miss the alert, get tired and move on. A machine does not need to remember. It just does it, again and again, at the same time every night.
We are not claiming Macct is objectively safer than every other accounting system — that is not something we can document. What we can do is show you exactly what runs, and when, and let you draw your own conclusion. Everything on this page is a job you can read the schedule for.
The machine behind the machine
Automating maintenance is only reassuring if the automation cannot reach production on its own. It cannot. This is the whole route a change must travel, and the gate is a person.
Every night the AI works through the system against a fresh copy of the production database on a separate test server — never against your live accounts.
A finding becomes a fix on its own branch, with a test that fails before the fix and passes after it. A quiet night produces no branch at all.
The same production copy is restored clean a second time, the branch is deployed onto the test server, and the finding is verified gone and nothing else broken.
Only then is a pull request opened. A human reads it and merges it, or does not. The automation cannot merge its own work, cannot push to the main branch and cannot deploy — those limits are enforced mechanically, not by good manners.
Within five minutes of the merge: every pending database migration is first dry-run inside a transaction that is rolled back, the new version is started alongside the old one and only takes over once it is healthy, and a smoke test of over 90 checks runs against the live system afterwards.
AI finds. AI analyses. AI proposes. The machine tests. The human has the last word where it matters. The full description of how changes are tested, reviewed and approved is a page of its own: how Macct changes.
Proof, not adjectives
Every figure here is counted from the system itself, not from a marketing meeting.
A sales page that only lists what works is not worth much. These are the real limits.
Rules and standards → Statutory requirements, point by point →
One price. Everything included.
NOK 250
per calendar month you actually use it
Set up the company, drag in the first document, and see what it proposes. That is the whole test — and it takes about the time it takes to read this page.