Federal Invoicing for Software Companies: Prompt Payment, IPP, WAWF and Annual Billing

2026-10-13#invoicing #saas #federal-market #small-business

By Philip Luca — Founder of GovExpress; prior domain experience at Bloomberg Government and GovWin IQ.

Winning a federal contract is the hard part. Getting the invoice through the government’s payment process is the part nobody explains. Agencies follow a fixed set of rules for invoices, and a software company that bills the way it bills commercial customers often finds its first invoice rejected, or sitting unpaid for weeks without anyone saying why.

This guide covers the payment clock, what makes an invoice “proper,” the systems you submit invoices through, and the one issue that catches SaaS companies most often: annual billing in advance.

The Prompt Payment Act clock

Federal payment timing is set by the Prompt Payment Act (31 U.S.C. chapter 39). The Treasury’s rules for it are at 5 CFR part 1315, and FAR subpart 32.9 applies them to contracts.

Under FAR 32.904, unless the contract sets a different date, payment is due on the later of:

30 days after the designated billing office receives a proper invoice, or
30 days after the government accepts the supplies or services.

For acceptance, the government generally has 7 days after delivery to accept or reject the work before acceptance is treated as having happened for purposes of the payment clock (constructive acceptance), unless the contract says otherwise.

If the agency pays late, it owes an interest penalty automatically. You don’t have to ask for it. The rate is set by the Treasury every six months, and the penalty runs from the day after the due date until the payment date.

Two details matter in practice:

The clock starts at the billing office named in your contract. An invoice emailed to your program contact, however friendly, hasn’t been received for payment purposes.
A rejected invoice resets the clock. Under FAR 32.905, the billing office has to return an improper invoice, with the reasons, within 7 days of receipt. The 30 days then start again when the corrected invoice arrives.

Small businesses: a 15-day goal

FAR 32.009 directs agencies to pay small business contractors as quickly as practicable, with a goal of 15 days after receiving a proper invoice. It’s a goal, not a deadline. The interest penalty still runs from the contract’s due date, not from day 15. If you’re a small business, check whether your contract includes FAR 52.232-40. If you’re a prime with small business subcontractors, that clause also asks you to pass faster payment down to them.

What makes an invoice “proper”

FAR 32.905(b) lists what a proper invoice must contain. The list is short but strict:

Your company name and the invoice date and number.
The contract number, including the order number if the work was ordered under an IDIQ contract, and the line item (CLIN) numbers.
A description of what was delivered, with quantity, unit of measure, unit price and extended price, matching the contract’s line items.
Shipping and payment terms, where applicable.
The name and address of the official who should receive payment, and a contact person for questions about the invoice.
Your taxpayer identification number and banking information, if the contract requires it.
Anything else the contract itself asks for.

The most common reason a software invoice is rejected is a mismatch with the contract. Commercial invoices group charges the way the vendor thinks of them: platform fee, seats, support, overages. A federal invoice has to bill against the CLINs the contracting officer wrote, at the prices in the contract, for the period the contract covers. If your price list and the contract’s line items don’t line up, sort that out before award, not when you send the first invoice.

Payment goes to the bank account in your SAM.gov registration. FAR 52.232-33 makes the System for Award Management the source of electronic funds transfer information, so a lapsed or out-of-date SAM.gov registration can stop payment even after the invoice has been approved.

Where you submit invoices

Federal invoicing is electronic. OMB memorandum M-15-19 directed agencies to move to electronic invoicing, and most now name a single system in the contract. The two you’re most likely to meet:

The Invoice Processing Platform (IPP). Run by the Treasury and free for vendors, IPP is used by many civilian agencies. You enroll, the agency links your account to its contracts, and you submit and track invoices there.
Wide Area WorkFlow (WAWF), inside PIEE. The Department of War uses WAWF in the Procurement Integrated Enterprise Environment. DFARS 252.232-7003 requires electronic payment requests, and DFARS 252.232-7006 tells you which document type, routing codes and inspection and acceptance officials to use. Most WAWF rejections come from a wrong document type or routing code, so copy those fields exactly from the contract.

Some agencies use their own portals, and some smaller buys still go through a government purchase card instead of an invoice. Your contract’s payment clauses are the authority. Read them on the day of award, enroll in the named system then, and send a test invoice early if the agency allows it.

If you sell through a reseller, the reseller invoices the government and you invoice the reseller on your commercial terms. That moves the federal invoicing work to a partner set up to do it, which is one reason resellers are a common first route for software companies.

Annual-in-advance billing

This is where SaaS billing and federal payment rules collide most often.

Commercial SaaS is usually billed annually in advance. Federal appropriations law generally bars that. Under 31 U.S.C. 3324, an agency generally can’t pay for goods or services before they’ve been delivered. Congress has made narrow exceptions, including one for subscriptions to publications, and GAO has applied that exception to some electronic subscriptions. Whether it covers a particular SaaS product isn’t something to assume, and it isn’t your call to make.

Inside a contract, the route for advance payment on commercial products and services is commercial financing under FAR 32.202. A contracting officer can agree to advance or interim payments when they’re customary in the commercial marketplace, subject to conditions such as adequate security. It’s something you negotiate, not a default, and many contracting officers won’t offer it on a first award.

In practice, software contracts commonly use one of these structures instead:

Billing in arrears, monthly or quarterly, for the service already delivered.
Billing per period of performance, with the invoice submitted once the period has started and acceptance terms written to match.
Billing per delivered milestone, for implementation or onboarding services priced separately from the subscription.

Raise this before award. If your pricing assumes cash up front and the contract is written for payment in arrears, your first year’s cash flow changes. Many companies set a separate federal price or billing schedule for that reason. It also connects to the federal fiscal year: an order placed in September against expiring funds can still be invoiced and paid on the normal schedule after October 1, but a gap in appropriations can slow the billing office down.

Your license terms need the same review. Auto-renewal, late fees and payment-in-advance clauses in a commercial agreement usually don’t survive inclusion in a federal contract, and the Prompt Payment Act, not your interest rate, governs late payment.

A short checklist for your first federal invoice

On award, read the payment clauses. Find the billing office, the invoicing system, the document type and any acceptance official.
Enroll in that system the same week. Enrollment in IPP or PIEE can take longer than you expect.
Map your invoice to the CLINs. Line items, units, prices and periods should match the contract exactly.
Check your SAM.gov record. It should be active, with current banking information, before the first invoice goes out.
Track the dates. Note when the invoice was received and when the work was accepted, so you know when payment is due and whether interest is owed.

None of this affects whether a buyer chooses you. It affects how smoothly your first federal contract runs, and contracting officers remember vendors whose invoices go through without problems.

To see your SAM.gov registration and the other categories federal buyers review, score your company’s federal readiness.

Frequently Asked Questions

How long does a federal agency have to pay a software invoice?

Under the Prompt Payment Act and FAR 32.904, the usual due date is 30 days after the designated billing office receives a proper invoice, or 30 days after the government accepts the work, whichever is later, unless the contract sets a different date. If the agency pays late, it owes an interest penalty automatically, at a rate the Treasury sets every six months.

Can a federal agency pay for a SaaS subscription annually in advance?

Not by default. 31 U.S.C. 3324 generally bars paying for goods or services before they are delivered. There are narrow statutory exceptions, and FAR 32.202 lets a contracting officer agree to commercial advance payments where they are customary, but advance billing has to be agreed in the contract. Many software contracts bill monthly, quarterly or per period of performance instead.

The CMMC brief

What the Phase 2 suspension changed and what it did not — the obligations that still bind, the assessment path a contract puts you on, the scoping decision that drives the cost, and the sequence that fits inside a pipeline. Sourced from the primary record.