Product: X12 EDI
Transaction: 568
Article Link: http://help.truecommerce.com/en/articles/10230619-x12-568-contract-payment-management-report
568 - Contract Payment Management Report
FUNCTIONAL GROUP=D5
This X12 Transaction Set contains the format and establishes the data contents of the Contract Payment Management Report Transaction Set (568) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set can be used to enable the transmission of a management report to provide the details of payments and collections made against funds obligated on contracts, orders, and other services.
SCHEMA
ST
Segment | Name | Position |
ST | 0100 | |
BGN | Beginning Segment | 0200 |
AMT | 0300 |
N1
Segment | Name | Position |
N1 | 0400 | |
N2 | 0500 | |
N3 | 0600 | |
N4 | 0700 | |
PER | 0800 |
CS
Segment | Name | Position |
CS | Contract Summary | 0100 |
N9 | 0200 | |
DTM | 0300 |
LM
Segment | Name | Position |
LM | Code Source Information | 0400 |
LQ | Industry Code Identification | 0500 |
REF
Segment | Name | Position |
REF | 0600 |
LX
Segment | Name | Position |
LX | Transaction Set Line Number | 0800 |
N9 | 0900 | |
AMT | 1000 | |
QTY | 1100 |
LM
Segment | Name | Position |
LM | Code Source Information | 1200 |
LQ | Industry Code Identification | 1300 |
N1
Segment | Name | Position |
N1 | 1400 | |
N2 | 1500 | |
N3 | 1600 | |
N4 | 1700 | |
N9 | 1800 |
FA1
Segment | Name | Position |
FA1 | Type of Financial Accounting Data | 1850 |
FA2 | Accounting Data | 1860 |
BAL
Segment | Name | Position |
BAL | Balance Detail | 1900 |
N9 | 2000 | |
RTE | Rate Information | 2100 |
SE
Segment | Name | Position |
CTT | 0100 | |
SE | Transaction Set Trailer | 0200 |
COMMENTS
Notes |
|
1/0200 | The BGN segment identifies the transaction set purpose code, a unique number used to identify this transmission, and the date and time of transaction set creation. |
1/0300 | The AMT segment identifies the collected amount and the disbursed amount to the extent that either amount applies to the transaction set. |
1/0400 | The N1 loop identifies the name and address information for the transmitting and receiving parties. |
1/0800 | The PER segment identifies the name and communications number of an information point of contact familiar with the details of the contract payment management report. |
2/0100 | The CS segment identifies the contract, modification, call, and order number of the procurement instrument, and the voucher number of the payment being reported on in this contract payment management report. |
2/0200 | The N9 segment identifies the number of the original voucher on which a payment was made if the voucher being reported on in this transmission is a change, correction, or adjustment to that previous voucher. |
2/0300 | The DTM segment identifies the date of the voucher being reported on in this transmission. |
2/0400 | The LM loop provides the capability to transmit industry-specific codes from an industry-specific code list. |
2/0500 | The LQ segment identifies the industry-specific codes. |
2/0600 | The REF segment identifies a reference number associated with the following appropriation data. |
2/0900 | The N9 segment identifies a contract line item, exhibit line item, or subclassification of either against which specific data is being reported. |
2/1000 | The AMT segment identifies the gross, net, deducted, or collected amounts and the net variance amount applicable to the line item being reported. |
2/1100 | The QTY segment identifies the quantity shipped. |
2/1300 | The LQ segment identifies industry-specific codes applicable to the line item. |
2/1400 | The N1 loop identifies address information for a quantity delivered in a specific shipment, to a specific ship-to address. |
2/1800 | The N9 segment identifies the shipment identification number and suffix number, if one exists, for the shipment which resulted in the voucher action. |
3/0100 | CTT01 identifies the number of CS segments used in the transaction. If used, CTT02 is the hash total of the values found in monetary amount (AMT02) for each AMT segment at position 100 in table 2. See data element 347 for proper hashing technique. |
rev 04/12/2024