Project Cost Reporting (839) is used to communicate detailed cost information for projects, programs, or contracts. Contractors, consultants, and project teams typically send this transaction to clients, government agencies, or project managers who need to track spending and financial performance. The transaction is often sent in response to a cost reporting request or submitted on a scheduled basis as part of contract administration. Key segments include the BCS (Beginning Segment for Project Cost Reporting), which initiates the report and provides overall context; the N1 loop, which identifies the parties involved such as the reporting contractor and receiving organization; and the CFT loop, which structures cost data by reporting format type and allows for detailed breakdown of expenses through nested BSD (Breakdown Structure Description) and CLI (Cost Line Item) loops.

Consider a construction scenario where BuildRight Construction submits a 839 transaction to Municipal Development Authority for a highway expansion project. BuildRight uses the BCS segment to establish the report period and project reference, populates the N1 loop with its own company information and the authority’s receiving details, and then organizes costs in the CFT loop using the authority’s required Work Breakdown Structure. Within each BSD segment, BuildRight reports categories such as “Excavation” and “Materials,” and within each CLI segment under those categories, it details line items like “Heavy Equipment Rental – October” with corresponding quantities, rates, and amounts. The transaction also includes DTM segments for reporting dates and REF segments for linking costs to specific contract line items or cost codes, enabling the authority to reconcile invoices and monitor budget burn-down in real time.