Connecting Tripletex to Understory means every booking, refund and gift card is bookkept for you. Understory creates a sales document for each sale, moves the revenue to the date the experience is actually delivered, and attaches the guest's receipt — so your ledger matches what happened without anyone typing it in.
The Tripletex integration is in private beta, which means you have to contact us to have it activated on your account.
Before you start
A few things have to be in place in Tripletex first. Most are one-off, and your accountant will recognise all of them.
1. Create an API token
Understory needs an employee token to act on your behalf. You cannot connect without one.
In Tripletex, go to Innstillinger → Vår API — the API settings page opens
Open "Mine API-tokens" — your existing tokens are listed here
Create a new token for Understory — give it a name you will recognise later
Copy the token — you will paste it into Understory in a moment
The token needs permission to create customers, products, invoices and vouchers. A narrower token connects successfully and then fails when the first booking arrives, which is harder to spot.
If you would like Understory's settlement vouchers to arrive as drafts for you to review rather than being posted straight away, the token also needs the Advanced Voucher permission.
2. Complete your company details
Tripletex refuses to create any invoice until both of these are registered:
Your organisation number — under Innstillinger → Selskap
A company bank account — under Innstillinger → Selskap → Bankkontoer
Either one missing stops every booking from reaching your accounts. If one is, Understory tells you which on the setup page.
3. Agree your accounts with your accountant
Understory books each sale when it is paid and moves the revenue to the date the experience is delivered. That needs:
What it is for | Usually already in your chart |
Sales, credited when the booking is paid | Yes |
Deferred income — the balance side | Yes |
Deferred income — the result side | Sometimes |
Revenue recognised at delivery | Sometimes |
Settlement account, one per payment provider | No — usually created |
Norwegian charts vary, so ask your accountant which existing accounts to use and to create anything missing.
One note for them on the settlement account: it holds money the payment provider owes you but has not paid out yet. Give it its own purpose-named account, do not use your real bank account, and do not flag it as a bank account — otherwise it is pulled into your bank reconciliation.
4. Create a payment type per provider
One payment type for each payment provider, each pointing at that provider's settlement account. These can only be created in Tripletex.
Each one must be set to show on orders. This is the setting that catches people out: a payment type without it looks completely normal in Tripletex, but Understory cannot see it at all and you will not be able to select it during setup.
5. Check you have a manual voucher type
Understory posts some entries as manual vouchers, so you need a voucher type suitable for that — often called Manuelt bilag. Not every Tripletex account has one. Some have only document-driven types such as Utgående faktura or Betaling, and a manual voucher cannot be posted under those.
How to connect
Requirements: the integration activated on your account, and your API token from step 1.
Click Accounting in the main menu — the accounting area opens on the Overview tab
Open the Settings tab — your accounting integrations are listed here
Click Add integration and choose Tripletex — the connect dialog opens
Paste your Employee API access token — this is the token you created in Tripletex
Click Connect Tripletex — you are sent to Understory to approve access
Approve the access request — you are returned to the Tripletex setup page
Finish the setup
The setup page is where you tell Understory which of your accounts to use. Nothing is sent to Tripletex until this is saved.
Choose your voucher type — Understory suggests one, but check the suggestion looks right rather than assuming it matched
Map your VAT rates to Tripletex VAT codes — see the note below
Choose your revenue and deferred income accounts — the ones you agreed with your accountant
Choose a payment type and settlement account per payment provider — from the payment types you created
Save — bookings start flowing from the next sale
On VAT codes: this is not a free choice. Each revenue account in Tripletex is locked to a particular VAT code, and the code you pick has to match the account you are booking to — Tripletex rejects the posting outright if they disagree. If your business is exempt from VAT, map your 0% rate to the code your revenue account actually uses, which may not be the one that simply looks like zero.
What lands in Tripletex
When a booking is paid, Understory creates a sales document for the order, itemised by what was sold, and marks it paid. The document is not sent to your guest — they already have their receipt from Understory. The revenue is held as deferred income, because the experience has not happened yet.
When the experience is delivered, Understory moves that revenue out of deferred income and into your revenue account, dated to the end of the experience. This is what makes each month's revenue reflect what you actually delivered that month.
When you refund a booking, Understory creates a credit note against the original document and settles it.
Gift cards work differently, and correctly so: buying one is an advance payment rather than a sale, so it is booked to a liability account. It becomes revenue when the gift card is redeemed against a booking.
Receipts are attached. The guest's receipt and the Understory platform-fee document are attached to the voucher in Tripletex, so your accountant has the underlying documentation without going looking for it.
If something stops working
Under Accounting, the Settings tab shows the state of the connection, and the Activity tab shows each booking as it is sent, with the reason if any of them fail. The Reconciliation tab shows how your Understory figures line up period by period.
The most common causes are a missing organisation number or company bank account, a VAT code that does not match the account it is booking to, or a token whose permissions are too narrow. All three are shown to you rather than failing silently.
Did this answer your question? If not, please reach out to us in the chat window at the bottom to the right, and we'll be happy to help 🤗