Contract delivery
Before your first government invoice: build a payment-ready file
Check billing instructions, line items, supporting records, and submission evidence before sending a federal contract invoice. Includes an illustrative service example.
Finishing the work and submitting an invoice are different steps
A completed service visit does not tell you where to send the invoice, which line item to use, or which supporting records the buyer needs. Establish those details before your first billing date, not after someone returns an incomplete submission.
FAR 32.905 connects payment to a proper invoice and satisfactory contract performance. Where the commercial-products-and-services clause FAR 52.212-4 applies, its payment paragraph addresses delivered items accepted by the government. Do not treat an upload confirmation as proof of acceptance or a promise of payment on a particular date.
This is an internal preparation workflow, not an official invoice template or legal advice. Your signed contract, applicable clauses, modifications, and agency instructions control. Cost-reimbursement, construction, and other arrangements may require a different approach.
Make a billing instruction sheet from the contract
Create a one-page sheet with a source reference beside each answer: billing period or milestone, authorized submission destination, invoice format, contract and order identifiers, relevant line items, required attachments, and contact for invoice problems. Write 'unconfirmed' where the documents do not provide a clear answer.
Use the designated contracting or billing contact to resolve uncertainty. Do not assume that the person supervising daily work is also the invoice recipient or the person authorized to accept performance. Keep the written clarification with the sheet.
If a portal is required, confirm the official access instructions and your ability to use it before billing is due. Avoid sending a second invoice by email simply because the portal is unfamiliar. Ask how to correct or resubmit through the authorized process without creating duplicate demands for payment.
Review the invoice in three passes
Pass 1 — identity and routing. FAR 32.905's invoice requirements include contractor identity, invoice date and number, contract or order and line-item references, payment-recipient details, and a contact for invoice defects. Verify that the identifiers match the actual award documents rather than a proposal draft.
Pass 2 — what is being billed. Check the description, quantity, unit of measure, unit price, and extended amount. Include shipping or payment terms and additional documentation when applicable. The contract may require evidence beyond these basics; this short review is not the complete regulatory checklist.
Pass 3 — sensitive information. FAR 52.212-4(g) makes inclusion of tax identification and bank details on an invoice conditional on the contract's requirements; it also addresses submitting correct electronic-payment information through applicable procedures. Do not put banking details on every attachment by default. Follow the official requirements and approved channel.
As a practical internal control, have someone compare the invoice with the billing instruction sheet and supporting record before submission. Recalculate the amount independently and check that the same period or deliverable has not already been billed.
Illustrative example: one monthly service line
These numbers and documents are invented for illustration, not an active contract or customer result. Suppose a signed contract authorizes one monthly office-support service unit at $2,400, billed after that month's service and required acceptance. The invoice review should show quantity 1, unit 'month,' unit price $2,400, and extended amount $2,400 against the correct line item.
The internal evidence file might contain the required monthly report, the submitted deliverable, and the available acceptance record. Use the documents and format that the actual contract requires; a contractor-created checklist is not government acceptance.
Now suppose someone asks informally for an extra $300 task. Do not simply add it to the monthly invoice because it was discussed. Check whether it is within the existing authorized scope and billing basis, and resolve any needed authorization with the contracting officer. Keep the original $2,400 line traceable instead of hiding an unresolved extra charge in its total.
Keep a submission trail you can actually use
Retain the exact invoice and attachments submitted, submission date, destination, available receipt or confirmation number, and current status. Use separate status labels such as Prepared, Submitted, Returned for correction, and Paid. A sent email alone should not be relabeled Paid or Accepted.
If the invoice is returned, record the stated defect and the correction you made. Preserve the earlier version and follow the billing office's resubmission instructions. For a status question, provide the invoice and contract references rather than forwarding an uncontrolled folder of client and banking information.
Before pursuing another contract, ask whether your team can support its reporting and billing workload as well as perform the service. BidGovAI can help organize company information and selected pursuits; it does not replace the agency's invoice portal, acceptance decision, or payment process. Use the bid/no-bid guide below to include delivery administration in your next pursuit decision.
Your next steps
- Read the actual contract's billing and acceptance instructions.
- Document the authorized destination, billing basis, and required attachments.
- Verify invoice, contract, order, and line-item identifiers.
- Recalculate quantities and prices against the authorized billing basis.
- Resolve unapproved extras before treating them as billable work.
- Share sensitive payment information only as required through approved channels.
- Save submission evidence and track corrections separately from payment.