Connect Field Software to Accounting: What Actually Syncs

When you connect field software to accounting, three things move automatically: the customer invoices you raise from the job, the customer register behind them, and — with Fortnox — supplier invoices. Almost nothing else does. Bank reconciliation, the VAT return, payroll, depreciation and year-end all stay in the accounting system, done by you or your bookkeeper. An accounting integration is an invoice pipe with a customer list attached, not a bookkeeping robot. The part that decides whether it works is boring and happens before you click connect: agreeing with your bookkeeper which article posts to which revenue account, and which VAT code goes with it.

What an accounting integration actually moves

Every field system markets this differently, but under the marketing the surface area is narrow. Here is what a modern OAuth-based link to Fortnox or Visma genuinely transfers.

What stays manual, permanently

This is where owners get surprised. None of the following is a gap that a better integration fixes — they are outside the scope of what an invoice pipe can do:

• Bank reconciliation. Matching payments to open invoices happens in accounting, against a bank feed. Even if it is automatic there, it is not the field system doing it.
• Chasing payment. Reminders and debt collection sit wherever your ledger is. Decide which system sends the reminder, then turn the other one off, or your customer gets two.
• The VAT return. Your integration supplies correctly coded lines. Someone still files.
• Payroll. A geofenced time clock can export hours to a payroll CSV, but the payroll run and the employer declaration are separate.
• Supplier invoice approval and coding. The photo capture gets the document in. A human still checks it against the job and approves it.
• Anything you post directly in accounting. Manual journal entries, adjustments and accruals never come back to the field system.

A fair expectation: an accounting integration removes retyping and typos. It does not remove your bookkeeper.

The mapping decisions to make with your bookkeeper before you connect

Book 45 minutes with whoever does your books. Bring your article list. Decide these six things and write the answers down, because you will be asked for them during setup and guessing costs you a month of corrections.

1. Which revenue account does each article post to

In Sweden this means the BAS chart of accounts. Most small trades firms end up splitting labour and materials — labour to a services sales account, materials to a goods sales account — because ROT reporting and gross-margin analysis both need the split. If you also do reverse-charge construction work, that needs a third, zero-VAT sales account. Your bookkeeper picks the actual numbers; your job is to make sure every article in your price list maps to exactly one of them and none is left on a default.

2. VAT code per article, not per invoice

The code travels with the line, not the document. Standard Swedish VAT is 25%. Reverse-charge construction services (omvänd byggmoms) between two construction businesses carry no VAT on the invoice and a mandatory reference on the document instead. Get this wrong on an article and every invoice using it is wrong. Check the current rules at Skatteverket rather than trusting an old template.

3. Customer numbers: who owns them

Two registers, one truth. Either the field system creates customers and the accounting system accepts its numbers, or the accounting system owns numbering and the field system matches against it. Matching is normally on organisation number or email. If your register has three versions of the same customer with different spellings, clean it up before you connect — otherwise you duplicate the mess.

4. Invoice number series

Pick one system to allocate invoice numbers. Numbers must be unbroken and sequential. Two systems allocating from the same range produces duplicates that you cannot simply delete your way out of, because a Swedish invoice number, once issued, is part of your accounting records.

5. The ROT split

ROT is the Swedish tax deduction for household work: 30% of the labour cost, with an annual per-person ceiling shared with RUT (check the current amount at Skatteverket). The customer pays the net; you claim the rest from the tax authority. That means one invoice becomes two receivables — one from the customer, one from Skatteverket — and your bookkeeper needs a separate receivable account for the Skatteverket half so it does not sit in your normal customer ledger looking overdue. Agree that account name at the same meeting. Green-tech (grön teknik) works the same way but is its own scheme with its own rate, so it needs its own mapping.

6. Terms, interest and delivery

Payment days, late-payment interest, and whether the invoice goes as PDF, email or e-invoice. Decide which system is authoritative. If your field system says 30 days and your accounting defaults to 20, whichever posts last wins and neither of you notices for a quarter.

How the connection works: OAuth, not a password

In 2026 the standard is OAuth. You click connect, get sent to Fortnox or Visma, log in there, and approve a scoped consent screen. The field system receives a token, never your password. Three practical consequences:

• The person clicking connect needs admin rights in the accounting system, not just the field system.
• Consent has scopes. If invoices post but customers do not, the scope for customers was probably not granted. Reconnect rather than debug.
• Tokens expire and can be revoked. If sync stops dead one morning, check the connection status before you assume data loss. Nothing is lost — it is queued or it is refused.

Connect day: the order that avoids a mess

1. Clean the customer register in whichever system is going to own it.
2. Map every article to an account and a VAT code. Leave nothing on a default.
3. Decide the invoice number series and switch off numbering in the other system.
4. Connect via OAuth with an admin account.
5. Push one real invoice. A small one, with both labour and materials, and ROT if you do ROT.
6. Open it in accounting. Check the accounts, the VAT, the customer, the number and the due date — all five.
7. Only then push the rest. Do not backfill history; start from a date and keep the old invoices where they are.

Where it breaks

Four failure modes account for most of the pain: an article with no account mapping silently falling to a catch-all; duplicate customers from loose matching; VAT codes copied from a pre-reverse-charge template; and both systems sending payment reminders. All four are decided before you connect, which is exactly why the setup meeting matters more than the software.

Outside Sweden: same map, different labels

If you are reading this in the UK, New Zealand or Australia, the structure is identical and only the names change. Swap BAS for your own chart of accounts, Swedish 25% VAT for UK VAT at 20% or NZ GST at 15%, and reverse-charge construction VAT for the UK's CIS domestic reverse charge. ROT has no direct equivalent, so ignore that decision — but the split-receivable problem it creates shows up anywhere a third party pays part of your invoice, including insurers and grant schemes. The one honest constant: the integration moves invoices and customers. Everything downstream of the bank is still bookkeeping.

What you actually get back

Roughly: no retyping, no transcription errors between the job and the ledger, and invoices that go out the day the job finishes instead of the weekend after. That is real money. It is just not the same as automated bookkeeping, and any vendor implying otherwise is selling you a disappointment.

OdinTask connects to both Fortnox and Visma over OAuth, and syncs customer invoices, supplier invoices and the customer register — including the ROT split and the Skatteverket claim file, so the deducted half does not go missing. Everything above about mapping still applies; we just make the decisions visible instead of hiding them behind a default. Start a 14-day free trial or see pricing.