What a government contract sale asks your books to produce

Government contractor accounting has to produce three artifacts an ordinary monthly close never generates: a schedule of every federal contract showing its remaining unpaid balance, balance sheets dated immediately before and immediately after a transfer, and evidence that a buyer can perform the work. All three are named in federal regulation. None of them can be built backward.

Here is the thing most owners of federal contracting businesses get wrong about selling one. They treat the government as a risk to the deal, something their attorney will handle when the time comes. The government is not evaluating your deal. It is reading documents. And the documents it reads are accounting deliverables, which means the constraint on your timeline is not your lawyer or your buyer. It is your chart of accounts and your close calendar.

That is good news, because unlike most of what happens in a sale, this part is published in advance. FAR 42.1204 lists what a contractor has to submit when it asks the government to recognize a buyer as the successor in interest to its contracts. You can read the list today and work backward from it. Almost nobody does.

The contract schedule your general ledger probably cannot produce

The single hardest document on the list is a schedule most federal contractors have never built, because their accounting is organized around customers and months rather than contracts and modifications. FAR 42.1204(e)(2) requires a list of all affected contracts between the seller and the Government as of the date of sale or transfer of assets, showing for each contract the contract number and type, the name and address of the contracting office, the total dollar value as amended, and the approximate remaining unpaid balance.

Read those four columns as an accounting request rather than a legal one and the problem becomes obvious. Total dollar value as amended means you have to be tracking modifications, not just the original award. Approximate remaining unpaid balance means you have to know, per contract, what has been billed against what was awarded. If your revenue rolls up by customer, and the federal government is one customer, you cannot produce either number without someone sitting down with a folder of modifications and a spreadsheet.

Contract backlog is the portion of awarded contract value that a contractor has not yet performed and billed. Whether a given contract's backlog splits into funded and unfunded depends on how that contract is funded, so the split belongs in your reporting rather than in a general rule, and your contract documents are what settle it.

The Contract Ledger. Build one row per federal contract and five columns: contract number and type, contracting office with address, current total value as amended, billed to date, and approximate remaining unpaid balance. Reconcile the whole thing to the general ledger every month, on the same calendar as your close, by the same person who closes the books. Four of those five columns are exactly what FAR 42.1204(e)(2) asks for as of the date of sale. The fifth, billed to date, is the only honest way to produce the fourth without reconstructing it by hand.

Then apply the test. If you cannot produce the remaining unpaid balance on any single contract within one business day, you do not have a contract ledger. You have a filing cabinet and a good memory, and neither of those survives being asked for a schedule as of a specific date under time pressure.

The one business day standard is a rule this post proposes, not a market benchmark. It is chosen because it is roughly the gap between a document that exists and a document that has to be assembled, and assembled schedules are the ones that come back with questions.

The two dated balance sheets, and the one place a regulation names an attestation

FAR 42.1204(f)(6) lists, among the documents to be submitted as they become available, balance sheets of the transferor and transferee as of the dates immediately before and after the transfer of assets, audited by independent accountants. That is not a document any company produces in the ordinary course of business, and it is not one that can be created after the fact on books that were never maintained to support it.

Now the caveat that matters, because it is in the same regulation. FAR 42.1204(g) provides that if the Government has acquired the documents during its participation in the pre-merger or pre-acquisition review process, or the Government's interests are adequately protected with an alternative formulation of the information, the responsible contracting officer may modify the list of documents to be submitted. So whether the audited version is required in your case is a real question with a real answer, and that answer belongs to a specific contracting officer rather than to any general rule.

The Two-Date Balance Sheet. The decision is not whether to go buy an audit. The decision is to ask the responsible contracting officer, in writing and roughly twelve months before you intend to transact, which version of FAR 42.1204(f)(6) will apply to you. That single answer determines what your monthly close has to be able to support, and it is the only item on the entire document list that cannot be produced retroactively. Every other document on the list can be assembled in the weeks before closing. This one depends on what your books looked like for the year leading up to it.

We have argued elsewhere on this site that clean books beat an audit when you sell, and that remains true for the reader it was written for. A buyer trusts numbers it can trace, not a stamp, and audit money spent instead of close discipline is usually money wasted. This is a different reader. The government is the rare counterparty that names the attestation in a regulation rather than asking for it in a diligence request. The two positions are consistent, and the order of operations does not change: fix the close first, because an audit of books that were never closed properly is the slowest and most expensive version of this problem, not the solution to it.

Evidence that the buyer can perform starts in your records

FAR 42.1204(e)(3) requires evidence of the transferee's capability to perform, which reads like the buyer's problem and is not. Your transaction closes when the government is satisfied, and the government is being asked to form a view about a company it has never contracted with. The material that makes that case is largely built out of your records: what the contracts are, what remains on them, what it costs you to deliver, and what the buyer is stepping into.

That has a practical consequence for how you run the finance function in the twelve months before a sale. Contract level cost, not just contract level revenue, is what lets a buyer build a credible capability case rather than an assertion. If your direct labor, subcontractor cost, and materials do not code to the contract they were spent on, the buyer is left arguing capability from its own balance sheet alone, and the schedule you handed over does not help it.

How you recognize revenue on longer-running contracts is a separate question, and the right method depends on the contract type and on your own accounting policy, so settle it with your CPA and document the policy rather than adopting whatever the software defaulted to. The point here is narrower: whatever the method, it should be applied consistently and it should be traceable to the contract.

What a clean close does differently when the customer is the federal government

The change is smaller than it sounds and it is structural rather than procedural: the contract has to become a reporting dimension in its own right, not a note in a customer record. Three specific moves cover most of it.

• Make the contract a dimension in the chart of accounts, so revenue and direct cost both code to a contract and a modification rather than to a customer and a month. Most accounting systems support a job, project, or class dimension that will do this without a migration.
• Reconcile the Contract Ledger to the general ledger as a step in the monthly close, with a named owner and a date, the same way you would reconcile a bank account. A schedule that is only correct when someone rebuilds it is not a control.
• Report backlog every month, split the way your contracts are actually funded, so that the number in your management pack is the same number that would go on a schedule for the government. Two versions of backlog is a finding waiting to happen.

None of this is exotic accounting. It is the ordinary discipline of a monthly close, pointed at a dimension most small contractors never set up, applied consistently for long enough that the records are a byproduct of how you operate rather than a project you run when a buyer appears.

What this actually asks of you

It asks for a year, and not much else. The three artifacts at the top of this article are not difficult to produce from books that were built to produce them, and close to impossible to produce from books that were not. A contract ledger is a spreadsheet with a reconciliation step. A chart of accounts change is an afternoon. Twelve months of consistent application is the part you cannot compress, which is why the work has a deadline that has nothing to do with when you decide to sell.

The owners who find this easy are not the ones with the best accounting software. They are the ones who set up the contract dimension years ago because they wanted to know which contracts made money, and then discovered that the same records answered a regulator's question they had never heard of. That is usually how readiness works. The reporting you build to run the business well is the reporting that holds up when someone else reads it.

If a sale is on your horizon and federal contracts are a meaningful share of your revenue, the mechanics of how those contracts move to a buyer, and which of your other agreements need somebody's consent, are covered on Texas Exit Advisors in which contracts transfer when you sell your business. Texas Exit Advisors and Optima Mergers & Acquisitions handle the transaction itself. The records that make it possible are what we do.

Where Thryve fits

Thryve Accounting & Advisory builds the monthly close, the contract level reporting, and the documented add-back and adjustment schedules that let a company answer this kind of question from records rather than from memory. For a federal contractor that means the contract dimension in the chart of accounts, a Contract Ledger reconciled to the general ledger every month, a backlog number that does not change depending on who runs it, and books closed to a standard that leaves your options open when someone asks which version of FAR 42.1204(f)(6) applies to you.

If you run a business with federal contracts and you would rather not find out what your books cannot produce in the middle of a transaction, that is a good conversation to have a year early.

Last reviewed: September 2026. This is general information, not legal, tax, or accounting advice, and Thryve Accounting & Advisory is not a tax preparation firm. FAR 42.1204 is quoted as currently published and is amended periodically, so confirm the current text and how it applies to your contracts with your transaction attorney and with the responsible contracting officer. Whether the audited balance sheets described in FAR 42.1204(f)(6) will be required in a specific transaction is a decision for that contracting officer under the modification authority at FAR 42.1204(g), not a general rule. Revenue recognition method on long-term contracts depends on the contract type and on your own accounting policy and should be settled with your CPA.