Vendion
    Accounting & Finance

    Direct Fortnox Integration

    5 min read#35

    Status: Available. If you choose Fortnox as your accounting system, Vendion can push the Z-voucher to Fortnox automatically at day-end – no SIE file needed. If you prefer to export manually, SIE works just as well – see "Export SIE from Vendion – step by step" and "Import SIE into Fortnox".

    Why use it?

    SIE export works, but requires manual handling every month. Restaurant owners who want full automation use the direct integration:

    • Zero manual work – vouchers created automatically in Fortnox
    • Real-time sync – Z-report created → voucher in Fortnox the same second
    • No risk of forgotten months – everything happens automatically
    • Two-way chart of accounts sync – Fortnox is source of truth, Vendion follows

    How does it work?

    OAuth2 connection

    The first time, you connect Vendion to Fortnox once:

    1. Go to Admin → Accounting → Integrations"Connect Fortnox"
    2. You're redirected to the Fortnox login page
    3. Log in with your Fortnox account
    4. Fortnox asks if you allow Vendion to create vouchers – click Allow
    5. You're sent back to Vendion
    6. Access is stored securely

    The connection renews automatically and persists. You don't need to log in to Fortnox inside Vendion after the first time.

    Automatic sync

    When a Z-report is created in Vendion:

    1. Vendion builds a voucher as usual
    2. The voucher is sent to Fortnox right after
    3. Fortnox creates the voucher and returns a voucher number and voucher series
    4. Vendion stores the link to the Fortnox voucher
    5. In Admin → Accounting you see status "Sent to Fortnox" ✓ on the voucher

    If the Fortnox call fails, the voucher goes into a retry queue and tries again every 5 minutes. After 3 failed attempts you get a notification.

    Chart of accounts mapping

    Before the first sync, accounts must be mapped:

    1. Vendion fetches the Fortnox chart of accounts
    2. You see a mapping view: "Vendion account 3001 → Fortnox account __"
    3. Select the corresponding Fortnox account for each Vendion account
    4. Save – the mapping is used for all future vouchers

    Default mapping for BAS chart (if Fortnox uses standard BAS):

    Vendion accountAssumed Fortnox account
    3001 Sales 25%3001
    3002 Sales 12%3002
    3003 Sales 6%3003
    1910 Cash1910
    1580 Card receivables1580
    2610 Output VAT 25%2610
    2620 Output VAT 12%2620
    2630 Output VAT 6%2630
    2421 Gift card liability2421

    Note: The numbers above are assumed standard BAS accounts. Your own chart of accounts in Fortnox may differ – that's why Vendion shows a mapping view where you match each Vendion account to the right Fortnox account. If unsure, check with your accountant.

    Frequency

    You pick the sync cadence in settings:

    • Real-time (recommended): Voucher sent the moment a Z-report is created
    • Nightly batch: All of today's vouchers sent at 03:00 – practical if you don't want ongoing traffic to Fortnox
    • Manual: "Sync now" button in Admin → Accounting – for those who want full control

    What will sync

    Phase 1 (MVP):

    • Vouchers (Z-reports) – Vendion → Fortnox
    • Chart of accounts – fetched from Fortnox, read in Vendion

    Phase 2 (later 2026):

    • Customers – if you invoice companies, customer data syncs
    • Supplier invoices – not in scope (Vendion is a POS, not an AP module)

    Error handling

    Fortnox is down:

    • Vendion retries automatically
    • After 3 failed attempts: notification + voucher marked "Awaiting sync"
    • When Fortnox is back up: the retry queue processes automatically

    Fortnox rejects the voucher:

    • Common cause: the account doesn't exist in the Fortnox chart
    • Fix: check the mapping under Admin → Accounting → Integrations → "Fortnox mapping"

    Connection has expired:

    • Vendion's access to Fortnox renews automatically in the background
    • If renewal fails (rare): you get a notification and need to reconnect Fortnox

    Duplicate in Fortnox:

    • Vendion marks each voucher with a unique reference so Fortnox doesn't create duplicates

    Security

    • Access stored encrypted
    • OAuth2 scope: Only "write vouchers" and "read chart" – not full Fortnox access
    • Access can be revoked anytime in Fortnox settings → Integrations → Vendion → "Remove"
    • Audit log: Every sync attempt is logged so you can follow up the history

    Who can connect?

    Requirements:

    • Active Fortnox subscription (all tiers work)
    • Admin rights in both Fortnox and Vendion

    Plan:

    • Included in Vendion from launch (no extra cost)
    • Fortnox API calls are free within Fortnox standard limits

    Difference vs SIE export

    SIE exportDirect Fortnox
    Manual (monthly)Automatic (real-time or nightly)
    File must be downloaded and importedNo file
    Duplicate data possibleDuplicates prevented automatically
    Works with all systemsFortnox only
    Available nowPlanned

    Timeline

    • Step 1: Architecture and MVP development
    • Step 2 (planned): Beta launch for selected customers
    • Step 3 (planned): General availability

    The timeline may shift – see the Vendion newsletter for updates.

    What you can do now

    Until the integration is live:

    1. Use SIE export every month (takes 5 minutes)
    2. Test SIE import in Fortnox so you know it works in your environment
    3. Ask your accountant to configure the Fortnox chart so that all Vendion accounts (2421, 3740, 3960) exist – makes future mapping smoother
    4. Watch the Vendion newsletter for launch dates

    See also "Direct Visma integration (planned)", "Import SIE into Fortnox" and "Export SIE from Vendion – step by step".

    This feature is part of Vendion POS.

    Curious how it looks in practice? Read more about the product or book a short demo.

    Was this article helpful?