Sponsored Research Administration Software: Why Your Award Portfolio Only Looks Reconciled

The award that closed while nobody was looking

A department administrator opens a report in the second week of October and finds a federal award whose period of performance ended in July. Salary is still posting to it. Two graduate research assistants were moved onto the award in June by a payroll action that never routed through the research office, and the spring effort certification was signed by a proxy who had no idea what the salary distribution actually said. The final financial report is due inside the 120 day closeout window in the Uniform Guidance. The fix will require cost transfers, the cost transfers will require written justifications, and the justifications will be read by an auditor who has seen this exact pattern at four other institutions this year.

None of that was fraud. It was a system boundary. The award lives in the research administration system, the salary lives in HR (Human Resources) and payroll, the expenditure lives in the ERP (Enterprise Resource Planning) general ledger, and the effort certification lives in a fourth place that reads a stale snapshot of the third. Every institution running a serious federal portfolio has this shape. Every institution has the same quiet answer to it: three or four people who reconcile it by hand and who are the only ones who understand why the numbers differ.

Why off the shelf research suites stop short

The named systems are real products doing real work, and it is worth being precise about where they end. Huron Research Suite is deep on compliance workflow and IRB, IACUC and conflict of interest review, but the configuration model is specialised enough that every change to a routing rule becomes a scoped engagement, and the financial side still depends on whatever you build to talk to your ERP. Kuali Research gives you a genuinely capable pre award module and source code you control, at the cost of owning the integration and upgrade burden yourself, which many institutions discover a year in. InfoEd Global covers an unusually broad module list, but the modules grew up at different times and a principal investigator moving between proposal development and progress reporting feels it. Cayuse is strong at proposal preparation and system to system submission to Grants.gov and Research.gov, and thinner once the award is active and the question becomes whether a specific salary charge is allowable against a specific budget line.

None of them is wrong. What none of them does is hold your institution's indirect cost rate agreement, your salary cap logic, your cost share commitments and your payroll distribution in one model that agrees with the ledger every night. That is the part your staff are doing manually, and that is the part worth building.

Effort certification is a signature on a number nobody can trace

Effort certification exists because federal salary charges have to be supported. The Uniform Guidance stopped prescribing a specific method, which institutions read as freedom and auditors read as an invitation to ask how you know. The common implementation is a period end statement generated from a payroll extract, sent to a faculty member who is in the field, certified by a proxy, and filed. If a cost transfer lands after certification, the statement is now wrong and almost nobody recertifies.

The build that fixes this treats certification as a reconciliation, not a form. The statement shows the payroll distribution alongside the committed effort from the proposal and the current award budget, flags the delta before it is sent, and refuses to generate a clean statement for a period that has an open cost transfer. Where an NIH award is involved, the salary cap is applied at the distribution level and the over the cap portion is carried on a companion cost centre automatically, because doing that by hand is exactly where the audit finding lives. Recertification triggers when a retroactive change touches a certified period, and the audit trail keeps both versions rather than overwriting the first.

Subrecipient monitoring is an email folder with legal exposure

You are responsible for your subrecipients under the Uniform Guidance. That means a risk assessment before the subaward is issued, a check that they are not suspended or debarred, collection of their Single Audit report if they have one, and evidence that somebody actually looked at their invoices rather than approving them because the PI said the work happened. At most institutions this lives in a shared mailbox, a spreadsheet of subaward numbers, and a filing convention that changes when the person changes.

What a build does here is small and high value: a subaward record that carries the risk tier, the reporting cadence that tier requires, the FFATA reporting status, the invoice history against the subaward budget, and the technical progress report attached to the invoice that approved it. Invoices that arrive without a matching progress report do not reach the PI queue. Cumulative invoicing over the subaward budget is blocked rather than flagged after the fact. When the auditor asks how you monitored a $400,000 subaward at a small college, you export the record instead of reconstructing it.

Cost sharing is a promise made in a proposal and forgotten in month three

Somebody committed twenty percent of a co investigator's effort as mandatory cost share to win the award. That commitment now has to be met, documented, and reported, and if it is not met the sponsor can reduce the award. In practice the commitment lives in a proposal PDF, and the actual cost share is assembled at report time by asking departments what they think they contributed.

Model it properly and the problem disappears: the commitment becomes a tracked obligation on the award with a source of funds, effort commitments feed the same distribution engine that drives certification, third party in kind contributions get a valuation and a supporting document, and the fulfilment percentage sits on the award dashboard next to the spend rate. Unrecovered indirect costs used as cost share are calculated from your own rate agreement rather than from somebody's memory of it.

What the build has to include to be worth doing

• A proposal routing chain that mirrors your actual approval order, including the department chair, the centre director for joint appointments, and the dean, with electronic signature and a hard stop for missing conflict of interest disclosures.
• Budget building that applies your own negotiated indirect cost rate agreement, the correct base by activity type, and escalation by budget period, with an automatic modular budget view for the sponsors that require one.
• Award setup that creates the ledger accounts in the ERP rather than emailing finance to do it, carrying the terms that matter downstream: expanded authorities, prior approval requirements, allowable cost exceptions.
• Payroll distribution reconciled nightly against the ledger, with the salary cap and cost share components computed rather than typed.
• Subaward issuance from the FDP template set, with amendment history and the monitoring record attached to the same object.
• Closeout as a checklist with owners and dates, driven backwards from the 120 day deadline, showing open encumbrances, unbilled cost and the residual balance disposition.
• A PI facing view that answers the only three questions a PI ever asks: how much is left, how long do I have, and can I pay this person from it.

What it costs and how long it takes

From Digital Heroes delivery experience across more than 2,000 projects, the honest shape for research administration work is this. A first release covering award financial management, payroll distribution reconciliation and effort certification runs $90,000 to $180,000 over 14 to 20 weeks. That is the piece that removes the manual reconciliation and the piece auditors care about most. The full platform adding proposal development and routing, budget building against your rate agreement, subaward issuance and monitoring, cost sharing and closeout runs $250,000 to $600,000 phased across 9 to 18 months.

What pushes the number up: the number of systems of record you must reconcile against, because Workday, Banner, PeopleSoft and Oracle Cloud each behave differently on retroactive payroll and each costs real weeks. Whether you have one indirect cost rate agreement or several by campus and activity. Clinical trial billing, if your academic medical centre wants it in the same platform, which is a separate discipline and should usually be a later phase. System to system submission to Grants.gov and Research.gov, which is a specification exercise, not a feature. And the number of legacy awards you must migrate mid life, which is always the ugliest part of the plan.

What keeps it down: starting with the active award population only, one campus, and the top three sponsors by expenditure. That covers most of your audit exposure and nearly all of your reconciliation labour.

Build, buy, or finish what you already bought

Buy if you administer a small portfolio, mostly foundation and state awards, with fewer than about forty active awards and no subrecipients. Cayuse or Kuali will hold it and a custom build would be an expensive way to feel modern. Buy also if you are mid implementation of Huron or Kuali. Half configured systems look like software failures and are usually project failures, and building a second system next to the first makes the reconciliation problem worse rather than better.

Build when two or more of these are true. Your federal expenditures put you in a Single Audit every year. Effort certification and payroll do not reconcile without a human. Subaward monitoring evidence would take a week to assemble. You carry cost sharing commitments across dozens of awards and cannot state the fulfilment percentage today. Or your research office has become the integration layer between four systems, staffed by people whose actual job was supposed to be helping faculty win grants.

How to choose a developer for research administration software

Ask them to draw the data model on a whiteboard before you sign anything. The correct picture has proposal, award, project or fund, budget period, and account as separate objects with their own lifecycles, because a single award routinely carries multiple projects with different end dates. A developer who models an award as one row with a start and end date has not done this and will discover the problem in month four of your project.

Ask how they will handle a retroactive payroll change that lands after an effort statement is certified. The answer should involve recertification triggers and version retention. If the answer is that the statement gets updated, walk.

Ask which ERP payroll interface they have actually written against, by name and version. Workday's approach to retroactive costing allocations is a different engineering problem from Banner's, and anyone who says integrations are integrations has not written either.

Ask who owns the code, the repository and the cloud accounts, and get it in the contract before kickoff. At Digital Heroes the institution owns everything from the first commit, including the right to hire someone else to continue the work. In a sector where research administration staff turn over and vendors get acquired, that ownership is the only real continuity you have.