Performance-Based Payments (PBP)
Performance-based payments are the government's preferred contract financing method under FAR 32.1001: fixed-price financing paid on completion of defined, verifiable performance events rather than incurred costs, capped at 90 percent of contract or delivery-item price and liquidated from delivery payments.
FAR subpart 32.10 pays financing when the contractor completes events the contract defines in advance — each one integral to performance and verifiable by the government, valued in total at no more than 90 percent of the contract or delivery-item price (FAR 32.1004). The clause is 52.232-32. PBPs attach only to fixed-price work: not to cost-reimbursement line items, not to sealed-bid awards, and never alongside progress payments on the same contract.
DoD leans hardest on them. 10 U.S.C. 3802(a)(2) bars conditioning PBPs on incurred costs: events, not cost reports, move the money. DFARS subpart 232.10 requires the contracting officer to run the PBP analysis tool before agreeing to a schedule, then attach 252.232-7012 or 252.232-7013 depending on whether payments run on a whole-contract or deliverable-item basis.
Event design is where schedules fail. A cumulative event that depends on a severable one nobody completed, or an event written loosely enough to argue over, converts financing into negotiation. Write each event so a stranger could verify completion from the contract file alone.
Regulatory Reference
FAR subpart 32.10; FAR 52.232-32; DFARS subpart 232.10; 10 U.S.C. 3802(a)(2)
RFO Status
The Part 32 model deviation simplifies the part while the GSA adoption memo lists no change to the performance-based payments subpart, and its clause updates (52.232-3, -12, -16, -20, -22, -36) do not include 52.232-32; GSA adopted the part as class deviation RFO-2025-32 (effective November 3, 2025), DoD through class deviation 2026-O0022 (issued December 18, 2025, effective February 1, 2026), and Part 32 appears in neither the June 23, 2026 first-batch proposed rules nor the September 18, 2026 second batch. (verified September 18, 2026)
Category
Processes & Methods
How AcqBot Helps
AcqBot drafts the PBP event schedule against the 32.1004 tests — integral, verifiable, severable or cumulative — prices the events inside the 90 percent cap, and flags contract features that rule PBPs out, such as a progress payments clause already on the contract.
Related glossary entries
Sources Sought Notice
A Sources Sought Notice is a pre-solicitation announcement, typically posted to SAM.gov, asking companies to identify their interest and capability to perform a prospective requirement — primarily used as market research to shape competition and set-aside decisions.
Request for Information (RFI)
A Request for Information (RFI) is a formal market research instrument used to gather industry input on capabilities, approaches, pricing structures, or draft requirements when the government is not yet ready to solicit — responses are voluntary and non-binding.
Lowest Price Technically Acceptable (LPTA)
Lowest Price Technically Acceptable (LPTA) is a source selection process that awards to the lowest-priced offeror whose proposal meets minimum acceptability standards — no credit is given for exceeding requirements, and tradeoffs between price and quality are not permitted.
Best-Value Tradeoff
The best-value tradeoff process permits award to other than the lowest-priced or highest-rated offeror when the source selection authority documents that the superior proposal's benefits are worth its price premium, or that a cheaper proposal's savings outweigh its weaknesses.