Grants and Student on Workday: the modules where programs stall

The FDM replaces a segmented chart of accounts with worktags. You choose a driver worktag (grant, gift, project), and the related worktags fill in by themselves: fund, function, class, program. For a grant, picking the grant driver should pull the restricted sponsored fund, the organized-research function and the funding-source class automatically, so a principal investigator (PI) or a department can't hand-pick the wrong fund.

The design mistakes are predictable:

• Replicating the legacy chart of accounts as hundreds of worktag values.
• Function coding that doesn't cleanly separate organized research from instruction, which corrupts the F&A rate proposal later.
• Failing to plan the two grant hierarchies (see GRT 120).
• Company and worktag mismatches. An expense booked to a different company than the award line drops off the sponsor invoice until someone moves it.

Facilities and Administrative recovery (F&A, Workday's term for indirect cost) is governed by federal cost principles. Workday calculates and posts it automatically off the award line's rate agreement.

Indirect cost is charged as a percentage of Modified Total Direct Cost, and that base leaves out seven kinds of cost. If equipment, tuition remission, patient care or the first-$25,000-per-subaward rule aren't flagged as non-overhead-bearing, Workday burdens them with F&A and over-bills the sponsor. It's a classic exception.

The money at stake is real. Universities recover only 25 to 30% of a project's total cost through their negotiated rate, and they reported a $6.8 billion under-recovery of indirect cost in a single year. A misconfigured base makes a thin recovery thinner.

Users never pick a ledger account. They pick worktags, and the account posting rule set maps the grant worktag bundle to the ledger behind the scenes. Because the grant shares the FDM with core Financials, sponsor billing, receivables, deferred revenue and revenue recognition all run natively on the award. There's no separate subledger to interface every night.

The benefit is that a whole class of interface-reconciliation failures goes away. The cost is that a bad rule-set entry posts with no error. On a real go-live, salary-cap transactions posted to grant-related funds when they should have gone to an institutional fund. That posting-rule defect took an exception report and a mass correction to fix. No user could have fixed it.

Salary is the largest cost on most awards. It flows from HCM appointments through payroll costing onto grant worktags, and effort certification is generated from that payroll distribution. The control object is the Payroll Costing Allocation: which grants a worker's salary charges, in what proportion, with effective dates. For an NIH award, Workday auto-splits pay above the salary cap onto a cost-share fund. If actual effort differs from the payroll distribution, commonly by more than a 5% institutional tolerance, the department has to run a Payroll Accounting Adjustment to move the charge before it can certify.

One institution's own published defect notes show where it breaks. Retro pay posts to the current costing allocation instead of the one in effect for the retro period, which undercharges the grants that should have carried the cost. The salary-cap engine misfires on non-standard pay. Mixing up the correction tools (a Payroll Accounting Adjustment versus a funding transfer) creates a second problem on top of the first.

Late cost transfers are the number-one audit theme. Auditors hold you to the 90-day standard, and "staff shortages" is explicitly an unallowable justification for a late transfer. A slow award-setup backlog after go-live manufactures exactly those late transfers. The consequence is on the record: one health science center paid $13 million to settle a False Claims Act case rooted in inaccurate effort tracking and inadequate internal controls.

At research institutions and academic medical centers, money arrives two ways that look similar and behave in opposite ways. A gift is a donation with no performance obligation, and contribution revenue is recognized when the unconditional promise is made. A sponsored grant carries a performance obligation. When it's conditional or a reimbursement, revenue is recognized only as it's earned, often only after the expense is incurred, and unearned money goes back to the sponsor.

They take different worktags, different funds and different revenue rules. Model them the same way and both restricted-fund reporting and revenue recognition break.