Mutual Aid Billing: From Handshake to Reimbursement

When help arrives, it feels like the hard part is over. A neighboring county sends a strike team, the state activates a compact, equipment and crews roll in, and the incident gets handled. The handshake happened. The mission ran.

But the handshake is not the transaction. The bill is the transaction — and if you never send it, or you send it without the records to back it up, the cost you incurred helping your neighbor (or the cost they incurred helping you) stays exactly where it landed. Mutual aid that is never properly billed isn't generosity. It's an unfunded liability sitting on someone's books.

This is the part of mutual aid that gets the least attention and loses the most money: the path from "help arrived" to "the providing agency got paid back." Here is what that path actually requires.

FEMA Pays the Requester — and Only If the Requester Was Charged

Start with the rule that surprises people. FEMA does not reimburse the agency that provided the aid. FEMA provides Public Assistance funding to the Requesting Entity — the jurisdiction legally responsible for the work — which then pays the Providing Entity. The aid flows one direction; the money flows back through the requester.

That means the receiving jurisdiction has to actually be charged for the aid. If your county sends a crew to help a neighbor and never bills them, FEMA has nothing to reimburse — there's no cost on the requester's books to fund. "We just helped each other out" is admirable and completely unreimbursable.

FEMA will reimburse mutual aid costs when four conditions hold:

• The agreement is in writing and in effect before the disaster. A handshake formalized after the incident doesn't qualify. The agreement has to predate the event.
• The receiving entity was actually charged. The cost has to exist as a real obligation, not an informal courtesy.
• The agreement contains no contingency clause. This is the trap. If your agreement says the providing agency gets paid "only upon receipt of FEMA funds," FEMA treats it as ineligible — because the receiving jurisdiction isn't genuinely obligated to pay. The obligation has to be real whether or not the federal money ever arrives.
• The costs are properly documented. Mutual aid work is held to the same eligibility standard as contract work: every cost tied to specific eligible work, adequately documented.

Most agencies clear the first three by having a sound agreement template on file. The fourth is where claims actually fail.

The EMAC Package: A Worked Example of the Standard

For interstate aid through the Emergency Management Assistance Compact, the billing path is formalized — and it's a useful model for what any mutual aid claim demands, even local intrastate aid.

Each EMAC mission generates a reimbursement package built on the R-2 intrastate form (or the R-1 interstate summary when an assisting state consolidates claims). That package isn't just a number. It includes the signed claim form, a cover letter stating the claim amount and remittance address, a W-9, and the part auditors actually scrutinize: source documentation — timesheets, payroll registers, equipment usage logs, receipts, and the salary, overtime, and per diem rate policies that justify every figure.

And it runs on a clock. EMAC operates on a 45-day cycle at every stage: deployed personnel submit records to their home agency within 45 days of returning; the resource provider forwards the package within 45 days; the assisting state audits and submits within 45 days; the requesting state pays within 45 days. One note worth underlining for the finance section: a state's obligation to pay EMAC reimbursement is not contingent on receiving federal funds. The compact pays regardless. FEMA reimbursement is a separate, downstream question.

Local and intrastate mutual aid rarely has paperwork this regimented — but the underlying requirement is identical. Whatever your agreement, you are eventually assembling a claim that says: this resource, for these hours, doing this eligible work, at these documented rates. The form changes. The evidence doesn't.

Where the 45-Day Window Goes Wrong

Here is the failure mode. The mission ends, everyone goes home, and the billing clock starts. Now someone in finance has to assemble a package proving who was deployed, what they did each Operational Period, how many hours they worked, and what eligible task each hour served — for resources that left days or weeks ago.

If that record was captured live, the package is an export. If it wasn't, the 45-day window becomes a reconstruction project: emailing crew leaders, reconciling memories against fuel receipts, guessing at start and end times. Every gap gets filled with an estimate, and FEMA disallows estimates. The eligible work was real. The proof evaporated.

The source records FEMA wants are the same records ICS already produces during operations. The ICS 211 check-in establishes who arrived and when. The ICS 214 activity log establishes what each resource did, shift by shift, tied to a specific task and Operational Period. The cost figures accumulate from those. When documentation is a byproduct of running the incident rather than a separate administrative scramble after it, the mutual aid package builds itself alongside the response.

That's the difference between tracking incident costs as operations unfold and doing cost archaeology in week three. Finance sections that see labor hours and equipment costs accumulating in real time — by resource, by Operational Period — already hold the package when the billing clock starts. The agencies still reconstructing are the ones leaving eligible dollars on the table, not because the aid wasn't real, but because they can no longer prove what it cost.

The Bill Is the Work

Mutual aid isn't finished when the strike team rolls home. It's finished when the providing agency is made whole — and that depends entirely on a bill that the records can defend.

So treat the agreement as the foundation, not the finish line: written, pre-existing, no contingency clause. Treat the billing package as a planned deliverable, not an afterthought. And treat the field documentation — check-in, activity logs, cost capture — as what it actually is: the evidence that turns a handshake into a reimbursement.

The help arrived. The work got done. Whether anyone gets paid back for it comes down to one question auditors will ask twelve months later: can you prove it?

---

See how NIMS Logic captures the resource and cost records mutual aid billing depends on — built live in the field, not reconstructed after the mission. Explore the platform.