Home / Insights
Notes on Workday Finance
Practical writing on design choices, close processes and data loads, drawn from implementation work.
Workday Finance · 6 min read
Design the financial data model before you configure anything
Most Workday Finance rework traces back to one early decision: how the business is cut up for reporting. The financial data model is the set of ledger accounts, worktags, custom organizations and hierarchies that every transaction carries. Changing it after go-live means touching history, so it deserves more of the design phase than it usually gets.
Start from the reports, not the chart of accounts
Ask the CFO, the controllers and the business heads which questions they need answered every month. Write down the cuts they use: by entity, by cost center, by product, by project, by region. Each cut is a candidate dimension. If nobody can name a report that uses it, it probably does not need to exist.
Decide what lives where
A simple split works for most businesses.
- Ledger accounts say what the amount is: software expense, accounts payable, depreciation.
- Worktags say who, where or what for: cost center, region, project.
- Custom organizations suit structures that need their own hierarchy and owners, such as business units.
If two values would never be reported separately, they should not be separate worktags.
Agree balancing early
Decide which dimensions must balance on every journal. Company is the usual one, and some businesses add more. Balancing requirements change how journals and intercompany transactions behave, so agree them before the build starts.
Walk one close through the model on paper
Take last month's close and trace it through the proposed structure. Where would accruals post? Which tags would an intercompany charge carry? Where would the board pack numbers come from? Gaps found on paper cost an hour. Gaps found in testing cost a sprint.
A good test: can you produce the board pack, the statutory accounts and the tax schedules from this model without a spreadsheet in between?
Back to the list
Workday Finance · 5 min read
Multi-book accounting: one business event, several sets of numbers
Many groups report under more than one framework: US GAAP for a parent, IFRS for the group, Local GAAP for statutory filings. The same invoice or asset purchase then needs to appear in more than one set of books, sometimes with different amounts. Workday supports this with additional ledgers and, for assets, separate books. Exact set-up depends on your release and your design, so check names and options in your own tenant.
Find the differences that are real
Most transactions are identical across frameworks. List the ones that are not: depreciation lives, lease treatment, revenue timing, foreign exchange. This list is usually shorter than the team expects, and it decides how much parallel structure you need.
Map accounts once, deliberately
Agree how each ledger account in the primary book relates to the equivalent in the other books. A written mapping that the controller has signed off prevents arguments during the first close.
Automate the adjustments
Where books differ, post the difference with automated or recurring journals, not by hand. Manual adjustments are where parallel books drift apart.
Close every book on the same calendar
Add each book's steps to the close checklist, with an owner. A framework that nobody owns will be the one that is late.
The common mistake is building a full parallel structure for differences that amount to a few journals a quarter. Size the design to the real list of differences.
Back to the list
Workday Finance · 4 min read
A month-end close checklist for Workday Finance teams
A close runs better when everyone sees the same list in the same order. This one assumes the main subledgers are live in Workday. Adjust it to your own calendar and tenant.
- Cut off the subledgers. Confirm that supplier invoices, customer invoices, expenses and asset transactions for the period are entered and approved.
- Run the recurring and automated journals. Accruals, prepayments, depreciation and allocations.
- Post intercompany. Confirm that both sides agree before you review balances.
- Reconcile banks. Match bank statement lines to payments and receipts and clear the exceptions.
- Reconcile key accounts. Subledger to ledger for payables, receivables and assets, then the balance sheet accounts with owners.
- Review variances. Use reports and drill-down to the transaction. Ask for explanations above an agreed threshold.
- Post adjustments. Record each with a reason and an approver.
- Close the period. Follow your period status steps and lock the period once sign-off is done.
- Publish the reports. Management pack, statutory trial balance and any tax schedules.
An interactive version of this list is on the Resources page.
Put a name and a date next to every step the first time you run it. After two closes you will know which steps hold everyone up.
Back to the list
Workday Finance · 5 min read
EIB or iLoad: choosing how to load data
Every implementation moves data into Workday, and every live tenant keeps loading it afterwards. The tool matters less than the discipline around it. Which tools you can use depends on your project and your agreement with Workday, so confirm with your implementation lead.
What each is generally used for
- EIB (Enterprise Interface Builder) is a tool for inbound and outbound integrations. Teams use it for spreadsheet-based loads and for scheduled files in and out.
- iLoad is a data-loading approach used on Workday Finance implementations to prepare and load conversion data.
- Workday Studio and APIs suit complex or high-volume interfaces with other systems.
Choose by volume, repeatability and ownership
One-off conversion data and a recurring interface are different jobs. Ask how often the load will run, who will own it after go-live and how failures will be noticed.
The steps that matter for any load
- Extract from the source and freeze a version.
- Map each source field to its Workday field and agree the mapping with the data owner.
- Prepare the load file in the template.
- Load a small batch and check it line by line.
- Load the full set.
- Reconcile totals back to the source: trial balance, open payables and receivables, asset cost and accumulated depreciation.
- Record the sign-off.
Run at least one full trial load before cutover. The first one always finds mapping gaps, and you want to find them in a trial.
Back to the list