Why conventions fail in daily work
The rule is usually not wrong but inaccessible: it lives in a wiki article somebody wrote two years ago. It would have to be applied at the moment the file is saved, in the middle of another task and under time pressure. Add new colleagues, temporary staff and holiday cover who have never seen the rule at all. Checking after the fact works no better, because nobody wants to rename other people's files and follow-up questions land as a reprimand.
How to recognise a usable convention
A good convention is short enough to keep in your head. The date goes first in ISO form so every folder sorts chronologically by itself. The field order is fixed, not situational. For document type and sender there is a manageable list of permitted values rather than free wording — otherwise Incoming invoice, Invoice and INV end up side by side. Spaces, accented characters and slashes stay out, because they cause trouble with sync and path lengths. And the total length stays moderate so deeply nested paths on Windows do not hit the limit.
The only place a convention takes hold
A convention is enforced where the name is created, not where it is noticed later. Everything else is rework. From that follows an uncomfortable but useful conclusion: as long as naming is a voluntary act under time pressure, it will stay inconsistent, however well the rule is written. You have three options — reduce the number of people who name files; move the moment at which naming happens; or take naming out of manual work altogether.
Organisational levers without extra software
The first option is often the most effective: one person opens the inbox and files everything, everyone else has read access only. That halves the variety of variants immediately. The second: an inbox folder where files may land raw, and a fixed slot at which they get named and moved — then the rule is no longer in the way when things are urgent. Add a small card with three examples right at the scanner, not in the wiki. That costs nothing and works.
Where a tool takes the convention over
The third route is to stop having the fields typed at all. Filery Rename reads the PDF, recognises sender, document date, document type and subject, and assembles the name from those according to your pattern, for example Date_Sender_Type with a configured date format. The configuration can hold lists that recognised values are checked against — so the document type comes from your list rather than from free wording. Before a file is renamed, the proposal stands next to the current name and you release it.
Limits you should plan for
Two constraints come with this. First: Filery is installed and configured per workstation. There is no central distribution of the pattern through a management console — you settle the pattern once and set it up identically at each machine. Second: Filery reads the PDF on your machine and sends the content encrypted for AI analysis; the metadata comes back, the renaming runs again on your own device, and the files are not stored permanently. Whether that is permitted is for your privacy assessment to decide, not for us.
FAQ
Related topics
Download Now
Choose your platform and start with automatic document renaming
Windows
Windows 10 & 11
We are currently working on official code signing for Windows. The download is already available – Windows Defender or SmartScreen may show a warning because the app is not yet certified. Choose “More info” → “Run anyway” to install.
System requirements: macOS 10.14+, Windows 10/11
All downloads are transmitted securely via HTTPS.