Data Panda brings your Visma.net 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.
Visma.net is the cloud ERP that Visma launched in 2014 as a white-labelled build on the Acumatica Cloud xRP platform, then extended with its own modules and country localisations. The product covers Financials, Logistics, Project Accounting, HRM and Payroll, with AutoInvoice for e-invoicing across the PEPPOL network and AutoReport for filings to government and pension authorities. The customer base sits in the mid-market across Norway, Sweden, Denmark, Finland and the Netherlands, where Visma already runs the books for over two million customers through its wider portfolio.
The point of pulling Visma.net into a warehouse is not that the ERP cannot draw a report. It is that a Visma.net customer almost always runs Salesforce or HubSpot for the commercial motion, Shopify or BigCommerce for the digital channel, and a country-specific accounting product like E-conomic in Denmark or Twinfield in the Netherlands for a subsidiary the group never moved off. The questions group finance asks sit between those systems and across borders, and they need MOMS, MVA, ALV and btw to line up on the same period. In a warehouse, Visma.net becomes the spine and the rest of the Visma stack stops being a quarterly export exercise.
Visma.net entities in Norway, Sweden, Denmark, Finland and the Netherlands rolled up to one P&L.
Keep Visma.net in sync with the systems sitting around it, without a per-pair add-on.
Use Visma.net history to forecast cash, demand and country-level risk on your own data.
Internal tools on Visma.net data for people who do not need a Visma login.
A list of concrete reports, automations and AI features we have built on Visma.net data. Pick the one that matches your situation.
Where does the group P&L drift between Visma.net countries?
Per-country P&L laid out on a single chart of accounts after FX translation, with intercompany flagged before consolidation. The line where MOMS-coded revenue in Denmark and MVA-coded revenue in Norway diverge from the group rate becomes visible the day after closing, not at year-end.
Which AutoInvoice destinations are silently failing?
AutoInvoice send events, PEPPOL acknowledgements and rejection codes per receiver and country. Surfaces the customer where invoices technically left Visma.net but never reached the buyer's inbox, before the AR controller flags the unpaid invoice as a payment problem.
How does project margin compare to financial margin per entity?
Project Accounting WIP, billed and unbilled hours next to the GL revenue and direct cost on the same period. The gap where the project ledger says profitable and the financial ledger says break-even gets a name, not a vague 'allocations' line.
Group finance teams running Visma.net across two or more Nordic-EU entities. Multi-currency consolidation, MOMS-MVA-ALV-btw reconciliation and intercompany elimination on data already booked in Visma.net, instead of four exports stitched together at month-end.
Country sales leads see pipeline-to-order-to-revenue timing per entity, with Salesforce or HubSpot opportunities tied back to Visma.net invoices. The forecast gets checked against AutoInvoice-routed revenue, not against optimistic CRM stages.
Operations leads running cross-Nordic logistics get one stock and fulfilment view across Visma.net warehouses. Carrier cost from Sendcloud and stock level per country sit beside project margin and supplier reliability in one timeline.
Closed-won Salesforce opportunities drop into Visma.net as sales orders in the right country tenant, with customer, item and pricing mapped to the local entity. Order status, AutoInvoice send and payment flow back to the opportunity, so sales and group finance see the same cycle from closed-won to cleared cash, instead of arguing across two reports.
Shopify orders land in the right Visma.net tenant as sales orders with items, pricing and tax handled per country, plus the matching stock movements in the local warehouse. Refunds post as credit notes. The DTC channel sits in the same group P&L as the rest of the business and stock stays in one ledger.
Closed-won HubSpot deals create or update customers in the right Visma.net entity and prepare draft sales orders with the local tax code. AutoInvoice send status and payment date flow back onto the HubSpot record, so sales sees the actual money cycle on the deal they sold, not a stale stage.
Sendcloud shipping labels and carrier invoices land in the right Visma.net tenant as supplier entries, allocated to the order or project they belong to. Logistics cost per Nordic order shows up in the same view as the gross margin on that order, instead of arriving as a quarterly carrier-statement surprise.
You keep the reporting tool you already have. We connect it to the warehouse where your Visma.net 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.
Visma.net launched in 2014 as a white-labelled build on the Acumatica Cloud xRP platform and Visma extended it with its own modules and country localisations. For the warehouse, the practical effect is that the underlying data model has clean object boundaries (GL, AR, AP, sales orders, purchase orders, inventory, projects, employees, time, expense), so first-class tables come across cleanly per country tenant.
Each Visma.net tenant lands in its own schema in the warehouse with a shared customer, supplier, item and project dimension on top. Group finance gets per-entity reporting plus a consolidated view, with the chart of accounts aligned once and FX translation applied per period.
We review your Visma.net setup and the systems around it. Together we pick the first thing worth building.