Skip to content
EN
Contact

Visma AccountView Power BI dashboard

We bring your AccountView accounting data together via the Web API in a single Power BI model, just as we brought Vivara’s sources together in one data model.

Discuss your accounting data Read the Vivara case study

Vivara analyses its data with a single custom-built data model, from finance to marketing

Vivara wanted to bring its data together in one central location, with data of the highest quality. We developed a data platform that retrieves data daily from sources such as SAP, Magento and SharePoint. Power BI is listed among the tools used in this case study.

Read the case study

Can you do it without opening each AccountView set of accounts separately and retyping the data?

If you manage many clients or companies in AccountView, you create the same report for each set of accounts and then combine the results in Excel. A Power BI model reads each set of accounts directly and displays the results by client or in aggregate.

Book a call

An AccountView dashboard starts with the Web-API provided by Visma

Discuss your accounts

Accessing data via the Web-API

Team and Business have a Web-API; from version 2026, Solo does too. Visma provides the documentation on request, which we use to build the data loading step.

Accounts side by side

Each account gets its own code in the data model. You can then view results by client, by group or in total, using the same measures.

Local, hosted or online

Whether AccountView runs on your own server, with a hosting provider or as AccountView Online determines how we can access it for data loading. We establish that first.

One data model for everyone

Finance, management and clients use the same model, as all departments at Vivara do with the data model they use to analyse their data.

The AccountView version and access determine how we start

  1. Version and access

    Which edition and version you use, whether it is hosted or installed locally, how many company accounts you have, and whether the Web-API is available.

  2. Loading step and model

    We make data from a few company accounts accessible, build the model and check the results against the reports in AccountView.

  3. All company accounts live

    The rest follow through the same loading step. Refreshes, access permissions and a designated owner are put in place.

Where is the line between AccountView reporting and Power BI for our firm?

Talk it through with us

A good fit if

You manage many sets of accounts in AccountView, as a firm or a group, and want to see figures by client or on a consolidated basis without running a report for each set of accounts.

Not a good fit if

The reports in AccountView give you what you need and you aren’t adding other sources. In that case, a custom model mainly means more maintenance.

What determines the scope

Your AccountView edition and version, the number of sets of accounts, how similar their charts of accounts are, which other sources you’ll add and who will manage the model.

Why not use an off-the-shelf connector?

Visma lists partners offering a Power BI connector for AccountView from version 2026 onwards. If such a connector meets your needs, we’ll say so. We build a solution when you need more sources or a custom model.

Web-API, connector or data warehouse: which is right for your AccountView reporting?

A partner connector

Choose this if you use AccountView 2026 or later and the connector’s standard reports answer your questions. There’s little for you to manage yourself.

The Web-API

Choose this if you want to combine multiple sets of accounts in your own model. We recommend it for accounting firms and groups that want to see results both by client and in aggregate.

A data warehouse

Choose this if hours, CRM or an online shop need to be included alongside AccountView. Read more about having a data warehouse built.

We’ve brought data sources together in a single data model before

Data Science Lab has worked with data and AI since 2016 and is a Microsoft Partner for Fabric. We built Vivara a data platform with a data model for every department, and developed several dashboards and a Power BI app for Ammega.

Book an introductory meeting

Your AccountView version and accounting records are the starting point for our first conversation

Stef Stoelwinder

Stef Stoelwinder

Business Development

Stef is your first point of contact. In our first conversation, we’ll discuss your AccountView version, your accounting records and the reports you currently prepare manually.

E-mail info@datasciencelab.nl

Phone +31 (0)20 3636 724

Which sets of accounts in AccountView should be combined in Power BI?

Tell us which version you use, how many sets of accounts you have and which reports you currently produce. We’ll reply by email or suggest an initial meeting.

Emailinfo@datasciencelab.nl Phone+31 (0)20 3636 724

Enter a valid email address.

Let us know how we can help you.

Frequently asked questions

AccountView has an open Web API in the Team and Business editions and, from version 2026, in Solo too. Visma provides the documentation on request and also lists partners that offer a Power BI connector. We retrieve the accounting data with a custom data-loading step and build the Power BI model on top of it.

To read about how a dashboard starts with the decision it needs to support, see Power BI dashboards.

Visma offers AccountView as a local installation, as a hosted option that removes the need for your own server, and as AccountView Online. For a local installation, you can choose Solo, Team or Business.

It matters for Power BI because the deployment option and edition determine whether and how the Web API is available. We establish this with your AccountView supplier before building anything.

According to Visma, Solo supports five accounting entities, while Team and Business support an unlimited number. During data loading, each entry is tagged with its entity’s code, so a new client automatically appears in the existing reports.

We map accounts to a common chart of accounts, even when the entities are set up slightly differently. That lets you view results by client or in aggregate.

For a financial dashboard, we look for general ledger transactions, balances by period, outstanding receivables and payables, cost centres and budgets.

Public documentation does not specify which of these the Web API for your version returns. We check the documentation Visma provides on request before drawing up a plan.

For each client: a profit and loss statement and balance sheet across periods, budget versus actuals by cost centre, and receivables ageing. For groups, a consolidated total across accounting entities.

Read about which management information belongs in a financial dashboard in Power BI on that page.

For data loading, we use a separate AccountView user account, distinct from staff accounts, with only the necessary permissions. In Power BI, row-level security ensures that a client or branch sees only its own accounting data.

We set up workspaces and apps for each audience as described under Power BI consultant.

Both come from Visma, but they are different products. AccountView describes itself as accounting software for accounting firms, with local, hosted and online versions. eAccounting is an online accounting package for self-employed professionals and smaller businesses, with a publicly documented API. See Visma eAccounting in Power BI.

Other products: Twinfield and Unit4 Multivers.

When you have only a few accounting entities and the reports in AccountView are sufficient. Or when each entity has its own chart of accounts without a consistent structure: in that case, start with data quality.

If a partner’s connector meets your needs, we recommend using it.

Looking to build beyond AccountView?

View all services