Data Panda brings your Visma E-conomic 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.
E-conomic was founded in Copenhagen in 2001 and built a steady following with Danish SMBs and accounting firms long before being acquired by Norwegian SaaS group Visma in 2018. Inside the Visma portfolio it now sits next to Visma eAccounting for Sweden and Norway, Visma.net for multi-country ERP and a long list of regional finance products. The Danish customer base, the MOMS-aware fiscal logic and the App Market of third-party extensions stayed in place under Visma ownership, which is why the connector is still called E-conomic on the front of the box.
For a Belgian group with a Danish entity, Visma E-conomic plays the role Exact Online or Yuki plays here. The point of pulling it into a warehouse is the same: the books are great at closing the period and not built to answer cross-system or cross-country questions. Group margin per customer, MOMS versus Belgian btw alignment, DSO across the Danish and Benelux entities, and cash forecasts that span more than one Visma product all sit between systems. The warehouse is where they meet.
Danish books, Benelux books and the rest of the Visma stack rolled up to one P&L.
Push and pull invoices, payments and masters between E-conomic and the rest of the stack.
Put your Danish payment history and MOMS-coded ledger behind AI that helps finance forecast.
Small finance tools on top of E-conomic data for people who should not need a Visma login.
A list of concrete reports, automations and AI features we have built on Visma E-conomic data. Pick the one that matches your situation.
How does the Danish entity perform inside the group?
Group P&L with the Danish entity on its own line, gross margin per customer aligned across MOMS-coded and btw-coded books. Replaces the quarterly export-and-mail-around with a number that updates the day after closing.
Are MOMS and btw being filed on the same revenue twice?
Cross-entity reconciliation between E-conomic and the Belgian or Dutch ledger that catches inter-company invoices booked on both sides without elimination. The number that should be zero shows up before the auditor finds it.
Which Danish customers are slipping into late payment?
Twelve-month DSO trend per Danish account, ranked by how much the customer's own average has worsened. Surfaces the account that is starting to drift while the absolute number still looks acceptable.
Group finance teams running a Danish entity on E-conomic and the rest of the books somewhere else. MOMS preparation, group consolidation and inter-company elimination on data that is already booked, instead of three exports stitched together at month-end.
Account managers selling into Danish customers see MOMS-coded receivables history before extending new credit, in the same view as their Benelux pipeline. The Danish number stops being a quarterly mystery.
Operations leads running cross-border supply or service get one cost-to-serve view across the Danish and Benelux books. Danish supplier concentration, payment terms and project margin show up beside the rest of the group's data.
A Danish webshop running on Shopify lands its orders, refunds and payouts in E-conomic with MOMS split out and the bank reconciliation already prepared. The Danish controller stops keeping a parallel spreadsheet for the webshop's MOMS coding.
Stripe payouts hit E-conomic as bank entries with fees split out and the underlying charges matched to invoices, in DKK or in the original transaction currency. The bank reconciliation screen stops showing aggregate Stripe lumps that someone has to pull apart by hand.
Closed-won HubSpot deals on Danish customers create or update contacts in E-conomic and prepare draft invoices with the right MOMS code and ledger account. Sales sees E-conomic payment history on the HubSpot record before they offer terms again.
Sendcloud shipping labels and carrier invoices land in E-conomic as supplier entries, allocated to the order or project they belong to. Logistics cost per Danish 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 24 tables we currently pull from Visma E-conomic 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 Visma E-conomic 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. MOMS codes, rates and reverse-charge indicators come across on every journal entry, so input and output MOMS can be totalled per period and per rate. The warehouse prepares the totals; the legally binding filing still goes through E-conomic and the Danish tax authority.
We connect E-conomic per agreement and other Visma products such as Visma.net or Visma eAccounting through their own connectors where available. At warehouse level the chart of accounts is aligned so a group P&L can roll up across Visma entities and any non-Visma ledgers.
No. App Market extensions stay in place for in-product workflows. The warehouse sits next to E-conomic for cross-system reporting, automation and AI; we do not push UI changes back into the E-conomic application.
We review your Visma E-conomic setup and the systems around it. Together we pick the first thing worth building.