What Makes an Accounting System "Adequate" for Government Work (SF1408, Plain English)

The gate in front of cost-type work

There is a checkpoint many small businesses hit the first time they pursue a cost-reimbursable government contract, and it surprises them: before the award, someone wants to know whether your accounting system is adequate to handle it. Not whether you do good work. Not whether your price is right. Whether your books can reliably do the things government cost accounting requires — segregate costs, track them by contract, handle labor properly, and keep out what does not belong.

The instrument behind that determination is a standard form, the SF1408 — Preaward Survey of Prospective Contractor Accounting System. It is a checklist an auditor works through to decide, essentially, "if we give this company a cost-type contract, will its accounting system produce numbers we can trust?" The good news for a small contractor is that the SF1408 is not a secret or a trap. It is a list of sensible capabilities, most of which overlap with simply keeping good books — and if you have already built your books around the direct/indirect split, you are most of the way there. This article translates the checklist into plain English. It is general educational information, not compliance or contracting advice — the actual survey is performed by auditors against specific criteria, and a DCAA-experienced CPA is the right guide for your situation.

"Adequate" means designed right and running

Two ideas sit underneath the whole survey. First, an adequate system has to be designed correctly — the structure has to exist. Second, in many cases it has to be shown operating — not just capable in theory but actually doing the job on real transactions. A chart of accounts that could segregate costs but is full of miscoded entries is not adequate. The auditor is checking both the blueprint and the building.

And crucially, the standard is reliability, not perfection on any single transaction. Can the system, run the way you actually run it, be depended on to keep costs where they belong? That framing helps: you are not proving you never make a mistake, you are proving the system is structured so the right answer is the default.

The capabilities the survey checks

Strip away the form's formality and the SF1408 asks whether your accounting system can do a specific set of things. In plain English:

• Is it based on GAAP-consistent accrual accounting? The system should follow generally accepted accounting principles and generally operate on an accrual basis, so costs are recognized when incurred, not just when paid.
• Does it segregate direct costs from indirect costs? The foundational one. Direct costs identifiable to a contract must be separated from indirect costs that get pooled and allocated — which is exactly what a government-ready chart of accounts is built to do.
• Does it accumulate costs by contract (final cost objective)? The system must gather the costs of each contract in one place, so you can say what any given job actually cost. This is job costing — every direct cost tagged to the contract it belongs to.
• Does it allocate indirect costs on a consistent, logical basis? Indirect costs must reach contracts through pools and rates applied the same way every time, not sorted out case by case.
• Does it handle labor correctly? A big one. The system has to accumulate labor cost by contract and by cost objective, which means a timekeeping and labor-distribution process where every hour an employee works is recorded and charged to the right place — direct to a contract or to an indirect category — with all time accounted for, not just billable time. Labor is where cost-type accounting is most closely scrutinized because it is the easiest thing to charge wrong.
• Does it identify and exclude unallowable costs? The system must keep unallowable costs (FAR 31.205) out of any billing or indirect pool — best done by giving them their own segregated accounts so they are excluded automatically.
• Can it determine costs on an interim basis? The system should produce cost information at least monthly — not only at year-end — so contract costs and rates can be tracked as work proceeds. In practice: you close your books every month.
• Does billing tie to the books? The costs you bill the government must reconcile to the costs recorded in your accounting records. Billing cannot be a separate spreadsheet that drifts from the ledger; the invoice and the books have to tell the same story.

Read that list again and notice something: almost every item is just good accounting, formalized and made provable. Accrual basis, a clean chart of accounts, costing jobs, closing monthly, keeping billing tied to the ledger — a well-run small business does most of this already. Government work adds the direct/indirect discipline, rigorous timekeeping, and the unallowable-cost segregation on top.

Where small contractors actually fall down

If most of the criteria are ordinary good practice, why do systems get found inadequate? A few recurring places:

• Costs are not really tracked by contract. The business bills off estimates and a spreadsheet, and the accounting file lumps everything together — so it cannot show what a specific contract cost. The fix is job costing every contract inside the accounting system itself.
• Direct and indirect are blurred. The same account holds costs that are sometimes billed direct and sometimes buried in overhead. Adequacy requires them cleanly separated, every time.
• Timekeeping is loose. No total-time accounting, hours not charged to cost objectives, no daily discipline. Labor is the single most-scrutinized area and the most common weakness.
• Billing floats free of the ledger. Invoices are built in a separate model that no longer reconciles to the books, so the reconciliation the survey expects cannot be produced.

Every one of those is a structural problem, which is the encouraging part — structure is fixable, and fixing it before you pursue cost-type work is far cheaper than failing a survey after you have bid.

The takeaway

An adequate accounting system, in the SF1408 sense, is one that reliably segregates direct from indirect costs, accumulates cost by contract, distributes labor correctly, excludes unallowable costs, produces cost information monthly, and keeps billing tied to the books — all designed into the system and shown to actually work. It sounds like a high bar, and it is a real one, but it is not exotic. It is disciplined, provable bookkeeping.

If you are a small business eyeing your first cost-type award, the move is not to panic about the survey — it is to build these capabilities into your books before you need them, so that when an auditor walks the SF1408 checklist, every answer is already sitting in your accounting system waiting to be shown.

Hosting Books is built around exactly these capabilities: a segmented chart of accounts that separates direct, indirect, and unallowable costs, per-contract job costing, monthly close and reporting, and a signed, hash-chained audit log that ties every billed cost back to the record behind it — so the system that has to be "adequate" is the same one you run your business on every day.

This article is general educational information about government-contract accounting-system requirements and is not compliance, legal, or contracting advice for your specific situation. Accounting-system adequacy is determined by auditors against detailed criteria — consult a qualified contract accountant or CPA before relying on any interpretation here.