Status (April 2026): Not implemented. Planned launch ~May 2026 in parallel with the Fortnox integration. This article describes how the integration will work. Until then, use manual SIE export – see "Export SIE from Vendion – step by step" and "Import SIE into Visma eAccounting".
Fortnox and Visma eEkonomi are Sweden's two largest accounting systems. Vendion supports both so no restaurant has to switch accounting systems because of its POS. Your accountant already works in one of these – we adapt to that.
The integration mirrors the Fortnox solution but against the Visma Developer API.
First time, you connect once:
Visma has shorter access lifetimes than Fortnox. Vendion renews automatically in the background.
When a Z-report is created in Vendion:
Error handling: retry every 5 minutes up to 3 times, then notification.
Visma has a more consistent chart than Fortnox (most Visma users run standard BAS). Mapping flow:
Default mapping (when Visma uses standard BAS chart):
| Vendion | Visma |
|---|---|
| 3001 Sales food 12% | 3001 Domestic sales, 12% VAT |
| 3003 Sales alcohol 25% | 3001 Domestic sales, 25% VAT |
| 1910 Cash | 1910 Cash |
| 1580 Card receivables | 1580 Receivables from credit card companies |
| 2610 Output VAT 25% | 2610 Output VAT |
| 2620 Output VAT 12% | 2620 Output VAT |
| 2421 Gift card liability | 2421 Other short-term liabilities |
| 3740 Penny rounding | 3740 Öre and krona rounding |
| 3960 Expired gift cards | 3960 Other income |
If you have customizations: adjust in the mapping view.
Both work similarly, but the details differ:
| Aspect | Fortnox | Visma eEkonomi |
|---|---|---|
| OAuth provider | Fortnox own | Visma Connect |
| Access lifetime | Longer | Shorter (renewed more often in background) |
| Webhooks | Supported | Partial support |
| Launch priority | Phase 1 | Phase 1 (parallel) |
Vendion abstracts the differences – you see the same UI regardless of system.
Same options as Fortnox:
Phase 1 (May 2026):
Phase 2 (later 2026):
Visma requires the fiscal year to be opened before you can import. If you sync January 2026, fiscal year 2026 must be opened in Visma. Vendion checks this before the first sync.
Visma uses "voucher number series". Vendion creates a new series "Z" on first sync (if not already present) so that Z-reports are separated from manual vouchers.
Visma has its own VAT codes linked to accounts. Vendion maps automatically:
Have custom VAT codes – change in the mapping view.
The integration also works against Visma eAccounting (international product), but:
Visma is down:
Visma rejects the voucher:
Connection has expired:
You have Visma: The Visma integration is for you. SIE export works now, direct API lands May 2026.
You have Fortnox: See the article "Direct Fortnox integration (planned)".
You have Bokio: No direct API planned, but SIE export to Bokio works fine.
You have Björn Lundén or other: SIE export is the only path and will remain so.
See also "Direct Fortnox integration (planned)", "Import SIE into Visma eAccounting" 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?