ITS File Format Attachment J-1.xlsx
XLSX spreadsheet 117 KB Posted
- Solicitation number
- 75P00121R00003
View the file
Other files
| File | Type | Posted |
|---|---|---|
| 75P00121R00003_00001.pdf | ||
| 75P00121R00003_BASE.pdf | ||
| J.4_Past Performance Questionaire.pdf | ||
| SPS 440 File Format - Attachment J-2.pdf | ||
| Estimated transaction voilumes J-6 final 09252020.docx | DOCX document | |
| Attachment J.5.pdf | ||
| Price Proposal Submission Sheet J-3 final 10022020.docx | DOCX document |
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Original
| FOREIGN WIRE PAYMENT |
| USD PAYMENT |
| File Header Record | |||||||
| EXAMPLE: XXMMDDYY.001 MMDDYY 01 VENDOR PAYMENTS | |||||||
| *ENDMSG* | |||||||
| # | Field Name | Type | Length | Start Position | End Position | KFC Validation Rules | Notes |
| 1 | File Name | AN | 12 | 1 | 12 | If invalid or missing, reject the file | Should be XXMMDDYY.001, where MMDDYY is current business month, day and year. The file extension".001" can be incremented if multiple file are porcessed on same day, for example ".002". The 2 character apha beginning is agency specific. Recommend using 2 characters that represent the customer Agency's name - this would need to be confirmed with ITS.gov prior to use |
| 2 | Current Date | AN | 6 | 14 | 19 | If invalid or missing, reject the file | Date should match date in file name |
| 3 | Batch Sequence Number | N | 2 | 21 | 22 | ||
| 4 | Descriptive File Title | AN | 19 | 24 | 43 | Type of payments | |
| 5 | *ENDMSG* | AN | 8 | 1 | 8 | Concludes header record | |
| Wire Payment Detail Record | |||||||
| # | Field Name | Type | Length | Start Position | End Position | KFC Validation Rules | Notes |
| 6 | [FXR] | A | Required for wire payments. Start of payment record | ||||
| 7 | :ALC: | N | 8 | 1 | 8 | If invalid or missing, reject the file | Should be Agency's ALC |
| 8 | :SCHEDULE: | AN | 14 | 1 | 14 | Manually validated against SPS certification | Schedule Number, no minimum |
| 9 | :30 VALUE DATE: | AN | 6 | 1 | 6 | Must be two business days from date in file name | In YYMMDD format. US holidays should be taken into consideration |
| 10 | :BASE AMT: | AN | 21 | 1 | 21 | If missing, reject the file | "USD" space USD amount indicated, including decimals |
| 11 | :FX AMT: | AN | 3 | 1 | 3 | If missing, reject the file | "USD" only |
| 12 | :57D PAY THRU: | AN | 8/11 | 1 | 11 | If missing, reject the file | SWIFT Address should be 8 or 11 alphanumeric characters |
| 13 | BANK NAME | AN | 35 | 1 | 35 | Not all foreign wires / countries require full bank name | |
| 14 | BANK ADDRESS | AN | 35 | 1 | 35 | Not all foreign wires / countries require full bank address | |
| 15 | BANK ADDRESS | AN | 35 | 1 | 35 | Not all foreign wires / countries require full bank address | |
| 16 | BANK ADDRESS | AN | 35 | 1 | 35 | Not all foreign wires / countries require full bank address | |
| 17 | :59 BENEFICIARY: | AN | 34 | 1 | 34 | Beneficiary Account Number can be up to 34 alphanumeric characters | |
| 18 | BENEFICIARY NAME | AN | 35 | 1 | 35 | ||
| 19 | BENEFICIARY ADDRESS | AN | 35 | 1 | 35 | Not all foreign wires / countries require full beneficiary address | |
| 20 | BENEFICIARY ADDRESS | AN | 35 | 1 | 35 | Not all foreign wires / countries require full beneficiary address | |
| 21 | BENEFICIARY ADDRESS | AN | 35 | 1 | 35 | Not all foreign wires / countries require full beneficiary address | |
| 22 | :70 BENEF INFO: | ||||||
| 23 | PAYMENT INFORMATION | AN | 35 | 1 | 35 | ||
| 24 | PAYMENT INFORMATION | AN | 35 | 1 | 35 | ||
| 25 | PAYMENT INFORMATION | AN | 35 | 1 | 35 | ||
| 26 | PAYMENT INFORMATION | AN | 35 | 1 | 35 | ||
| 27 | :72 RECEIVER INFO: | ||||||
| 28 | BANK DETAILS | AN | 35 | 1 | 35 | Some foreign currencies require additional bank details (i.e. bank contact phone number, in country vendor codes). These requirements should be populated in this field | |
| 29 | BANK DETAILS | AN | 35 | 1 | 35 | Some foreign currencies require additional bank details (i.e. bank contact phone number, in country vendor codes). These requirements should be populated in this field | |
| 30 | BANK DETAILS | AN | 35 | 1 | 35 | Some foreign currencies require additional bank details (i.e. bank contact phone number, in country vendor codes). These requirements should be populated in this field | |
| 31 | BANK DETAILS | AN | 35 | 1 | 35 | Some foreign currencies require additional bank details (i.e. bank contact phone number, in country vendor codes). These requirements should be populated in this field | |
| *32 | :TAS: | N | 2 | 1 | 2 | TAS Sub-level Prefix Code | |
| *33 | N | 3 | 3 | 5 | TAS Allocation Transfer Agency Identifier | ||
| *34 | N | 3 | 6 | 8 | TAS Agency Identifier | ||
| *35 | N | 4 | 9 | 12 | TAS Beginning Period of Availability | ||
| *36 | N | 4 | 13 | 16 | TAS Ending Period of Availability | ||
| *37 | AN | 1 | 17 | 17 | TAS Availability Code | ||
| *38 | N | 4 | 18 | 21 | TAS Main Account Code | ||
| *39 | N | 3 | 22 | 24 | TAS Sub-Account Code | ||
| *40 | :BETC: | AN | 8 | 1 | 8 | Businss Event Type Code | |
| *41 | :AMT: | N | 17 | 1 | 17 | USD amount including decimals | |
| *42 | *ENDMSG* | A | Constitutes end of payment record | ||||
| Trailer Record | |||||||
| EXAMPLE: *ENDFILE* 000001 00000000000000000 | |||||||
| # | Field Name | Type | Length | Start Position | End Position | KFC Validation Rules | Notes |
| 43 | *ENDFILE* | A | 9 | 1 | 9 | ||
| 44 | Record Count | N | 6 | 11 | 16 | Front fill with zeroes; total number of payments in file | |
| 45 | File Total | AN | 16 | 18 | 33 | Total USD found in file for all payments, no punctuation | |
| Footnotes | |||||||
| * Lines 32, 33, 34, 35, 36, 37, 38, 39, 40, 41 can repeat up to 100 per payment to fulfill agency requirements for TAS / BETC |
| FOREIGN WIRE PAYMENT |
| FOREIGN CURRENCY PAYMENT |
| File Header Record | |||||||
| EXAMPLE: XXMMDDYY.001 MMDDYY 01 VENDOR PAYMENTS | |||||||
| *ENDMSG* | |||||||
| # | Field Name | Type | Length | Start Position | End Position | KFC Validation Rules | Notes |
| 1 | File Name | AN | 12 | 1 | 12 | If invalid or missing, reject the file | Should be XXMMDDYY.001, where MMDDYY is current business month, day and year. The file extension".001" can be incremented if multiple file are porcessed on same day, for example ".002". The 2 character apha beginning is agency specific. Recommend using 2 characters that represent the customer Agency's name - this would need to be confirmed with ITS.gov prior to use |
| 2 | Current Date | AN | 6 | 14 | 19 | If invalid or missing, reject the file | Date should match date in file name |
| 3 | Batch Sequence Number | N | 2 | 21 | 22 | ||
| 4 | Descriptive File Title | AN | 19 | 24 | 43 | Type of payments | |
| 5 | *ENDMSG* | AN | 8 | 1 | 8 | Concludes header record | |
| Wire Payment Detail Record | |||||||
| # | Field Name | Type | Length | Start Position | End Position | KFC Validation Rules | Notes |
| 6 | [FXR] | A | Required for wire payments. Start of payment record | ||||
| 7 | :ALC: | N | 8 | 1 | 8 | If invalid or missing, reject the file | Should be Agency's ALC |
| 8 | :SCHEDULE: | AN | 14 | 1 | 14 | Manually validated against SPS certification | Schedule Number, no minimum |
| 9 | :30 VALUE DATE: | AN | 6 | 1 | 6 | Must be two business days from date in file name | In YYMMDD format. US holidays should be taken into consideration |
| 10 | :BASE AMT: | AN | 3 | 1 | 3 | If missing, reject the file | "USD" only |
| 11 | :FX AMT: | AN | 21 | 1 | 21 | If missing, reject the file | 3 digit currency code space FX total including decimal |
| 12 | :57D PAY THRU: | AN | 8/11 | 1 | 11 | If missing, reject the file | SWIFT Address should be 8 or 11 alphanumeric characters |
| 13 | BANK NAME | AN | 35 | 1 | 35 | Not all foreign wires / countries require full bank name | |
| 14 | BANK ADDRESS | AN | 35 | 1 | 35 | Not all foreign wires / countries require full bank address | |
| 15 | BANK ADDRESS | AN | 35 | 1 | 35 | Not all foreign wires / countries require full bank address | |
| 16 | BANK ADDRESS | AN | 35 | 1 | 35 | Not all foreign wires / countries require full bank address | |
| 17 | :59 BENEFICIARY: | AN | 34 | 1 | 34 | Beneficiary Account Number can be up to 34 alphanumeric characters | |
| 18 | BENEFICIARY NAME | AN | 35 | 1 | 35 | ||
| 19 | BENEFICIARY ADDRESS | AN | 35 | 1 | 35 | Not all foreign wires / countries require full beneficiary address | |
| 20 | BENEFICIARY ADDRESS | AN | 35 | 1 | 35 | Not all foreign wires / countries require full beneficiary address | |
| 21 | BENEFICIARY ADDRESS | AN | 35 | 1 | 35 | Not all foreign wires / countries require full beneficiary address | |
| 22 | :70 BENEF INFO: | ||||||
| 23 | PAYMENT INFORMATION | AN | 35 | 1 | 35 | ||
| 24 | PAYMENT INFORMATION | AN | 35 | 1 | 35 | ||
| 25 | PAYMENT INFORMATION | AN | 35 | 1 | 35 | ||
| 26 | PAYMENT INFORMATION | AN | 35 | 1 | 35 | ||
| 27 | :72 RECEIVER INFO: | ||||||
| 28 | BANK DETAILS | AN | 35 | 1 | 35 | Some foreign currencies require additional bank details (i.e. bank contact phone number, in country vendor codes). These requirements should be populated in this field | |
| 29 | BANK DETAILS | AN | 35 | 1 | 35 | Some foreign currencies require additional bank details (i.e. bank contact phone number, in country vendor codes). These requirements should be populated in this field | |
| 30 | BANK DETAILS | AN | 35 | 1 | 35 | Some foreign currencies require additional bank details (i.e. bank contact phone number, in country vendor codes). These requirements should be populated in this field | |
| 31 | BANK DETAILS | AN | 35 | 1 | 35 | Some foreign currencies require additional bank details (i.e. bank contact phone number, in country vendor codes). These requirements should be populated in this field | |
| *32 | :TAS: | N | 2 | 1 | 2 | TAS Sub-level Prefix Code | |
| *33 | N | 3 | 3 | 5 | TAS Allocation Transfer Agency Identifier | ||
| *34 | N | 3 | 6 | 8 | TAS Agency Identifier | ||
| *35 | N | 4 | 9 | 12 | TAS Beginning Period of Availability | ||
| *36 | N | 4 | 13 | 16 | TAS Ending Period of Availability | ||
| *37 | AN | 1 | 17 | 17 | TAS Availability Code | ||
| *38 | N | 4 | 18 | 21 | TAS Main Account Code | ||
| *39 | N | 3 | 22 | 24 | TAS Sub-Account Code | ||
| *40 | :BETC: | AN | 8 | 1 | 8 | Businss Event Type Code | |
| *41 | :AMT: | N | 17 | 1 | 17 | USD amount including decimals | |
| *42 | *ENDMSG* | A | Constitutes end of payment record | ||||
| Trailer Record | |||||||
| EXAMPLE: *ENDFILE* 000001 00000000000000000 | |||||||
| # | Field Name | Type | Length | Start Position | End Position | KFC Validation Rules | Notes |
| 43 | *ENDFILE* | A | 9 | 1 | 9 | ||
| 44 | Record Count | N | 6 | 11 | 16 | Front fill with zeroes; total number of payments in file | |
| 45 | File Total | AN | 16 | 18 | 33 | Total USD found in file for all payments, no punctuation | |
| Footnotes | |||||||
| * Lines 32, 33, 34, 35, 36, 37, 38, 39, 40, 41 can repeat up to 100 per payment to fulfill agency requirements for TAS / BETC |
| FOREIGN WIRE PAYMENT |
| USD CONVERTED TO FOREIGN CURRENCY PAYMENT |
| File Header Record | |||||||
| EXAMPLE: XXMMDDYY.001 MMDDYY 01 VENDOR PAYMENTS | |||||||
| *ENDMSG* | |||||||
| # | Field Name | Type | Length | Start Position | End Position | KFC Validation Rules | Notes |
| 1 | File Name | AN | 12 | 1 | 12 | If invalid or missing, reject the file | Should be XXMMDDYY.001, where MMDDYY is current business month, day and year. The file extension".001" can be incremented if multiple file are porcessed on same day, for example ".002". The 2 character apha beginning is agency specific. Recommend using 2 characters that represent the customer Agency's name - this would need to be confirmed with ITS.gov prior to use |
| 2 | Current Date | AN | 6 | 14 | 19 | If invalid or missing, reject the file | Date should match date in file name |
| 3 | Batch Sequence Number | N | 2 | 21 | 22 | ||
| 4 | Descriptive File Title | AN | 19 | 24 | 43 | Type of payments | |
| 5 | *ENDMSG* | AN | 8 | 1 | 8 | Concludes header record | |
| Wire Payment Detail Record | |||||||
| # | Field Name | Type | Length | Start Position | End Position | KFC Validation Rules | Notes |
| 6 | [FXR] | A | Required for wire payments. Start of payment record | ||||
| 7 | :ALC: | N | 8 | 1 | 8 | If invalid or missing, reject the file | Should be Agency's ALC |
| 8 | :SCHEDULE: | AN | 14 | 1 | 14 | Manually validated against SPS certification | Schedule Number, no minimum |
| 9 | :30 VALUE DATE: | AN | 6 | 1 | 6 | Must be two business days from date in file name | In YYMMDD format. US holidays should be taken into consideration |
| 10 | :BASE AMT: | AN | 21 | 1 | 21 | If missing, reject the file | "USD" space USD amount to be converted including decimals |
| 11 | :FX AMT: | AN | 3 | 1 | 3 | If missing, reject the file | 3 digit currency code of payment to be converted to |
| 12 | :57D PAY THRU: | AN | 8/11 | 1 | 11 | If missing, reject the file | SWIFT Address should be 8 or 11 alphanumeric characters |
| 13 | BANK NAME | AN | 35 | 1 | 35 | Not all foreign wires / countries require full bank name | |
| 14 | BANK ADDRESS | AN | 35 | 1 | 35 | Not all foreign wires / countries require full bank address | |
| 15 | BANK ADDRESS | AN | 35 | 1 | 35 | Not all foreign wires / countries require full bank address | |
| 16 | BANK ADDRESS | AN | 35 | 1 | 35 | Not all foreign wires / countries require full bank address | |
| 17 | :59 BENEFICIARY: | AN | 34 | 1 | 34 | Beneficiary Account Number can be up to 34 alphanumeric characters | |
| 18 | BENEFICIARY NAME | AN | 35 | 1 | 35 | Not all foreign wires / countries require full beneficiary address | |
| 19 | BENEFICIARY ADDRESS | AN | 35 | 1 | 35 | Not all foreign wires / countries require full beneficiary address | |
| 20 | BENEFICIARY ADDRESS | AN | 35 | 1 | 35 | Not all foreign wires / countries require full beneficiary address | |
| 21 | BENEFICIARY ADDRESS | AN | 35 | 1 | 35 | ||
| 22 | :70 BENEF INFO: | ||||||
| 23 | PAYMENT INFORMATION | AN | 35 | 1 | 35 | ||
| 24 | PAYMENT INFORMATION | AN | 35 | 1 | 35 | ||
| 25 | PAYMENT INFORMATION | AN | 35 | 1 | 35 | ||
| 26 | PAYMENT INFORMATION | AN | 35 | 1 | 35 | ||
| 27 | :72 RECEIVER INFO: | ||||||
| 28 | BANK DETAILS | AN | 35 | 1 | 35 | Some foreign currencies require additional bank details (i.e. bank contact phone number, in country vendor codes). These requirements should be populated in this field | |
| 29 | BANK DETAILS | AN | 35 | 1 | 35 | Some foreign currencies require additional bank details (i.e. bank contact phone number, in country vendor codes). These requirements should be populated in this field | |
| 30 | BANK DETAILS | AN | 35 | 1 | 35 | Some foreign currencies require additional bank details (i.e. bank contact phone number, in country vendor codes). These requirements should be populated in this field | |
| 31 | BANK DETAILS | AN | 35 | 1 | 35 | Some foreign currencies require additional bank details (i.e. bank contact phone number, in country vendor codes). These requirements should be populated in this field | |
| *32 | :TAS: | N | 2 | 1 | 2 | TAS Sub-level Prefix Code | |
| *33 | N | 3 | 3 | 5 | TAS Allocation Transfer Agency Identifier | ||
| *34 | N | 3 | 6 | 8 | TAS Agency Identifier | ||
| *35 | N | 4 | 9 | 12 | TAS Beginning Period of Availability | ||
| *36 | N | 4 | 13 | 16 | TAS Ending Period of Availability | ||
| *37 | AN | 1 | 17 | 17 | TAS Availability Code | ||
| *38 | N | 4 | 18 | 21 | TAS Main Account Code | ||
| *39 | N | 3 | 22 | 24 | TAS Sub-Account Code | ||
| *40 | :BETC: | AN | 8 | 1 | 8 | Businss Event Type Code | |
| *41 | :AMT: | N | 17 | 1 | 17 | USD amount including decimals | |
| *42 | *ENDMSG* | A | Constitutes end of payment record | ||||
| Trailer Record | |||||||
| EXAMPLE: *ENDFILE* 000001 00000000000000000 | |||||||
| # | Field Name | Type | Length | Start Position | End Position | KFC Validation Rules | Notes |
| 43 | *ENDFILE* | A | 9 | 1 | 9 | ||
| 44 | Record Count | N | 6 | 11 | 16 | Front fill with zeroes; total number of payments in file | |
| 45 | File Total | AN | 16 | 18 | 33 | Total USD found in file for all payments, no punctuation | |
| Footnotes | |||||||
| * Lines 32, 33, 34, 35, 36, 37, 38, 39, 40, 41 can repeat up to 100 per payment to fulfill agency requirements for TAS / BETC |
| FOREIGN CHECK PAYMENT |
| FOREIGN CURRENCY PAYMENT |
| File Header Record | |||||||
| EXAMPLE: XXMMDDYY.001 MMDDYY 01 VENDOR PAYMENTS | |||||||
| *ENDMSG* | |||||||
| # | Field Name | Type | Length | Start Position | End Position | KFC Validation Rules | Notes |
| 1 | File Name | AN | 12 | 1 | 12 | If invalid or missing, reject the file | Should be XXMMDDYY.001, where MMDDYY is current business month, day and year. The file extension".001" can be incremented if multiple file are porcessed on same day, for example ".002". The 2 character apha beginning is agency specific. Recommend using 2 characters that represent the customer Agency's name - this would need to be confirmed with ITS.gov prior to use |
| 2 | Current Date | AN | 6 | 14 | 19 | If invalid or missing, reject the file | Date should match date in file name |
| 3 | Batch Sequence Number | N | 2 | 21 | 22 | ||
| 4 | Descriptive File Title | AN | 19 | 24 | 43 | Type of payments | |
| 5 | *ENDMSG* | AN | 8 | 1 | 8 | Concludes header record | |
| Wire Payment Detail Record | |||||||
| # | Field Name | Type | Length | Start Position | End Position | KFC Validation Rules | Notes |
| 6 | [DFT] | A | Required for check payments. Start of payment record | ||||
| 7 | :ALC: | N | 8 | 1 | 8 | If invalid or missing, reject the file | Should be Agency's ALC |
| 8 | :SCHEDULE: | AN | 14 | 1 | 14 | Manually validated against SPS certification | Schedule Number, no minimum |
| 9 | :30 VALUE DATE: | AN | 6 | 1 | 6 | Must be two business days from date in file name | In YYMMDD format. US holidays should be taken into consideration |
| 10 | :PAY TO: | AN | 35 | 1 | 35 | Check Beneficiary Name. This name will print on check. | |
| 11 | CHECK BENEFICIARY ADDRESS | AN | 35 | 1 | 35 | This address will be used to mail the check | |
| 12 | CHECK BENEFICIARY ADDRESS | AN | 35 | 1 | 35 | This address will be used to mail the check | |
| 13 | CHECK BENEFICIARY ADDRESS | AN | 35 | 1 | 35 | This address will be used to mail the check. Line three must contain the country | |
| 14 | :BASE AMT: | AN | 3 | 1 | 3 | If missing, reject the file | "USD" only |
| 15 | :FX AMT: | AN | 21 | 1 | 21 | If missing, reject the file | 3 digit currency code space FX total including decimal |
| 16 | :BENEF INFO: | ||||||
| 17 | CHECK PAYMENT INFORMATION | AN | 35 | 1 | 35 | This information will print on the check stub | |
| 18 | CHECK PAYMENT INFORMATION | AN | 35 | 1 | 35 | This information will print on the check stub | |
| 19 | CHECK PAYMENT INFORMATION | AN | 35 | 1 | 35 | This information will print on the check stub | |
| 20 | CHECK PAYMENT INFORMATION | AN | 35 | 1 | 35 | This information will print on the check stub | |
| *21 | :TAS: | N | 2 | 1 | 2 | TAS Sub-level Prefix Code | |
| *22 | N | 3 | 3 | 5 | TAS Allocation Transfer Agency Identifier | ||
| *23 | N | 3 | 6 | 8 | TAS Agency Identifier | ||
| *24 | N | 4 | 9 | 12 | TAS Beginning Period of Availability | ||
| *25 | N | 4 | 13 | 16 | TAS Ending Period of Availability | ||
| *26 | AN | 1 | 17 | 17 | TAS Availability Code | ||
| *27 | N | 4 | 18 | 21 | TAS Main Account Code | ||
| *28 | N | 3 | 22 | 24 | TAS Sub-Account Code | ||
| *29 | :BETC: | AN | 8 | 1 | 8 | Businss Event Type Code | |
| *30 | :AMT: | N | 17 | 1 | 17 | USD amount including decimals | |
| *31 | *ENDMSG* | A | Constitutes end of payment record | ||||
| Trailer Record | |||||||
| EXAMPLE: *ENDFILE* 000001 00000000000000000 | |||||||
| # | Field Name | Type | Length | Start Position | End Position | KFC Validation Rules | Notes |
| *32 | *ENDFILE* | A | 9 | 1 | 9 | ||
| *33 | Record Count | N | 6 | 11 | 16 | Front fill with zeroes; total number of payments in file | |
| *34 | File Total | AN | 16 | 18 | 33 | Total USD found in file for all payments, no punctuation | |
| Footnotes | |||||||
| * Lines 21, 22, 23, 24, 25, 26, 27, 28, 29, 30 can repeat up to 100 per payment to fulfill agency requirements for TAS / BETC |
| FOREIGN CHECK PAYMENT |
| USD CONVERTED TO FOREIGN CURRENCY PAYMENT |
| File Header Record | |||||||
| EXAMPLE: XXMMDDYY.001 MMDDYY 01 VENDOR PAYMENTS | |||||||
| *ENDMSG* | |||||||
| # | Field Name | Type | Length | Start Position | End Position | KFC Validation Rules | Notes |
| 1 | File Name | AN | 12 | 1 | 12 | If invalid or missing, reject the file | Should be XXMMDDYY.001, where MMDDYY is current business month, day and year. The file extension".001" can be incremented if multiple file are porcessed on same day, for example ".002". The 2 character apha beginning is agency specific. Recommend using 2 characters that represent the customer Agency's name - this would need to be confirmed with ITS.gov prior to use |
| 2 | Current Date | AN | 6 | 14 | 19 | If invalid or missing, reject the file | Date should match date in file name |
| 3 | Batch Sequence Number | N | 2 | 21 | 22 | ||
| 4 | Descriptive File Title | AN | 19 | 24 | 43 | Type of payments | |
| 5 | *ENDMSG* | AN | 8 | 1 | 8 | Concludes header record | |
| Wire Payment Detail Record | |||||||
| # | Field Name | Type | Length | Start Position | End Position | KFC Validation Rules | Notes |
| 6 | [DFT] | A | Required for check payments. Start of payment record | ||||
| 7 | :ALC: | N | 8 | 1 | 8 | If invalid or missing, reject the file | Should be Agency's ALC |
| 8 | :SCHEDULE: | AN | 14 | 1 | 14 | Manually validated against SPS certification | Schedule Number, no minimum |
| 9 | :30 VALUE DATE: | AN | 6 | 1 | 6 | Must be two business days from date in file name | In YYMMDD format. US holidays should be taken into consideration |
| 10 | :PAY TO: | AN | 35 | 1 | 35 | Check Beneficiary Name. This name will print on check. | |
| 11 | CHECK BENEFICIARY ADDRESS | AN | 35 | 1 | 35 | This address will be used to mail the check | |
| 12 | CHECK BENEFICIARY ADDRESS | AN | 35 | 1 | 35 | This address will be used to mail the check | |
| 13 | CHECK BENEFICIARY ADDRESS | AN | 35 | 1 | 35 | This address will be used to mail the check. Line three must contain the country | |
| 14 | :BASE AMT: | AN | 21 | 1 | 21 | If missing, reject the file | "USD" space USD amount to be converted including decimals |
| 15 | :FX AMT: | AN | 3 | 1 | 3 | If missing, reject the file | 3 digit currency code of payment to be converted to |
| 16 | :BENEF INFO: | ||||||
| 17 | CHECK PAYMENT INFORMATION | AN | 35 | 1 | 35 | This information will print on the check stub | |
| 18 | CHECK PAYMENT INFORMATION | AN | 35 | 1 | 35 | This information will print on the check stub | |
| 19 | CHECK PAYMENT INFORMATION | AN | 35 | 1 | 35 | This information will print on the check stub | |
| 20 | CHECK PAYMENT INFORMATION | AN | 35 | 1 | 35 | This information will print on the check stub | |
| *21 | :TAS: | N | 2 | 1 | 2 | TAS Sub-level Prefix Code | |
| *22 | N | 3 | 3 | 5 | TAS Allocation Transfer Agency Identifier | ||
| *23 | N | 3 | 6 | 8 | TAS Agency Identifier | ||
| *24 | N | 4 | 9 | 12 | TAS Beginning Period of Availability | ||
| *25 | N | 4 | 13 | 16 | TAS Ending Period of Availability | ||
| *26 | AN | 1 | 17 | 17 | TAS Availability Code | ||
| *27 | N | 4 | 18 | 21 | TAS Main Account Code | ||
| *28 | N | 3 | 22 | 24 | TAS Sub-Account Code | ||
| *29 | :BETC: | AN | 8 | 1 | 8 | Businss Event Type Code | |
| *30 | :AMT: | N | 17 | 1 | 17 | USD amount including decimals | |
| *31 | *ENDMSG* | A | Constitutes end of payment record | ||||
| Trailer Record | |||||||
| EXAMPLE: *ENDFILE* 000001 00000000000000000 | |||||||
| # | Field Name | Type | Length | Start Position | End Position | KFC Validation Rules | Notes |
| *32 | *ENDFILE* | A | 9 | 1 | 9 | ||
| *33 | Record Count | N | 6 | 11 | 16 | Front fill with zeroes; total number of payments in file | |
| *34 | File Total | AN | 16 | 18 | 33 | Total USD found in file for all payments, no punctuation | |
| Footnotes | |||||||
| * Lines 21, 22, 23, 24, 25, 26, 27, 28, 29, 30 can repeat up to 100 per payment to fulfill agency requirements for TAS / BETC |
| FOREIGN WIRE PAYMENT |
| ADVANCED RATE PAYMENT |
| File Header Record | |||||||
| EXAMPLE: XXMMDDYY.001 MMDDYY 01 VENDOR PAYMENTS | |||||||
| *ENDMSG* | |||||||
| # | Field Name | Type | Length | Start Position | End Position | KFC Validation Rules | Notes |
| 1 | File Name | AN | 12 | 1 | 12 | If invalid or missing, reject the file | Should be XXMMDDYY.001, where MMDDYY is current business month, day and year. The file extension".001" can be incremented if multiple file are porcessed on same day, for example ".002". The 2 character apha beginning is agency specific. Recommend using 2 characters that represent the customer Agency's name - this would need to be confirmed with ITS.gov prior to use |
| 2 | Current Date | AN | 6 | 14 | 19 | If invalid or missing, reject the file | Date should match date in file name |
| 3 | Batch Sequence Number | N | 2 | 21 | 22 | ||
| 4 | Descriptive File Title | AN | 19 | 24 | 43 | Type of payments | |
| 5 | *ENDMSG* | AN | 8 | 1 | 8 | Concludes header record | |
| Wire Payment Detail Record | |||||||
| # | Field Name | Type | Length | Start Position | End Position | KFC Validation Rules | Notes |
| 6 | [FXR] | A | Required for wire payments. Start of payment record | ||||
| 7 | :ALC: | N | 8 | 1 | 8 | If invalid or missing, reject the file | Should be Agency's ALC |
| 8 | :SCHEDULE: | AN | 14 | 1 | 14 | Manually validated against SPS certification | Schedule Number, no minimum |
| 9 | :30 VALUE DATE: | AN | 6 | 1 | 6 | Must be two business days from date in file name | In YYMMDD format. US holidays should be taken into consideration |
| 10 | :BASE AMT: | AN | 21 | 1 | 21 | If missing, reject the file | "USD" space USD amount indicated, including decimals |
| 11 | :FX AMT: | AN | 21 | 1 | 21 | If missing, reject the file | 3 digit currency code space FX total including decimal |
| 12 | :57D PAY THRU: | AN | 8/11 | 1 | 11 | If missing, reject the file | SWIFT Address should be 8 or 11 alphanumeric characters |
| 13 | BANK NAME | AN | 35 | 1 | 35 | Not all foreign wires / countries require full bank name | |
| 14 | BANK ADDRESS | AN | 35 | 1 | 35 | Not all foreign wires / countries require full bank address | |
| 15 | BANK ADDRESS | AN | 35 | 1 | 35 | Not all foreign wires / countries require full bank address | |
| 16 | BANK ADDRESS | AN | 35 | 1 | 35 | Not all foreign wires / countries require full bank address | |
| 17 | :59 BENEFICIARY: | AN | 34 | 1 | 34 | Beneficiary Account Number can be up to 34 alphanumeric characters | |
| 18 | BENEFICIARY NAME | AN | 35 | 1 | 35 | Not all foreign wires / countries require full beneficiary address | |
| 19 | BENEFICIARY ADDRESS | AN | 35 | 1 | 35 | Not all foreign wires / countries require full beneficiary address | |
| 20 | BENEFICIARY ADDRESS | AN | 35 | 1 | 35 | Not all foreign wires / countries require full beneficiary address | |
| 21 | BENEFICIARY ADDRESS | AN | 35 | 1 | 35 | ||
| 22 | :70 BENEF INFO: | ||||||
| 23 | PAYMENT INFORMATION | AN | 35 | 1 | 35 | ||
| 24 | PAYMENT INFORMATION | AN | 35 | 1 | 35 | ||
| 25 | PAYMENT INFORMATION | AN | 35 | 1 | 35 | ||
| 26 | PAYMENT INFORMATION | AN | 35 | 1 | 35 | ||
| 27 | :72 RECEIVER INFO: | ||||||
| 28 | BANK DETAILS | AN | 35 | 1 | 35 | Some foreign currencies require additional bank details (i.e. bank contact phone number, in country vendor codes). These requirements should be populated in this field | |
| 29 | BANK DETAILS | AN | 35 | 1 | 35 | Some foreign currencies require additional bank details (i.e. bank contact phone number, in country vendor codes). These requirements should be populated in this field | |
| 30 | BANK DETAILS | AN | 35 | 1 | 35 | Some foreign currencies require additional bank details (i.e. bank contact phone number, in country vendor codes). These requirements should be populated in this field | |
| 31 | BANK DETAILS | AN | 35 | 1 | 35 | Some foreign currencies require additional bank details (i.e. bank contact phone number, in country vendor codes). These requirements should be populated in this field | |
| *32 | :TAS: | N | 2 | 1 | 2 | TAS Sub-level Prefix Code | |
| *33 | N | 3 | 3 | 5 | TAS Allocation Transfer Agency Identifier | ||
| *34 | N | 3 | 6 | 8 | TAS Agency Identifier | ||
| *35 | N | 4 | 9 | 12 | TAS Beginning Period of Availability | ||
| *36 | N | 4 | 13 | 16 | TAS Ending Period of Availability | ||
| *37 | AN | 1 | 17 | 17 | TAS Availability Code | ||
| *38 | N | 4 | 18 | 21 | TAS Main Account Code | ||
| *39 | N | 3 | 22 | 24 | TAS Sub-Account Code | ||
| *40 | :BETC: | AN | 8 | 1 | 8 | Businss Event Type Code | |
| *41 | :AMT: | N | 17 | 1 | 17 | USD amount including decimals | |
| *42 | *ENDMSG* | A | Constitutes end of payment record | ||||
| Trailer Record | |||||||
| EXAMPLE: *ENDFILE* 000001 00000000000000000 | |||||||
| # | Field Name | Type | Length | Start Position | End Position | KFC Validation Rules | Notes |
| 43 | *ENDFILE* | A | 9 | 1 | 9 | ||
| 44 | Record Count | N | 6 | 11 | 16 | Front fill with zeroes; total number of payments in file | |
| 45 | File Total | AN | 16 | 18 | 33 | Total USD found in file for all payments, no punctuation | |
| Footnotes | |||||||
| * Lines 32, 33, 34, 35, 36, 37, 38, 39, 40, 41 can repeat up to 100 per payment to fulfill agency requirements for TAS / BETC |
Revision History
| Date | Version | Author | Release | Bug | Description |
| 09/02/16 | 1.2 | T. Spratte | 13.3 | n/a | PMT1025 - corrected KFC Validation of BASE AMT and FX AMT; if missing reject. Line 13 and 14 - called out that file will be rejected fi the tag is not provided. Added footnote for lines 13 and 14. |
PMT1026 - added "required" to ENDMSG, line #35; inserted line # for row 34
| 01/09/17 | 1.3 | J.Wilcher | 13.3 | n/a | PMT1025, 1032, 1033, & 1034 - corrected :57D Pay Thru: tag to correctly show the /xx- required Party Identifier |
| 02/24/17 | 1.4 | J.Wilcher | 13.3 | n/a | Updated to include file naming conventions for Auto & Manual upload files. |
| 03/17/17 | 1.5 | J.Wilcher | 14.0 | n/a | Updated Auto upload file name to reflect Required 'E' in optional agency extension field. |
| 03/30/17 | 2.0 | J.Wilcher | 14.0 | n/a | Consoliidated and re named table to reflect 1 wire and 1 check specification that can be used for the various exchange rate payment types. |
| 04/07/17 | 3.0 | J.Wilcher | 14.0 | n/a | Updated File Name Examples, Corrected FX AMT Length, Updated TAS AMT Length and example |
| 05/16/17 | 4.0 | J.Mack | 14.0 | n/a | 57D PAY THRU: so that /SA- with no SWIFT code is valid, calculation of file total instruction. |
| 05/22/17 | 5.0 | J.Mack | 15.0 | n/a | :70 BENEF INFO: Updated on Check payment to include length and the number 70 |
| 04/05/18 | 6.0 | J.Wilcher | 17.0 | n/a | Updated foot notes for line nubers 3 & 12 for both Checks & Wires to correctly state how Value Date is derived by ITS |
PMT1025-FS-STInput-Wire
FOREIGN WIRE PAYMENT
| TDO ST Manual Upload File Naming Convention |
| When the file is delivered to ITS manually via the file upload functionality with in ITS.gov by an ITS.gov user the following file naming convention must be followed: ST*MMDDCCYY.001, |
Example: STDA02242017.001 or STDLA102242017.001 -[ Where * is a two/four byte alpha character value associated with specific agency
- [.MMDDCCYY is current business month, day and year.
- [The file extension ‘.001’ can be incremented if multiple files are processed on same day, for example ‘.002’.
| TDO ST Auto Upload File Naming Convention |
| <file type>.<agency ID>[.Eagency extension field][.source system custom field].D<YYYYMMDD>.T<HHMMSSsss> |
Examples: ST.DA.EABC12334.TEST213.D20170224.T221115024 or ST.DLA1.EABC123.TEST213.D20170224.T221115024 or ST.AB.TEST213.D20170224.T221115024 or ST.ABC1.TEST213.D20170224.T221115024 or ST.DA.D20170224.T221115024 or ST.DLA1.D20170224.T221115024 -[ File name length limited to 44 characters -[ <file type> ST is the required required file type -[ <agency ID> is a two/four byte alphanumeric character value associated with specific agency -[.Eagency extension field] is optional - if used must begin with capital E -[.source system custom field] is optional
| File Header Record | |||||||
| EXAMPLE: | |||||||
| STMMDDYY.0NN MMDDYY 01 VENDOR PAYMENTS | |||||||
| *ENDMSG* | |||||||
| # | Field Name | Type | Length | Start Position | End Position | KFC Validation Rules | Notes |
| 1 | File Name | AN | 12 | 1 | 12 | If invalid or missing, reject the file | "XXMMDDYY.0NN " |
X = Alpha characters; 2 characters that represent the file (ITS.gov recommends "ST") M = Month D = Day Y = Year N = start with 1 each day; increment if multiple files are processed on same day
| 2 | Space | - | 1 | 13 | 13 | ||
| *3 | Current Date | AN | 6 | 14 | 19 | If invalid or missing, reject the file | "MMDDYY " |
- Date should match date in file name
- Date the file is generated
- Format: MMDDYY
| 4 | Space | - | 1 | 20 | 20 | |
| 5 | Batch Sequence Number | N | 2 | 21 | 22 | - 01-99 |
- unique for each file creation date
| 6 | Space | - | 1 | 23 | 23 | ||
| 7 | Descriptive File Title | AN | 20 | 24 | 43 | - Type of payments (e.g., VENDOR PAYMENTS) | |
| 8 | *ENDMSG* | AN | 8 | 1 | 8 | If missing, reject the file | - positions 1-8 = *ENDMSG* |
- Concludes header record
| Wire Payment Detail Record | |||||||
| # | Field Name | Type | Length | Start Position | End Position | KFC Validation Rules | Notes |
| 9 | [FXR] | A | 5 | 1 | 5 | If invalid or missing, reject the file | - positions 1-5 = [FXR] |
- Required. Start of payment record.
10 :ALC: N 13 1 13 If invalid or missing, reject the file - positions 1-5 = :ALC:
- positions 6-13 = Agency's ALC
- required 11 :SCHEDULE: AN 24 1 24 Validated against SPS certification - positions 1-10 = :SCHEDULE:
- positions 11-24 = schedule number
- schedule number has no minimum requirement
- schedule number maximum is 14 characters
- required *12 :30 VALUE DATE: AN 21 1 21 - positions 1-15 = :30 VALUE DATE:
- positions 16-21 = YYMMDD
- required
- US holidays should be taken into consideration 13 :BASE AMT: AN 28 1 28 ** If missing, reject the file
See foot notes for usage information! - Debit Currency Amount / required
- positions 1-10 = :BASE AMT:
- positions 11-13 = USD
Or
- positions 11-13 = USD
- position 14-14 = 'space'
- positions 15-28 = amount, including decimal
14 :FX AMT: AN 26 1 26 ** If missing, reject the file
See foot notes for usage information! - Foreign currency and amount / required
- positions 1-8 = :FX AMT:
- positions 9-11 = 3 character currency code
OR
- positions 9-11 = 3 character currency code
- position 12-12 = 'space'
- positions 13-26 = amount, including decimal NOTE: amount is 14 characters for 3 digit countries; 13 characters for 2 digit countries 15 :57D PAY THRU: AN 31 1 31 If missing, reject the file - positions 1-14 = :57D PAY THRU:
- positions 15-18 = /XX- XX = SA or SC
SA = SWIFT
SC = Sort Code
- positions 19-31 = SWIFT or Sort Code, or None Swift (8 or 11 alphanumeric characters, or None) Sort Code (up to 13 alphanumeric characters) NOTE: Countries may have specific Sort Code requirements, Refer to country specific requirements for length and content detail). When country requirements require use of country specific code use /SA- followed by no value.
- required
Examples :57D PAY THRU:/SC-1122AABBCCDDE
:57D PAY THRU:/SA-ABCD1234567
:57D PAY THRU:/SA-
| 16 | BANK NAME | AN | 35 | 1 | 35 | - positions 1-35 = name of bank; not all foreign wires require full bank name |
| 17 | BANK ADDRESS 1 | AN | 35 | 1 | 35 | - positions 1-35 = bank address line 1 |
- Not all foreign wires / countries require full bank address 18 BANK ADDRESS 2 AN 35 1 35 - positions 1-35 = bank address line 2
- Not all foreign wires / countries require full bank address 19 BANK ADDRESS 3 AN 35 1 35 - positions 1-35 = bank address line 3
- Not all foreign wires / countries require full bank address 20 :59 BENEFICIARY: AN 54 1 54 Validated based on the value in the field means (IBAN or account number length) - positions 1-16 = :59 BENEFICIARY:
- positions 17-20 = /DD-
- positions 21-54 = beneficiary account number; can be up to 34 alphanumeric characters 21 BENEFICIARY NAME AN 35 1 35 - positions 1-35 = beneficiary name
- Not all foreign wires / countries require full beneficiary address 22 BENEFICIARY ADDRESS 1 AN 35 1 35 - positions 1-35 = beneficiary address line 1
- Not all foreign wires / countries require full beneficiary address 23 BENEFICIARY ADDRESS 2 AN 35 1 35 - positions 1-35 = beneficiary address line 2
- Not all foreign wires / countries require full beneficiary address 24 BENEFICIARY ADDRESS 3 AN 35 1 35 - positions 1-35 = beneficiary address line 3
- Not all foreign wires / countries require full beneficiary address
| 25 | :70 BENEF INFO: | AN | 15 | 1 | 15 | - positions 1-15 = :70 BENEF INFO: | ||
| 26 | PAYMENT INFORMATION 1 | AN | 35 | 1 | 35 | - positions 1-35 = payment information line 1 | ||
| 27 | PAYMENT INFORMATION 2 | AN | 35 | 1 | 35 | - positions 1-35 = payment information line 2 | ||
| 28 | PAYMENT INFORMATION 3 | AN | 35 | 1 | 35 | - positions 1-35 = payment information line 3 | ||
| 29 | PAYMENT INFORMATION 4 | AN | 35 | 1 | 35 | - positions 1-35 = payment information line 4 | ||
| 30 | :72 RECEIVER INFO: | AN | 18 | 1 | 18 | - positions 1-18 = :72 RECEIVER INFO: | ||
| 31 | BANK DETAILS 1 | AN | 30 | 1 | 30 | - System prepends "/ACC/" | ||
| - System validates total length is 35 characters or less, including "/ACC/" | - positions 1-30 = bank details |
NOTE: Some foreign currencies require additional bank details (i.e. bank contact phone number, in country vendor codes). These requirements should be populated in this field
| 32 | BANK DETAILS 2 | AN | 33 | 1 | 33 | - System prepends "//" | |
| - System validates total length is 35 characters or less, including "//" | - positions 1-33 = bank details |
NOTE: Some foreign currencies require additional bank details (i.e. bank contact phone number, in country vendor codes). These requirements should be populated in this field
| 33 | BANK DETAILS 3 | AN | 33 | 1 | 33 | - System prepends "//" | |
| - System validates total length is 35 characters or less, including "//" | - positions 1-33 = bank details |
NOTE: Some foreign currencies require additional bank details (i.e. bank contact phone number, in country vendor codes). These requirements should be populated in this field
| 34 | BANK DETAILS 4 | AN | 33 | 1 | 33 | - System prepends "//" | |
| - System validates total length is 35 characters or less, including "//" | - positions 1-33 = bank details |
NOTE: Some foreign currencies require additional bank details (i.e. bank contact phone number, in country vendor codes). These requirements should be populated in this field
| *35 | :TAS: | A | 5 | 1 | 5 | positions 1-5 = :TAS: |
| *36 | N | 2 | 6 | 7 | TAS Sub-level Prefix Code | |
| *37 | N | 3 | 8 | 10 | TAS Allocation Transfer Agency Identifier | |
| *38 | N | 3 | 11 | 13 | TAS Agency Identifier | |
| *39 | N | 4 | 14 | 17 | TAS Beginning Period of Availability | |
| *40 | N | 4 | 18 | 21 | TAS Ending Period of Availability | |
| *41 | AN | 1 | 22 | 22 | TAS Availability Code | |
| *42 | N | 4 | 23 | 26 | TAS Main Account Code | |
| *43 | N | 3 | 27 | 29 | TAS Sub-Account Code | |
| *44 | :BETC: | AN | 14 | 1 | 14 | - positions 1-6 = :BETC: |
- positions 7-14 = Business Event Type Code *45 :AMT: N 22 1 22 - positions 1-5 = :AMT:
- positions 6-22 = USD amount; (string 14, including decimal) *46 *ENDMSG* A 8 1 8 - positions 1-8 = *ENDMSG*
- required
- Constitutes end of payment record
| Trailer Record | |||||||
| EXAMPLE: *ENDFILE* 000001 0000000000000000 | |||||||
| # | Field Name | Type | Length | Start Position | End Position | KFC Validation Rules | Notes |
| 47 | *ENDFILE* | A | 9 | 1 | 9 | If missing, reject the file | - required |
- positions 1-9 = *ENDFILE*
| 48 | Space | - | 1 | 10 | 10 | |
| 49 | Record Count | N | 6 | 11 | 16 | - required |
- positions 11-16 = total count of messages in file
- right justified and zero filled, with no punctuation
| 50 | Space | - | 1 | 17 | 17 | ||
| 51 | File Total | AN | 16 | 18 | 33 | See foot notes for information! | - positions 18-33 = Total found in file for all payments, no punctuation |
- right-justified and zero filled, with no punctuation
| 52 | Carriage Return / Line feed | Defining end of the File Trailer record |
| Footnotes |
ITS treatment for Value Date - ITS requires that payment files & certifications be delivered at least two days in advance of value date to allow time for processing. In order to ensure this, ITS derives the Value Date by advancing it a number of days from the current date of the file (indicated on the file header in the current date field) or in the case of an ad hoc payment from the cycle date.
The actual Value Date is determined using a value configured in ITS as "Value Date Advance" which represents the actual numbers of days (Can range from 0 to 5) to advance. This number was determined when the agencies ALC was setup in ITS and was based in part upon the number of days in advance of the value date the agency wanted to deliver the payment data to ITS. The Foot Notes below for Line 3 and 12 define the specifics of this value date advance.
| * Line 3 Current Date - Note! ITS uses this date and the Value Date Advance value configured in the ITS application (associated with the ALC in the header record) to derive what the calculated Value Date of the actual payments will be. |
| *Line 12 :30 VALUE DATE: - NOTE! This value is not used by ITS. Please see foot note for line 3 above for information on how ITS sets the value date. |
| *Lines 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45 can repeat up to 100 per payment to fulfill agency requirements for TAS / BETC |
| **Lines 13 Currency code is required to be USD |
**Line 14: Currency code is required ** An amount is required after :BASE AMT: currency code or :FX AMT: currency code
When :BASE AMT: amount is provided and :FX AMT: amount is not provided, ITS.gov will use :BASE AMT: for the exchange rate calculation of the :FX AMT: amount. using the exchange rate configured in the application for the ALC. The :BASE AMT: values should be used to calculate the file total.
Example: :BASE AMT:USD 550.00
:FX AMT:CAD
- When :BASE AMT: amount is not provided and :FX AMT: amount is provided, ITS.gov will use :FX AMT: amount for exchange rate calculation using the exchange rate configured in the application for the ALC. The :FX AMT: values in the file should be used to calculate the file total.
Example: :BASE AMT:USD
:FX AMT:CHF 86.45
- When :BASE AMT: amount is provided and :FX AMT: amount is provided, ITS.gov will use :FX AMT: amount for exchange rate calculation using the exchange rate configured in the application for the ALC. The :BASE AMT: Amount provided will be bypassed. The :FX AMT: values in the file should be used to calculate the file total.
Example: :BASE AMT:USD 3000.00
:FX AMT:TND 2595.300
Advanced Rate - Foreign Wire Payment v4.0 &P of &N
PMT1026-FS-STInput-Chk
FOREIGN CHECK PAYMENT
| TDO ST Manual Upload File Naming Convention |
| When the file is delivered to ITS manually via the file upload functionality with in ITS.gov by an ITS.gov user the following file naming convention must be followed: ST*MMDDCCYY.001, |
Example: STDA02242017.001 or STDLA102242017.001 -[ Where * is a two/four byte alpha character value associated with specific agency
- [.MMDDCCYY is current business month, day and year.
- [The file extension ‘.001’ can be incremented if multiple files are processed on same day, for example ‘.002’.
| TDO ST Auto Upload File Naming Convention |
| <file type>.<agency ID>[.Eagency extension field][.source system custom field].D<YYYYMMDD>.T<HHMMSSsss> |
Examples: ST.DA.EABC12334.TEST213.D20170224.T221115024 or ST.DLA1.EABC123.TEST213.D20170224.T221115024 or ST.AB.TEST213.D20170224.T221115024 or ST.ABC1.TEST213.D20170224.T221115024 or ST.DA.D20170224.T221115024 or ST.DLA1.D20170224.T221115024 -[ File name length limited to 44 characters -[ <file type> ST is the required required file type -[ <agency ID> is a two/four byte alphanumeric character value associated with specific agency -[.Eagency extension field] is optional - if used must begin with capital E -[.source system custom field] is optional
| File Header Record | |||||||
| EXAMPLE: | |||||||
| STMMDDYY.0NN MMDDYY 01 VENDOR PAYMENTS | |||||||
| *ENDMSG* | |||||||
| # | Field Name | Type | Length | Start Position | End Position | KFC Validation Rules | Notes |
| 1 | File Name | AN | 12 | 1 | 12 | If invalid or missing, reject the file | "XXMMDDYY.0NN " |
X = Alpha characters; 2 characters that represent the file (ITS.gov recommends "ST") M = Month D = Day Y = Year N = start with 1 each day; increment if multiple files are processed on same day
| 2 | Space | - | 1 | 13 | 13 | ||
| *3 | Current Date | AN | 6 | 14 | 19 | If invalid or missing, reject the file | "MMDDYY " |
- Date should match date in file name
- Date the file is generated
- Format: MMDDYY
| 4 | Space | - | 1 | 20 | 20 | |
| 5 | Batch Sequence Number | N | 2 | 21 | 22 | - 01-99 |
- unique for each file creation date
| 6 | Space | - | 1 | 23 | 23 | ||
| 7 | Descriptive File Title | AN | 20 | 24 | 43 | - Type of payments (e.g., VENDOR PAYMENTS) | |
| 8 | *ENDMSG* | AN | 8 | 1 | 8 | If missing, reject the file | - positions 1-8 = *ENDMSG* |
- Concludes header record
| Wire Payment Detail Record | |||||||
| # | Field Name | Type | Length | Start Position | End Position | KFC Validation Rules | Notes |
| 9 | [DFT] | A | 5 | 1 | 5 | If invalid or missing, reject the file | - positions 1-5 = [DFT] |
- Required for check payments. Start of payment record 10 :ALC: N 8 1 13 If invalid or missing, reject the file - positions 1-5 = :ALC:
- positions 6-13 = Agency's ALC
- required 11 :SCHEDULE: AN 24 1 14 Validated against SPS certification - positions 1-10 = :SCHEDULE:
- positions 11-24 = schedule number
- schedule number has no minimum requirement
- schedule number maximum is 14 characters
- required *12 :30 VALUE DATE: AN 21 1 21 - positions 1-15 = :30 VALUE DATE:
- positions 16-21 = YYMMDD
- US holidays should be taken into consideration
- required 13 :PAY TO: AN 35 1 35 - positions 1-8 = :PAY TO:
- positions 9-35 = check beneficiary name; this name will print on check
- required 14 CHECK BENEFICIARY ADDRESS 1 AN 35 1 35 - This address 1 will be used to mail the check
- required 15 CHECK BENEFICIARY ADDRESS 2 AN 35 1 35 - This address 2 will be used to mail the check
- required 16 CHECK BENEFICIARY ADDRESS 3 AN 35 1 35 - required
- This address 3 will be used to mail the check.
- Line three must contain the country 17 :BASE AMT: AN 28 1 28 **If missing, reject the file
See foot notes for usage information! - Debit Currency Amount / required
- positions 1-10 = :BASE AMT:
- positions 11-13 = USD
Or
- positions 11-13 = USD
- position 14-14 = 'space'
- positions 15-28 = amount, including decimal 18 :FX AMT: AN 26 1 26 **If missing, reject the file
See foot notes for usage information! - Foreign currency and amount / required
- positions 1-8 = :FX AMT:
- positions 9-11 = 3 character currency code
OR
- positions 9-11 = 3 character currency code
- position 12-12 = 'space'
- positions 13-26 = amount, including decimal NOTE: amount is 14 characters for 3 digit countries; 13 characters for 2 digit countries
| 19 | :70 BENEF INFO: | A | 15 | 1 | 15 | positions 1-15 = :70 BENEF INFO: |
| 20 | CHECK PAYMENT INFORMATION 1 | AN | 35 | 1 | 35 | This information will print on the check stub |
| 21 | CHECK PAYMENT INFORMATION 2 | AN | 35 | 1 | 35 | This information will print on the check stub |
| 22 | CHECK PAYMENT INFORMATION 3 | AN | 35 | 1 | 35 | This information will print on the check stub |
| 23 | CHECK PAYMENT INFORMATION 4 | AN | 35 | 1 | 35 | This information will print on the check stub |
| *24 | :TAS: | A | 5 | 1 | 5 | positions 1-5 = :TAS: |
| *25 | N | 2 | 6 | 7 | TAS Sub-level Prefix Code | |
| *26 | N | 3 | 8 | 10 | TAS Allocation Transfer Agency Identifier | |
| *27 | N | 3 | 11 | 13 | TAS Agency Identifier | |
| *28 | N | 4 | 14 | 17 | TAS Beginning Period of Availability | |
| *29 | N | 4 | 18 | 21 | TAS Ending Period of Availability | |
| *30 | AN | 1 | 22 | 22 | TAS Availability Code | |
| *31 | N | 4 | 23 | 26 | TAS Main Account Code | |
| *32 | N | 3 | 27 | 29 | TAS Sub-Account Code | |
| *33 | :BETC: | AN | 14 | 1 | 14 | - positions 1-6 = :BETC: |
- positions 7-14 = Business Event Type Code *34 :AMT: N 22 1 22 - positions 1-5 = :AMT:
- positions 6-22 = USD amount (string 14, including decimal) *35 *ENDMSG* A 8 1 8 - positions 1-8 = :ENDMSG:
- required
- signifies end of the DFT transaction
| Trailer Record | |||||||
| EXAMPLE: *ENDFILE* 000001 0000000000000000 | |||||||
| # | Field Name | Type | Length | Start Position | End Position | KFC Validation Rules | Notes |
| 36 | *ENDFILE* | A | 9 | 1 | 9 | If missing, reject the file | - positions 1-9 = *ENDFILE* |
- required
| 37 | Space | - | 2 | 10 | 10 | |
| 38 | Record Count | N | 6 | 11 | 16 | - required |
- positions 11-16 = total count of messages in file
- right justified and zero filled, with no punctuation
| 39 | Space | - | 17 | 1 | 17 | ||
| 40 | File Total | AN | 16 | 18 | 33 | See foot notes for information! | - required |
- positions 18-33 = Total found in file for all payments, no punctuation
- right-justified and zero filled, with no punctuation
| 41 | Carriage Return / Line feed | Defining end of the File Trailer record |
| Footnotes |
ITS treatment for Value Date - ITS requires that payment files & certifications be delivered at least two days in advance of value date to allow time for processing. In order to ensure this, ITS derives the Value Date by advancing it a number of days from the current date of the file (indicated on the file header in the current date field) or in the case of an ad hoc payment from the cycle date.
The actual Value Date is determined using a value configured in ITS as "Value Date Advance" which represents the actual numbers of days (Can range from 0 to 5) to advance. This number was determined when the agencies ALC was setup in ITS and was based in part upon the number of days in advance of the value date the agency wanted to deliver the payment data to ITS. The Foot Notes below for Line 3 and 12 define the specifics of this value date advance.
| * Line 3 Current Date - Note! ITS uses this date and the Value Date Advance value configured in the ITS application (associated with the ALC in the header record) to derive what the calculated Value Date of the actual payments will be. |
| * Line 12 :30 VALUE DATE: - NOTE! This value is not used by ITS. Please see foot note for line 3 above for information on how ITS sets the value date. |
| * Lines 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34 can repeat up to 100 per payment to fulfill agency requirements for TAS / BETC |
**Lines 17 Currency code is required to be USD **Line 18: Currency code is required ** An amount is required after :BASE AMT: currency code or :FX AMT: currency code
When :BASE AMT: amount is provided and :FX AMT: amount is not provided, ITS.gov will use :BASE AMT: for the exchange rate calculation of the :FX AMT: amount. using the exchange rate configured in the application for the ALC. The :BASE AMT: values should be used to calculate the file total.
Example: :BASE AMT:USD 550.00
:FX AMT:CAD
- When :BASE AMT: amount is not provided and :FX AMT: amount is provided, ITS.gov will use :FX AMT: amount for exchange rate calculation using the exchange rate configured in the application for the ALC. The :FX AMT: values in the file should be used to calculate the file total.
Example: :BASE AMT:USD
:FX AMT:CHF 86.45
- When :BASE AMT: amount is provided and :FX AMT: amount is provided, ITS.gov will use :FX AMT: amount for exchange rate calculation using the exchange rate configured in the application for the ALC. The :BASE AMT: Amount provided will be bypassed. The :FX AMT: values in the file should be used to calculate the file total.
Example: :BASE AMT:USD 3000.00
:FX AMT:TND 2595.300
Advanced Rate - Check Payment v5.0 &P of &N
File details come from the government source that posted it. Updated .