# File Definitions

Learn how payment data is structured and validated.

Payment files contain the payment and remittance information submitted to Payment Network for processing.

Before a payment can be processed, the submitted file must meet formatting requirements and pass validation checks. Payment Network validates both the file structure and the individual payment records it contains before processing begins.

For field-level requirements, formats, and supported values, see [**Payment File Schema →**](/products/deluxe-payment-network/developer-resources/payment-file-schema).

### Before You Submit

Before submitting a payment file, verify that:

The file is saved as a CSV file.

Required fields are populated.

Payment amounts use the expected format.

Routing and account numbers are valid.

Referenced documents are accessible.

Each record contains a unique `recordIdentifier`.

Performing these checks before submission helps reduce validation failures and processing delays.

### File Requirements

Payment files must:

- Use the `.csv` file extension.
- Be comma-delimited.
- Enclose values containing commas in double quotation marks (`"`).
- Include all required fields.
- Conform to the Payment File Schema.


Failure to meet these requirements may result in file rejection or validation errors.

### Validation Rules

Payment Network validates both the file and the records it contains.

#### File-Level Validation

File-level validation verifies that:

- The file can be opened and read.
- The file contains payment records.
- The file structure is valid.
- Required headers are present.


Examples of file-level failures include:

- Unreadable files
- Empty files
- Files containing only headers


File-level validation failures prevent the file from being processed.

#### Record-Level Validation

Record-level validation evaluates individual payment records.

Examples include:

- Missing required fields
- Invalid routing numbers
- Invalid account numbers
- Invalid payment amounts
- Invalid addresses
- Missing document references


A file may pass file-level validation while individual records fail record-level validation.

#### Conditional Fields

Some fields are required only under specific conditions.

Examples include:

- Banking and payor information when a payment amount is provided.
- Payment attachments for certain Print + Scan scenarios.
- Fields that apply only to Print + Scan workflows.


See [**Payment File Schema**](/products/deluxe-payment-network/developer-resources/payment-file-schema) for complete field requirements.

### Common Validation Failures

The following issues are frequently encountered during implementation:

| Validation Failure | Typical Cause |
|  --- | --- |
| Invalid routing number | Routing number is not 9 digits. |
| Invalid account number | Unsupported characters are present. |
| Missing payment amount | Required payment information is incomplete. |
| Missing address information | Recipient address fields are incomplete. |
| Invalid signature URL | URL is missing, inaccessible, or unsupported. |
| Unsupported attachment type | Unsupported document format. |


For a complete list of validation and processing errors, see [**Error Codes & Messaging →**](/products/deluxe-payment-network/developer-resources/error-codes-messaging).

### Best Practices

Follow these recommendations when generating payment files:

- Validate data before submission.
- Use unique `recordIdentifier` values.
- Include lockbox information when available.
- Verify attachment and signature URLs.
- Test with representative payment data before moving to production.