Rev. Proc. 2026-32: Build a Construction Tax Transition Register
Rev. Proc. 2026-32 gives construction controllers a reason to review residential-contract tax methods with their advisers now. Build a register connecting each contract to its taxpayer, tax year, existing method, and filing evidence. Keep the resulting tax calculations separate from management WIP so a tax transition doesn't obscure job performance.
Why now: September guidance creates an immediate review task
The IRS released Rev. Proc. 2026-32 on 2026-09-04. It adds automatic-change procedures for certain residential construction contracts, including DCN 275. The specified changes use a cutoff approach without a Section 481(a) adjustment. Its limited transition provision concerns qualifying returns filed on or before September 21, 2026, for taxable years beginning after July 4, 2025, where the specified methods were properly applied.
September 21 is not a universal contractor filing deadline. Have the tax adviser assess the actual return, year, method, and procedural conditions before relying on that provision. The practical task on September 16 is to gather enough evidence for that assessment, rather than assume every residential job needs a new filing.
Alvarez & Marsal's September 14 analysis places the new procedure within the broader accounting-method changes following OBBBA. Its discussion of transition options also illustrates why filing history belongs beside the accounting analysis. A list of projects alone cannot answer whether a particular procedural route fits.
This article proposes an operating workflow for controllers and construction accounting firms. The output is an adviser-ready register and a reporting reconciliation, not a tax election generated from a spreadsheet. A reviewer should be able to start with a proposed treatment, find the affected contracts, and trace every amount back to the same approved accounting snapshot.
Start with the taxpayer and contract population
A project name is a useful operational label, but it isn't a sufficient tax identifier. One development can involve several contracts, legal entities, and accounting records. Before modeling a change, identify which taxpayer signed each agreement and which reporting entity holds the related revenue, costs, receivables, and customer advances.
Create one row per contract under review, with a stable contract ID and links to any associated job IDs. Where a single accounting job groups several agreements, document the allocation method instead of silently treating the job total as one contract. Ask the tax adviser to resolve uncertain contract boundaries before the model assigns treatment.
The date distinction deserves its own field. JAG CPA's September 6 construction-method analysis explains that the expanded residential rule concerns contracts entered into in taxable years beginning after July 4, 2025. For a calendar-year taxpayer, that generally points to contracts entered during 2026 and later, rather than every agreement signed after July 4, 2025. Its discussion also separates first adoption from changing an established method and flags capitalization as an additional analysis.
Capture both the contract date and the first day of the taxpayer's tax year. For example, two agreements signed in August 2025 and February 2026 might both appear in the same September 2026 open-job report. Their presence in that report doesn't establish identical tax treatment. The register should make the dates visible without requiring the reviewer to open two separate files.
| Register field | Evidence to attach | Review question |
|---|---|---|
| Taxpayer and contract ID | Executed agreement and entity record | Which taxpayer and agreement are being assessed? |
| Contract date and tax-year start | Signed contract and prior return | Which date-based population does the agreement belong to? |
| Contract classification | Scope, property details, and adviser conclusion | Has the classification been resolved? |
| Existing method and history | Prior workpapers and method-change records | Is this adoption, a change, or an unresolved correction? |
| Costs and capitalization | Job ledger and allocation schedules | Which costs require separate tax analysis? |
| Filing status | Return copy and submission evidence | What procedural options need review? |
| Approval status | Dated review note and named owner | Can the result enter the approved forecast? |
Add an explicit unresolved status. A missing agreement or uncertain classification should remain visible as an exception, rather than become an assumed favorable answer. Include a responsible person and requested response date for each exception. That turns a collection of missing documents into a manageable review queue.
Keep three calculations connected and separately labeled
The controller needs three views: management job performance, the adviser's tax calculation, and the cash forecast. They should share contract identifiers and reconciled inputs. Each view answers a different question, so give each a clear basis, period, and approval status.
The management view asks what work has been earned and what margin remains. The tax view applies the approved treatment to the relevant taxpayer and period. The cash view asks when collections, supplier payments, payroll, and tax payments affect liquidity. A change in one calculation does not by itself supply an entry or assumption for either of the others.
If the starting WIP schedule is unreliable, fix that first. FinBoard's guide to building a construction WIP schedule from QuickBooks provides the underlying reporting workflow. The transition register should reference that approved schedule rather than recreate its job-cost totals from a second, differently dated export.
A worked reporting example
Assume a hypothetical contractor has an approved management schedule for one job showing a $1,200,000 contract value, $960,000 estimated total cost, and $480,000 cost incurred to date. For this example only, assume the approved reporting policy uses those costs as its progress measure and that no excluded costs or other adjustments apply.
The calculation gives 50% progress: $480,000 divided by $960,000. Cumulative management revenue is $600,000, and cumulative management gross profit is $120,000. With cumulative billings of $650,000, billings exceed the calculated earned revenue by $50,000. These are illustrative management calculations, not a conclusion about tax eligibility or a universal revenue-recognition policy.
Now assume the tax adviser supplies a reviewed scenario with zero current contract taxable profit and provides the supporting treatment of both revenue and costs. The bridge shows $120,000 management contract profit less a $120,000 reconciling difference, producing zero contract taxable profit in that scenario. Label the difference by its approved explanation. Don't enter an unexplained balancing figure called tax savings.
The bridge does not tell the team to erase $600,000 of management revenue. Nor does it establish $120,000 of cash savings. It explains why two calculations differ. Other jobs, overhead, taxpayer characteristics, and the adviser's complete tax computation still sit outside this deliberately narrow example.
If the adviser later estimates a $30,000 reduction in a particular scheduled tax payment, record that approved amount and payment date in the cash scenario. Show any expected later reversal separately. Management can then evaluate timing without confusing a temporary payment difference with additional construction margin or collected customer cash.
For liquidity planning, connect the approved payment schedule to a 13-week cash-flow forecast. Retain the original forecast as a comparison so the CFO can identify how much of the change comes from taxes and how much comes from collections or spending.
Accounting controls: evidence, calculation, review, and decision
Source data: preserve the accounting snapshot
Keep the source data export date, ledger period, entity, and reporting basis with every input file. Reconcile job costs to the relevant ledger accounts and explain unassigned costs. Tie contract billings to the billing records, and distinguish billed amounts from collections. A contract register that mixes yesterday's costs with last month's invoices can appear precise while answering the wrong question.
Use a signed-off snapshot for the initial analysis. Subsequent changes should produce a new version with a short explanation of the affected rows. That makes it possible to distinguish a revised legal conclusion from a late supplier invoice or an updated estimate to complete.
Calculation: make the bridge repeatable
Keep imported amounts separate from formulas and adviser-approved assumptions. Assign a single sign convention to the management-to-tax bridge: begin with book profit, show additions and subtractions explicitly, and end with the calculated tax amount. Check the reconciliation in both directions.
For underlying ledger balances, retain debit and credit polarity. Revenue typically carries a credit balance while expenses typically carry a debit balance; a presentation that displays both as positive numbers needs a documented transformation. Don't use absolute values to make a reconciliation appear to work. A credit to an expense account might be a genuine reversal.
Separate period activity from cumulative balances. In the worked example, cumulative revenue and cumulative billings support the job-position comparison. Monthly revenue belongs in the monthly performance report. Summing successive month-end WIP balances would count the same position repeatedly. Keep the labels visible next to every exported number.
Review: test exceptions before totals
The reviewer should inspect contracts with missing dates, changed classifications, unusually large reconciling differences, and unsupported capitalization assumptions. Recalculate at least one ordinary contract and each material exception using the underlying documents. Checking that the grand total agrees is useful, but it won't reveal two contracts assigned to the wrong population with offsetting effects.
Document what was reviewed, who reviewed it, and which version passed. If the accounting firm prepares the register, ask the client's project lead to confirm operational facts and the client's controller to confirm the ledger reconciliation. Each person should approve the evidence within their responsibility.
Decision: name the owners
The tax adviser owns the tax classification, permissible method, and filing conclusion. The controller owns the accounting reconciliation and any proposed book entry. The CFO or owner decides whether an approved tax-payment scenario changes spending, borrowing, or distributions. A spreadsheet preparer should not acquire those authorities merely by maintaining the workbook.
If the review identifies a book adjustment, document its basis and balanced debit and credit entries separately. A tax scenario alone isn't sufficient support for a revenue reversal or a tax-provision entry. FinBoard's discussion of controls that support the close offers a broader framework for assigning review responsibility.
Use the September review to produce a bounded decision
Start with taxpayers that have relevant residential contracts and a return or method-change filing that may need immediate attention. Ask the adviser to prioritize those cases. Don't make every open job urgent simply because it appears in the same construction report.
For the first review meeting, send a compact packet: the register, the reconciled accounting snapshot, filing evidence, material assumptions, and unresolved questions. State the decision requested for each taxpayer. A useful request is whether the available evidence supports a particular procedural route and what additional information is needed before implementation.
Avoid three common shortcuts. Don't classify a contract solely from a project name such as apartments. Don't interpret an empty tax-method field as permission to select a new method. Don't label a modeled reduction in taxable income as a realized benefit. These shortcuts make the workbook easier to finish while leaving the actual decision unresolved.
Agree on what happens when information arrives late. The team can update the register, obtain a revised review, and issue a new forecast version. It should not overwrite the previously approved analysis without preserving the reason for the change. This matters when project managers revise cost estimates at the same time the tax team revises its conclusions.
Close the review with a short decision record for each taxpayer: approved treatment or unresolved status, affected contract population, required follow-up, filing owner, and permitted forecast use. Include the next review date. The value of the register is that the next person can understand both the conclusion and its limits without reconstructing the September conversation.
Frequently Asked Questions
Does this tax update replace the management WIP report?
No. Keep the management WIP report on its approved reporting basis and maintain a separate reconciliation to the tax calculations.
What should the controller send to the tax adviser?
Send the contract register, taxpayer year-start dates, signed agreements, method history, reconciled job costs, filing records, and a list of unresolved classifications.
Is a modeled tax reduction cash available today?
No. A scenario is not a bank balance. Update cash planning only after the tax adviser approves the treatment and the timing of payments.
Who approves changes to the transition register?
The tax adviser approves tax classifications and methods. The controller approves the accounting reconciliation, and the CFO or owner approves cash-planning decisions.
To discuss the financial reporting foundation for your construction review, explore FinBoard with your controller.
