Workday Financial Management and Microsoft Power BI integration

What moves between them

Financial records flow from Workday Financial Management into Microsoft Power BI. ml-connector polls your Workday instance for suppliers, invoices, purchase orders, payments, and GL accounts on a schedule you define (typically hourly for invoices, daily for suppliers). Each record is transformed into Power BI table columns and pushed into a push dataset via REST. GL account balances, cost center totals, and aging schedules are computed and stored as Power BI tables, keeping dashboards and reports current without requiring manual refreshes or external ETL tools.

How ml-connector handles it

ml-connector stores Workday ISU credentials and OAuth2 refresh tokens encrypted, and refreshes the Power BI service principal token automatically when it expires (typically hourly). On the Workday side, it polls using date-range filters to avoid duplicates and handles Workday rate limiting with exponential backoff. It accepts your Workday tenant hostname and constructs the correct SOAP and REST endpoints. For Power BI, ml-connector manages the service principal oauth2 flow, obtains tokens, and POSTs transformed rows into datasets that you define with table schemas beforehand. Polling intervals are configurable per entity, so invoices can update hourly while suppliers update daily. Every row carries a Workday record ID and timestamp, so downstream updates can be matched and deduplicated. All activity is logged and can be replayed if a Power BI push fails.

A real-world example

A mid-sized financial services company runs Workday Financial Management for accounts payable and general ledger across three business units. The CFO and AP manager need current visibility into invoice aging, GL account balances, and expense trends without waiting for manual month-end reports. Before the integration, the accounting team exported GL and AP data from Workday monthly and rebuilt Power BI reports by hand, a process that took three days and was always out of date by the time stakeholders reviewed it. With Workday and Power BI connected, invoices and GL activity flow into Power BI hourly. The CFO opens a dashboard to see invoice aging and GL balances that are never more than an hour old, and controllers can drill down to transaction detail without asking the accounting team for custom exports.

What you can do

• •Poll Workday Financial Management for suppliers, invoices, purchase orders, payments, and GL accounts on a schedule that matches your business calendar.
• •Push financial transactions into Power BI datasets as rows, keeping dashboards and reports current without manual exports or scheduled scripts.
• •Transform Workday GL account hierarchies and cost center dimensions into Power BI table schemas so reports can slice and filter by financial dimension.
• •Authenticate Workday with ISU credentials or OAuth2 refresh tokens, and Power BI with service principal OAuth2, refreshing tokens automatically when they expire.
• •Track every record with Workday IDs and timestamps, deduplicate on Power BI retries, and carry a full audit trail of all financial data that flows between systems.

Questions

Which direction does data flow between Workday Financial Management and Power BI?

Data flows from Workday Financial Management into Microsoft Power BI. ml-connector polls Workday for suppliers, invoices, purchase orders, payments, and GL accounts, then pushes them into Power BI push datasets as rows. Power BI is a destination for analysis and reporting, not a source of financial truth, so data does not flow back into Workday.

How does the integration handle Workday's lack of webhooks and the need for polling?

ml-connector polls your Workday instance on a schedule you configure, using date-range filters to fetch only records changed since the last poll. Intervals are tunable per entity type, so invoices might poll every hour while suppliers poll daily. The polling respects Workday rate limits and backs off with exponential jitter if the tenant is throttled.

What happens if the Power BI token expires or a push fails?

ml-connector refreshes the Power BI service principal token automatically before it expires (typically before the 1-hour limit). If a push to Power BI fails, the record is logged with a full audit trail and can be replayed on the next sync cycle. ml-connector tracks Workday record IDs and timestamps so deduplicated rows are matched and updated, not inserted twice.