Junipeer settlement reconciliation
Connect Junipeer so Kustom settlement payouts reconcile automatically against the invoices in Fortnox, Visma or Business Central, with Kustom's fees written off — a payout-only integration that never syncs orders.
Junipeer is an integration platform that connects Kustom Checkout to your accounting or ERP system and reconciles your Kustom settlement payouts into it. Each payout line is matched against the corresponding invoice in your books and Kustom’s fees are written off, so settlements reconcile without manual matching. This is a settlement-side integration only: orders and invoices reach your accounting system through your existing store or ERP setup, and Junipeer never syncs them, so it can’t create duplicate records.
Before you start
Section titled “Before you start”You need:
- A Kustom Checkout account with settlement API credentials generated in the Kustom Merchant Portal, or supplied by your Kustom representative.
- A Junipeer account at app.junipeer.io.
- A supported accounting or ERP system — Fortnox, Visma, Business Central and others — that you can authorize over OAuth.
- Orders and invoices already flowing into that accounting system. Junipeer matches payouts against invoices that are already there. If they aren’t, there’s nothing to reconcile.
- The account numbers your bookkeeping uses for Kustom payouts, bank costs and outgoing tax. Your accountant will know them.
Step by step
Section titled “Step by step”1. Get your Kustom settlement API credentials
Section titled “1. Get your Kustom settlement API credentials”From the Kustom Merchant Portal, collect:
- The settlements API URL
- The API user or ID
- The API password or secret
2. Enable the Payouts flow in Junipeer
Section titled “2. Enable the Payouts flow in Junipeer”In the Junipeer app, go to Get Started → Select Flows and enable Payouts. That’s the only flow the Kustom integration uses.
3. Connect both systems
Section titled “3. Connect both systems”Go to Get Started → Connect Systems.
- Your accounting system. Authorize over OAuth. A green checkmark confirms it. Prepare the system first — for Fortnox, follow Junipeer’s Fortnox preparation guide before connecting.
- Kustom. Enter the three values from step 1.
In the Junipeer app, the Kustom fields are labelled with Klarna names — Klarna settlements API URL, Klarna API user/ID, Klarna API password. That’s legacy labelling in Junipeer’s own UI from before the rename. Put each Kustom value into the matching Klarna-named field. They are the same fields.
If you trade in several markets and hold more than one set of credentials, Junipeer can store several Kustom configurations.
Both systems must show a green checkmark before you configure.
4. Map the settlement accounts
Section titled “4. Map the settlement accounts”Go to Configure → Settings. Anything marked “This setting is required and must be saved” is mandatory.
Under Configure → Settings → Booking Accounting / Settlements, map Kustom’s payment methods to your account numbers. You need the account Kustom payouts land in — your bank account or an interim account — plus account numbers for bank costs and outgoing tax.
Without this mapping, payouts will not book correctly. This is the step to get right.
5. Set the general settings
Section titled “5. Set the general settings”Under Configure → Settings → General Settings, this is the recommended starting point for a standard Kustom and Fortnox payout setup:
| Setting | Recommended value |
|---|---|
| Payout Reference Field | ExternalInvoiceReference1 |
| Fallback Payout Reference Field | leave empty |
| Use Payment ID as Payout Reference | No — use the payment (merchant) reference |
| Search for the Payout Reference on the Order | Off — search on the invoice |
| Book keep invoice payment | Off, unless you want Junipeer to pay the invoice automatically |
6. Schedule the sync
Section titled “6. Schedule the sync”Set the payout sync schedule in the Junipeer app. Running it at 23:00 is typical, so each day’s Kustom settlements are processed overnight.
Check that it works
Section titled “Check that it works”Payouts can’t be tested in advance — the schedule runs against production data, so the first real sync is the test. After it runs:
- Check that your Kustom payouts have booked against the right invoices.
- Check that Kustom’s fees have been written off as expected.
- Check the payout account, bank cost account and outgoing tax account each received what you mapped them to.
- Contact your Junipeer onboarding contact to review the setup before you rely on it unsupervised.
Until you’ve done this once successfully, keep reconciling manually in parallel.
Variations
Section titled “Variations”Several markets, several credential sets
Section titled “Several markets, several credential sets”Kustom issues settlement credentials per market. Junipeer holds multiple Kustom configurations, so add one per credential set rather than trying to make one configuration serve two markets.
Troubleshooting
Section titled “Troubleshooting”Payouts book to the wrong account, or not at all. The settlement account mapping in step 4 is missing or points at the wrong account numbers.
Payouts don’t match any invoice. The payout reference field is looking in the wrong place.
Confirm ExternalInvoiceReference1 is the field your invoices actually carry the merchant
reference in, and that the search is set to run against the invoice rather than the order.
Nothing syncs at all. Check both connections still show green — an OAuth authorization to the accounting system can expire — and that the schedule is enabled.
For Junipeer questions, contact support@junipeer.io. For questions about the settlement data
itself, contact support@kustom.co.
Related
Section titled “Related”- Settlements — what a Kustom payout contains and when it arrives
- Refunds — how refunds appear in a settlement
- Authentication and environments — how Portal credentials work generally
- Platform catalogue — the e-commerce platforms and other partner integrations
This page is also available as Markdown — append .md to its URL — and is indexed in llms.txt.