Why ERP Reports Fail Research Administrators

Every institution running federal awards has an ERP. Workday, PeopleSoft, Banner, Kuali, Oracle Cloud — the system of record exists, it is well implemented, and it is accurate. And yet almost every sponsored programs office also maintains a set of spreadsheets alongside it.

That is not a failure of discipline. It is a mismatch between what the reporting layer produces and what post-award administration actually needs.

Reports answer what happened. Administration asks what will happen.

An ERP report tells you what has been posted. It reconciles to the general ledger, it satisfies the auditor, and it is correct as of the close date. But award management is a forward-looking exercise: will this award exhaust its budget before the period end date, is there enough salary runway for the personnel committed to it, will there be unspent balance at closeout that has to be returned.

Those questions require projection — burn rate against elapsed time, committed effort against remaining months, encumbrances layered on top of actuals. Standard reports do not model any of that, because that is not what they were built to do.

The gap gets filled by hand

So the administrator exports the report, drops it into a spreadsheet, adds the columns the report does not have, and answers the question manually. Once that spreadsheet exists, it becomes the operational system — and the ERP becomes the compliance system. Two systems, one portfolio.

The fix is not a better report. It is a layer that takes the ERP's authoritative data and answers the operational question directly.