To schedule a Workday report extract, enable an advanced custom report as a web service and call its RaaS URL. Use SOAP or REST APIs for broader object access, or outbound integrations for files and payroll feeds. For a warehouse that answers past-period questions, preserve effective-dated history and backdated corrections alongside the extracted records.
HR asks for a daily headcount and compensation feed into the warehouse. The Workday administrator has a report with those fields. Calling it through RaaS can supply the rows without another manual export.
The next request may ask who reported to each manager last quarter. Decide whether the feed must retain current records, dated snapshots or the history behind each change. A report that supplies the first of these may leave the historical question unanswered.
Workday offers five ways to get data out
Start with the records the receiving application needs and the period they must describe. A RaaS feed gets its columns from a report. An API integration asks for business objects or selected fields, with the developer controlling the request and its date scope.
RaaS suits a maintained report whose columns already answer the question. Workday Web Services supports programmatic integrations, while REST endpoints and Workday Query Language provide routes to selected records and fields. WQL uses SQL-like syntax over Workday data sources, with access limited to the caller's permissions.
An outbound file needs to match its receiving system's layout. A payroll feed has a narrower purpose: the records and changes required by that payroll recipient. Check those requirements before using the same feed for broader finance history.
The method also determines where business logic lives. With RaaS, inspect the report's data source, fields and prompts. With an API, inspect the requested objects and dates. Keep the requested dates with each load so a warehouse user can tell which period its records describe.
| Method | Best for | Returns | Watch for |
|---|---|---|---|
| RaaS | A maintained custom report | Report rows in JSON, CSV or XML | Report fields, prompts and access |
| SOAP Web Services (Get_Workers) | Broad business-object extraction | Structured object responses | Requested dates and response scope |
| REST API and WQL | Selected objects or field queries | Endpoint or query results | Coverage, permissions and paging |
| EIB outbound files | Scheduled file delivery | Configured outbound file | File layout and destination |
| PECI and payroll connectors | Payroll-provider feeds | Payroll-oriented change records | Payroll scope and recipient requirements |
RaaS turns a custom report into a URL
Workday Report-as-a-Service gives an integration a web-service address for a report's results. A scheduled job can retrieve those results, removing the manual export from the daily feed while keeping the report's fields and logic.
Start with an advanced custom report and enable it as a web service. The report still determines which data source, fields and calculated values the caller receives. Workday supports output formats including JSON, CSV and XML, so the receiving job can use a format it already handles.
The report's prompts become inputs to the request. A date prompt can select the period being returned, provided the report uses that prompt in its logic. Check the report's filter against that prompt: the parameter must select the period you intend to load.
Workday documents the output links under the report's related actions, in Web Services and View URLs. Required prompts must have values before the output can be retrieved. Save the format and prompt values in the job configuration. The next run should request the same kind of result the report owner has reviewed.
The report owner continues to maintain the definition behind the URL. When HR adds a field or finance changes a calculation, review the output before the receiving job loads the revised rows.
Large RaaS reports fail without date filters
A scheduled request needs a defined population and date range. Leaving its prompts open can return far more records than the report owner sees in a narrow review. Test that larger result, including the initial load, before choosing the recurring schedule.
An updated-from prompt can restrict a run to records selected by the report's change logic. Pair it with an explicit end point when the report supports that range. Record both values with the file. A repeated run can then use the same interval when you compare its rows.
Filters need to match the purpose of the extract. An effective date asks which values applied at a point in time. An update date asks which records changed during an interval. A request can finish successfully and still miss required records if it filters on the wrong date.
If the report remains too large for the intended schedule, consider smaller organisational scopes and runs outside busy periods. Test that the combined results cover the required population. Check the returned population after each change to the filter or schedule.
Workday can throttle requests under high tenant load. Test the initial extraction as well as the smaller requests that follow it. A daily job may usually return a small set, while its first run or a repeated period requires substantially more data. Make sure the job can complete both the initial load and a later request to repeat a period.
Calculated fields and security trip up extracts
The caller's permissions and the report's calculations determine which values reach the warehouse. A successful request alone does not establish that the receiving table contains every record finance expects.
An integration system user, or ISU, needs access to the report and the underlying domains. Test with that identity after the report owner has checked the result. The owner may be able to see records that the scheduled integration cannot read, so the two runs can return different populations.
Some Workday entities need additional permissions. Decide whether the application needs those entities before requesting that access. An extract should follow the approved scope and make any missing records visible during reconciliation.
Calculated fields also need review. Many cannot cross business-object boundaries or be used outside Workday. A single exported value may depend on related records or report logic that the receiving model lacks.
Identify which calculations can be extracted safely and which must be rebuilt in prepared data. Then compare the resulting measures with the Workday report for the same population and period. When the totals differ, trace the missing records and the calculation separately. That helps distinguish an access problem from logic that changed during extraction.
Current-value extracts lose Workday history
Last June's headcount needs the manager, grade, salary and cost centre that applied in June. Loading today's values into every historical row can change the meaning of the earlier report even when the worker identifier stays the same.
Workday changes have effective dates. A correction entered today can apply to an earlier reporting period, so the time the warehouse receives it differs from the time it affects. The historical model needs to represent that distinction.
A last-modified watermark can miss changes needed by a historical report, including changes to related objects. Following only the worker record's update time can leave a dependent measure unchanged when its underlying context has changed. Define how the extract will revisit affected periods and related records.
A daily snapshot gives you evidence of what was extracted that day. It does not by itself reconstruct the effective-dated history before the snapshots began, or explain a later correction to an earlier period. Match the retained history to the questions HR and finance intend to ask.
Test a backdated manager or compensation correction before relying on the feed for past-period reporting. Follow it from extraction into the prepared table and then into the earlier report. The useful test is whether the report reflects the intended historical definition after the correction arrives.
Databasin keeps Workday history as it extracts
We connect Workday and prepare dated records for the finance and HR questions the warehouse must answer. The native connector covers 39 Workday feeds across HCM, Financial Management, Resource Management and Higher Education, with a Workday semantic layer included.
Databasin preserves Type 2 effective-dated history so the prepared records can retain successive versions of a worker's attributes. Incremental loads follow related-object changes and backdated corrections. The records arrive with that history in your lakehouse, Databricks, Snowflake or Fabric, so a past-period query can use the values that applied then.
A separate RaaS connector uses the custom reports your team already maintains. We use existing report definitions where they answer the request, and prepare business objects when the warehouse needs history beyond those reports. The product flags entities that require additional permissions, while the permissions approved in Workday determine what it can read.
Our team extracts the calculated fields that can leave Workday safely and rebuilds the other calculations in prepared data. You review those measures against the source reports. The Workday architecture explains the history model, and the Workday integration describes the connector routes for the reports and objects you need.
Example: a daily headcount extract through RaaS
This illustrative headcount feed calls a Workday report each day and loads the returned rows into a warehouse.
| Step | In Workday | Result |
|---|---|---|
| Build the report | Create an Advanced custom report using a worker data source | A report designed for one row per worker |
| Make it a web service | Enable the report as a web service and add an effective-date prompt | A report callable with a date |
| Give it a caller | Share with an ISU whose security group has the needed domain access | The scheduled caller can run the report |
| Copy the URL | Use related actions, Web Services, View URLs, then choose JSON or CSV | A report URL for the receiving job |
| Call it | Send an HTTPS request with the ISU credentials and prompt value | JSON or CSV rows for the requested date |
| Schedule and load | Schedule the receiving job to load the file nightly | A daily headcount table in the warehouse |
This produces the rows selected by the report for the requested date. Past-period analysis also needs retained history and a way to incorporate backdated corrections.
Five checks before the first extract
- Name the report ownerIdentify who maintains the report definition and can explain changes to its data source, calculated fields and required prompts.
- List the history you needSpecify which past periods the warehouse must answer and which worker attributes must reflect the values effective at that time.
- Request the ISU's access earlyDefine the required report and domain access, then test the returned population using the identity that will run the schedule.
- Test the largest runInclude the initial load and a repeated reporting period so the extraction plan covers more than the usual daily changes.
- Plan for backdated correctionsFollow a correction into an earlier period and confirm that the prepared history and the report reflect its intended effective date.
Sources
Workday, Concept: Reports-as-a-Service (RaaS), 2026 · developer.workday.com/doc/hto1529968349582.md
Workday, Concept: Accessing RaaS Output, 2026 · developer.workday.com/doc/fdy1570549197818.md
Workday, Concept: Workday Web Services, 2026 · developer.workday.com/doc/dan1370797670978.md
Workday, Concept: Workday Query Language, 2026 · developer.workday.com/doc/GUID-6546152a-bcf0-447d-8d64-230f9e2ac291-enHYPHENus.md
Workday, Reference: Integrations, EIB, and Web Service Limits, 2026 · developer.workday.com/doc/dan1370797408285.md
Workday, Concept: Workday Web Services Response Filter Element, 2026 · developer.workday.com/doc/jas1383238226367.md
Workday, Extract Data from Extend Business Objects Using EIBs, 2026 · developer.workday.com/doc/GUID-bb9aa5c0-b58b-41a9-96bd-cd1c1af495ca-enHYPHENus.md
Workday, raas-python, 2026 · github.com/Workday/raas-python
Workday, Global Payroll REST APIs, 2026 · developer.workday.com/doc/GUID-26ab7e0b-5b02-47a5-a924-ce370a17d209.md
Workday, Global Payroll Effective Changes REST API, 2026 · developer.workday.com/doc/GUID-fa4b5d46-47d0-4df5-8904-5576031d51f5.md
Microsoft Learn, Create RaaS reports on the Workday portal, 2026 · learn.microsoft.com/en-us/viva/learning/workday-create-raas-report
Plan your Workday data with us
We can discuss what finance and HR need to know about past periods as well as today. A demo shows the extraction route, how we prepare dated records and how your team would use them in an application.