Direct Visma Integration (Planned)
Status: Not implemented yet – planned, 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".
Why both Fortnox and Visma?
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.
How will it work?
The integration mirrors the Fortnox solution but against the Visma Developer API.
OAuth2 connection
First time, you connect once:
- Go to Admin → Accounting → Integrations → "Connect Visma eEkonomi"
- You're redirected to Visma's OAuth gateway
- Log in with your Visma account
- Visma asks if you allow Vendion to create vouchers – click Allow
- You're sent back to Vendion
- Access is stored securely
Visma has shorter access lifetimes than Fortnox. Vendion renews automatically in the background.
Automatic sync
When a Z-report is created in Vendion:
- Vendion builds the voucher internally
- The voucher is sent to Visma right after
- Visma creates it and returns a voucher ID and voucher number
- Vendion stores the link to the Visma voucher
- Status "Sent to Visma" ✓ shows in Admin → Accounting
Error handling: retry every 5 minutes up to 3 times, then notification.
Chart of accounts mapping
Visma has a more consistent chart than Fortnox (most Visma users run standard BAS). Mapping flow:
- Vendion fetches Visma's chart of accounts
- Mapping view shown where each Vendion account matches a Visma account
- Auto-suggestion based on account numbers (3001 → 3001, 1580 → 1580)
- You confirm or change
- The mapping is saved
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.
Differences vs the Fortnox integration
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.
Frequency
Same options as Fortnox:
- Real-time (recommended): Voucher sent immediately
- Nightly batch: All of today's vouchers at 03:00
- Manual: "Sync now" button in Admin → Accounting
What syncs
Phase 1:
- Vouchers (Z-reports) – Vendion → Visma
- Chart of accounts – fetched from Visma
Phase 2 (later 2026):
- Customer register – for invoicing company customers
- Invoices (if Vendion's invoice module is used)
Security
- Access encrypted
- Scope: Only "write vouchers" and "read chart"
- Revoke: Visma Connect → Applications → Vendion → "Remove"
- Audit: Every sync attempt is logged so you can follow up the history
Visma-specific gotchas
Unique fiscal years
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.
Voucher series
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.
VAT codes
Visma has its own VAT codes linked to accounts. Vendion maps automatically:
- 12% → VAT code "V12"
- 25% → VAT code "V25"
- 6% → VAT code "V6"
Have custom VAT codes – change in the mapping view.
Visma eAccounting (international)
The integration also works against Visma eAccounting (international product), but:
- Swedish VAT code mapping is used anyway (assumes Swedish fiscal year)
- BAS chart required (not other countries' charts)
- Only for Swedish restaurants
Error handling
Visma is down:
- Retry every 5 minutes
- Status "Awaiting sync" until back up
Visma rejects the voucher:
- Common cause: fiscal year not opened, or account missing
- Fix: check under Admin → Accounting → Integrations → "Visma mapping"
Connection has expired:
- Vendion tries to renew the connection automatically in the background
- If renewal fails: notification + reconnection required
Who can connect?
- Active Visma eEkonomi subscription (Smart, Pro or Fakturering)
- Admin rights in both Visma and Vendion
- Included in Vendion at no extra cost
Timeline
- Step 1: Architecture and Visma Developer Registration
- Step 2 (planned): Beta launch in parallel with Fortnox
- Step 3 (planned): General availability
What you can do now
- Use SIE export monthly – works today
- Test SIE import in Visma – confirm it works for you
- Make sure your Visma chart has accounts 2421, 3740 and 3960 (arrange with your accountant)
- Follow the Vendion newsletter for launch dates
If you've already decided on an accounting system
You have Visma: The Visma integration is for you. SIE export works now, the direct API is planned.
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.
Related
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?
