Workday Multidimensional Position Management

A research coordinator at a state university is paid from three sources: forty percent from a federal grant, forty percent from a department operating budget, and twenty percent from a foundation gift. The grant ends in March. The department absorbs the difference. Six months later, finance asks why the effort report and the payroll journal disagree, and nobody can answer, because the position record in Workday only ever carried one cost center.

That is the problem multidimensional position management solves. It is not a feature you switch on. It is a configuration pattern in which the position object itself carries multiple funding, organizational, and reporting dimensions, so the funding story travels with the seat rather than with whoever happens to be sitting in it.

This article covers what the capability actually is, how it interacts with the staffing model decision you probably made years ago, what the configuration components are, how costing allocation resolves at run time, and where implementations go wrong. It is written for organizations of 1,000 employees or more where a single position is routinely funded from more than one place: higher education, health systems, state and local government, nonprofits, and research institutions.

What Multidimensional Position Management Means in Workday

Workday does not sell a licensed module called multidimensional position management. Be clear about that before you take a proposal to a steering committee. The term describes a design pattern built from standard Workday HCM components: the position management staffing model, position restrictions, worktags, default organization assignments, and position-level costing allocations, configured together so that a position carries more than one dimension of financial and organizational meaning at the same time.

A dimension in Workday terms is a worktag or an organization assignment attached to a transaction or an object. Cost Center, Grant, Gift, Program, Project, Fund, Function, and Location are all dimensions. Some are delivered organization types, some are custom organizations, and some are Financials-side worktags that become available to HCM objects once the two are provisioned together. When you attach several of these to a single position and allocate a percentage split across them, the position becomes multidimensional.

Standard position management gives you one seat with one set of restrictions and, typically, one default cost center inherited from the supervisory organization. That is sufficient when a position is funded from one place and stays there. It stops being sufficient the moment a position is split, because the split then has to live somewhere else: on the worker, in a spreadsheet, or in a payroll accounting adjustment after the fact.

The distinction matters operationally. Worker-level costing follows the person. Position-level costing follows the seat. If your grant-funded coordinator resigns and you backfill the position, worker-level costing leaves with them and the replacement defaults to the supervisory organization’s cost center until someone remembers to rebuild the split. Position-level costing survives the vacancy. That single behavioral difference is the strongest argument for the pattern, and it is the argument most implementations fail to make clearly.

Workday Staffing Models and Where Multidimensional Position Management Fits

Every supervisory organization in Workday is assigned a staffing model, and the model determines the level at which staffing limits, restrictions, and costing hooks exist. Workday’s own organization management datasheet describes position management as the model that carries budgetary control and commitment accounting. That sentence is the whole reason this article exists: multidimensional position management is only available under position management.

Job Management

Job management defines one set of hiring restrictions for an entire supervisory organization with no limit on how many jobs can be filled. There is no position object to hang dimensions on. You get flexibility and low administrative overhead, and you give up headcount control, position-level budgeting, and position-level costing entirely. It is a reasonable choice for high-churn contingent populations, adjunct pools, and per diem staff. It is the wrong choice anywhere funding is split.

Position Management

Position management creates a distinct position object with its own restrictions for every seat. This is the only model that supports position-level costing allocation, position budgeting, and position-level reporting on open, filled, frozen, and closed states. It costs you administrative effort, because somebody has to create and maintain every position. Use it where headcount is budgeted, funded externally, or subject to a collective bargaining agreement. Do not use it for populations where the seat has no independent existence.

Headcount Management

Headcount management sits between the two. You control a headcount group with a total number, and workers occupy slots within it, but individual seats do not carry their own restriction sets or costing. It suits large uniform populations, such as a call center or a hospital float pool, where you care about the total number and not about which specific chair is funded from where.

The Hybrid Model Applied Per Supervisory Organization

Because the staffing model is set per supervisory organization, most large US organizations run a hybrid. Faculty and staff regular sit in position management. Student workers, adjuncts, and temporary staff sit in job management. This is normal and supported. What it is not is free: reporting has to account for the fact that some populations produce position rows and some do not, and any headcount metric that assumes one row per seat will misstate the total. Before you commit to a model per organization, understand how Workday position restrictions behave under each one, because the restriction set is what actually enforces the control you are buying.

When a new supervisory organization is created beneath an existing one, it takes the superior organization’s staffing model by default, but changing the superior’s model does not cascade to existing subordinates. You have to change each one. Changing the model on an organization that already contains workers is where the difficulty concentrates. Moving from job management to position management requires that every existing worker be associated with a newly created position, and moving in the other direction discards position history that downstream reports and audits may depend on. Treat the staffing model decision as effectively permanent and plan the reorganization work accordingly.

The Business Case

The case for multidimensional positions is strongest where compliance obligations attach to the funding split rather than to the person. Under 2 CFR 200.430, charges to federal awards for salaries and wages must be based on records that accurately reflect the work performed, supported by an internal control system that gives reasonable assurance the charges are accurate, allowable, and properly allocated. The same section requires that nonexempt employees under the FLSA also have records of total hours worked each day. If your system of record cannot represent the split, your internal control story rests on spreadsheets, and spreadsheets are exactly what single audits find.

The burden this creates is documented rather than assumed. The Federal Demonstration Partnership’s faculty workload surveys, conducted in 2005 and again in 2012 across large samples of federally funded principal investigators, found that roughly 42 percent of the time investigators committed to federally funded research was spent on administrative activities rather than research. The Government Accountability Office reviewed federal efforts to reduce that load in GAO-16-573 and reported that universities and stakeholder organizations continued to cite increasing administrative workload and costs for complying with requirements, with limited results from streamlining efforts.

Neither finding tells you that Workday configuration fixes research administration. It does not. What they establish is that the administrative surface around split funding is large enough to be worth engineering, and that manual reconciliation is the default state most institutions are trying to escape.

The second part of the case is quieter and more reliable: position-level dimensions make vacancy costing correct without human intervention. In an organization with several hundred split-funded positions and normal turnover, the number of times per year someone has to remember to rebuild a funding split drops to near zero. That is a labor saving you can size from your own turnover data, which is more defensible than any vendor benchmark.

Core Configuration Components

Position Restrictions and What Each Restriction Controls

Position restrictions are the attribute set attached to the position object that determines what a valid hire into that seat looks like. They are created by the Create Position business process and amended by Edit Position Restrictions. The commonly configured fields are:

• Job profile and job family, which drive FLSA exempt status, compensation eligibility rules, and job-based security
• Worker type and worker sub-type, which separate employee from contingent worker and drive downstream payroll eligibility
• Time type, scheduled weekly hours, and default weekly hours, which produce FTE
• Location and business site, which drive tax jurisdiction, holiday calendar, and time profile
• Compensation grade and grade profile, which constrain the offer range
• Availability date, earliest hire date, and position availability, which control when the seat can be filled
• Company, cost center, and any additional organization assignments carrying dimensions

Set restrictions to the loosest value that still enforces a control you actually need. Every restriction you tighten becomes a rejected staffing action later, and rejected staffing actions become HR service tickets. The exception is any restriction tied to a compliance obligation, such as job profile driving FLSA classification, where tight is correct.

Worktags and Allocation Dimensions

Worktags are the mechanism by which a position carries dimensions beyond its organization assignments. Some are related worktags that populate automatically: assigning a Grant will typically pull in the associated Fund, Function, and Program depending on how the Financials chart of accounts is configured. Others must be assigned explicitly. The behavior you need to test in a sandbox tenant is what happens when a driver worktag changes on an existing allocation line, because related worktags update with it and the resulting journal lines will differ from what the requester expected.

Default Organization Assignments

Every supervisory organization can carry default organization assignments that flow to positions created within it, and positions can override them. This inheritance is convenient and it is also the most common source of silent misallocation, because a position created before an organization default was corrected keeps the old value indefinitely. Build a report that compares position-level organization assignments against the current supervisory organization defaults, and run it after every reorganization.

Position Budgeting and Headcount Controls

Position management supports tracking positions as open, filled, frozen, and closed, and supports budgetary controls tied to those states. Freezing a position prevents new hires against it without deleting it, which is the correct action for a seat you are holding through a hiring pause. Closing a position removes it from availability permanently. Neither action corrects a restriction or costing problem; if you unfreeze a position with a bad allocation, the bad allocation comes back with it.

Effective Dating Behavior

Position restrictions, costing allocations, and organization assignments are all effective dated, and they are dated independently of each other and of worker events. A position restriction change effective the first of the month and a job change effective the fifteenth produce two different states, and reports run as of different dates will legitimately disagree. Decide early whether your convention is pay period start dates or calendar dates, write it down, and enforce it in the business process definition rather than in training material.

How Position Level Costing Allocation Works

Costing allocation is where HCM configuration becomes an accounting entry. The position, its worktags, and its allocation percentages feed the payroll costing process, which produces the journal that posts to the ledger.

The HCM and Financials Boundary

The dimensions available to a position come from the Financials side of the tenant. If you have provisioned Workday Financial Management alongside Workday HCM, Grant, Gift, Fund, Program, and Project worktags are natively available and payroll costing results post directly. If your general ledger is a third party system, you can still configure cost centers and custom organizations in HCM, but the worktag set is narrower and the posting happens through an outbound integration, which means someone owns a reconciliation between what Workday allocated and what the ledger recorded. Organizations running a third party GL or a third party payroll should scope that reconciliation as part of the project, and treat Workday integration design and stabilization as a first-class workstream rather than a downstream task.

Costing Allocation Levels and Their Precedence

Workday resolves costing from the most specific applicable level to the least specific. In practice the levels you will use are position restrictions costing for unfilled positions, worker and position costing for a filled seat, worker and position and earning costing for a specific pay component, and organization-level default costing as the fallback. Payroll input overrides and period activity pay costing sit above all of these for the transactions they apply to. Verify the exact precedence order in your tenant before design sign-off, because it interacts with your payroll configuration and with which levels you have enabled.

The Practical Consequence of Allocating at the Wrong Level

Allocating at worker level when you meant position level is the error that costs the most to unwind. It works perfectly while the incumbent is in the seat and fails silently the moment they leave, because the allocation departs with the worker and the vacant position falls back to the organization default. The reverse error, allocating at position level for a split that is genuinely personal, such as an individual’s temporary assignment to a special project, produces a funding split that incorrectly persists to the next incumbent. The test is simple: ask whether the funding belongs to the work or to the person. Fund the position when the answer is the work.

Implementation Approach

Discovery and Data Readiness

Start by counting. How many positions are split today, across how many dimensions, and where does that split currently live? In most organizations the honest answer is a departmental spreadsheet and a payroll accounting adjustment cycle. Extract the current splits, reconcile them against the general ledger for at least two closed periods, and resolve the differences before you design anything. Splits that do not total 100 percent, splits pointing at expired grants, and splits attached to terminated workers are all normal findings and all have to be cleaned before load.

Tenant Configuration Sequence

Configure in dependency order. Foundation data organizations first: companies, cost centers and hierarchies, custom organizations, locations, and the worktag types you intend to use. Supervisory organizations next, with staffing models assigned deliberately rather than inherited by accident. Then job profiles, job families, and compensation grades, because position restrictions reference them. Then business process definitions for Create Position, Edit Position Restrictions, and Assign Costing Allocation, including the security groups on each step. Only then create positions. Organizations retrofitting this pattern into a live tenant rather than building it during an initial deployment should scope it as targeted Workday configuration enhancement work, because the sequencing constraints are tighter when live data already exists.

Data Loading

Load with EIBs in the same dependency order, and load in waves rather than all at once. Position restrictions load through the Put Position Restriction service, costing allocations through Assign Costing Allocation. Load positions before workers, and costing allocations after positions but before the hire events that will reference them. Validate each wave in a sandbox refreshed from production, not in an implementation tenant with synthetic data, because stale reference values in a sandbox are the single most common cause of a load that passes in test and fails in production.

Validation and Reporting Checks

Build these before go-live, not after:

• Every active position has allocation lines totaling exactly 100 percent for every effective-dated period
• No allocation line references a grant, gift, or project whose funding period has expired
• Position organization assignments match current supervisory organization defaults, with documented exceptions
• Headcount by supervisory organization reconciles between a position-based report and a worker-based report
• FTE totals reconcile to budgeted FTE by cost center

Choosing the right report data source matters more than the report design here, so confirm which advanced Workday report data sources return position rows versus worker rows before you build the reconciliation.

Change Management for Managers

Under position management, a manager who previously hired against an open headcount now has to request a position and wait for it. That is a real change in their day and it will generate resistance if you present it as a system upgrade. Present it as what it is: the seat now has a funding record attached to it, and the approval exists because someone has to confirm the money. Train the position request path, the expected turnaround, and the specific exception cases before go-live.

Common Failure Points and How to Avoid Them

Restrictions set too tightly is the most frequent one. A position restricted to a single job profile and a single location blocks a lateral transfer that everyone agrees should proceed, and the fix requires an Edit Position Restrictions event that the manager cannot initiate. Set restrictions to the loosest value that enforces a real control.

Allocation percentages that do not total correctly cause payroll costing to route the remainder to a default account nobody monitors. Run the totaling check as a scheduled report, not a one-time validation.

Effective date misalignment between position events and worker events produces reports that disagree with each other and both are correct. Standardize on pay period boundaries where payroll is involved.

Security domain gaps block managers from actions the design assumed they could take. The position creation domains, the restriction edit domains, and the costing allocation domains sit in different functional areas and are granted to different groups. Use the View Security for Securable Item report against each task in your process before go-live rather than discovering the gaps through tickets.

Headcount double counting appears when a worker holds multiple positions and a report counts position rows as people. Decide whether your headcount metric is primary-position based or all-position based, publish the definition, and use it consistently in IPEDS submissions, board reporting, and functional expense reporting alike.

Most of these surface in the first two payroll cycles after go-live rather than during testing, which is why post go live Workday stabilization capacity should be planned into the schedule instead of borrowed from the project team after they have rolled off.

Who Should Not Use It

If every position in your organization is funded from exactly one cost center and always has been, this pattern adds administrative overhead and returns nothing. A single default organization assignment on the supervisory organization does the same job with none of the maintenance.

If your workforce is dominated by high-churn, short-tenure, or pooled populations where the seat has no independent existence, position management itself is the wrong model and the multidimensional layer compounds the mistake. Job management or headcount management will serve you better.

If you have no Workday Financials and no near-term plan to integrate a third party ledger, you can configure the dimensions but you cannot complete the accounting loop, and you will build a parallel reconciliation you did not budget for.

And if your current funding splits are not reconciled to the ledger today, fix that first. Loading unreconciled splits into a system of record does not correct them; it makes them harder to see.

Frequently Asked Questions

What is the difference between position management and multidimensional position management in Workday?

Position management is a delivered staffing model. Multidimensional position management is a configuration pattern built on top of it, in which a single position carries several funding and organizational dimensions with allocation percentages. Workday does not license it as a separate product, so do not go looking for it on a price sheet.

Can staffing models be changed after go-live?

Yes, but the cost rises with the population in the organization. Moving to position management requires creating a position for every existing worker and associating them correctly. Moving away from it discards position history that reporting and audit may depend on. Plan the model as a long-term decision rather than something you will revisit.

Can a single position be funded from more than one grant or cost center?

Yes. That is the point of the pattern. You assign multiple allocation lines to the position, each carrying its own worktag combination and percentage, and the lines must total 100 percent for every effective-dated period.

How do position-level costing allocations interact with worker-level allocations?

Workday resolves from most specific to least specific, and worker-level allocations sit above position-level allocations for a filled seat. Use worker level for splits that belong to the individual, and position level for splits that belong to the job. Mixing the two without a documented rule produces allocations that nobody can explain six months later.

What happens to open positions when a supervisory organization is reorganized?

Positions move with the reorganization event, but organization defaults on the receiving organization do not retroactively overwrite dimensions already assigned to the position. That is usually what you want and occasionally not. Reconcile position organization assignments against the new defaults after every reorganization.

Does this require Workday Financials?

Not strictly, but the useful version of it does. Without Financials, the worktag set available to positions is narrower and posting to the general ledger happens through an outbound integration you have to build and reconcile. With Financials, grant, gift, fund, and program dimensions are natively available and costing results post directly.

How does headcount reporting change once positions carry multiple dimensions?

Position rows and worker rows stop being interchangeable. A worker in two positions produces two position rows. Any report that filters or groups by a dimension will also split a single worker across multiple lines when their funding is split. Define whether each published metric counts people, positions, or FTE, and label it on the report.

What security domains control who can create and edit positions?

Position creation and restriction edits are governed by domains in the staffing functional area, while costing allocation entry is governed separately under payroll. Domain names vary across tenant versions, so confirm yours by running View Security for Securable Item against each task in your business process rather than working from a list.

How are position restrictions inherited by the worker on hire?

Job profile, worker type, time type, scheduled hours, location, and compensation grade default from the position restrictions onto the worker record during the Hire business process. Some fields are editable at hire depending on your business process configuration, which means a restriction can be satisfied at validation and then overwritten in the same transaction. Lock down the editable fields you care about.

What drives the implementation timeline?

Data cleanup, not configuration. Configuring the components takes weeks. Reconciling existing funding splits against the general ledger, resolving expired grants, and agreeing on the position versus worker allocation rule takes months in most organizations. Size the project from the state of your current splits, not from the length of the configuration checklist.

Where to Start

Pull a list of every worker whose pay was charged to more than one funding source in the last two closed pay periods, and find out where that split currently lives. If it lives in Workday at the worker level, you have a vacancy problem waiting to happen. If it lives in a spreadsheet or in a post-payroll accounting adjustment, you have both a control problem and a reconciliation problem.

That list, reconciled against the general ledger, is the input to every subsequent decision: whether the pattern is worth the overhead, which supervisory organizations need position management, and how much data cleanup sits between you and a design session. It is a query, not a project, and it will tell you more about feasibility than any assessment will.