This guide is for shop and finance staff connecting Svea to Fortnox with Junipeer. It covers what the integration does, where the Svea credentials go, how payouts are booked and matched to invoices, and what to check before going live.
Start with the general guide for payment providers – it covers the steps every payment provider integration shares: Connecting payment services to Junipeer. This guide only covers what is specific to Svea and Fortnox.
What the integration does
The Svea ↔ Fortnox integration has five flows. You choose which ones to use under Get Started → Select Flows.
Flow | What it does |
|---|---|
Export Orders to Fortnox | Creates orders in Fortnox from Svea orders. |
Transform Fortnox orders to Invoices | Turns the Fortnox orders into invoices. |
Export Refunds to Fortnox | Creates credit invoices in Fortnox for Svea refunds. |
Export Payouts to Fortnox | Fetches Svea payouts and marks the matching invoices as paid, booking Svea's fees. |
Create InStore orders in SVEA | Creates Svea InStore orders (a Svea Checkout link) from Fortnox orders. |
If your webshop already sends orders to Fortnox (for example through a webshop → Fortnox integration), do not turn on the Orders flow here. Orders would be created twice. In that case, use Export Payouts to Fortnox and, if you need it, Export Refunds to Fortnox.
Card payments are captured later. Svea captures card payments in its own nightly job, so right after the purchase a card payment is still waiting to be captured (CAPTPENDING in Svea). Svea's reconciliation report, which the payout flow reads, only includes captured payments.
Credentials
Go to Get Started → Connect Systems. Connect Fortnox first (you authorise it in Fortnox), then enter your Svea details:
Setting | What to enter |
|---|---|
Merchant ID | Your Svea Merchant ID. You find it in Svea Admin. |
Secret | Your Svea secret word. You find it in Svea Admin. |
Test Mode | Yes sends to Svea in test mode. No for normal use. |
Instore API username / Instore API password | Only if you use InStore orders. Otherwise leave them empty. |
If you don't have the Merchant ID and Secret, ask your Svea contact for exactly those two values. When both systems show a green checkmark, you can start configuring.
Payout booking: Booking Accounting Settings for Settlements
Go to Configure → Settings and open Booking Accounting Settings for Settlements. Add Svea as the payment provider and fill in:
Setting | What to enter |
|---|---|
Payment Method | The payment method (betalsätt) in Fortnox that Svea payouts are booked against. The list comes from Fortnox – if Svea is missing, create it in Fortnox first, then click Clear Cache on the settings page. Required. |
Map Currency with Mode of Payment (if different than (default) Payment Method above) | Optional. Use it only if payouts in a certain currency should use a different payment method. Currencies you don't map use the Payment Method above. |
Account Number Bank Costs | The account for Svea's fee, excluding VAT. Often 6570. Required. |
VAT account for provider fees | Where VAT on Svea's fees is booked. This is input VAT you can deduct. Only used when Svea reports VAT on a fee. Required. |
Account Number for Incoming Tax | Only used when the payout isn't from Sweden. Leave it empty for Swedish payments. |
Account Number for Penny rounding | Small differences between the invoice amount and the paid amount. Often 3740. Required. |
Account Number for Currency Profit / Account Number for Currency Loss | Small differences caused by currency conversion. Often 3960 and 7960. Leave them empty to book these on the penny rounding account instead. |
The account numbers above are common Swedish values, not rules. Confirm every account with whoever does your bookkeeping before you save. Click the ? next to each setting for details.
Without this section, payouts can't be booked in Fortnox.
How payouts are matched to invoices
How a payout is reconciled
From the customer's payment to the right account in your ERP.
Matching relies on the reference saved on the order or invoice when the order was synced. Without the reference the payout cannot be matched.
Each Svea payout lists the payments it contains. For each payment, Junipeer looks for the matching invoice in Fortnox, registers the payment against it and books the fee. To find the invoice, Junipeer compares a reference from the payout with a field on the Fortnox invoice or order. Both sides must hold the same value.
The invoice is marked paid by this payout run, not when the customer pays. Svea Invoice and card orders stay booked but unpaid in Fortnox until the nightly payout that contains them has been matched, usually a day or two after the purchase. Each payout is read once. If the invoice doesn't exist yet or isn't booked when the payout runs, that payment is logged as an error and is not tried again by itself. See Invoice still unpaid after a payout.
General Settings
Setting | What it does |
|---|---|
Payout Reference Field | Which Fortnox field holds the reference – usually where the shop order ID or payment order ID is stored. Required. |
Fallback Payout Reference Field | A second field to look in if the reference isn't found in the first one. Optional. |
Use Payment ID as Payout Reference | Whether to search with the merchant reference or the Payment ID (usually the Svea Order ID). |
Search for the Payout Reference on the Order | Yes looks on the Fortnox order and then finds its invoice. No looks directly on the invoice. |
Book keep invoice payment | Books (bokför) the payment in Fortnox. On by default, and needed if invoices should be marked as paid automatically. |
Fortnox offers these fields:
DocumentNumber (ID)
ExternalInvoiceReference1
ExternalInvoiceReference2
OurReference (not commonly used)
YourOrderNumber (only on invoices – can't be used to search orders)
Use Payment ID as Payout Reference chooses which reference from the payout Junipeer searches for:
No, use payment (merchant) reference (default)
Yes, use Payment (order) ID
Use Payment (order) ID, then (merchant) Reference if not found
Use (merchant) Reference, then Payment (order) ID if not found
Payout settings
Setting | What it does |
|---|---|
Svea Order Reference Manipulation | Cleans up the merchant reference from Svea before it is used – for example removing a prefix, or splitting on |
Use Checkout ID as payout payment reference (Payment ID) | Yes uses the Svea Checkout ID as the Payment ID on payout transactions. No uses the Svea Order ID. |
How to choose the right field
Open a recent invoice in Fortnox that was paid with Svea.
Look at the reference fields and find the one that holds the value Svea sends in its payout – usually the shop order ID.
Set Payout Reference Field to that field.
If the reference on the invoice is Svea's own ID rather than your order number, set Use Payment ID as Payout Reference (and, if needed, Use Checkout ID as payout payment reference (Payment ID)) to match.
If orders reach Fortnox through a different integration, that integration decides which field gets the reference. The payout settings here must point to the same field. Read more in Matching payout references in Fortnox.
Refunds
Export Refunds to Fortnox creates credit invoices. If the original invoice was not created by this integration (for example orders from before you started using Junipeer), set Refund Reference Field and Search Refund Reference on Order so Junipeer can find it. Book keep credit invoices is on by default.
Svea sends a credit as one generic row. The credit invoice therefore has a single row for the credited amount instead of the original order rows, and no stock is returned in Fortnox. If the amount looks wrong, check the credit with Svea.
A credit invoice is only created when Svea has a credit for the order. An order that was cancelled in Svea without a credit gives no credit invoice. Like an invoice, the credit invoice is settled by the payout that contains the refund.
InStore orders (optional)
With Create InStore orders in SVEA, Fortnox orders become Svea InStore orders. Set these under Order Settings:
How do you want to identify your Svea orders? – Payment Method (only orders with a chosen terms of payment) or Include all incoming orders.
Identify Svea Orders by Payment Method – the Fortnox terms of payment that marks an order as a Svea order.
Svea merchant name and Svea terms uri – shown to the customer on Svea Checkout. Required.
Svea minutes until link expires – 20 minutes if left empty, maximum 256320 (180 days).
Defer Svea delivery – Yes stops the order from being delivered automatically in Svea Payment Admin.
Exclude Orders created before this date – older Fortnox orders are skipped.
You also need Instore API username and Instore API password.
Go-live checklist
Fortnox and Svea both show a green checkmark under Connect Systems.
Only the flows you need are turned on – no Orders flow if your webshop already sends orders to Fortnox.
Svea exists as a payment method in Fortnox.
Booking Accounting Settings for Settlements is filled in for Svea, and your bookkeeper has approved the accounts.
Payout Reference Field matches the field your invoices actually use. Check it on a real invoice.
Test Mode is set to No.
Test orders and refunds with a few Svea Order IDs or Checkout IDs in the test panel. Payouts usually can't be tested – watch the first runs in production.
Schedule Export Payouts to Fortnox to run once a day, typically at 23:00.
Contact your Junipeer onboarding contact to review the setup before you go live.
Common pitfalls
"No invoice found" on payouts. Junipeer is looking in the wrong field, the reference format differs (for example a prefix), or the invoice hasn't been created yet. Check Payout Reference Field, Use Payment ID as Payout Reference and Svea Order Reference Manipulation, then re-run the failed payout task.
Orders created twice. The Orders flow is on here and in your webshop integration. Turn it off here.
Refunds created as invoices instead of credit invoices. Contact Junipeer support straight away – the refund mapping must be corrected.
"The payment date cannot precede the invoice date" (Swedish: "Betaldatum kan inte ligga före fakturadatum"). The invoice was dated after Svea registered the payment, for example because it was created on delivery. Running the payout again gives the same error. Register the payment by hand in Fortnox, and make sure invoices are created soon after the payment.
"Invoice … is not booked, cannot add payment". Fortnox only accepts payments on booked invoices. Book the invoice in Fortnox, then re-run the payout task for that date.
Payment method missing in the list. Create it in Fortnox, then click Clear Cache.
Svea turned on in the webshop before Junipeer was set up. Early orders can get the wrong payout references. Always configure Junipeer first.
For more errors, see the Error Codes reference or contact support@junipeer.io.