Reimbursement or advance: which grants make you spend the money first
Last reviewed

Reimbursement or advance: which grants make you spend the money first

Some grants pay you before the work; most pay you back after it. The difference decides whether an organisation can accept an award at all, and almost no grant database records it as a field.

Two grants of the same size can be completely different propositions. One pays on award. The other pays after you have spent the money, filed a claim, and waited for it to clear review.

For an organisation with reserves, that is an accounting detail. For one without, it decides whether the award can be accepted at all — and it is almost never in the headline.

The field nobody stores

A grant record usually carries an amount, a deadline, an eligibility list and a description. Payment mechanism is not normally among them, even though it is one of the few facts that can make an award unusable for the applicant it was designed for.

We store it as its own field. A record is marked as reimbursement where the notice says costs are recovered after they are incurred, and as an advance where the notice says funds are provided up front. The two have their own glossary entries because they are read together: each is defined against the other, and a reader who has only met one of them will misread the other.

Where the notice addresses neither, the field says so. That matters more here than on most fields, because the default assumption in the sector is reimbursement, and encoding a common assumption as a stored value is how a database starts asserting things its sources never said.

What reimbursement actually costs

The gap is not just the claim cycle. It starts earlier than most planning allows for.

The period of performance — the window in which costs may be charged — usually begins some time after notification, and costs incurred outside it are normally unallowable however clearly they served the project. So the sequence for a reimbursement award is: win it, wait for the period to open, spend your own money, document it, claim, wait again.

An in-kind match interacts badly with this. In-kind contributions cost nothing up front and can be disallowed at closeout if the documentation does not satisfy the funder, at which point the shortfall becomes cash — on a reimbursement programme, cash you have already spent.

None of that makes reimbursement programmes bad. Most public funding works this way, and the mechanism exists to make sure money follows delivered work. It means the question to ask before accepting is a financing question, not a programme question: can we carry this, for how long, and against what.

What the rest of the category does

We surveyed the free surface of eight grant services on 2 September 2026 and found no reimbursement or payment-mechanism dimension in any of them — not as a filter, not as a displayed field, not as a facet.

Two are worth crediting on the adjacent ground. Grantsights ships a free deadline planner that builds a real backward schedule from a deadline, which is the closest free tool in the category to the cash-flow timing question. Candid's free 990 Finder is the most authoritative free layer on funder financials in the sector, and its compliance data is verified daily against six federal and state sources.

The absence is not evidence that the others are careless. Payment mechanism is a clause buried in award terms rather than a structured field on a portal, and extracting it costs more than copying an amount. It is exactly the kind of field that gets dropped when a listing is built for volume.

What we cannot tell you

We do not publish how many records in the catalogue are marked reimbursement, how many advance, and how many are silent. We hold the field; the breakdown is not on a public page, and a number's first appearance is not going to be in a blog post.

There is also a known limitation in our own schema, and it is more honest to state it than to let it sit. The reimbursement flag currently defaults to "not reimbursement" when a source says nothing, which means no and the source did not say are stored as the same value on this one field. That is the exact trap the match requirement field is built to avoid, and it is written up as a data gap rather than quietly carried. Until it is fixed, treat an unmarked record as unknown rather than as an advance programme, and read the notice.

Coverage is early besides: 832 records from 2 connected feeds as of 2 September 2026. Where a slice of the catalogue is large enough to publish, the field is shown on every row of it — grants open to state and local government is the slice where the reimbursement default bites hardest, because almost everything on it is a government award and almost every government award is paid in arrears.

If the timing rather than the mechanism is what you are planning around, the deadline planner works backwards from a deadline to the date each step has to be done, and which feeds are connected shows how quickly a change on the grantmaker's side reaches a record at all.

Sources

Field definitions

How we compare

In the catalogue

Read next

Author

avatar for GrantTrove Editorial
GrantTrove Editorial

Series

Reading a grant record

The four fields that decide whether an award is worth a week of your time, and what each of them means when the notice is silent.

Categories

More Posts

3

Newsletter

Join the community

Subscribe to our newsletter for the latest news and updates