Native bookkeeping & SIE export

Availability: Included in the Stable Plus plan and above, once your organization has enabled the Native bookkeeping feature.

Native bookkeeping records every invoice, payment, and supplier bill directly inside EquiDuty against a Swedish BAS chart of accounts (or the equivalent local chart for NO / DK / FI / NL). The result is a complete verifikat (voucher) ledger you can export at any time as an SIE 4 file — the format Fortnox, Visma, Bokio, and your accountant read with a single click.

That means you no longer need a Fortnox or Visma sync as a separate integration. You run everything inside EquiDuty and hand over the SIE file at month-end or year-end.

What gets booked automatically?

As soon as Native bookkeeping is enabled, EquiDuty writes a voucher every time you:

• Create a customer invoice → voucher in series A: debit Accounts receivable (1510), credit the income account for the item type and VAT rate (3041 / 3043 / 3051 / 3052 / 3230), and credit Output VAT per rate (2611 / 2621 / 2631).
• Record an inbound payment → voucher in series I: debit Bank (1930, or 1931 for Swish) and credit Accounts receivable (1510).
• Create a supplier invoice → voucher in series B: credit Accounts payable (2440), debit each expense account, and debit Input VAT (2641).
• Pay a supplier invoice → voucher in series L: debit Accounts payable (2440) and credit Bank (1930).
• Credit-note an invoice → reversal: same series as the original, but with debit and credit swapped.
• Post a manual journal → voucher in series M.

Every amount is stored in minor units (öre / cents). The voucher date is the accounting date, not the registration date — that matches how Skatteverket expects VAT to be periodised.

Per-country chart of accounts

EquiDuty picks the chart automatically based on your Organization country (under Settings → Organization):

You can adjust which accounts are used for each income type (boarding, feed, lessons, transport, etc.) under Invoice → Settings → Bookkeeping. Save, and new vouchers immediately use your customised accounts.

SIE export — one fiscal year per file

The SIE 4 format describes one fiscal year per file. EquiDuty follows the spec strictly:

• You can’t export a range that spans two fiscal years (e.g. Dec–Jan). Adjust the date range.
• The file contains #IB 0 (opening balances for balance-sheet accounts), #UB 0 (closing balances), and #RES 0 (result per income/expense account) for the whole year — even if you only exported a single month.
• Each voucher series (A, B, I, L, M) has its own running number that restarts at 1 on every new fiscal year.
• #KSUMMA on the last line is a checksum across every amount in the file. Importers like Fortnox and Visma use it to detect corruption.
• Files are encoded in CP437 (#FORMAT PC8). EquiDuty handles the conversion — you don’t need to worry about Å, Ä, Ö, Æ, Ø, etc.

How to export

1. Go to Invoice → Bookkeeping → SIE export.
2. Pick a from date and a to date (must fall inside the same fiscal year).
3. Click Preview — you’ll see a summary per voucher series and the total count.
4. Click Download SIE file.
5. Email the file to your accountant, or upload it directly to Fortnox / Visma / Bokio.

EquiDuty saves every export as an export batch with a timestamp, voucher count, and SHA-256 of the file contents. If you need to regenerate a range (e.g. to correct a typo) pass force=true and a short reason — the new batch links to the previous one via supersedes so the audit trail stays intact.

Multi-currency

An SIE 4 file may declare only one currency (#VALUTA SEK, #VALUTA NOK, etc.). EquiDuty picks the currency automatically based on the vouchers in the export range:

• All vouchers in SEK → #VALUTA SEK.
• All vouchers in NOK → #VALUTA NOK.
• A mix of SEK and NOK → the export fails with “Mixed currencies in export range”. Filter your export per currency and download one file per currency.

For a Swedish bureau managing a Norwegian subsidiary, this means two files per fiscal year — one with Swedish BAS accounts and #VALUTA SEK, one with Norwegian NS accounts and #VALUTA NOK.

Handing the SIE file to your accountant

What your accountant needs to know:

• The file is named equiduty-{org}-{YYYY-MM-DD}-{YYYY-MM-DD}.sie. The dates are the export range.
• The file is complete — it includes the full chart of accounts (#KONTO), every voucher, and both opening and closing balances.
• The file is immutable. Once you download it the corresponding vouchers in EquiDuty are locked. If you need to correct a voucher after export, post a credit note (a reversing voucher) rather than editing the original — that’s what Swedish accounting law (Bokföringslagen) requires.

FAQ

What do I do if I used the wrong VAT rate on an invoice?

1. Credit-note the original invoice (create a credit invoice). EquiDuty automatically books a reversing voucher.
2. Create a new invoice with the correct VAT rate.
3. On the next SIE export both vouchers ride along and the net effect is correct.

How does EquiDuty handle fiscal year close?

When you close a fiscal year under Invoice → Bookkeeping → Fiscal year, EquiDuty captures a balance snapshot (the opening balances for next year) and refuses to post any new voucher into the closed year. Back-dated invoices with a date inside the closed range are rejected.

Can I still sync with Fortnox or Visma?

Yes — if you already have an active sync it keeps working. But once Native bookkeeping is enabled, the SIE export becomes the recommended hand-off because it’s complete, checksum-validated, and doesn’t depend on third-party API availability.

What happens if I enable Native bookkeeping mid-fiscal-year?

Vouchers are recorded from the moment of activation. For the period before activation you’ll need to import opening balances manually (your accountant can give them to you from the previous year) or accept that the first fiscal year with Native bookkeeping is incomplete and start “clean” from the next year.

What if the SIE file errors in Fortnox / Visma?

Use EquiDuty’s built-in checks first:

• The preview flags warnings for balance discrepancies, unmapped accounts, and closed fiscal years — fix them before download.
• #KSUMMA is validated automatically on every export. If the file is corrupted between download and upload the importer will catch it instantly.

If you still get an error, email support@equiduty.se with the message from Fortnox / Visma and we’ll help you interpret it.