Home / Services

How I can help with Workday Finance

Eight areas where a functional consultant with an accounting background is useful, from the first workshop to the weeks after go-live.

A functional lead for Workday Financial Management, from requirements to go-live.

Best for: Teams starting or part-way through an implementation that need deeper finance functional capacity.
Typical scope: Stakeholder workshops and requirement gathering
Financial data model and ledger design
Configuration of Record to Report, banking, assets, customers and suppliers
Business process and security design
Testing support, cutover and handover
You receive: Design documents, a configured tenant, test evidence and runbooks.

A structured look at how your ledger accounts, worktags and hierarchies support the reports you need.

Best for: Live tenants where reporting needs workarounds, or where worktags and organizations have multiplied.
Typical scope: Review of ledger accounts, worktags, custom organizations and hierarchies
Check of balancing rules and intercompany behaviour
Gap analysis against management, statutory and tax reporting
A target model and a sequence for getting there
You receive: A written findings document with prioritised recommendations.

Parallel reporting under US GAAP, IFRS and Local GAAP without a spreadsheet in the middle.

Best for: Groups that report under more than one framework.
Typical scope: Ledger and book design
Account mapping across frameworks
Automated adjustment journals
Close steps for each book on a shared calendar
You receive: Design, mapping, configuration and test scripts for each book.

Clean opening data and reliable interfaces with the systems around Workday.

Best for: Projects moving from a legacy ERP, or live tenants adding new source systems.
Typical scope: Source-data analysis and mapping to Workday structures
Load templates, trial loads and reconciliation of opening balances
EIB, iLoad, Workday Studio and API-based interfaces
Support for inbound and outbound files
You receive: Mapping documents, load files and tie-out reports.

Reports finance teams use in the close and in management meetings.

Best for: Teams that export to Excel to answer questions Workday should answer.
Typical scope: Custom, composite and matrix reports
Executive dashboards
Source-to-GL drill-down for audit traceability
BIRT business documents such as customer invoices
You receive: Tested reports and documents with a short user guide.

A period close that is repeatable and an audit trail that is already there.

Best for: Finance teams with manual journals, slow reconciliations or approval gaps.
Typical scope: Automated journals for revenue, accruals, intercompany and assets
Bank statement reconciliation set-up
Approval workflows, escalation rules and notifications
Security roles, segregation of duties and custom validations
You receive: Configured controls and a close calendar your team can run.

Disciplined testing and a calm cutover.

Best for: Any project approaching a test cycle or go-live.
Typical scope: Unit testing, SIT and UAT coordination
Defect triage and root-cause analysis
Go-live planning and cutover activities
Hypercare and production stabilization
You receive: Test scripts and results, a cutover plan and a post-launch issue log.

Finance users who can run the system without calling the project team.

Best for: Teams preparing for go-live or inheriting a tenant.
Typical scope: End-user training sessions
Job aids and user guides
Configuration and process documentation
Mentoring for junior consultants
You receive: Training materials, process documents and recorded walkthroughs.

How it starts

From first message to a plan

Short call
You describe the entities, the Workday status and what is not working. I ask questions about the finance side first.
Written scope
I send a short note on what I would do, what I need from your team and what you would receive.
Agreed plan
We confirm timeline, working pattern and the people involved on both sides, then begin.

Send a few lines about where you are in the project.