NYC Indirect Cost Rate: Policy Traps That Drain Budgets

It is a rate applied to a defined cost base, within an eligible contract, through a budget that an agency has accepted and processed.

The distinction produces the core of NYC nonprofit indirect cost rate reimbursement gaps. A provider can hold a City Accepted ICR, submit an allowable budget, and still see less indirect-cost cash than its headline rate suggests. The losses are usually not hidden. They sit in the denominator, the excluded-cost rules, the contract budget, or the modification queue.

The original City ICR Funding Initiative established Accepted ICRs for 361 organizations and baselined $94 million annually. That was a material change in municipal contracting practice. It was not a universal settlement of nonprofit overhead reimbursement in NYC.

The denominator trap: an ICR does not apply to the total contract value

An indirect cost rate is a ratio. Its numerator contains allowable indirect costs. Its denominator contains a defined direct-cost base. The percentage is therefore only meaningful after the base is identified.

Under the City’s Simplified Allocation Methodology, indirect costs are costs incurred for a common or joint purpose that cannot readily be assigned to one final cost objective but still benefit the contract. Executive management, finance, human resources, information systems, insurance, occupancy administration, and general compliance functions may fall into this category depending on the facts and the cost-allocation method.

The rate is calculated across the organization. It is not built from a single City award.

That organizational requirement matters. A provider cannot isolate a difficult HHS contract, load it with central-office costs, and calculate a City rate from that contract alone. Allowable direct costs from the organization enter the denominator. Allowable indirect costs enter the numerator. Unallowable costs do not become recoverable merely because they have been placed in an indirect pool.

The second constraint is the Direct Cost Base. The City’s methodology excludes several categories from that base, including:

• Capital expenditures and equipment costing more than $5,000.
• Rental costs.
• Participant-support costs.
• The portion of subcontract amounts above $25,000.
• Other items that would distort the base.

This is where simplistic reimbursement estimates fail. A $1 million contract is not automatically a $1 million indirect-cost base. If substantial spending sits in excluded categories, the base can be materially smaller.

A provider with a 15% City Accepted ICR and a contract containing $400,000 in excluded rental, equipment, participant-support, and excess subcontract costs does not receive 15% of the entire award. The rate attaches to the applicable base, not to the gross contract headline.

The rate is not the reimbursement. The rate is one input into the reimbursement calculation.

This is also the reason that an organization’s fiscal health cannot be assessed by comparing its Accepted ICR with its audited overhead ratio. The two measurements answer different questions. One describes a negotiated or accepted allocation methodology. The other may describe the organization’s cost structure under financial reporting rules. Neither figure independently predicts cash received from a particular City contract.

The de minimis disconnect: 10% in New York City is not 15% under federal rules

The City’s 10% de minimis ICR and the federal de minimis rate of up to 15% under Uniform Guidance are frequently placed in the same category. They should not be.

Federal rules permit eligible entities without a current negotiated rate to use a de minimis rate of up to 15% of Modified Total Direct Costs. New York City’s current default City de minimis rate is 10%. The applicable eligibility rules, cost bases, award terms, and exclusions can differ. A federal grant framework does not rewrite a City HHS contract budget.

The operational problem appears when a nonprofit uses the federal number as its planning baseline. That produces a five-point variance before any difference in the cost base is measured. For an organization running thin unrestricted reserves, the variance is not administrative. It is a structural budget exposure.

A second error is treating the City’s 10% figure as a guaranteed minimum payment. It is not a guarantee that every dollar of a contract will carry 10% indirect reimbursement. The organization still needs an eligible agreement, an applicable rate, an allowable cost base, a budget that reflects the rate, and agency processing.

There is a further distinction between the rate and actual expenses. City guidance states that agencies may use allowance funding to cover increases in Accepted ICRs where appropriate. Providers should not assume an allowance allocation where actual allowable expenses fall below the Accepted ICR or where direct-cost funding is surplus. A higher accepted rate does not automatically create a new funding stream.

The relevant planning comparison is therefore not “10% versus 15%.” It is more exact:

1. What is the organization’s City Accepted ICR or applicable de minimis rate?

2. Which contracts are actually within the applicable HHS policy structure?

3. What portion of each contract budget remains inside the Direct Cost Base?

4. Does the PASSPort budget reflect the rate during its validity period?

5. Are actual allowable indirect expenses sufficient to support the claimed amount?

This is slower than a gross-contract calculation. It is also the only calculation that measures the likely reimbursement gap.

PASSPort friction: the budget record controls the operational outcome

Indirect-cost policy is often described as an accounting issue. In City contracting, it is also a workflow issue.

An Accepted ICR may be used in PASSPort contract budgets only during its applicable validity dates. The rate must be translated into the contract’s budget structure. That translation is not cosmetic. A rate that exists in the provider’s files but is absent from an approved budget does not produce an invoiceable indirect-cost line.

PASSPort provides an automatic budget-modification route for cumulative changes of up to 10% of the total fiscal-year budgeted amount. This can reduce delay for qualifying adjustments. The threshold is useful, but it is not a general exemption from review.

Two limits remain:

• The 10% threshold is cumulative. Several small changes can exhaust it.
• Adding a new budget line or changing an item category triggers agency review regardless of the percentage.

The practical consequence is clear. A provider that discovers an indirect-cost shortfall late in the fiscal year may not have a simple administrative correction available. If the adjustment requires a new indirect category, shifts the classification of costs, or exceeds the cumulative modification threshold, the matter returns to agency review.

This is the operational layer behind many reported NYC ICR initiative delays. The delay may not be caused by the ICR calculation itself. It can arise from contract registration, budget alignment, agency review, amendment sequencing, invoicing controls, or the classification of costs inside PASSPort.

The distinction matters because corrective action changes with the cause. A finance team cannot solve an agency review queue by recalculating its overhead ratio. Conversely, a contract manager cannot solve an invalid cost allocation through a PASSPort modification.

PASSPort can accelerate a compliant modification. It cannot convert an ineligible cost into an allowable one.

The City Comptroller’s FY2024 review provides the cash-flow context. At seven of eight reviewed agencies, first payments to human-services providers arrived more than 200 days on average after the contract start date. That finding does not establish that delayed payments were indirect-cost reimbursement delays. It does establish that reimbursement timing is a material fiscal risk even where the budget is theoretically correct.

For providers with limited working capital, the distinction between “approved,” “budgeted,” “invoiceable,” and “paid” must be tracked as four separate compliance metrics.

FY2027: the default rate is a deadline consequence

The FY2027 City ICR cycle ran from September 24, 2025 through December 8, 2025. Organizations eligible to apply that did not apply or did not receive a City Accepted ICR by the deadline defaulted to the City’s 10% de minimis ICR.

Accepted rates established in that cycle are valid for FY2027 through FY2029. This makes the application cycle more than a routine filing exercise. It determines the rate framework available over a multi-year period.

The expired FY2024 Accepted ICRs referenced in the FY2027 process had a June 30, 2026 expiration date. A provider moving between rate periods should not assume that a prior rate continues indefinitely in every budget and contract. Validity dates are active controls. They should appear in the organization’s contract inventory alongside award dates, renewal dates, amendment status, and agency contacts.

The relevant risk is not merely defaulting to 10%. It is defaulting without a contract-by-contract map of the consequences.

A nonprofit may have:

• A 10% City de minimis rate for eligible City work.
• A separate federal framework for federally funded work.
• Contracts outside the HHS Cost Manual’s operative scope.
• Subcontracts or emergency arrangements subject to different treatment.
• Existing budgets carrying assumptions from an earlier rate period.
• Costs that are organizationally allowable but excluded from a contract’s direct-cost base.

These categories should not be combined in a single “overhead recovery” spreadsheet cell. They require separate fields.

A workable internal database begins with the contract as the unit of analysis, then connects that contract to the organization-wide ICR calculation. At minimum, the record should capture the agency, contract type, funding source, policy eligibility, applicable rate, rate-validity dates, direct-cost base, excluded-cost categories, PASSPort budget status, modification history, invoicing status, and cash receipt date.

This is not administrative excess. It is how an organization identifies whether a gap is caused by rate policy, base exclusions, missing budget entries, or payment timing.

Legislative limbo: a 20% proposal is not a current rate

Introduction 245-2026 would require a methodology using a 20% de minimis indirect-cost rate for covered nonprofit City service contractors, with alternatives that include a federal NICRA.

The proposal was introduced on January 29, 2026 and referred to the New York City Council Committee on Contracts. As reflected in the Council record dated July 31, 2026, it had no enactment date and no law number.

That status governs the analysis. The 20% figure is a proposed policy parameter. It is not an enacted City requirement, a current minimum, or a basis for billing current contracts at 20%.

The bill nevertheless matters. It identifies the policy direction under debate: whether the existing 10% default rate adequately reflects the administrative infrastructure required to deliver City-funded human services. But a discussion paper is not an appropriation, and legislative introduction is not contract authority.

Organizations should separate advocacy analysis from revenue recognition.

For advocacy purposes, a provider can model the difference between its actual allowable indirect cost structure, its City Accepted ICR, the 10% de minimis default, and the proposed 20% framework. The resulting figures can show the effect of under-recovery on compliance staffing, financial controls, technology, audit readiness, and central administration.

For budgeting purposes, the organization should use only the rate and contractual authority currently available to it. Building a FY2027 operating plan on a pending 20% rule would convert legislative uncertainty into a fiscal exposure.

The same restraint applies to sector-wide claims. There is no authoritative current figure establishing the total value of unreimbursed indirect costs across all NYC nonprofits in FY2026 or FY2027. There is also no single average City Accepted ICR that can stand in for the entire human-services field. Contract structures vary too widely.

The control point is not the headline rate

The policy trap is numerical. A nonprofit sees 10%, 15%, or a proposed 20% and assumes the percentage defines the outcome. It does not.

The outcome is produced by a chain: organizational allocation, allowable cost classification, defined direct-cost base, contract eligibility, budget configuration, agency modification, invoice processing, and payment timing. A break at any point creates a reimbursement gap.

The City’s ICR framework has improved the visibility of overhead as a legitimate contract cost. It has not eliminated the need for contract-level controls. Providers that manage the rate as a single annual compliance item will continue to miss losses embedded in budget exclusions and workflow delays.

The more reliable approach is a contract ledger built for variance analysis.

• Query contracts where the applicable ICR validity date ends before the contract end date or renewal date.
• Query all budgets in which the indirect-cost line differs from the organization’s currently applicable Accepted ICR or de minimis rate.
• Query contracts with large rental, participant-support, equipment, or subcontract amounts above $25,000; these are the highest-priority denominator reviews.
• Query PASSPort modifications approaching the 10% cumulative threshold and flag any change that introduces a new budget line or category.
• Query the interval between contract start, budget approval, first invoice, first payment, and final payment. Do not label the result an ICR delay without evidence.
• Query contracts outside the applicable HHS framework separately. Their overhead treatment cannot be inferred from the City HHS Cost Manual.
• Model the 20% proposal only as a policy scenario. Keep it outside current revenue forecasts until legal authority and contract implementation exist.