Twinfield connector · Bookkeeping
Twinfield connector for Power BI and Excel
Use DigiData as your Twinfield connector for Power BI, Excel, and AI. Connect selected offices through OAuth2 and automatically sync transactions, relations, ledger accounts, projects, cost centers, and VAT codes through OData.
Here you will find the supported data, operation and availability of the connection. Follow the practical guide Twinfield Power BI setup guide for the steps in Power BI.
Want to learn DigiData on your Twinfield data? Take the Twinfield training: build dashboards, automate reports and work with the AI agent in one day.
Last reviewed:
The reason
Why connect Twinfield to DigiData?
DigiData connects Twinfield through OAuth2 and synchronizes the offices you select. The Twinfield connector provides structured tables for transaction headers, transaction lines, debtors, creditors, general ledger accounts, cost centers, projects, offices, and VAT codes. Use the same synchronized data through a stable OData feed in Power BI and Excel, as a CSV export, or for AI analysis within DigiData. Build financial dashboards across multiple offices without manual exports or custom API scripts.
Connecting Twinfield to Power BI in short
The Twinfield connector is available and synchronizes supported tables such as Transaction Headers, Transaction lines (Lines), Transaction types and Customers (Debtors). DigiData offers these source records via OData for Power BI and Excel and via CSV for separate exports. The connector only supplies the entities listed on this page; source permissions, the source API, and your sync schedule determine which records and updates are available. You set up relationships, calculations and dashboards in the reporting tool.
Twinfield connector for finance, Excel and Power Query
The Twinfield connector synchronizes financial entities per selected office. Power BI and Excel read the same OData tables for recurring reports and checks.
Twinfield offices and transactions
Select the Twinfield offices and work with transaction headers, transaction lines, debtors, creditors and general ledger accounts.
Twinfield Power Query and Excel
Load the same OData tables into Power Query, Power BI, or Excel without manual XML or CSV exports.
Consolidation and checks
Use office codes as a stable dimension, schedule report refresh after synchronization, and reconcile totals by office and period.
Twinfield product information and guides
This product page lists which Twinfield data DigiData synchronizes and how the OData connection works. Use the guides below for setting up Power BI, working with Power Query and comparing different connection methods.
Conditions
Availability, setup and conditions
- Availability
- Status: Available. The connector provides the entities listed on this page under "Available data".
- Setup
- Via a secure OAuth2 connection. You log in to Twinfield, authorize DigiData and select the offices you want to synchronize. No passwords are stored.
- Refresh
- Automatic synchronization based on the integration schedule. New source data will not appear until the source sync and then the Power BI refresh are complete.
- Security
- API keys and tokens for linked applications are stored encrypted.
- Limitations
- Only the listed entities are supported. Availability and timeliness depend in part on the source API and your rights in Twinfield. DigiData supplies the source data to DigiData dashboards and the AI agent, and through OData and CSV to your own reporting tool. In Power BI or Excel you set up relationships and measures yourself.
- Price and trial period
- €50 per month for the Twinfield connector, plus a €95 monthly DigiData platform fee, without start-up costs. You can test DigiData 14 days for free. View current prices.
What you get
What do you get with the Twinfield link?
An overview of what DigiData does with your Twinfield data:
Which data
Available Twinfield data in DigiData
The following entities are automatically synchronized and available via OData or CSV export:
Twinfield data model: tables and relationships
Every OData table starts with Twinfield_. Codes are only unique within an office, so always join on office code and code. Column names start with a lowercase letter in the feed, exactly as shown below.
| Table | Contents | Key |
|---|---|---|
| Twinfield_TransactionHeaders | Transaction header: office (officeCode), daybook (code), number, period, date, currency, status and relation. | id |
| Twinfield_TransactionLines | Transaction lines: dim1 (GL account), dim2 (relation or cost centre), dim3 (project), debit and credit in the transaction currency, baseValue in the office currency, VAT code, invoice number and open amount. | transactionHeaderId → TransactionHeaders |
| Twinfield_LedgerAccounts | GL accounts per office with code, name and type. | officeCode + code |
| Twinfield_Customers and Twinfield_Suppliers | Customers and suppliers per office. | officeCode + code |
| Twinfield_CostCenters and Twinfield_Projects | Cost centres and projects per office. | officeCode + code |
| Twinfield_GeneralLedgerAccountMappingAccounts | Account mapping from your Twinfield reporting structures, with hierarchy, level and path. An account repeats per hierarchy: filter on one hierarchyCode before you join. | companyCode + hierarchyCode + hierarchyElementId + type + code + balanceType |
| Twinfield_Offices | The selected offices with code and name. | officeCode |
Relationships in your model
- Twinfield_TransactionLines.transactionHeaderId = Twinfield_TransactionHeaders.id
- Twinfield_TransactionLines.dim1 = Twinfield_LedgerAccounts.code
- Twinfield_TransactionLines.dim2 = Twinfield_Customers.code or Twinfield_Suppliers.code on balance sheet lines, Twinfield_CostCenters.code on profit and loss lines
- Twinfield_TransactionLines.dim3 = Twinfield_Projects.code
- Always join dim1, dim2 and dim3 on officeCode as well, taken from the transaction header
Check the numbers
The debit and credit columns are in the transaction currency. For a balance, sum baseValue instead: it is signed and in the office currency. Filter the headers on the same status as your trial balance (final, provisional or both) and compare per office and period with the trial balance in Twinfield before you add cost centres and projects.
Use cases
What can you do with Twinfield data?
Multi-office reporting across multiple Twinfield companies in one dashboard
Detailed VAT reports for all offices
Cash flow analyses with transaction data in Power BI
Comparison of project budgets with actual costs
How it works
How does the Twinfield link work?
Connect Twinfield
Link your Twinfield account via the DigiData dashboard. Safe and fast.
Select your dates
Check which accounts, environments, and entities are available for this resource. The options differ per connector.
Analyze in Power BI
Use the OData feed in Power BI, Excel or download CSV exports.
Build a Twinfield dashboard with AI
Describe which overview of your Twinfield data you want to see and the DigiData AI agent builds the dashboard, with filters, drilldowns and a presentation mode for TV screens or meetings. You do not need a Power BI model and you do not pay per viewer.
Often used in: Solution for Construction & Field Service, Solution for Accounting & Advisory Firms
Twinfield in Power BI
Load Twinfield transactions, debtors, creditors, general ledger accounts, projects, and VAT codes into Power BI with the DigiData OData feed. Combine selected offices in a clean multi-office reporting model and schedule report refresh after DigiData synchronization.
Discuss your Twinfield numbers with AI
Let AI analyse your Twinfield data. Use the DigiData AI agent with fixed definitions, or connect your numbers to Claude securely and read-only.
Frequently asked questions
Questions about the Twinfield integration
How do I connect Twinfield to Power BI?
With DigiData you automatically synchronize Twinfield data to an OData feed. In Power BI Desktop, choose 'Get Data', select OData feed and paste the DigiData URL. You can then load, combine and refresh the tables without building a Twinfield API connection yourself.
How often is Twinfield data refreshed?
DigiData synchronizes Twinfield according to your integration schedule. The exact frequency and availability of new records depend on your settings and the source API.
What does the Twinfield connection cost?
DigiData charges platform costs plus an amount per active integration. There are no start-up costs and you can test for 14 days for free. View the current price on the prices page.
How do I report across Twinfield offices?
Load transaction lines, ledger accounts and offices through OData. Keep office identifiers in your keys and align currencies and account mappings. Fictional example: €100,000 revenue in office A and €80,000 in B totals €180,000 before eliminations. Filter by office or compare matching periods. DigiData supplies the source data; consolidation rules belong in your report model.
How do I connect Twinfield to DigiData?
Via a secure OAuth2 connection. You log in to Twinfield, authorize DigiData and select the offices you want to synchronize. No passwords are stored.
Can I link multiple Twinfield offices?
Yes, after connecting you can choose per office which data is synchronized to DigiData. Records include the corresponding office identifier for multi-company dashboards.
How up to date are Twinfield figures in DigiData and Power BI?
DigiData synchronizes the selected offices every night at midnight UTC by default and only fetches what changed. Schedule the refresh in Power BI or Excel after that synchronization, for example in the morning, so you report on yesterday's position. DigiData only reads from Twinfield and never writes back.
How do I get Twinfield data into Power BI?
Connect Twinfield to DigiData through OAuth2 and choose the offices. After the first synchronization, copy the OData URL from DigiData, choose 'Get data' and then 'OData feed' in Power BI Desktop, and paste the URL. You then see tables for transaction lines, general ledger accounts, customers, suppliers, projects and VAT codes. The 'Connect Twinfield to Power BI' guide on the blog describes every step and the scheduled refresh.
How do I check that the figures in Power BI match Twinfield?
After the first synchronization, compare a few totals per office and period with Twinfield itself: revenue, costs per ledger category, open receivables and open payables. Use the same office code, period and filters as in Twinfield. If a total differs, first check that all offices are selected and that the synchronization had finished before Power BI refreshed. Add customers, projects and cost centers only once that base matches.
Combine
Other integrations that may interest you
Most companies do not run on one package. Place Twinfield next to your other sources, so that you have one report.
14 days free · no start-up costs
Ready to connect Twinfield to DigiData?
Use the trial period to validate the available tables, synchronization and your reporting model with your own data.
