Link Twinfield Power BI via OData

Why link Twinfield to Power BI?

Twinfield is one of the most used accounting packages in the Netherlands. Many companies want to use their Twinfield data in Power BI for financial reporting, but encounter the same problems: there is no direct Power BI connector for Twinfield, the API is technically complex and you have to write scripts yourself to retrieve data.

The result? People manually export CSV files from Twinfield and load them into Power BI. That works, but it takes time, is prone to errors and your data is never completely up to date.

The solution: DigiData as an intermediate layer

DigiData automatically retrieves all your Twinfield data and prepares it as OData feed. OData is the protocol that Power BI natively supports. You don't have to build an API, write scripts or do exports.

In concrete terms, this means: you connect Twinfield to DigiData (one-time, takes 5 minutes), and then DigiData synchronizes your transactions, customers, suppliers, general ledger accounts, projects and VAT codes on a daily basis.

Conditions and prior check

You need access to the Twinfield organization and the offices you want to report, plus a DigiData account and Power BI Desktop. Twinfield links API requests to a CompanyCode or Company ID. Therefore, check in advance which offices the authorizing user is allowed to open and record which office codes belong in the report.

Step by step: Load Twinfield data into Power BI

Step 1: Connect Twinfield to DigiData

Log in to your DigiData dashboard and add a new Twinfield integration. You will be redirected to Twinfield where you log in and authorize DigiData. Select which offices you want to synchronize. DigiData does not store passwords, the connection is via OAuth2.

Step 2: Wait for the first sync

DigiData immediately starts retrieving your data. Depending on the size of your administration, this will take a few minutes to an hour. You can track progress in the dashboard.

Step 3: Open Power BI Desktop

Click 'Get Data' in the top ribbon and search for 'OData feed'. Select this option.

Step 4: Paste your DigiData OData URL

In your DigiData dashboard you will find the OData URL for your Twinfield data. Copy this and paste it into Power BI. After authentication, you will see all available tables: transaction headers, transaction lines, customers, suppliers, general ledger accounts, projects and more.

Step 5: Select tables and build your dashboard

Choose the tables you need and load them into Power BI. Establish relationships between tables (for example transaction lines to general ledger accounts) and build your dashboards.

Resolve limitations and issues

If you do not see an office, check the access of the Twinfield user and the selected offices in DigiData. A valid login alone is not enough: Twinfield also requires office context for API requests. If there are missing rows, first compare the office code, accounting period and filters used.

If only the refresh fails in Power BI Service, update the source references there again and test the service root first without manually adding query options. Then check whether the DigiData synchronization has been completed before Power BI refreshes; a successful Power BI refresh cannot show source changes that have not yet been synced.

Which Twinfield data is available?

Via DigiData you have access to, among other things: transaction headers and transaction lines (with complete booking details), customers (debtors), suppliers (creditors), general ledger accounts, cost centers, projects, offices and VAT codes. View the full Twinfield coupling for full details.

Tips for your Twinfield Power BI dashboard

Set up a scheduled refresh through the Power BI Service so that your reports are automatically updated daily. Use the transaction lines as the basis for your financial analyzes and link them to general ledger accounts for categorization. If you have multiple Twinfield offices, you can build consolidation reports by merging data from all offices.

OData vs Twinfield API vs exports vs connector

For recurring Power BI reports, an OData feed is usually more stable than separate exports or a direct API connection. CSV exports are useful for one-time checks, but they are static and must be recreated over and over again. A direct Twinfield API connection gives a lot of freedom, but brings authentication, pagination, error handling, rate limits and maintenance into your Power Query model. A local third-party connector can work, but often requires additional installation or gateway management.

DigiData therefore opts for an intermediate layer. DigiData synchronizes Twinfield in the background, stores the data in a structured way and delivers it as an OData feed to Power BI. Your report is therefore less dependent on live API calls and remains easier to transfer within your organization.

Security, refresh and costs

The Twinfield connection runs via OAuth2, so DigiData does not store Twinfield passwords. You decide which offices and tables you use. For reports, you set a scheduled refresh in Power BI Service so that dashboards automatically show current data. At DigiData you pay per integration, without start-up costs and with the option of a 14-day free trial.

Analyzing Twinfield data with ChatGPT, Claude and Gemini

In addition to Power BI, you can also use structured Twinfield exports for AI analysis. With DigiData you can export transactions, customers, suppliers, general ledger accounts and projects as controlled CSV files. You can analyze this with ChatGPT, Claude or Gemini, according to your own data policy.

Examples of useful questions are: "Which cost items stand out this month?", "Summarize the cash flow development for management" or "Which general ledger accounts have deviating changes compared to the previous period?" This way you use LLMs for quick interpretation, while DigiData ensures that the underlying Twinfield data is clean and up to date.

OData or CSV: what suits Power Query?

For recurring reports, OData is the best choice. Power Query can retrieve the tables, apply filters, and refresh your model without anyone having to download a file. This fits well with monthly closing, VAT checks, cash flow reports and dashboards for management or customers.

CSV is especially useful for casual analyses, audits, or when you want to share a limited data set with someone outside of Power BI. A controlled CSV export is also practical for LLM analysis, because you determine exactly which columns and periods you include.

Which refresh strategy will you choose?

For monthly reports, daily synchronization is usually sufficient. You especially want to make sure that month-end closing figures are complete. For operational dashboards, more frequent refreshes can be useful, for example when project managers view hours, invoices or open items on a daily basis.

Adjust the Power BI refresh to the DigiData synchronization. If the source data is retrieved daily, refreshing every hour in Power BI has little additional value. It is better to consciously plan synchronization and report renewal one after the other.

After the initial setup, always check whether totals correspond with Twinfield. Compare turnover, costs, debtors and creditors per period. If that basis is correct, you can add more complex analyzes such as cash flow, project results or consolidation across offices.

Handle AI analysis safely

When you use Twinfield data with ChatGPT, Claude or Gemini, carefully choose which data you export. Do not send complete administration if a summary of cost items is sufficient. Use periods, columns and filters that suit the question.

DigiData makes this manageable because the same structured data is available as OData and as CSV. Power BI uses the recurring feed; AI analysis uses a controlled export. This prevents employees from removing loose, undocumented files from Twinfield.

Common mistakes with Twinfield in Power Query

The biggest mistake is to use Power Query directly as an API client. Then authentication, pagination, limits and data transformations all end up in your report. This makes dashboards vulnerable and difficult to transfer.

A second mistake is to load only transaction lines without reference tables. For useful reports you also need general ledger accounts, projects, offices and VAT codes. Otherwise you can add amounts, but not explain them properly.

A third mistake is that companies do not agree on fixed definitions. Determine in advance what turnover, costs, outstanding items and cash flow mean in your model. DigiData supplies the source data; Power Query and Power BI turn that into your reporting logic.

Summary

Linking Twinfield to Power BI does not have to be complicated. With DigiData as an intermediate layer, you will have up-to-date Twinfield data in your Power BI dashboards within an hour. You can also use the same structured data for analysis with ChatGPT, Claude and Gemini. No exports from Twinfield, no scripts, no API knowledge required. Contact us to get started.