ATTACHMENT 6 Insert Mail MRDF Layout.xls
XLS spreadsheet 125 KB Posted
- Attached to
- T2836 - Printing: Production Print Services
- Solicitation number
- 25DPP01109
- Issued by
- New Jersey
About this file
This file is a technical specification document for a mail processing and tracking file layout, primarily involving Pitney Bowes and the State of New Jersey (NJ). The document details a comprehensive Mail Run Data File (MRDF) layout that defines precise field specifications for tracking and processing mail jobs, including header records, input file configurations, output file layouts, and select file formats. The specification covers critical tracking elements such as job identification, creation dates, service level agreements, postage rates, insert feeder modes, recipient information, and mailpiece disposition tracking across different file record types.
The file provides extensive technical guidance for mail processing systems, with specific configurations tailored to the State of New Jersey's requirements. It includes detailed specifications for chargeback accounting, carrier and class identification, postal tracking codes (like IMB, Postnet, and Planet Code), and mechanism for tracking mailpiece status through various stages of processing. The document supports multiple operational modes, accommodates up to 16 insert feeders, and provides robust tracking mechanisms for quality control, including options for auditing, outsourcing, and reprinting damaged mailpieces. The specification is designed to ensure precise tracking, accounting, and processing of mail jobs across different document types and operational scenarios.
View the file
Other files
Show all 20
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
FileBased Header
| Input File Header Record Layout | ||||||||
| Field Name | Field | Start | Length | Type | ADF Source | ADF Sample | Description | |
| JobID | 1 | 1 | 8 | A | 8 digit ADF PRINT job id | |||
| (not Download job id) | e.g. 10345238 | This field must match the barcoded Job ID that is printed on the input documents, so that there is no doubt that the physical material loaded for the job should be run using the Input file that was opened. It is highly recommended that this value is unique for a given mailing cycle. | ||||||
| RunID | 2 | 9 | 15 | A | same as JobId | e.g. 10345238 | Typically this field is populated with the same value as Job ID, however, it can be used as an alias for Job ID. It is highly recommended that this value is unique for a given mailing cycle, and ideally that is unique for a given year. The Run ID is required for InSite and DFWorks Job Tracking. | |
| CreationDate | 3 | 24 | 19 | A | Date MRDF file is created; after print. | e.g. 04/16/2008 | This field specifies the creation date and time of the mailrun. Use the format MM/DD/YYYY HH:MM:SS. (Note that there is one space between the date and time). The Creation Date is required for InSite and DFWorks Job Tracking. Use extrenal MRDF timestamp for the State of NJ. | |
| GroupID | 4 | 43 | 15 | A | Job.ProductionUnit which is set to CA7 userid or will be set for NJKids jobs in hotfolder attributes. | e.g. OOXDILL | This field specifies the group classification, and is normally assigned the same value as Job Type. The Group ID can, however, contain a different value than Job Type if required. The Group ID is required for InSite Job Tracking. | |
| JobType | 5 | 58 | 15 | A | Job.MRDF.JobType (new attribute 5/17) | e.g. Fold | This field specifies the job classification type (e.g., statements, checks, letters, etc.) to which this mailrun belongs. The Job Type is required for InSite and DFWorks Job Tracking. (NJ plans to use a form type.) | |
| ApplicationID | 6 | 73 | 15 | A | Job.MVS.JobName | e.g. JJ0031PD or NJKIDSD | This field specifies the parent Application ID for this mailrun. The Application ID is required for InSite and DFWorks Job Tracking. | |
| CycleID | 7 | 88 | 5 | A | Job.ProductionUnit Cycle; altered to mm_dd format | e.g. ADF_Nd-1 Daily 04/10/2008 becomes 04_10 | This field specifies the billing cycle (i.e., the month and day) to which this mailrun belongs. Use the format MM_DD. The Cycle ID is required for InSite and DFWorks Job Tracking. | |
| ClientID | 8 | 93 | 15 | A | Job.MVS.Account | e.g. 99450000 | This field specifies the internal or external client associated with this mailrun. The Client ID is required for InSite and DFWorks Job Tracking. (NJ Charge Code) | |
| SLADueDate | 9 | 108 | 19 | A | Job.SLA.Plan(Insert) | e.g. 04/17/2008 11:30:00 | This field specifies the Service Level Agreement due date for the mailrun. Use the format MM/DD/YYYY HH:MM:SS. (Note that there is one space between the date and time). The SLA Due Date is required for InSite and DFWorks Job Tracking. This is set to the ADF Job SLA Insert Milestone timestamp for the State of NJ. | |
| SLAWarningOffset | 10 | 127 | 5 | N | 216000 (this can be overidden, from MRDF right?) | 216000 | This field specifies the time in seconds prior to the Service Level Argeement due date by which a warning should be declared if the mailrun has not reached a “closed” state. The SLA Warning Offset is required for InSite and DFWorks Job Tracking. (Static 6 Hour offset Warning for th State of NJ) | |
| ReprintDueDate | 11 | 132 | 19 | A | Fill with ascii blanks x'20' | This field specifies the Reprint Level Agreement due date for damaged mailpieces associated with the mailrun when it is in a “reprint state”. Use the format MM/DD/YYYY HH:MM:SS. (Note that there is one space between the date and time). This field is intended for future use. No Pitney Bowes software currently uses the information in this field. | ||
| ReprintWarningOffset | 12 | 151 | 5 | N | Fill with ascii zeros | This field specifies the time in seconds prior to Reprint Level Agreement due date by which a warning should be declared if the mailrun has not reached a “closed” state. This field is intended for future use. No Pitney Bowes software currently uses the information in this field. | ||
| DataSetType | 13 | 156 | 1 | N | Always 2, no function to currently support others from ADF | 2 | This field identifies the type of mailrun. Possible values for this field are: |
1 = Non File-Based Application (i.e, no piece records, header record only), 2 = File-Based Application (i.e., contains piece records) 3 = The Data Set Type is required for InSite and DFWorks Job Tracking.
| PlannedMailpieceCount | 14 | 157 | 6 | N | Job.TotalDocs from the Print Job, limited to 999999, right? Thus the segment size for a Print job must be set to something that caps this. | e.g. 100043 | This field specifies the number of mailpieces in the mailrun. The Planned Mailpiece Count is required for InSite and DFWorks Job Tracking when you are running a non file-based application. |
| PlannedSheetCount | 15 | 163 | 10 | N | Job.TotalSheets from the Print job | e.g. 2456985 | This field specifies the number of physical sheets in the mailrun. The Planned Mailpiece Count is required for InSite and DFWorks Job Tracking when you are running a non file-based application. |
| ChargebackAccount | 16 | 173 | 16 | A | Job.MVS.Account (could reduce size) | e.g. 99450000 | This field is used for chargeback accounting. The value must match the preassigned values in your OMS (Operations Management System) or PAM (Postage Accounting Management) software, and is the account to which the mailrun should be charged. |
| ChargebackSubAccount | 17 | 189 | 24 | A | Fill blanks | This field is used for chargeback accounting. The value must match the preassigned values in your OMS or PAM software, and is the subaccount to which the mailrun should be charged. | |
| ChargebackCarrier | 18 | 213 | 3 | N | Map Job.Dispatch to the correct code: USPS= 001 | e.g. 001 | This field is used for chargeback accounting. The value must match the preassigned values in your OMS or PAM software, and is the numerical value that identifies the carrier (e.g., USPS, UPS, Fedex, etc) for this mailrun. |
| ChargebackClass | 19 | 216 | 3 | N | Use code based on Job.Dispatch type, eg. 001 | e.g. 001 | This field is used for chargeback accounting. The value must match the preassigned values in your OMS or PAM software, and is the numerical value that identifies the postage or shipping class (e.g., 1st class, 2nd class, 3rd class mail) for this mailrun. |
| InserterMode | 20 | 219 | 8 | A | Set to the ONLY mode for NJ setup: 'FILEBASE' | FILEBASE | This field is only used when you have the File-Based Job Setup feature. The value specifies the name of the pre-established inserter operating mode associated with this mailrun. |
| PostageRate_Setting_01 | 21 | 227 | 5 | A | From Postage configuration | This field is only used when you have the File-Based Job Setup feature and Meter Links at each meter. This field specifies the amount of postage to be applied to each mailpiece at the given meter. This field must be a decimal number with one digit to the left of the decimal point, and three digits to the right (e.g., 0.370 is used to indicate 37 cents). There are four Postage Meter Setting fields available to accommodate as many as four postage meters on the inserter. | |
| PostageRate_Setting_02 | 22 | 232 | 5 | A | From Postage configuration | See PostageRate_Setting_01Setting for field definition | |
| PostageRate_Setting_03 | 23 | 237 | 5 | A | From Postage configuration | See PostageRate_Setting_01Setting for field definition | |
| PostageRate_Setting_04 | 24 | 242 | 5 | A | From Postage configuration | See PostageRate_Setting_01Setting for field definition | |
| PostageRate_Setting_05 | 21 | 247 | 5 | A | From Postage configuration | See PostageRate_Setting_01Setting for field definition | |
| PostageRate_Setting_06 | 22 | 252 | 5 | A | From Postage configuration | See PostageRate_Setting_01Setting for field definition | |
| PostageRate_Setting_07 | 23 | 257 | 5 | A | From Postage configuration | See PostageRate_Setting_01Setting for field definition | |
| PostageRate_Setting_08 | 24 | 262 | 5 | A | From Postage configuration | See PostageRate_Setting_01Setting for field definition | |
| PostageRate_Setting_09 | 25 | 267 | 5 | A | From Postage configuration | See PostageRate_Setting_01Setting for field definition | |
| PostageRate_Setting_10 | 26 | 272 | 5 | A | From Postage configuration | See PostageRate_Setting_01Setting for field definition | |
| PostageRate_Setting_11 | 27 | 277 | 5 | A | From Postage configuration | See PostageRate_Setting_01Setting for field definition | |
| PostageRate_Setting_12 | 28 | 282 | 5 | A | From Postage configuration | See PostageRate_Setting_01Setting for field definition | |
| InsertFeeder01Mode | 29 | 287 | 1 | N | Always set to Data Select = 2 if there are inserts for this feeder in the job. Or 1=Never | 2 or 1 | This field is only used when you have the File-Based Job Setup feature. This field specifies the operational mode for this insert feeder. Possible values for this field are: 1 = Never, 2 = Data Select, 3 = Priority Select, 4 = Priority Fill, 6 = Always. There are 16 of these fields available to accommodate as many as 16 insert feeders. |
| InsertFeeder02Mode | 30 | 288 | 1 | N | Always set to Data Select = 2 if there are inserts for this feeder in the job. Or 1=Never | 2 or 1 | See Insert Feeder01Mode for field definition |
| InsertFeeder03Mode | 31 | 289 | 1 | N | Always set to Data Select = 2 if there are inserts for this feeder in the job. Or 1=Never | 2 or 1 | See Insert Feeder01Mode for field definition |
| InsertFeeder04Mode | 32 | 290 | 1 | N | Always set to Data Select = 2 if there are inserts for this feeder in the job. Or 1=Never | 2 or 1 | See Insert Feeder01Mode for field definition |
| InsertFeeder05Mode | 33 | 291 | 1 | N | Always set to Data Select = 2 if there are inserts for this feeder in the job. Or 1=Never | 2 or 1 | See Insert Feeder01Mode for field definition |
| InsertFeeder06Mode | 34 | 292 | 1 | N | Always set to Data Select = 2 if there are inserts for this feeder in the job. Or 1=Never | 2 or 1 | See Insert Feeder01Mode for field definition |
| InsertFeeder07Mode | 35 | 293 | 1 | N | Always set to Data Select = 2 if there are inserts for this feeder in the job. Or 1=Never | 2 or 1 | See Insert Feeder01Mode for field definition |
| InsertFeeder08Mode | 36 | 294 | 1 | N | Always set to Data Select = 2 if there are inserts for this feeder in the job. Or 1=Never | 2 or 1 | See Insert Feeder01Mode for field definition |
| InsertFeeder09Mode | 37 | 295 | 1 | N | Always set to Data Select = 2 if there are inserts for this feeder in the job. Or 1=Never | 2 or 1 | See Insert Feeder01Mode for field definition |
| EnvelopeFeederDocID | 38 | 296 | 8 | A | Outer Envelope (OSE) from the Inserter setup named by Job.Inserter. PlanName | e.g. ? | This field is only used when you have the File-Based Job Setup feature. This value is a unique document ID assigned to the envelope feeder, and is the reference needed to access envelope attributes (e.g., weight, priority, loading instructions) in the Document Database that are used to automate envelope feeder setup. |
| InsertFeeder01DocID | 39 | 304 | 8 | A | Fill Blanks OR from Inserter Plan Bin 1 if TLE requested Bin 1 | e.g. ? | This field is only used when you have the File-Based Job Setup feature. This value is a unique document ID assigned to an insert feeder, and is the reference needed to access insert attributes (e.g., weight, priority, loading instructions) in the Document Database that are used to automate insert feeder setup. There are 16 of these fields available to accommodate as many as 16 insert feeders on the inserter. |
| InsertFeeder02DocID | 40 | 312 | 8 | A | Fill Blanks OR from Inserter Plan Bin 2 if TLE requested Bin 2 | e.g. ? | See InsertFeeder01DocID for field definition |
| InsertFeeder03DocID | 41 | 320 | 8 | A | Fill Blanks OR from Inserter Plan Bin 3 if TLE requested Bin 3 | e.g. ? | See InsertFeeder01DocID for field definition |
| InsertFeeder04DocID | 42 | 328 | 8 | A | Fill Blanks OR from Inserter Plan Bin 4 if TLE requested Bin 4 | e.g. ? | See InsertFeeder01DocID for field definition |
| InsertFeeder05DocID | 43 | 336 | 8 | A | Fill Blanks OR from Inserter Plan Bin 5 if TLE requested Bin 5 | e.g. ? | See InsertFeeder01DocID for field definition |
| InsertFeeder06DocID | 44 | 344 | 8 | A | Fill Blanks OR from Inserter Plan Bin 6 if TLE requested Bin 6 | e.g. ? | See InsertFeeder01DocID for field definition |
| InsertFeeder07DocID | 45 | 352 | 8 | A | Fill Blanks OR from Inserter Plan Bin 7 if TLE requested Bin 7 | e.g. ? | See InsertFeeder01DocID for field definition |
| InsertFeeder08DocID | 46 | 360 | 8 | A | Fill Blanks OR from Inserter Plan Bin 8 if TLE requested Bin 8 | e.g. ? | See InsertFeeder01DocID for field definition |
| InsertFeeder09DocID | 47 | 368 | 8 | A | Fill Blanks OR from Inserter Plan Bin 9 if TLE requested Bin 9 | e.g. ? | See InsertFeeder01DocID for field definition |
| IMB Mailer ID | 48 | 376 | 9 | A | Fill Blanks | USPS IMB Mialer ID. If six digit mailer ID, then use leading zero's | |
| UserDefinedField1 | 49 | 385 | 30 | A | Fill Blanks | This field is a user-defined field that does not affect the control of the inserter, but is intended for custom functionality. The data in this field is significant to your own applications. There are two of these fields available to accommodate as many as two user-defined fields. | |
| UserDefinedField2 | 50 | 415 | 30 | A | Fill Blanks | See UserDefinedField1 for field definition | |
| UserDefinedField3 | 50 | 445 | 30 | A | Fill Blanks | See UserDefinedField1 for field definition | |
| Filler | 51 | 475 | 875 | A | Fill Blanks | This field is for the purpose of making the header record of the Input file the same length as the piece level records of the Input file. The Input file is easier to work with when all records within the Input file have the same record length. | |
| EOR “X” | 52 | 1350 | 1 | A | X | X | End of Record Indicator. Insures FTP Client does not truncate trailing spaces. |
| Total | 1350 | ||||||
| A =ASCII_Alpha = Alphanumeric and special characters allowed. Field is left-justified and padded with right-most trailing spaces. | |||||||
| N=ASCII_Number = Numeric characters only. No alphabetic or special characters allowed. Field is right-justified and padded with left-most leading zeros. | |||||||
| Important Note: Unused alphanumeric fields must be filled with spaces. Unused numeric fields must be filled with zeros. |
FileBased Input
| Input File Record Layout, Records #2 & so on. | ||||||||
| Field Name | Field | Start | Length | Type | ADF Source | ADF Sample | Description | |
| JobID | 1 | 1 | 8 | A | 6 digit ADF PRINT job id with zero fill | |||
| (not Download job id) | e.g. 00345238 | The value in this field must match the barcoded Job ID that is printed on the input documents, so that there is no doubt that the physical material loaded for the job should be run using the Input file that was opened. It is highly recommended that this value is unique for a given mailing cycle. | ||||||
| PieceID | 2 | 9 | 15 | A/N | If not supplied by the originating application, Sequential from 1 to n | e.g. 000000000000001 | The value in this field must match the barcoded Piece ID that is printed on the input documents. It is the link between the scancode and the mailpiece record within the Input file that contains the assembly instructions for that mailpiece. This value must be unique for each mailpiece, and must increment by 1 for each record within the file. | |
| TotalSheetsInputFdr1 | 3 | 24 | 1 | N | Number of ADF sheets for this mailpiece. | e.g. 9 | This field identifies the total number of physical sheets of paper that should be fed from the input feeder for the mailpiece. If you have multiple input feeders, you will need a Total Sheets field for each input feeder. There are two of these fields available to accommodate as many as two input feeders on the inserter (e.g., a RAT1 with east and north feeder inputs). | |
| TotalSheetsInputFdr2 | 4 | 25 | 3 | N | No Fdr 2 | 0 | See TotalSheetsInputFdr2 for field definition | |
| SubsetSheetNumInptFdr1 | 5 | 28 | 2 | N | 1 RULE ONLY for HalfFold: If over 8 sheets, divide by 2, adding remainder. | e.g. 9-10 pages, this number is 5 | ||
| e.g. 11-12 pages, this number is 6 ... | This field is used for application control of subsetting. It should be populated with the physical sheet number within the mailpiece at which the subset should occur. There are two of these fields available to accommodate as many as two input feeders on the inserter (e.g., a RAT1 with east and north feeder inputs). | |||||||
| SubsetSheetNumInptFdr2 | 6 | 30 | 2 | N | No Fdr 2 | 0 | See SubsetSheetNumInptFdr2 for field definition | |
| StitchSheetNumInptFdr1 | 7 | 32 | 2 | N | 0 | 0 | This field is used for application control of stitching. It should be populated with the physical sheet number within the mailpiece at which the stitch should occur. There are two of these fields available to accommodate as many as two input feeders on the inserter (e.g., a RAT1 with east and north feeder inputs). | |
| StitchSheetNumInptFdr2 | 8 | 34 | 2 | N | 0 | 0 | See StitchSheetNumInptFdr2 for field definition | |
| AccountIdendifier | 9 | 36 | 20 | A | Doc Index ADFClientMPID from TLE or Blanks | e.g. 123456789 | This field should be populated with an account identifier that is also found in human readable format on the physical mailpiece. This identifier is shown within Direct Connect when mailpiece specific information is displayed, and it helps the operator to relate a physical mailpiece to this information within the software. | |
| InputWeight | 10 | 56 | 5 | A | PB will calculate, use 0.0000 | 0 | This field must contain a value. Either enter 0.000 (when all input document pages weigh the same), or enter the finished accumulated weight of the input documents (when different weighted paper is used within the input feeder). This field must be a decimal number with one digit to the left of the decimal point, and three digits to the right (e.g., 1.020). IMPORTANT NOTE: When different weighted input documents are not used, the amount of postage applied is based on the weight that that is specified in the input feeder setup screen. Each time a page is fed, the weight for an individual sheet is added to the total. If there is a value greater than zero in this field, it too will be added to the total weight, and therefore the meter will add postage based on a weight that is heavier than the mailpiece actually is.IMPORTANT NOTE: When different weighted input documents are used, enter the total weight for the input pages in this field, and specify 0.000 for the weight within the input feeder setup screen so that additional weight is not added to the total accumulated weight. | |
| InsertFeeder01 | 11 | 61 | 1 | N | 0 or 1 | 0 or 1 | This field specifies whether an insert feeder should feed an insert or not feed an insert. Possible values for this field are: 0 = Don’t feed, 1 = Feed. | |
| InsertFeeder02 | 12 | 62 | 1 | N | 0 or 1 | 0 or 1 | See InsertFeeder01 for field definition | |
| InsertFeeder03 | 13 | 63 | 1 | N | 0 or 1 | 0 or 1 | See InsertFeeder01 for field definition | |
| InsertFeeder04 | 14 | 64 | 1 | N | 0 or 1 | 0 or 1 | See InsertFeeder01 for field definition | |
| InsertFeeder05 | 15 | 65 | 1 | N | 0 or 1 | 0 or 1 | See InsertFeeder01 for field definition | |
| InsertFeeder06 | 16 | 66 | 1 | N | 0 or 1 | 0 or 1 | See InsertFeeder01 for field definition | |
| InsertFeeder07 | 17 | 67 | 1 | N | 0 or 1 | 0 or 1 | See InsertFeeder01 for field definition | |
| InsertFeeder08 | 18 | 68 | 1 | N | 0 or 1 | 0 or 1 | See InsertFeeder01 for field definition | |
| InsertFeeder09 | 19 | 69 | 1 | N | 0 or 1 | 0 or 1 | See InsertFeeder01 for field definition | |
| SelectiveAccessory1 | 20 | 70 | 1 | N | 0 | 0 | This field specifies whether the selective accessory (usually an edge marker) should be activated for the mailpiece. There are two ways to setup the edge marker for activation. Either a change in value can activate the edge marker (i.e., possible values are 1 to 9, wrapping back to 1), or a value of 1 can activate the edge marker (i.e., 1=Activate, 0=Don’t activate). The recommended method is to activate it when there is a change in value. This is because if you use only values 0 and 1, and a mailpiece having a value of 1 is missing from the mailstream, then two zipcode groups will be combined. Using the change in value to trigger the accessory assures that even if a mailpiece that should activate the edge marker is missing, the following mailpiece will activate the marker instead. | |
| SelectiveAccessory2 | 21 | 71 | 1 | N | 0 | 0 | See SelectiveAccessory1 for Field Definition | |
| AccountPull | 22 | 72 | 1 | N | 1 if Doc Index ADFAcctPull from TLE is Yes or 0 | 0 or 1 | This field specifies whether a mailpiece should or should not be pulled from the inserter, and is used to tag particular mailpieces for outsorting. Possible values for this field are: 0 = No Pull, 1 = Pull (i.e., no meter and outsort to VBIN). Important Note: Mailpieces that are pulled may, for example, be foreign mail that needs to be outsorted so that proper postage can be placed on it, or you may need to pull a mailpiece for a high profile account that requires special handling. | |
| QualityAudit | 23 | 73 | 1 | N | 1 if Doc Index ADFQualAudit from TLE is Yes or 0 | 0 or 1 | This field specifies whether a mailpiece should or should not be pulled from the inserter for quality control purposes. Mailpieces outsorted for a quality audit are checked to see whether the mailpiece was assembled correctly. Possible values for this field are: 0 = No Audit, 1 = Audit (i.e., no seal and outsort to VBIN). | |
| AlertAndClear | 24 | 74 | 1 | N | Not used: 0 | 0 | This field specifies when to clear the inserter deck of all mailpieces. This could be used as a signal to change the inserts in the enclosure feeders. Possible values for this field are: 0 = Don’t clear, 1 = Clear. | |
| RecipientName | 25 | 75 | 50 | A | Doc Index ADFRecptName from TLE (or blanks if none) | e.g. Brent Schutts | This field specifies the name of the receiver of this mailpiece, and is necessary when you are using a printer in the output section for printing the recipient address on a closed-faced envelope. It can also be used to assist in mailpiece identification. | |
| RecipientAddress1 | 26 | 125 | 50 | A | Doc Index ADFRcptAddr1 (or Blanks if none) | e.g. 200 Riverview St | This field specifies the address of the receiver of this mailpiece, and is necessary when you are using a printer in the output section for printing the recipient address on a closed-faced envelope. Up to five recipient address fields allow for an address of up to five lines including name, address, city, state, zip, and any additional information needed. | |
| RecipientAddress2 | 27 | 175 | 50 | A | Doc Index ADFRcptAddr2 (or Blanks if none) | e.g. Trenton, NJ 50306-0200 | Recipient Address2 | |
| RecipientAddress3 | 28 | 225 | 50 | A | Doc Index ADFRcptAddr3 (or Blanks if none) | RecipientAddress3 | ||
| RecipientAddress4 | 29 | 275 | 50 | A | Doc Index ADFRcptAddr4 (or Blanks if none) | RecipientAddress4 | ||
| RecipientAddress5 | 30 | 325 | 50 | A | Doc Index ADFRcptAddr5 (or Blanks if none) | RecipientAddress5 | ||
| Zip5 | 31 | 375 | 5 | N | Not used from ADF: 0 | 0 | This field specifies the standard 5-digit zipcode for the recipient of this mailpiece. These three zip code fields are used to print a POSTNET barcode on an envelope, as well as controlling edge marking and tray breaks. | |
| Zip4 | 32 | 380 | 4 | N | Not used from ADF: 0 | 0 | This field specifies an additional four digits if you are using a 9 or 11-digit zipcode for the recipient of this mailpiece. These three zip code fields are used to print a POSTNET barcode on an envelope, as well as controlling edge marking and tray breaks. | |
| Zip2 | 33 | 384 | 2 | N | Not used from ADF: 0 | 0 | This field specifies an additional two digits if you are using an 11-digit zipcode for the recipient of this mailpiece. These three zip code fields are used to print a POSTNET barcode on an envelope, as well as to control edge marking and tray breaks. | |
| ZipCheckDigit | 34 | 386 | 1 | A | Not used from ADF: Fill Blanks | This field specifies the check digit that pertains to the 11-digit PostNet barcode. (The PostNet barcode is equivalent of the Zip5 + Zip4 + Zip2). | ||
| PlanetCode | 35 | 387 | 14 | A | Not used from ADF: Fill Blanks | This field contains the 14-digit Planet Code. | ||
| PlanetCodeCheckDigit | 36 | 401 | 1 | A | Not used from ADF: Fill Blanks | This field specifies the check digit that pertains to the 11-digit Planet Code. | ||
| BusinessReturnAddress1 | 37 | 402 | 50 | A | Doc Index ADFBusRtnAddr1 (or blanks) | e.g. Trenton County | This field specifies the address of the sender of this mailpiece, and is necessary when you are using a printer in the output section for printing the return address on a closed-faced envelope. Up to five return address fields allow for an address of up to five lines including name, address, city, state, zip, and any additional information needed. | |
| BusinessReturnAddress2 | 38 | 452 | 50 | A | Doc Index ADFBusRtnAddr2 (or blanks) | e.g. 405 River Road | BusinessReturnAddress2 | |
| BusinessReturnAddress3 | 39 | 502 | 50 | A | Doc Index ADFBusRtnAddr3 (or blanks) | e.g. Trenton, NJ 800934 | BusinessReturnAddress3 | |
| BusinessReturnAddress4 | 40 | 552 | 50 | A | Doc Index ADFBusRtnAddr4 (or blanks) | BusinessReturnAddress4 | ||
| BusinessReturnAddress5 | 41 | 602 | 50 | A | Doc Index ADFBusRtnAddr5 (or blanks) | BusinessReturnAddress5 | ||
| BusinessReturnAddress6 | 41 | 652 | 50 | A | "UNITED STATES" if Foreign mail piece | BusinessReturnAddress6 (Country) | ||
| LogoBitmapSelect1 | 42 | 702 | 8 | A | Not used from ADF: Fill Blanks | This field specifies a filename of the logo to be printed on the outside of the mailing envelope. Enter the logo bitmap file name in this field. There are two of these fields available to accommodate as many as 2 logo bitmaps. | ||
| LogoBitmapSelect2 | 43 | 710 | 8 | A | Not used from ADF: Fill Blanks | This field specifies a filename of the logo to be printed on the outside of the mailing envelope. Enter the logo bitmap file name in this field. There are two of these fields available to accommodate as many as 2 logo bitmaps. | ||
| MarketingTextMessage_1 | 44 | 718 | 40 | A | Doc Index ADFENVMsg1 (or blanks) | This field specifies a marketing message to be printed on the outside of the mailing envelope. | ||
| MarketingTextMessage_2 | 45 | 758 | 40 | A | Doc Index ADFENVMsg2 (or blanks) | This field specifies a marketing message to be printed on the outside of the mailing envelope. | ||
| HManifestSeqNumber | 46 | 798 | 25 | A | Not used from ADF: Fill Blanks+F12 | The Host Manifest Sequence Number is required for host-based manifesting (i.e., this does not apply to machine-based manifesting). The value in this field contains the mailpiece sequence number that appears in the keyline on the manifested mailpiece. | ||
| HManifestFinishedWeight | 47 | 823 | 7 | A | Not used from ADF: Fill Blanks | The Host Manifest Finished Weight is required for host-based manifesting (i.e., this does not apply to machine-based manifesting). The value in this field contains the finished mailpiece weight that appears in the keyline on the manifested mailpiece. This field must be a decimal number with three digits to the left of the decimal point, and three digits to the right (e.g., 001.320). | ||
| HManifestRateBreak | 48 | 830 | 2 | N | Not used from ADF: Fill Blanks | The Host Manifest Rate Break is required for host-based manifesting (i.e., this does not apply to machine-based manifesting). The value in this field contains the numerical rate break that appears in the keyline on the manifested mailpiece. | ||
| HManifestPostage | 49 | 832 | 6 | A | Not used from ADF: Fill Blanks | The Host Manifest Postage is required for host-based manifesting (i.e., this does not apply to machine-based manifesting). The value in this field contains the postage that appears in the keyline on the manifested mailpiece. This field must be a decimal number with two digits to the left of the decimal point, and three digits to the right (e.g., 00.370). | ||
| HManifestUserDefined | 50 | 838 | 25 | A | Not used from ADF: Fill Blanks | The Host Manifest User Defined field is required for host-based manifesting (i.e., this does not apply to machine-based manifesting). The value in this field contains a user-defined value, if any, that appears in the keyline on the manifested mailpiece. | ||
| PresortID | 51 | 863 | 20 | A | Not used from ADF: Fill Blanks | The Presort ID is required for both host-based and machine-based manifesting. The value in this field identifies a specific batch of mailpieces to which this mailpiece belongs. The mailpieces in this batch were processed together for manifesting purposes by presort software, such as Mailer’s Choice. A value must be entered in this field for all mailpiece records that are intended to be manifested. If the field is blank, DFWorks will not allow the piece to be manifested, and all of the remaining manifesting fields will be ignored. Important Notes: 1) The Presort ID must be unique from all other Presort IDs that came before (i.e., at least for the last 12 months and typically more). 2) There must never be more than one Presort ID within a single Input file. 3) A single Presort ID is allowed to appear in more than one Input file. 4) Mailpieces within a Presort ID must appear in the Input file in sorted order, which must also be the same order that the printed material is presented to the inserter. 5) If single-piece rate mailpieces are included in the same Presort ID as presorted rate mailpieces, the single-piece rate mailpieces must be listed last within the Presort ID (i.e., they will be the last mailpieces in the Input file that are processed). | ||
| ProcessingCategory | 52 | 883 | 2 | A | Not used from ADF: Fill Blanks | The Processing Category is required for both host-based and machine-based manifesting. The value in this field identifies the type of manifest being generated for this particular mailpiece. Possible values are: AL = Automation Letters, AF = Automation Flats, ML = Machinable Letters, NL = Non-machinable Letters, PF = Presorted Flats, SL = Single-piece Rate Letters, SF = Single-piece Rate Flats | ||
| RateCategory | 53 | 885 | 2 | A | Not used from ADF: Fill Blanks | The Rate Category is required for both host-based and machine-based manifesting. The value in this field specifies the 2-character rate category as defined in the USPS Domestic Mail Manual (DMM) specifications. It is used to compute the postage for the mailpiece. Possible values are: AC, AV, AT, AB, MB, FP and SP (see the DMM for the meaning of these codes). | ||
| TrayNumber | 54 | 887 | 4 | N | Not used from ADF: 0 | 0 | The Tray Number is required for both host-based and machine-based manifesting. This field is a 4-digit number and specifies the tray number into which the mailpiece will be placed. When a mailpiece arrives at the IST (Intelligent Stacker Trayer) and has a tray number different from the previous mailpiece, a tray break will occur. All tray numbers within a particular Presort ID must be unique, consecutive and increasing. When this field is being filled with valid tray numbers, “0000” should not be used. | |
| TraySize | 55 | 891 | 1 | A | Not used from ADF: Fill Blanks | The Tray Size is required for both host-based and machine-based manifesting. This field specifies the type of tray into which the mailpiece will be placed. Possible values are: 0 = Flats tray, 1 = One-foot tray, 2 = Two-foot tray | ||
| TraySortationLevel | 56 | 892 | 4 | A | Not used from ADF: Fill Blanks | The Tray Sortation Level is required for both host-based and machine-based manifesting. The value in this field specifies the level of sortation being placed in the tray. Possible values are listed below. Reference the “Tray Lvl” field in the USPS Domestic Mail Manual (DMM) PO12.2.4 for further information about this field. CRD = Carrier Route Tray, CR3 = 3-Digit Carrier Route Tray, CR5 = 5-Digit Carrier Route Tray, 5DG = 5-Digit Tray, 5DGS = 5-Digit Scheme Tray, 3DG = 3-Digit Tray, 3DGS = 3-Digit Scheme Tray, ADC = ADC Tray, AADC = AADC Tray, MADC = Mixed ADC Tray, MAAD = Mixed AADC Tray, SP = Single Piece | ||
| TrayDestination | 57 | 896 | 11 | A | Not used from ADF: Fill Blanks | The Tray Destination is required for both host-based manifesting and machine-based manifesting. The value in this field contains the zip code destination of the tray into which the mailpiece will be placed. Enter the five-digit zip code or the first three digits of the zip code followed by two ASCII spaces. Enter ASCII spaces when single-piece rate manifesting. Reference the “Tray Zip” field in the USPS Domestic Mail Manual (DMM) for further information about this field. | ||
| GroupDestination | 58 | 907 | 10 | A | Not used from ADF: Fill Blanks | The Group Destination is required for both host-based and machine-based manifesting. When the Tray Sortation field equals CRD, CR5, CR3, 5DGS, 3DGS, AADC, MAAD, ADC or MADC, enter the group destination in this field. Reference the “Group Dest” or “Pkg Dest” column in the USPS Domestic Mail Manual (DMM) PO12.2.2.c.3 for further information about this field. When the Tray Sortation field equals 5DG, 3DG or SP, fill this field with ASCII spaces. Since it is required that mailpieces within a Presort ID must appear in the Input file in sorted order, then the Group Destination will also be in the correct sorted order in the Input file. | ||
| ReprintIndex | 59 | 917 | 20 | A | Not used from ADF: Fill Blanks | This field is a pass-through field that does not affect the control of the inserter, but will be passed on to the output and select files, and in turn back to your applications. The value in this field provides an indexed reference for easily locating records in the original print image for damaged mailpieces that are tagged for reprinting. | ||
| IMB | 60 | 937 | 31 | A | Not used from ADF: Fill Blanks | USPS IMB | ||
| UserDefinedField1 | 61 | 968 | 20 | A | Doc Index ADFUserDefField1 from TLE | This field is a user-defined pass-through field that does not affect the control of the inserter, but will be passed on to the output and select files, and in turn back to your applications. The data in this field is significant to your own applications. There are three of these fields available to accommodate as many as three user-defined fields. Examples of user-defined fields are Social Security number, check number and phone number. Also can be Document Identifiers for each document within the mail piece. | ||
| UserDefinedField2 | 62 | 988 | 20 | A | Doc Index ADFUserDefField2 from TLE | This field is a user-defined pass-through field that does not affect the control of the inserter, but will be passed on to the output and select files, and in turn back to your applications. The data in this field is significant to your own applications. There are three of these fields available to accommodate as many as three user-defined fields. Examples of user-defined fields are Social Security number, check number and phone number. Also can be Document Identifiers for each document within the mail piece. | ||
| UserDefinedField3 | 63 | 1008 | 200 | A | Doc Index ADFUserDefField3 from TLE | This field is a user-defined pass-through field that does not affect the control of the inserter, but will be passed on to the output and select files, and in turn back to your applications. The data in this field is significant to your own applications. There are three of these fields available to accommodate as many as three user-defined fields. Examples of user-defined fields are Social Security number, check number and phone number. Also can be Document Identifiers for each document within the mail piece. | ||
| Extra - Future Use | 64 | 1208 | 142 | A | ||||
| EOR “X” | 65 | 1350 | 1 | A | End of Record Indicator. Insures FTP Client does not truncate trailing spaces. | |||
| Total | 1350 |
FileBased Output
| Output File Record Layout | |||||
| Field Name | Field | Start | Length | Type | Description |
| Input File Header | 1 | 1 | 1350 | A | This is a Mirror of the Input Header Record for the job |
| Output File Record Layout | |||||
| Field Name | Field | Start | Length | Type | Description |
| JobID | 1 | 1 | 8 | A | This field contains the same value as the JobID field in Input file. |
| PieceID | 2 | 9 | 15 | A | This field contains the same value as the PieceID field in Input file. |
| RecipientName | 3 | 24 | 50 | A | This field specifies the name of the receiver of this mailpiece to assist in mailpiece identification. |
| AccountIndetifier | 4 | 74 | 20 | A | This field contains the same value as the Account Identifier field in Input file. |
| ChargebackAccount | 5 | 94 | 16 | A | This field is used for chargeback accounting. The value must match the preassigned values in your DFWorks Postage Accounting Module software, and is the account to which the mailrun should be charged. |
| ChargebackSubAccount | 6 | 110 | 24 | A | This field is used for chargeback accounting. The value must match the preassigned values in your DFWorks Postage Accounting Module software, and is the subaccount to which the mailrun should be charged. |
| ChargebackCarrier | 7 | 134 | 3 | N | This field is used for chargeback accounting. The value must match the preassigned values in your DFWorks Postage Accounting Module software, and is the numerical value that identifies the carrier (e.g., USPS, UPS, Fedex, etc) for this mailrun. |
| ChargebackClass | 8 | 137 | 3 | N | This field is used for chargeback accounting. The value must match the preassigned values in your DFWorks Postage Accounting Module software, and is the numerical value that identifies the postage or shipping class (e.g., 1st class, 2nd class, 3rd class mail) for this mailrun. |
| Postnet | 9 | 140 | 12 | A | This field contains the Postnet Code. |
| PlanetCode | 10 | 152 | 12 | A | This field contains the Planet Code. |
| IMB | 11 | 164 | 31 | A | USPS IMB |
| ComputedWeight | 12 | 195 | 5 | A | The value in this field specifies the actual computed weight of the finished mailpiece in ounces. This information is collected by Direct Connect during the inserting process. This field must be a decimal number with one digit to the left of the decimal point, and three digits to the right (e.g., 1.320). |
| ActualWeight | 13 | 200 | 5 | A | When a Weigh on the Fly scale is part of the inserter, a value will be present in this field. The value in this field specifies the actual measured weight of the finished mailpiece in ounces. This information is collected by Direct Connect during the inserting process. This field must be a decimal number with one digit to the left of the decimal point, and three digits to the right (e.g., 1.320). |
| ActualPostage | 14 | 205 | 5 | A | When the inserter has meter links on each meter, a value will be present in this field. The value in this field specifies the actual postage applied to the finished mailpiece. This information is collected by Direct Connect during the inserting process. This field must be a decimal number with one digit to the left of the decimal point, and three digits to the right (e.g., 0.370). |
| ReprintIndex | 15 | 210 | 20 | A | This field contains the same value as the Reprint Index field in Input file. |
| TotalSheetsInptFdr1 | 16 | 230 | 2 | N | This is a pass-through field from the Input file. This field specifies the total number of physical sheets of paper that were supposed to be fed from the input feeder for the mailpiece. |
| TotalSheetsInptFdr2 | 17 | 232 | 2 | N | This is a pass-through field from the Input file. This field specifies the total number of physical sheets of paper that were supposed to be fed from the input feeder for the mailpiece. |
| InsertFeeder01 | 18 | 234 | 1 | N | This is a pass-through field from the Input file. This field specifies whether or not the insert feeder was supposed to feed an insert for the mailpiece. Possible values for this field are: 0 = Don’t feed, 1 = Feed. |
| InsertFeeder02 | 19 | 235 | 1 | N | See InsertFeeder01 above for Field Definition |
| InsertFeeder03 | 20 | 236 | 1 | N | See InsertFeeder01 above for Field Definition |
| InsertFeeder04 | 21 | 237 | 1 | N | See InsertFeeder01 above for Field Definition |
| InsertFeeder05 | 22 | 238 | 1 | N | See InsertFeeder01 above for Field Definition |
| InsertFeeder06 | 23 | 239 | 1 | N | See InsertFeeder01 above for Field Definition |
| InsertFeeder07 | 24 | 240 | 1 | N | See InsertFeeder01 above for Field Definition |
| InsertFeeder08 | 25 | 241 | 1 | N | See InsertFeeder01 above for Field Definition |
| InsertFeeder09 | 26 | 242 | 1 | N | See InsertFeeder01 above for Field Definition |
| TotalSheetsFedInptFdr1 | 27 | 243 | 2 | N | The value in this field is the total number of sheets fed from this input feeder for this mailpiece. This information is collected by Direct Connect during the inserting process. There are three of these fields available to accommodate as many as three input feeders on the inserter. |
| TotalSheetsFedInptFdr2 | 28 | 245 | 2 | N | See TotalSheetsFedInptFdr1 for field definition |
| InsertFeeder1Ack | 29 | 247 | 1 | N | The value in this field specifies whether an insert was fed or not fed from this insert feeder for this mailpiece. This information is collected by Direct Connect during the inserting process. There are 16 of these fields available to accommodate as many as 16 insert feeders on the inserter. Possible values include: 0 = Not fed, 1 = Fed. |
| InsertFeeder2Ack | 30 | 248 | 1 | N | See InsertFeeder1Ack for field definition |
| InsertFeeder3Ack | 31 | 249 | 1 | N | See InsertFeeder1Ack for field definition |
| InsertFeeder4Ack | 32 | 250 | 1 | N | See InsertFeeder1Ack for field definition |
| InsertFeeder5Ack | 33 | 251 | 1 | N | See InsertFeeder1Ack for field definition |
| InsertFeeder6Ack | 34 | 252 | 1 | N | See InsertFeeder1Ack for field definition |
| InsertFeeder7Ack | 35 | 253 | 1 | N | See InsertFeeder1Ack for field definition |
| InsertFeeder8Ack | 36 | 254 | 1 | N | See InsertFeeder1Ack for field definition |
| InsertFeeder9Ack | 37 | 255 | 1 | N | See InsertFeeder1Ack for field definition |
| InsertFeeder10Ack | 38 | 256 | 0 | N | See InsertFeeder1Ack for field definition |
| InsertFeeder11Ack | 39 | 256 | 0 | N | See InsertFeeder1Ack for field definition |
| InsertFeeder12Ack | 40 | 256 | 0 | N | See InsertFeeder1Ack for field definition |
| InsertFeeder13Ack | 41 | 256 | 0 | N | See InsertFeeder1Ack for field definition |
| InsertFeeder14Ack | 42 | 256 | 0 | N | See InsertFeeder1Ack for field definition |
| InsertFeeder15Ack | 43 | 256 | 0 | N | See InsertFeeder1Ack for field definition |
| InsertFeeder16Ack | 44 | 256 | 0 | N | See InsertFeeder1Ack for field definition |
| PassThroughData | 45 | 256 | 748 | A | This field is a user-defined field that does not affect the operation of the system. The data in this field is significant to your own applications. |
| End-of-data flag | 46 | 1004 | 1 | A | Always “X” to indicate the end of a record. |
| MachineID | 47 | 1005 | 10 | A | The value in this field identifies the machine on which the mailpiece was processed. This information is collected by Direct Connect during the inserting process. |
| OperatorID | 48 | 1015 | 10 | A | The value in this field identifies the operator who processed the mailpiece. This information is collected by Direct Connect during the inserting process. |
| MailpieceStatus | 49 | 1025 | 10 | A | The value in this field specifies the high-level mailpiece status. Possible values are: Good, Maybe, Bad, Pending or Null (unprocessed). This information is collected by Direct Connect during the inserting process. |
| MailPieceStatusText | 50 | 1035 | 10 | A | The value in this field specifies the text description of the high-level mailpiece status. Possible values are: Good, Maybe, Bad, Pending or Null (unprocessed). This information is collected by Direct Connect during the inserting process. |
| Disposition | 51 | 1045 | 1 | N | The value in this field specifies the mailpiece disposition. This information is collected by Direct Connect during the inserting process. |
Possible values are:
0 = Unknown 1 = On Inserter 2 = Removed due to Jam 3 = Removed by Operator 4 = Outsorted 5 = Successfully Rendered 6 = Never Processed 7 = Manually Rejected 8 = Manually Repaired 9 = Deferred ALL Dispositions EXCEPT 5 and 8 will be reprinted.
| DispositionText | 52 | 1046 | 25 | A | The value in this field specifies the text description of the mailpiece disposition. This information is collected by Direct Connect during the inserting process. |
| Cause | 53 | 1071 | 4 | N | The value in this field specifies the reason code why the mailpiece disposition was changed. This information is collected by Direct Connect during the inserting process. Contact a Pitney Bowes customer service representative to obtain a list of valid reason codes. |
| CauseText | 54 | 1075 | 20 | A | The value in this field specifies the text description of why the mailpiece disposition was changed. This information is collected by Direct Connect during the inserting process. |
| StatusSource | 55 | 1095 | 25 | A | The value in this field specifies the name of machine element that set the mailpiece disposition. This information is collected by Direct Connect during the inserting process. |
| ExitLocation | 56 | 1120 | 25 | A | The value in this field specifies the physical location where the mailpiece left the inserter. This information is collected by Direct Connect during the inserting process. |
| TimeStamp | 57 | 1145 | 20 | A | The value in this field specifies the date and time the mailpiece was processed. This information is collected by Direct Connect during the inserting process. Use the format MM/DD/YYYY HH:MM:SS. (Note that there is one space between the date and time). |
| Mode | 58 | 1165 | 8 | A | The value in this field identifies the inserter mode that was loaded for the job. This information is collected by Direct Connect during the inserting process. |
| ActualInsertFeederScan | 59 | 1173 | 6 | A | When the Job Match feature or the Insert to Piece Match feature is used, a value will be present in this field. The value in this field specifies the actual scancode that was read at the matching insert feeder. This information is collected by Direct Connect during the inserting process. |
| ActualOutputScan | 60 | 1179 | 6 | A | When the Output Scan feature is used, a value will be present in this field. The value in this field specifies the actual scancode read at the output scanner. This information is collected by Direct Connect during the inserting process. |
| UserDefinedField1 | 61 | 1185 | 20 | A | This field contains the same value as the User Defined Field in Input file. |
| UserDefinedField2 | 62 | 1205 | 20 | A | This field contains the same value as the User Defined Field in Input file. |
| UserDefinedField3 | 63 | 1225 | 200 | A | This field contains the same value as the User Defined Field in Input file. |
| Extra - Future Use | 64 | 1425 | 141 | A | |
| End of record “X” | 65 | 1566 | 1 | A | End of Record Indicator. Insures FTP Client does not truncate trailing spaces. |
| Total | 1566 |
FileBased Select
| Select File Layout | |||||
| Field Name | Field | Start | Length | Type | Description |
| JobID | 1 | 1 | 8 | A | This field contains the same value as the JobID field in Input file. |
| PieceID | 2 | 9 | 15 | A | This field contains the same value as the PieceID field in Input file. |
| AccountIdentifier | 3 | 24 | 20 | A | This field contains the same value as the Account Identifier field in Input file. |
| MailpieceStatus | 4 | 44 | 10 | A | High-level mailpiece status (Good, Maybe, Bad, Pending or Null (unprocessed)). |
| Disposition | 5 | 54 | 1 | N | The value in this field specifies the mailpiece disposition. This information is collected by Direct Connect during the inserting process. |
Possible values are:
0 = Unknown 1 = On Inserter 2 = Removed due to Jam 3 = Removed by Operator 4 = Outsorted 5 = Successfully Rendered 6 = Never Processed 7 = Manually Rejected 8 = Manually Repaired 9 = Deferred ALL Dispositions EXCEPT 5 and 8 will be reprinted.
| DispositionText | 6 | 55 | 25 | A | The value in this field specifies the text description of the mailpiece disposition. This information is collected by Direct Connect during the inserting process. |
| CauseBin | 7 | 80 | 4 | N | The value in this field specifies the reason code why the mailpiece disposition was changed. This information is collected by Direct Connect during the inserting process. Contact a Pitney Bowes customer service representative to obtain a list of valid reason codes. |
| CauseBinText | 8 | 84 | 20 | A | The value in this field specifies the text description of why the mailpiece disposition was changed. This information is collected by Direct Connect during the inserting process. |
| IMB | 9 | 104 | 31 | A | USPS IMB |
| ReprintIndex | 10 | 135 | 20 | A | This field contains the same value as the Reprint Index field in Input file. |
| UserDefinedField1 | 11 | 155 | 20 | A | This field contains the same value as the User Defined Field in Input file. There are 5 of these fields available to accommodate as many as 5 user-defined pass-through fields. |
| UserDefinedField2 | 12 | 175 | 20 | A | This field contains the same value as the User Defined Field in Input file. There are 5 of these fields available to accommodate as many as 5 user-defined pass-through fields. |
| UserDefinedField3 | 13 | 195 | 200 | A | This field contains the same value as the User Defined Field in Input file. There are 5 of these fields available to accommodate as many as 5 user-defined pass-through fields. |
| End of record “X” | 14 | 395 | 1 | A | End of Record Indicator. Insures FTP Client does not truncate trailing spaces. |
| Total | 395 |
Revision
| Rev ID | Date | Revision Description |
| 1 | 4/10/08 | Added 8 possible rates for a total of 12. To accomidate flats. |
| 2 | 7/29/08 | Revised the Header, Input and Output spreadsheet to correctly indentify End of Record "X" positions. All Modifications are in RED |
| Cont. | The Header and Input records are 1350 bytes. The Output record is 1566 bytes. As of 7/29/08 Jerry Morrison 609-777-3911 | |
| 3 | 9/10/12 | Stole one byte from Field #3 (TotalSheetsInputFdr1) and increased Field #4 (TotalSheetsInputFdr2) by 1 byte to allow for mail pieces over 99 pages. |
| 4 | 10/24/13 | Updated documentation to reflect change noted above in Rev ID #3 |
File details come from the government source that posted it. Updated .