Stacking Federal Programs Without Tripping the 100% Rule
Almost every meaningful capital project on reserve in 2026 carries two or three federal contribution agreements layered on top of each other. That stacking is necessary, the budgets are too large for any single program. It is also where audit findings, clawbacks and reputation damage most often originate.
The rule is simple to state and difficult to live by: total government assistance, federal plus provincial plus municipal, cannot exceed 100% of eligible costs on any single activity. The hard part is proving, line by line, three years after substantial completion, that no cost was reimbursed twice.
Recent context
Weekly Voice on 2026 implementation challenges
The governance and PM angle
Stacking risk is not a finance problem in isolation. It is a project-controls problem. The cure is a single, auditable cost ledger that maps each invoice line to a specific eligible-cost category in a specific contribution agreement, with no double-counting allowed at source.
How XNM helps
XNM builds the stacking architecture before applications are submitted: an eligible-cost matrix per program, a master WBS that all agreements key to, and a claim sequence that holds the strongest-recourse program in reserve. We treat the auditor's eventual question as the brief from day one.
Practical takeaways
Map first, apply second. Build the eligible-cost matrix across all candidate programs before drafting any application.
One ledger, one truth. A single project cost ledger with program-coded line items beats reconciling three sets of books later.
Sequence the claims. Draw on the most restrictive program first and keep flexible dollars for surprises.
Disclose proactively. Tell each funder what other dollars are stacked. Surprises in audit cost more than disclosure does upfront.
FAQ
Is 100% stacking always permitted?
Most ISC infrastructure agreements allow stacking up to 100% of eligible costs. Some programs cap federal contribution lower. Always check the specific terms and conditions, not the general policy.
What is the most common audit finding?
Same invoice claimed against two programs for two different cost categories, when the cost was actually one indivisible service. A clear WBS prevents this.
How far back can a clawback reach?
Recovery rights typically extend through the retention period in the agreement, often six or seven years. Treat records accordingly.
The bottom line
Stacking is a tool, not a trick. The communities that win in 2026 will be the ones whose project-controls discipline matches the ambition of their funding stack. That is governance work, and it pays back many times over when the audit letter arrives.