File Naming Conventions and Datestamping

The job ran, reported success, and moved nothing, because the file it wanted was called Sales_ and the pattern said sales_. In an automated flow, a file's name is not a label — it is an interface. Scripts route on it, dedupe on it, sort by it, and troubleshoot from it. A good convention lets a half-asleep admin read a filename and know what the file is, where it came from, and which day it belongs to. A bad one guarantees a future incident involving a space, an ampersand, or two files with the same name and different contents. The incident is not scheduled. It is merely certain.

This series treats naming with the seriousness automation demands. It covers why names make or break pipelines, datestamp formats that sort correctly, and sequence numbers and collision avoidance. It covers characters that survive every system a file will touch. It explains how to design and document a convention for your flows, and how to parse names reliably in scripts. Examples throughout use pattern tokens like YYYYMMDD, so the convention outlives any particular date. So does every joke about the one called final2.

Articles in This Series

• Why File Names Make or Break Automated Transfers
  The name is the pipeline's API: routing, sorting, deduplication, and troubleshooting all read it. This article adds the incident stories behind spaces, case changes, and creative punctuation.
• Datestamp Formats That Sort Correctly
  Learn about the big-endian YYYYMMDD family and why alphabetical order equals chronological order. This article covers the which-day-is-it time zone question, stamp placement in the name, and formats parsers love.
• Sequence Numbers, Uniqueness, and Collision Avoidance
  This article covers multiple files per day, retries that regenerate, and zero-padding so sorting works. It covers choosing a uniqueness source - counters, time-to-the-second, identifiers - and a collision policy decided in advance.
• Safe Characters: Names That Survive Every System
  This article covers case-sensitivity differences, spaces and quoting, the honest unicode story, reserved names and characters, and length limits. It gives the conservative character set that never causes a ticket.
• Designing a File Naming Convention for Your Flows
  Learn which fields are worth encoding - source, type, date, sequence, environment. This article covers delimiter choices, versioning the convention itself, writing it down, and migrating existing flows gently.
• Parsing File Names Reliably in Scripts
  Learn about extracting fields in bash, PowerShell, and Python, validating before trusting, and rejecting nonconforming names to the error folder. This article gives the small test set that keeps the parser honest.

Explore More Topics

This series is part of the Sysax file transfer topic library. The library covers the protocols, security practices, automation techniques, and operational skills behind reliable file transfer. It pairs well with the practical tools we build. Sysax Multi Server is a secure FTP, FTPS, SFTP, and HTTPS server for Windows. Sysax FTP Automation schedules and scripts secure transfers so the routine ones run themselves.