This guide is for shop and finance staff connecting Walley to Fortnox through Junipeer. It covers the flows, the connection, how payouts are booked and matched, and what to check before going live.
Work through Connecting payment services to Junipeer first. It covers the steps every payment provider shares. This guide covers what is specific to Walley and Fortnox.
What the integration does
The Walley ↔ Fortnox integration has three flows. All read from Walley and write to Fortnox.
Flow | What it does |
|---|---|
Export Invoices to Fortnox | Creates invoices in Fortnox from Walley. Can run on a schedule or by webhook. |
Export Refunds to Fortnox | Creates credit invoices in Fortnox for refunds made in Walley. |
Export Payouts to Fortnox | Reads Walley payouts, matches each transaction to its Fortnox invoice, marks the invoice as paid and books the fees. |
Choose your flows carefully. If your orders already reach Fortnox through a webshop integration (for example Shopify, Centra or WooCommerce), don't create the same sales again from Walley — you would get duplicates. In that case, limit this integration to Export Payouts to Fortnox (and refunds only if your webshop integration does not already handle them). When in doubt, ask your Junipeer onboarding contact.
Before you start
Fortnox is prepared: an integration user, currencies, VAT rates and a payment method for Walley. See Prepare Fortnox for integration.
You can log in to Walley and create an API key.
You know which Fortnox accounts to use for fees, VAT on fees and rounding. Ask your bookkeeper.
Connecting Walley and Fortnox
In the Junipeer app, go to Get Started → Connect Systems. Connect Fortnox by clicking the Fortnox button and logging in. Then fill in the Walley fields:
Field | What to enter |
|---|---|
Client ID | Create it in Walley: profile icon → Manage Organization → Create New → Api Key. Choose unlimited. |
Client Secret | Shown when you create the API key. Copy it right away and paste it here. It is stored as a secret. |
Test mode | No (default) for your live Walley account. Yes only if you are connecting to Walley's test environment. |
All three are required. When both systems show a green checkmark, you are ready to configure.
Invoices
Export Invoices to Fortnox has these settings under Invoice Settings:
Setting | What it does |
|---|---|
Mark order as Warehouse Ready / Delivered before creating invoice | Marks the order as delivered before the invoice is created. Needed when you use the warehouse module in Fortnox. |
Automatically mark Invoices as Paid | Advanced. Marks invoices as paid right away instead of waiting for the payout. Usually leave this off when you use the payouts flow, so that the payout marks the invoice as paid. |
Specify the methods that we should consider the order paid AND automatically mark as paid the invoice (if the above setting is enabled) | Advanced. Connects the Walley payment method to a Fortnox mode of payment. Only invoices with a mapped method are marked as paid. |
Refunds
Export Refunds to Fortnox creates a credit invoice in Fortnox when a refund is made in Walley. These settings are advanced:
Setting | What it does |
|---|---|
Book keep credit invoices | Default Yes. Books (bokför) the credit invoice in Fortnox. |
Send credit invoices | Default No. Yes sends the credit invoice to the customer with the customer's delivery method in Fortnox. |
Refund Reference Field | Which Fortnox field Junipeer uses to find the original invoice, when that invoice or order was not created by this integration — for example orders from before you started using Junipeer. |
Search Refund Reference on Order | Yes looks for the original order and credits its invoice. No looks directly for the invoice. |
The refunds flow also shows Automatically mark Invoices as Paid and the matching payment-method list, described under the invoices flow above.
Booking settings for payouts
Open Configure → Settings and find Booking Accounting Settings for Settlements. Add Walley as the payment provider and fill in the accounts below. This decides how each payout is booked in Fortnox. Without it, payouts will not book correctly.
The account numbers below are the usual Swedish examples shown in the app. Confirm every account with your bookkeeper before you save — your chart of accounts may differ.
Setting | What to enter |
|---|---|
Payment Method | The payment method (betalsätt) in Fortnox for Walley. Required. The list is read from Fortnox — if Walley is missing, add it in Fortnox first. |
Map Currency with Mode of Payment (if different than (default) Payment Method above) | Optional (advanced). Use a different Fortnox payment method for payouts in a certain currency, for example EUR payouts that go to a separate EUR account. Currencies you don't map use the Payment Method above. |
Account Number Bank Costs | The account for Walley's fee, excluding tax. Required. The app suggests 6570. |
VAT account for provider fees | Where VAT on Walley's fees is booked. This is input VAT you can deduct. Required. Only used when Walley reports VAT on a fee. The app suggests 2641 in Sweden. |
Account Number for Incoming Tax | Only used when the payout isn't from Sweden. Leave empty for Swedish payments. |
Account Number for Penny rounding | Small differences between the invoice amount and the paid amount. Required. The app suggests 3740. |
Account Number for Currency Profit | Optional. Small differences caused by currency conversion that give a profit. The app suggests 3960. Leave empty to use the penny rounding account for both profit and loss. |
Account Number for Currency Loss | Optional. The same for a loss. The app suggests 7960. |
Click the ? next to each setting in the app for more details.
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.
When Walley pays out, Junipeer reads the payout and finds the Fortnox invoice for each transaction. Matched invoices are marked as paid, and the fees are booked to the accounts you set above.
To find the right invoice, Junipeer takes a reference from the payout and searches for it in a field on the Fortnox invoice (or order). You decide where it looks under General Settings:
Setting | What it does |
|---|---|
Payout Reference Field | Required. The Fortnox field that holds the reference, usually the shop order ID or the payment order ID. In many setups this is ExternalInvoiceReference1. Open a recent invoice in Fortnox to see which field holds the order reference. |
Fallback Payout Reference Field | Optional (advanced). A second field to try if the reference isn't found in the first one, for example ExternalInvoiceReference2. |
Use Payment ID as Payout Reference | Optional (advanced). By default Junipeer searches for the merchant reference (usually your order number). Choose this to search for the payment ID instead (usually the Walley order ID), or to try one and then the other. Pick what is actually stored in your Payout Reference Field. |
Search for the Payout Reference on the Order | Optional (advanced). Yes searches on the Fortnox order and then finds its invoice. No searches directly on the invoice. |
Book keep invoice payment | Optional (advanced), default Yes. Books (bokför) the payments Junipeer creates from payouts. Keep it on Yes if invoices should be marked as paid automatically. |
Read more in Matching payout references in Fortnox and Payout reconciliation.
Going live
Payouts are usually not something you can test in advance. The scheduled run must run in production, and you should check the results after each run.
Fortnox is connected and prepared, including a payment method for Walley.
Client ID and Client Secret are filled in, Test mode is No, and the connection shows a green checkmark.
Only the flows you need are on. Don't create invoices or refunds from Walley if your webshop integration already does.
Booking Accounting Settings for Settlements is filled in for Walley, and your bookkeeper has confirmed the accounts.
Payout Reference Field matches the field the order reference is stored in. Check one recent Fortnox invoice.
If you use the invoices or refunds flows, test one or two with the test panel first.
Schedule Export Payouts to Fortnox. Payouts are usually run once a day, for example at 23:00.
Contact your Junipeer onboarding contact to review the setup before you go live.
After the first payouts, check in Fortnox that invoices are marked as paid and that fees are booked to the right accounts.
Common pitfalls
Lost Client Secret. It is only shown when you create the API key. If you didn't copy it, create a new API key in Walley.
Test mode left on. With Test mode set to Yes, Junipeer talks to Walley's test environment and will not see your live data.
Refund amount counted twice. In some setups a refund is applied once as a negative payout line and once as a refund, so the invoice shows twice the refund. Contact Junipeer support with the order and payout IDs.
Invoices marked as paid too early. If Automatically mark Invoices as Paid is on, invoices are paid at creation, not when Walley pays out.
"No invoice found" on a payout. Usually the Payout Reference Field points to a field that is empty or holds a different reference than the payout carries. Open the failing task in the logs, note the reference, and check which Fortnox field holds it. The invoice may also not exist yet, if the payout arrived before the order was synced.
The payment method is missing from the list. Create it in Fortnox first, then click Clear Cache on the settings page.
Payment date before invoice date. Fortnox can reject a payment dated before the invoice. See Error codes.
Invoices in another currency than the payout. This gives "Unsupported currency combination". If you sell in several currencies, contact Junipeer support to set it up.
New payment provider switched on in the webshop before Junipeer was configured. Payouts for those early orders can get wrong references. Configure Junipeer first. If it already happened, contact support.