Data Panda brings your Tripletex data together with the data from the rest of your business. From one place, we turn it into dashboards, automations, AI workflows and custom apps your team uses every day.
Tripletex started in Oslo in 2002 as a cloud time-tracking and project tool, added bookkeeping and invoicing in 2006, and grew into one of the dominant accounting platforms for Norwegian SMBs. Visma bought the company in 2016, ran it as a standalone brand within the Visma group and saw the customer base grow past 150,000 since the acquisition. The product covers bookkeeping (bokforing), invoicing (faktura), payroll (lonn), time tracking (timeregistrering), expense reports, project accounting and inventory.
The localisation is the reason a Norwegian entity uses Tripletex instead of Exact Online or Yuki: Norwegian VAT (MVA), the A-melding payroll reporting flow to Skatteetaten, automatic bank reconciliation against Norwegian bank feeds and project accounting tuned to how Norwegian firms run hourly work. For a Belgian group with a Norwegian subsidiary, that depth is exactly what makes Tripletex hard to consolidate by hand. The books close cleanly in Oslo, but group reporting in Brussels waits on a monthly export, FX is handled twice and intercompany lines drift. The warehouse is where Tripletex sits next to the Benelux books and the commercial stack, and the group P&L stops being a manual merge.
Consolidated P&L across the Norwegian Tripletex entity and the Benelux books, with FX, MVA and project margin handled.
Let the commercial stack post into the right Tripletex ledger without keying twice.
Use Tripletex history to score risk, classify project hours and forecast cash across entities.
Internal tools on Tripletex data for group finance and the Norwegian entity manager.
A list of concrete reports, automations and AI features we have built on Tripletex data. Pick the one that matches your situation.
How does the Norwegian entity look on the same group P&L as Belgium?
Tripletex lands in the warehouse next to Exact Online or Yuki, with FX translated and the chart of accounts mapped. Consolidation becomes a view that is ready the day the local books close, not a monthly export from Oslo that the Brussels controller has to re-key.
Are MVA codes consistent between Tripletex and the Benelux books?
Norwegian VAT codes from Tripletex are mapped against the Belgian and Dutch btw codes used in Exact Online or Yuki. Drift between entities (a Norwegian reverse-charge that lands as standard btw in the group view, for instance) is flagged before it becomes a year-end correction.
Can we see Tripletex project hours next to project revenue?
Tripletex timeregistrering, project costs and project invoices come into the warehouse with the same project ID, so margin per project shows up in one view across the Norwegian entity and the rest of the group, instead of three exports stitched together at month-end.
Group consolidation across Tripletex, Exact Online and Yuki updated daily, with intercompany, FX and MVA handled. Month-end becomes a review, not a merge with an Oslo export.
AR visibility per entity and per account before offering new credit cross-border. A deal in the Norwegian entity is judged on the same customer-payment behaviour visible in the Benelux books.
Norwegian payroll, project hours and cost-centre data on the same timeline as the Benelux operations. Shared-services finance stops guessing why the Nordic numbers drift.
Shopify orders shipping to Norway land in Tripletex as sales journal entries with MVA handled per rate, while orders shipping to Benelux post to Exact Online or Yuki. Refunds flow back as credit notes in the right book. The Nordic webshop revenue stops needing a weekly export to the Oslo accountant.
Stripe payouts in NOK and EUR are booked per Tripletex entity, fees split out and the underlying charges matched to the Tripletex invoices they paid. The bank reconciliation screen stops showing multi-currency Stripe lumps that the Norwegian controller has to split by hand.
Closed-won HubSpot deals create or update customers in the Norwegian Tripletex entity and prepare draft invoices with the right MVA coding. Sales sees Tripletex payment history on the HubSpot record before offering net-30 to a Norwegian account that already pays late.
Sendcloud shipping labels and carrier invoices for Norwegian deliveries land in Tripletex as supplier entries, allocated to the order or project they belong to. Logistics cost per Norwegian order shows up in the same view as the gross margin on that order, instead of arriving as a quarterly carrier-statement surprise.
These are the 17 tables we currently pull from Tripletex into your warehouse. Query them directly in SQL, join them to the rest of your stack, or build reports on top.
Missing a table you need? We can extend the sync. Tell us what is missing and we will build it for you.
You keep the reporting tool you already have. We connect it to the warehouse where your Tripletex data lives.
OAuth authentication. Read-only by default. We sign a DPA and your admin keeps the keys.
Data flows into your warehouse on your schedule. Near real time or nightly, your call. You own the data.
We build the first dashboard, workflow or AI feature with you, then hand over the keys. Or we stay on for ongoing delivery.
We set up the foundation. Your team builds on top.
Best fit Teams that already have a BI analyst or data engineer and want to own the build.
We build the whole thing, end to end.
Best fit Teams without in-house BI or dev capacity. You tell us what you need and we deliver it.
You do. It lands in your warehouse, on your cloud account. We don't resell or aggregate it. If you stop working with us, the warehouse stays yours and keeps running.
Near real time for most operational systems. For heavier sources we schedule hourly or nightly. You pick based on what the reports need.
No. If you don't have one, we help you pick one and set it up as part of the first delivery. Common starting points are Snowflake, Microsoft Fabric, or a small Postgres start.
Yes. Tripletex publishes a REST API covering customers, invoices, vouchers, accounts, projects, hours and payroll. We connect per Tripletex company with a token and pull each domain on a schedule, so the warehouse has yesterday's books available the moment finance walks in.
Yes. MVA codes, rates and reverse-charge indicators come across on every voucher, so input and output VAT can be totalled per period and per rate. That makes the Skatteetaten return preparation a report instead of a re-coding exercise, and lets the group view spot drift between Norwegian and Benelux btw treatment.
Yes. Project headers, project hours and project-tagged invoices arrive in the warehouse with the same project ID, which is what makes margin per project visible alongside the booked revenue and cost rather than as a separate Tripletex report.
We review your Tripletex setup and the systems around it. Together we pick the first thing worth building.