Why process excellence comes first
Finance technology projects often begin with configuration and end with a process that is faster but still fragmented. Process excellence starts earlier. Before a team configures a ledger, an approval, or a report, it needs to agree on how work should flow, who owns each decision, which control prevents or detects error, and which measure shows improvement.
In a Workday context, that means treating the financial data model, security roles, approvals, and reporting as one design. A change to a cost center hierarchy or an approval rule is not only a technical change. It changes who can see data, who can approve spend, and how quickly the close can move.
Every configuration choice should have a process owner, a control, and a measure. If a choice has none of the three, the team is not ready to build it.
The workshop map
Finance work is easier to discuss when it is grouped into four process chains. The workshop uses these chains as a map, then visits the modules that support them.
| Process chain | Workday focus | Core question |
|---|---|---|
| Record to report | General ledger, close, consolidation, reporting | Are the numbers complete, controlled, and timely? |
| Procure to pay | Sourcing, purchase orders, supplier invoices, payments | Is spend authorized, received, and paid correctly? |
| Order to cash | Customers, billing, receivables, collections | Is revenue billed accurately and collected on time? |
| Plan to perform | Budgets, forecasts, expenses, planning | Does the plan connect to actuals and decisions? |
The nine modules visit these chains in sequence, starting with the financial data model that all four depend on. The order matters because a weak foundation in ledgers, companies, or cost centers shows up later as a close issue, an approval problem, or a reporting gap.
The nine modules
The module map below is the working spine of the workshop. Each module combines process design, Workday configuration topics, and a control question.
Financial Management Foundation
- Workday Finance architecture overview
- Ledgers, companies, and cost centers
- Financial data model configuration
- Accounting periods and fiscal years
General Ledger and Accounts Payable
- General ledger configuration
- Journal entries
- Accounts payable setup
- Payment runs and reconciliation
Accounts Receivable and Billing
- Accounts receivable configuration
- Customer management
- Invoicing and billing schedules
- Billing adjustments
Asset Management
- Fixed assets
- Depreciation methods
- Asset lifecycle management
- Capital budgeting
- Asset reporting and reconciliation
Budgeting and Expense Management
- Budget plans and budget tracking
- Expense policy
- Travel management
- Procurement integration
Adaptive Planning and Consolidation
- Workday Adaptive Planning overview
- Scenario modeling
- What if analysis
- Consolidation
Analytics and Reporting
- Workday Prism Analytics
- Financial reports and calculated fields
- Dashboards
- Discovery boards and story reports
- Workforce analytics
Security and Integration
- Financial security configuration
- Bank integration and payment files
- SOX compliance
- Internal controls
Capstone
- End to end finance implementation
- Real business scenario practice
- Configuration and integration testing
- Project documentation and walkthrough
The foundation module defines the data structures that the other modules use. The capstone brings them back together in one flow, so the team can see where a transaction starts, where a control applies, and where a report picks it up.
The process lens
Every module is reviewed through four questions. The lens keeps the workshop from becoming a configuration tour and gives the team a consistent way to judge each design choice.
| Lens | Question | Evidence to leave behind |
|---|---|---|
| Standard | Is there one agreed way to perform the process? | Process map, roles, decision rights |
| Control | What prevents or detects error? | Approval design, segregation of duties, audit trail |
| Data | Is the data complete, timely, and owned? | Field definitions, reconciliation, exception log |
| Measure | How will we know the process improved? | Cycle time, exception rate, close days |
A module is finished only when the team can name the standard, the control, the data owner, and the measure. That test is more useful than a long list of screens. It also gives the workshop a practical output that can survive the next reorganisation.
Facilitation and capstone
A strong workshop moves through four beats. Each beat produces something the team can review, rather than a conversation that stays in the room.
-
Map the process
Draw the current and future flow, including handoffs, approvals, and exceptions. Mark where the process waits, where it repeats work, and where it relies on a person rather than a control.
-
Configure the control
Translate the future flow into Workday setup, security roles, and approval rules. Keep the process map open so each configuration choice can be traced back to a step.
-
Test the exception
Use a realistic scenario such as a missing receipt, a duplicate invoice, or a late payment. Trace what the system does, who is alerted, and what evidence remains.
-
Document the handoff
Record the process, the control, the report, and the owner. The design should still make sense to the next team that runs it.
The capstone ties the modules together. Choose one chain, such as procure to pay or record to report, and walk it from transaction to report. The output should be a process map, a configuration checklist, a control matrix, and a reporting walkthrough.
Preparation and outcomes
Who should attend
The workshop works best when finance and system roles are in the same room. A mix of perspectives produces better decisions than a single team working alone.
- Finance process owners and controllers
- Accounts payable and accounts receivable leads
- Planning, budgeting, and FP&A teams
- Workday implementation and support analysts
- Security, risk, and internal controls partners
Helpful preparation
No prior Workday experience is required for the process discussions. The following background helps the team move faster through the configuration topics.
- A basic understanding of finance and accounting
- Familiarity with any ERP system
- An IT background is helpful but not mandatory
What the workshop can produce
- A shared process language across finance and system teams
- A Workday module map tied to four process chains
- A control checklist for approvals, access, and audit evidence
- A reporting plan for the measures that matter
- A capstone walkthrough from transaction to report
This workshop is an outline for process design. Formal certification and tenant configuration practice remain separate steps, and teams that need structured Workday finance training can pursue a dedicated program.
References
These sources support the controls, process frameworks, professional practice, and research discussed in this field guide.
- COSO Internal Control Framework
- ISACA COBIT
- IFRS Foundation
- Deloitte Insights
- Harvard Business Review
- MIT Sloan Management Review
- Harvard Law School Forum on Corporate Governance
- Bain Insights
- KPMG Insights
External resources are listed for further reading and are not part of the Funcostarica workshop.