Use your Visma E-conomic data for reporting, automation and AI.

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.

Data Panda Reporting Automation AI Apps
Visma E-conomic logo

Where Danish SMBs keep their books.

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.

What you get once Visma E-conomic is connected.

Group reporting across Visma

Danish books, Benelux books and the rest of the Visma stack rolled up to one P&L.

  • Group P&L across E-conomic, Exact, Yuki and other ledgers
  • MOMS and btw side by side, per period
  • Gross margin per customer, even when invoicing entity differs from selling entity

Cross-border ledger automation

Push and pull invoices, payments and masters between E-conomic and the rest of the stack.

  • Operational invoices into E-conomic with the right MOMS code
  • Customer master sync between E-conomic and the group CRM
  • Inter-company billing reconciled across Visma entities

AI workflows on Nordic books

Put your Danish payment history and MOMS-coded ledger behind AI that helps finance forecast.

  • Credit risk scoring on Danish customer payment behaviour
  • AI-assisted MOMS coding and journal classification
  • Cash forecasting that respects Danish payment terms and holiday calendars

Custom apps on your Nordic data

Small finance tools on top of E-conomic data for people who should not need a Visma login.

  • Group receivables portal that includes the Danish entity
  • MOMS preparation app with audit trail back to E-conomic
  • Self-service budget-versus-actual for the Danish controller

Use cases we deliver with Visma E-conomic data.

A list of concrete reports, automations and AI features we have built on Visma E-conomic data. Pick the one that matches your situation.

MOMS preparationDanish VAT totals per period and per rate, ready for review.
AR aging (Denmark)Open Danish receivables per customer, by bucket.
Group consolidationDanish entity rolled into the group P&L on closing day.
Inter-Visma reconciliationE-conomic against eAccounting or Visma.net, period by period.
DSO trendDays sales outstanding for Danish customers, twelve-month view.
Gross margin per customerRevenue net of credit notes against direct cost, per customer.
Cash forecastDanish receivable aging plus recurring revenue, thirteen weeks out.
Late-payer listDanish accounts ranked by exposure and slippage versus terms.
Project profitabilityJournal totals per project or department, per quarter.
Inter-company billingVisma group invoices flagged, matched and reconciled.
Budget versus actualDanish actuals against group budget, per cost centre.

Answers you will finally get.

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.

Where each function gets value.

For finance leaders

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.

For sales leaders

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.

For operations

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.

What you can automate with Visma E-conomic.

Pair with Shopify

Reconcile Shopify orders with E-conomic invoices

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.

Pair with Stripe

Reconcile Stripe payouts in E-conomic

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.

Pair with HubSpot

Sync HubSpot deals into E-conomic invoices

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.

Pair with SendCloud

Match Sendcloud shipments to E-conomic costs

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.

Want more information about this connector?

I'm interested in this connector

Available Visma E-conomic data.

Visma E-conomic data covers 24 available tables across the supported connection options. The exact selection depends on your connection and access rights. Use the data in reports, combine it with the rest of your stack, or query it directly in your warehouse.

The tables at the top of the list open up to show their columns and data types.

  • Customers 38 columns
    • Ean String
    • Zip String
    • City String
    • Name String
    • Email String
    • Barred Boolean
    • Address String
    • Balance Number
    • Country String
    • PNumber String
    • Website String
    • Contacts String
    • Currency String
    • DueAmount Number
    • VatNumber String
    • CreditLimit Number
    • LastUpdated Date & time
    • MobilePhone String
    • Totals_booked String
    • Totals_drafts String
    • CustomerNumber Integer
    • Invoices_booked String
    • Invoices_drafts String
    • DeliveryLocations String
    • PublicEntryNumber String
    • Templates_invoice String
    • Layout_layoutNumber Integer
    • TelephoneAndFaxNumber String
    • Templates_invoiceLine String
    • VatZone_vatZoneNumber Integer
    • SalesPerson_employeeNumber Integer
    • EInvoicingDisabledByDefault Boolean
    • CorporateIdentificationNumber String
    • Attention_customerContactNumber Integer
    • PaymentTerms_paymentTermsNumber Integer
    • CustomerGroup_customerGroupNumber Integer
    • CustomerContact_customerContactNumber Integer
    • DefaultDeliveryLocation_deliveryLocationNumber Integer
  • Orders Sent 49 columns
    • Date Date & time
    • DueDate Date & time
    • Currency String
    • NetAmount Number
    • VatAmount Number
    • GrossAmount Number
    • LastUpdated Date & time
    • OrderNumber Integer
    • Delivery_zip String
    • ExchangeRate Number
    • Pdf_download String
    • Delivery_city String
    • Notes_heading String
    • Recipient_cvr String
    • Recipient_ean String
    • Recipient_zip String
    • Recipient_city String
    • Recipient_name String
    • RoundingAmount Number
    • Notes_textLine1 String
    • Notes_textLine2 String
    • Delivery_address String
    • Delivery_country String
    • MarginPercentage Number
    • References_other String
    • PaymentTerms_name String
    • Recipient_address String
    • Recipient_country String
    • Soap_orderHandle_id Integer
    • MarginInBaseCurrency Number
    • Delivery_deliveryDate Date & time
    • Project_projectNumber Integer
    • Delivery_deliveryTerms String
    • CostPriceInBaseCurrency Number
    • Customer_customerNumber Integer
    • NetAmountInBaseCurrency Number
    • GrossAmountInBaseCurrency Number
    • PaymentTerms_daysOfCredit Integer
    • Recipient_publicEntryNumber String
    • PaymentTerms_paymentTermsType String
    • Templates_upgradeInstructions String
    • PaymentTerms_paymentTermsNumber Integer
    • Recipient_vatZone_vatZoneNumber Integer
    • References_salesPerson_employeeNumber Integer
    • DeliveryLocation_deliveryLocationNumber Integer
    • Recipient_attention_customerContactNumber Integer
    • References_vendorReference_employeeNumber Integer
    • References_customerContact_customerContactNumber Integer
    • References_customerContact_customer_customerNumber Integer
  • Invoices Sent 9 columns
    • Id Integer
    • SendBy String
    • Status String
    • CreatedBy String
    • CreationDate Date & time
    • Recipient_ean String
    • Recipient_name String
    • Recipient_mobilePhone String
    • Invoice_bookedInvoiceNumber Integer
  • Products
  • Journals 12 columns
    • Name String
    • Entries String
    • Vouchers String
    • JournalNumber Integer
    • Templates_financeVoucher String
    • Settings_entryTypeRestrictedTo String
    • Templates_manualCustomerInvoice String
    • Settings_voucherNumbers_maximumVoucherNumber Integer
    • Settings_voucherNumbers_minimumVoucherNumber Integer
    • Settings_contraAccounts_financeVouchers_accountNumber Integer
    • Settings_contraAccounts_customerPayments_accountNumber Integer
    • Settings_contraAccounts_supplierPayments_accountNumber Integer
  • Accounts 13 columns
    • Name String
    • Barred Boolean
    • Balance Number
    • AccountType String
    • DebitCredit String
    • DraftBalance Number
    • AccountNumber Integer
    • AccountsSummed Array
    • AccountingYears String
    • BlockDirectEntries Boolean
    • VatAccount_vatCode String
    • ContraAccount_accountNumber Integer
    • TotalFromAccount_accountNumber Integer
  • Customer Groups 13 columns
    • Name String
    • Customers String
    • Layout_name String
    • Account_name String
    • Layout_deleted Boolean
    • Account_balance Number
    • Account_accountType String
    • Account_debitCredit String
    • CustomerGroupNumber Integer
    • Layout_layoutNumber Integer
    • Account_accountNumber Integer
    • Account_accountingYears String
    • Account_blockDirectEntries Boolean
  • Invoices Paid 45 columns
    • Date Date & time
    • Sent String
    • DueDate Date & time
    • Currency String
    • NetAmount Number
    • Remainder Number
    • VatAmount Number
    • GrossAmount Number
    • Delivery_zip String
    • Pdf_download String
    • Delivery_city String
    • Notes_heading String
    • Recipient_cvr String
    • Recipient_ean String
    • Recipient_zip String
    • Recipient_city String
    • Recipient_name String
    • RoundingAmount Number
    • Notes_textLine1 String
    • Notes_textLine2 String
    • Delivery_address String
    • Delivery_country String
    • References_other String
    • PaymentTerms_name String
    • Recipient_address String
    • Recipient_country String
    • BookedInvoiceNumber Integer
    • Layout_layoutNumber Integer
    • Delivery_deliveryDate Date & time
    • Project_projectNumber Integer
    • Delivery_deliveryTerms String
    • Customer_customerNumber Integer
    • NetAmountInBaseCurrency Number
    • RemainderInBaseCurrency Number
    • PaymentTerms_daysOfCredit Integer
    • Recipient_publicEntryNumber String
    • PaymentTerms_paymentTermsType String
    • PaymentTerms_paymentTermsNumber Integer
    • Recipient_vatZone_vatZoneNumber Integer
    • References_salesPerson_employeeNumber Integer
    • DeliveryLocation_deliveryLocationNumber Integer
    • Recipient_attention_customerContactNumber Integer
    • References_vendorReference_employeeNumber Integer
    • References_customerContact_customerContactNumber Integer
    • References_customerContact_customer_customerNumber Integer
  • Orders Drafts 49 columns
    • Date Date & time
    • DueDate Date & time
    • Currency String
    • NetAmount Number
    • VatAmount Number
    • GrossAmount Number
    • LastUpdated Date & time
    • OrderNumber Integer
    • Delivery_zip String
    • ExchangeRate Number
    • Pdf_download String
    • Delivery_city String
    • Notes_heading String
    • Recipient_cvr String
    • Recipient_ean String
    • Recipient_zip String
    • Recipient_city String
    • Recipient_name String
    • RoundingAmount Number
    • Notes_textLine1 String
    • Notes_textLine2 String
    • Delivery_address String
    • Delivery_country String
    • MarginPercentage Number
    • References_other String
    • PaymentTerms_name String
    • Recipient_address String
    • Recipient_country String
    • Soap_orderHandle_id Integer
    • MarginInBaseCurrency Number
    • Delivery_deliveryDate Date & time
    • Project_projectNumber Integer
    • Delivery_deliveryTerms String
    • CostPriceInBaseCurrency Number
    • Customer_customerNumber Integer
    • NetAmountInBaseCurrency Number
    • GrossAmountInBaseCurrency Number
    • PaymentTerms_daysOfCredit Integer
    • Recipient_publicEntryNumber String
    • PaymentTerms_paymentTermsType String
    • Templates_upgradeInstructions String
    • PaymentTerms_paymentTermsNumber Integer
    • Recipient_vatZone_vatZoneNumber Integer
    • References_salesPerson_employeeNumber Integer
    • DeliveryLocation_deliveryLocationNumber Integer
    • Recipient_attention_customerContactNumber Integer
    • References_vendorReference_employeeNumber Integer
    • References_customerContact_customerContactNumber Integer
    • References_customerContact_customer_customerNumber Integer
  • Account Entries 26 columns
    • Date Date & time
    • Text String
    • Amount Number
    • DueDate Date & time
    • Currency String
    • EntryType String
    • Quantity1 Number
    • Quantity2 Number
    • Remainder Number
    • EntryNumber Integer
    • InvoiceNumber String
    • VoucherNumber Integer
    • Unit1_unitNumber Integer
    • Unit2_unitNumber Integer
    • VatAccount_vatCode String
    • AmountInBaseCurrency Number
    • Account_accountNumber Integer
    • Project_projectNumber Integer
    • SupplierInvoiceNumber String
    • CostType_costTypeNumber Integer
    • Customer_customerNumber Integer
    • RemainderInBaseCurrency Number
    • Supplier_supplierNumber Integer
    • BookedInvoice_bookedInvoiceNumber Integer
    • PaymentDetails_paymentType_paymentTypeNumber Integer
    • DepartmentalDistribution_departmentalDistributionNumber Integer
  • Invoices Unpaid
  • Invoices Overdue
Show the other 12 tables
  • Invoices Booked
  • Invoices Booked Lines
  • Orders Sent Lines
  • Orders Drafts Lines
  • Orders Archived
  • Orders Archived Lines
  • Vouchers
  • Journal Entries
  • Accounting Years
  • Suppliers
  • Booked Entries
  • Draft Entries

Need another table, field or write-back action? Tell us what you need. We can check the available options or help extend the connector.

Your data lands in a warehouse. Your BI tools read from it.

You keep the reporting tool you already have. We connect it to the warehouse where your Visma E-conomic data lives.

Power BI logo
Power BI Microsoft
Microsoft Fabric logo
Fabric Microsoft
Snowflake logo
Snowflake Data warehouse
Google BigQuery logo
BigQuery Google
Tableau logo
Tableau Visualisation
Microsoft Excel logo
Excel Sheets & pivots

From Visma E-conomic to answers in three steps.

01

Connect securely

OAuth authentication. Read-only by default. We sign a DPA and your admin keeps the keys. Read our DPA

02

Land in your warehouse

Data flows into your warehouse on your schedule. Near real time or nightly, your call. You own the data.

03

Reporting, automation, AI

We build the first dashboard, workflow or AI feature with you, then hand over the keys. Or we stay on for ongoing delivery.

Pick the track that fits how you work.

Track 01

Self-serve

We set up the foundation. Your team builds on top.

  • Visma E-conomic connector configured and running
  • Warehouse set up in your cloud account
  • Clean access for your Power BI, Fabric or Tableau team
  • Documentation on what's in the data model
  • Sync monitoring so you're warned before reports break

Best fit Teams that already have a BI analyst or data engineer and want to own the build.

Track 02

Done for you

We build the whole thing, end to end.

  • Everything in Self-serve
  • Dashboards built to the questions your team actually asks
  • Automations between your systems
  • AI workflows scoped to real tasks your team runs
  • Custom apps where a dashboard does not cut it
  • Ongoing delivery at a pace that fits your team

Best fit Teams without in-house BI or dev capacity. You tell us what you need and we deliver it.

Frequently asked questions.

Who owns the data?

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.

How fresh is the data?

Near real time for most operational systems. For heavier sources we schedule hourly or nightly. You pick based on what the reports need.

Do I need a warehouse already?

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.

Is Danish MOMS handled natively in the warehouse?

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 also use other Visma products. Can the warehouse line them up?

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.

Does the warehouse replace E-conomic App Market extensions?

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.

GDPR-compliant
Data stays in the EU
You own the warehouse

A first deliverable live in four to six weeks.

We review your Visma E-conomic setup and the systems around it. Together we pick the first thing worth building.