The hidden cost of ad hoc names
Names such as final, final-2 or latest do not explain which customer, market, date or commercial version a file belongs to. The problem becomes visible when a quotation returns months later or several people touch the same request.
A file name is a small interface. It should carry enough context to support recognition without becoming a paragraph.
A deterministic pattern
A useful pattern can combine quotation identifier, country code, customer abbreviation, date and version. Each field needs a written rule: allowed characters, length, separator and what happens when a value is unknown.
The same inputs should always create the same base name. A version change should create a new file rather than overwrite the earlier commercial record.
Automation should keep the rule visible
Excel is sufficient for this class of internal tool when validation and output logic are explicit. The goal is consistent daily use, not architectural novelty.
AI can help enumerate edge cases and draft formulas, but the business convention should remain readable to the people who own the quotation process.