A developer cost certification often becomes most consequential after the construction activity has slowed. At that point, lenders, housing agencies, investors, and asset-management teams need more than a budget-to-actual comparison. They need support for the final development cost, a clear explanation of variances, and confidence that the costs presented are eligible under the governing financing and program documents.
For affordable-housing developers and owners, this process can affect the release of retainage, the calculation of eligible basis, the recognition of developer fees, permanent loan conversion, and the closeout of public subsidies. A well-prepared certification is therefore not simply a formality. It is a financial accountability document that must withstand review by parties with different interests and different reporting standards.
What Developer Cost Certification Actually Establishes
A developer cost certification is a representation of the actual costs incurred to develop or rehabilitate a property, supported by underlying accounting records, contracts, invoices, payment evidence, and financing documentation. The required format, scope, and level of independent review depend on the project’s capital stack and the requirements of the lender, allocating agency, investor, or government program.
The certification commonly reconciles approved development costs to actual expenditures by cost category. Those categories may include acquisition, hard construction, architect and engineering fees, legal costs, financing fees, reserves, developer fees, syndication costs, and other soft costs. It also identifies project funding sources, including debt, equity, grants, tax credit equity, and deferred fees.
The central question is not merely whether money was spent. Reviewers are evaluating whether the cost was incurred for the project, properly classified, adequately supported, and allowable under the relevant agreements. A cost can be valid from a business standpoint but still be excluded from a particular program calculation or fee determination.
That distinction is particularly important for projects with layered financing. A cost treatment accepted by a construction lender may not produce the same result under a housing agency’s cost-certification instructions, a tax credit partnership agreement, or a HUD-related program requirement.
Why Cost Certification Deserves Early Attention
The quality of a final certification is largely determined long before the final draw. Organizations that wait until project completion to organize their records often face avoidable delays, unsupported adjustments, and difficult conversations about costs that cannot be traced cleanly to the general ledger.
A disciplined process begins with the development budget and chart of accounts. Project costs should be coded consistently with the categories that will ultimately appear in the certification. If the accounting system combines several distinct types of soft costs into a single account, the finance team may be forced to reconstruct detail from invoices months later. That work is expensive, disruptive, and more vulnerable to error.
The project team should also maintain a current reconciliation between the construction budget, lender draw schedule, general ledger, accounts payable activity, and sources-and-uses statement. Each record serves a different purpose. Together, they create the audit trail necessary to explain why the final cost differs from the approved budget or from prior draw submissions.
For related-party transactions, documentation should be especially clear. Developer affiliates may provide construction management, property acquisition, consulting, or other services. These arrangements are not inherently problematic, but they receive close scrutiny. Written agreements, board or manager approvals, allocation methodologies, invoices, payment records, and evidence of compliance with program limits should be retained from the outset.
The Documents Behind a Credible Certification
A certification package should tell a coherent story from original approval through final completion. That requires more than a ledger export. The strongest packages connect each significant reported amount to the agreement, invoice, payment, and accounting entry that support it.
For construction costs, support often includes executed contracts, change orders, contractor applications for payment, architect certifications where applicable, lien waivers, invoices, and proof of payment. For soft costs, the relevant support may include engagement letters, legal invoices, engineering agreements, financing statements, insurance documentation, and evidence of payment.
Developer fees require particular care because their treatment varies by transaction. The governing documents may establish a maximum fee, specify when the fee is earned, defer some portion of payment, or limit the amount that is includable in a specified cost base. The accounting treatment, cash payment history, and certification presentation should align with those requirements.
Sources require equally careful reconciliation. A final cost certification that does not agree to the financing sources can raise immediate questions about unspent proceeds, equity timing, deferred obligations, sponsor contributions, and funds held in escrow. The balance sheet, project bank account activity, partnership records, and closing statements should be considered together rather than in isolation.
Cost eligibility is not a one-size-fits-all determination
Eligibility depends on the specific program and agreement. A cost may be eligible for reimbursement under one funding source but excluded from eligible basis, a grant calculation, or a maximum development cost test. Similarly, timing matters. Costs incurred outside an approved project period, without required prior approval, or after a contractual cutoff may receive different treatment even when they relate to the project.
This is why the project’s finance leadership should identify the controlling requirements early. The operative documents may include loan agreements, regulatory agreements, subsidy contracts, tax credit allocation documents, investor agreements, and agency cost-certification guidance. When requirements conflict or use different definitions, the team needs a documented approach for each reporting purpose.
The CPA’s Role in Developer Cost Certification
The phrase “cost certification” can describe several different engagements. In some cases, a developer signs a certification and a CPA performs agreed-upon procedures or provides an accountant’s report in a prescribed form. In other situations, an agency, lender, or investor may require an audit or another form of assurance. The required report language, testing procedures, and independence considerations should be confirmed before fieldwork begins.
An experienced CPA can help management prepare for the engagement by identifying reconciliation gaps, reviewing the proposed schedule against the required format, and clarifying the documentation that will be needed for material costs. Once engaged to perform independent procedures, however, the CPA’s work must remain distinct from management’s responsibility for the representation itself.
That separation matters. Management is responsible for maintaining the books and records, preparing the cost schedule, and making the certification. The CPA evaluates information within the scope of the engagement and reports findings or an opinion in accordance with the applicable professional standards and the requesting party’s requirements.
For boards, audit committees, and finance leaders, this independent perspective can be valuable beyond the immediate closing requirement. It can expose inconsistent cost coding, incomplete related-party documentation, draw-to-ledger differences, unsupported accruals, or weaknesses in the controls surrounding construction disbursements.
Common Issues That Delay Review
Most delayed certifications do not fail because of a single large error. They stall because several smaller inconsistencies accumulate. The reported construction cost may not tie to contractor payments. Change orders may be approved operationally but missing from the formal contract file. A development fee may be recorded without a clear schedule of what was paid, deferred, or waived.
Other recurring issues include costs charged to the wrong entity, invoices paid from a nonproject account without a clear reimbursement trail, unsupported allocations between projects, and unresolved differences between lender draws and general ledger activity. Capitalized interest, reserves, and closing costs also require careful classification because their treatment may differ across reporting frameworks.
A final review should focus on explanations, not just arithmetic. Material variances from the approved budget should be described in plain language and supported by project records. Reviewers are more likely to accept a well-documented variance than an unexplained amount that happens to fit within a budget category.
Building a More Controlled Closeout Process
The practical objective is to make the final certification the last step in an ongoing financial-control process, not an emergency reconstruction exercise. Finance leaders should assign clear ownership for the cost schedule, source reconciliation, document retention, and communication with the development team. A periodic closeout review during construction can identify deficiencies while invoices, approvals, and project personnel are still accessible.
For organizations managing multiple developments, standardized cost codes, document-retention protocols, and related-party approval procedures can materially improve consistency. They also give boards and lenders a clearer picture of how project funds are being governed across the portfolio.
Goldenthal & Suss approaches these engagements with the same discipline applied to audit and assurance work: a precise understanding of the governing requirements, focused testing of the underlying records, and partner-level attention to issues that can affect compliance and financial reporting.
The most useful time to prepare for a developer cost certification is before the project reaches its final draw. A current reconciliation, a disciplined supporting file, and a clear understanding of which costs are allowable can turn a pressured closeout into an accountable final record of the project’s stewardship.
This article is general information, not accounting, audit, or tax advice, and it does not create a client relationship. Thresholds and filing requirements change. Confirm anything you intend to rely on against the current rules or speak with us directly.
Talk to an auditor
Goldenthal & Suss performs nonprofit audits, single audits, and Yellow Book government engagements from offices in Staten Island, NY and Freehold, NJ.
Request a Proposal