Metro 2 Header Record
The Header Record is the first record in every Metro 2 file, containing essential file-level information and data furnisher identification.
Overview
The Header Record is a mandatory component that appears once at the beginning of every Metro 2 credit reporting file. It identifies the data furnisher submitting the file and provides critical metadata about the file contents. The Header Record must be exactly 426 characters in length and follows a fixed-width format.
This record establishes the context for all subsequent Base Segments and optional segments in the file, ensuring proper routing and processing by credit bureaus. Without a valid Header Record, the entire file will be rejected by the receiving credit bureau.
Header Record Structure
| Field | Position | Length | Type | Description |
|---|---|---|---|---|
| Record Descriptor Word | 1-4 | 4 | Alpha | Must be "HEADER" (left-justified) |
| Record Identifier | 5-8 | 4 | Numeric | Cycle number (right-justified, zero-filled) |
| Processing Date | 9-16 | 8 | Date (MMDDYYYY) | Date file was created |
| Program Identifier | 17-21 | 5 | Alpha | Software identifier (left-justified) |
| Program Version | 22-26 | 5 | Alphanumeric | Software version number |
| Reporter Name | 27-66 | 40 | Alphanumeric | Data furnisher's name |
| Reporter Address | 67-162 | 96 | Alphanumeric | Complete furnisher address |
| Reporter Telephone | 163-172 | 10 | Numeric | 10-digit phone number |
| Software Vendor Name | 173-212 | 40 | Alphanumeric | Name of software vendor |
| Software Vendor Contact | 213-252 | 40 | Alphanumeric | Vendor contact person |
| Software Vendor Phone | 253-262 | 10 | Numeric | Vendor phone number |
Note: This table shows primary fields. The complete Header Record contains additional fields for a total length of 426 characters.
Key Components
Record Descriptor Word
The first four positions must contain "HEADER" (left-justified with trailing spaces). This identifier tells the credit bureau that this is the file header and not a Base Segment or other record type.
Processing Date
The date the file was created in MMDDYYYY format. This is critical for file tracking and ensuring data is processed in the correct sequence. The processing date helps credit bureaus identify duplicate submissions and maintain proper chronological order.
Reporter Identification
The reporter name, address, and telephone number identify the data furnisher submitting the file. This information must match the furnisher's registration with the credit bureau and is used for communication regarding file issues or questions.
Software Information
The program identifier, version, software vendor name, contact, and phone number provide traceability for the software that generated the Metro 2 file. This information is valuable for troubleshooting formatting issues and ensuring compliance with Metro 2 specifications.
Example Header Record
HEADER0001112020251234VEND1.0 ABC Financial Services Inc. 123 Main Street, Suite 500, New York, NY 10001
2125551234Switch Labs John Smith 8005551234Note: This is a simplified example showing key fields. Actual Header Records include additional fields and must be exactly 426 characters.
Important Notes
- •The Header Record must always be exactly 426 characters in length
- •Only one Header Record is permitted per Metro 2 file
- •The Header Record must be the first record in the file, before any Base Segments
- •Alphanumeric fields should be left-justified and space-filled
- •Numeric fields must be right-justified and zero-filled
- •All dates must be in MMDDYYYY format with valid month, day, and year values
- •Phone numbers must be 10 digits without formatting characters (no dashes, spaces, or parentheses)
Best Practices
Maintain Consistent Information
Ensure that your reporter information (name, address, phone) remains consistent across all file submissions and matches your registration with the credit bureau.
Validate Before Submission
Always validate your Header Record before submitting files to credit bureaus. A single character error can cause the entire file to be rejected.
Keep Software Information Current
Update the program identifier and version fields whenever you upgrade your reporting software. This helps with troubleshooting and tracking file generation.
Use Accurate Processing Dates
Set the processing date to the actual date the file was created. Incorrect dates can cause processing delays or file rejections.
Document Your Header Configuration
Maintain documentation of your Header Record configuration for reference and to ensure consistency across team members and systems.
Common Errors to Avoid
- •Incorrect record length (not exactly 426 characters)
- •Using "HEAD" instead of "HEADER" in the descriptor word
- •Invalid date formats (e.g., YYYYMMDD instead of MMDDYYYY)
- •Including formatting in phone numbers (dashes, spaces, parentheses)
- •Leaving required fields blank or filled with only spaces
- •Using special characters in fields designated for alphanumeric data
Ready to Start Reporting?
Our platform makes Metro 2 Header Record creation simple and error-free