X12 567 — Contract Completion Status
The 567 transmits the progress status of a US federal contract — physically complete, financially complete, closed — from a contracting officer to Treasury, GAO, or an administrative partner.
Purpose
The 567 documents contract completion milestones in the federal acquisition ecosystem: physically complete (delivery done), financially complete (payments made), administratively complete (close-out done). It carries contract number, status, milestone date, cumulative value.
It feeds contract close-out systems (PCR, IGCE, Procurement Closeout System) and triggers the 568 (Contract Payment Management Report). Acknowledged by 997.
Envelope structure
The 567 travels within the three X12 envelope levels (ISA/IEA,
GS/GE with functional group CY, and ST/SE).
Didactic example in release 004010:
ISA*00* *00* *ZZ*CONTRACTOFFICR*ZZ*USTREASURY *260515*0900*U*00401*000000567*0*P*>~
GS*CY*CONTRACTOFFICR*USTREASURY*20260515*0900*1*X*004010~
ST*567*0001~
BGN*00*COMP-CT-W912DY-0099*20260515~
N1*BY*US ARMY CORPS OF ENGINEERS*24*EIN-USACE~
N1*SE*ACME CONSTRUCTION*24*EIN-ACME~
REF*ZZ*CONTRACT-W912DY26C0099~
DTM*090*20260515~
MSG*PHYSICALLY-COMPLETE~
AMT*ZZ*4250000.00~
SE*9*0001~
GE*1*1~
IEA*1*000000567~ Common segments
- Header —
ST,BGN. - Agency / Contractor —
N1*BY(Buyer / contracting agency),N1*SE(Seller / contractor). - Contract —
REF*ZZ(contract number). - Status —
DTM*090(milestone date),MSG(PHYSICALLY-COMPLETE, FINANCIALLY-COMPLETE, CLOSED),AMT*ZZ(cumulative value). - Summary —
SE.
Common pitfalls
- FAR close-out periods: a fixed-price contract > $750K has 6 months for close-out, cost-reimbursement 36 months. The 567 must fire within the window.
- MOCAS legacy: for DCMA-administered contracts, the 567 feeds MOCAS — a wrong contract number breaks MOCAS and blocks future payments.
- Status sequence: jumping directly to "closed" without prior "financially complete" is a FAR error — respect the sequence.
Related transactions
Documentation
The code 567 and the name Contract Completion Status are public and listed on x12.org/products/transaction-sets. The complete structure of loops, qualifiers and code lists is distributed by DISA via the proprietary Implementation Guides (TR3). ediverse.io covers only public concepts, the envelope and didactic examples.