Platform: Workday Adaptive Planning
Scope: internal allocation eliminations in a fund-based planning model
The business problem
Finance reported that eliminations for one fund and one cost centre were landing in a different fund. Two internal allocation accounts were affected, one revenue and one expense. Fund-level reports were wrong for both funds.
Existing architecture
The model eliminates internal allocations through a dedicated elimination cube. Each elimination row has a linked filter that selects the source data, and separate attributes that set where the elimination posts: the account, the cost centre and the fund.
Why it happened
We checked the net zero list sheets and the account setup first. Neither caused the problem.
The cause sat in the elimination cube. On the two rows for this fund, the linked filter pointed to the correct fund, but the destination fund attribute pointed to another fund. The source and the destination are two independent fields, and on these rows they disagreed.
Design decision
We corrected the destination attribute on the two rows and changed nothing else. No formula, loader or account needed to change, so we kept the fix as small as the cause.
Implementation approach
- Confirm the exact combinations that post wrongly: fund, account and cost centre.
- Rule out the mapping sheets and the account configuration.
- Open the elimination rows for the fund and compare the source filter with the destination attributes.
- Correct the destination in the sandbox tenant.
- Ask the finance owner to validate both accounts before promotion.
Controls and validation
The fix went into the sandbox tenant first. Promotion to production waited on user acceptance testing by the finance owner who reported the issue.
Outcome
The destination attribute was corrected in a controlled test environment. Finance validation and production promotion follow.
Lessons learned
- When an elimination posts to the wrong place, check the destination attributes on the elimination row first.
- The filter that selects the data and the attribute that sets the destination can point to different members. Review both when a row is created or copied.
Scope of the outcome
Root cause identified and corrected in a test environment; production deployment not asserted.
EPMLogic | Implementation insight based on an anonymized scenario. Exact operational amounts and client details are intentionally omitted.