XERIA lets you control how personalized PDF output files are named so that a batch of recipient-specific documents can be easier to identify, sort, review, archive, and deliver. A clear filename policy becomes especially important when one source PDF produces dozens or hundreds of personalized copies.
Good output naming is not only a convenience feature. The filename can become part of the operational link between the recipient record, the generated PDF, the e-mail attachment, the archive folder, and later troubleshooting. The goal is to create names that are unique enough to avoid confusion without placing unnecessary sensitive information in the filename itself.
The Short Answer
Open the personalized PDF workflow, locate the output filename or naming settings, choose the naming pattern shown by the current XERIA interface, include only the recipient fields or variables that are actually supported, preview or generate a small sample, and confirm that every output has the intended name before running the full batch.
A practical filename should help you identify the document without creating collisions. For example, a stable document label plus a supported recipient value or another unique field can be more useful than a generic name such as `Document.pdf` repeated for every recipient.
Why Output Filenames Matter in Personalized PDF Workflows
In a personalized batch, the visual content inside each PDF may differ by recipient while the source document remains the same. If every generated file receives an indistinguishable name, manual review becomes harder and the risk of attaching or moving the wrong copy increases.
A consistent naming policy makes later operations easier: checking the output folder, matching files to recipient records, sending attachments, finding a specific copy, comparing a failed job with a resumed job, or archiving the final distribution set.
1. Decide What the Filename Needs to Communicate
Before configuring the naming pattern, decide what a user should be able to understand from the filename alone. The answer depends on the workflow. An internal batch may benefit from recipient identity, while an externally visible attachment name may need to be more neutral for privacy or professionalism.
- Identify whether filenames are mainly for internal operators or external recipients
- Decide which document label should remain constant across the batch
- Choose only recipient values that are actually useful for identification
- Avoid unnecessary personal or confidential information in filenames
- Plan how duplicate or similar recipient names will be distinguished
- Keep the naming pattern short enough to remain readable
2. Configure Personalized PDF Output Filenames in XERIA
Step 1: Open the Personalized Batch Workflow
Open the XERIA workflow you use to generate personalized PDFs and load the source document and recipient data. If the recipient list first needs to be imported from a spreadsheet, see [Import an Excel Recipient List into XERIA](/resources/articles/import-excel-recipient-list-into-xeria/). If the list already exists but needs review or maintenance, see [Create and Manage Recipient Lists in XERIA](/resources/articles/create-manage-recipient-lists-in-xeria/).
Step 2: Locate the Output Filename Settings
Find the output filename, output naming, or equivalent control shown by the current XERIA interface. Use the options presented by the installed version rather than assuming an older naming syntax still applies.
Step 3: Build the Naming Pattern
Create the pattern using the fixed text and dynamic recipient values supported by the interface. Keep the fixed portion meaningful—for example, a project, report, course, invoice, proposal, or distribution label—and use dynamic values only where they improve identification.
Step 4: Preview or Generate a Small Sample
Generate a few representative outputs before the production batch. Include recipients with similar names, long values, non-Latin characters, and any edge cases present in the actual list. Check the resulting filenames exactly as Windows and the destination folder display them.
Step 5: Confirm the Pattern Before the Full Batch
Once the sample is correct, verify the production recipient list and output folder, then run the full batch. After generation, review the folder for duplicate-looking names, unexpected substitutions, missing values, or files that do not match the intended recipient records.
3. Use Dynamic Recipient Values Carefully
Dynamic filename values are useful because they reduce the need to rename files manually. Depending on the current XERIA version and the recipient data available to the workflow, the naming interface may allow supported recipient fields or variables to be inserted into the filename pattern.
Treat the current interface as the source of truth. A token that works inside a visible watermark is not automatically a filename variable, and a spreadsheet column is not automatically available for output naming unless XERIA exposes it for that purpose.
4. Keep Filenames Compatible and Readable
Output names ultimately have to work as Windows filenames and may later be uploaded to cloud storage, attached to e-mail, copied to network folders, or handled by other systems. Use a simple naming convention that avoids avoidable path and character problems.
- Keep names reasonably short
- Avoid decorative punctuation that adds no identification value
- Do not rely on characters that Windows does not allow in filenames
- Avoid trailing spaces or ambiguous repeated separators
- Use a predictable separator such as a hyphen or underscore when helpful
- Test non-Latin recipient values if your recipient list is multilingual
5. Prevent Duplicate Filenames
Two recipients can share the same name, initials, company, or other visible identifier. If the naming pattern is not unique enough, different personalized outputs may produce identical or nearly identical filenames, creating confusion or overwrite risk depending on how the output workflow handles duplicates.
Use another supported differentiator when necessary, such as a unique recipient value, internal reference, e-mail-derived identifier, sequence, or another field shown by XERIA. Do not invent a variable that the interface does not support; instead revise the recipient data or naming pattern using the controls actually available.
6. Balance Identification with Privacy
A filename can be visible outside the PDF itself. It may appear in e-mail clients, download folders, cloud storage activity, recent-file lists, backup systems, or screenshots. For that reason, avoid placing sensitive personal, medical, financial, contractual, or security information in the filename unless there is a clear operational need.
For external delivery, a neutral naming pattern can be preferable—for example, a document label plus a limited recipient identifier—while more detailed association remains inside XERIA records, the personalized watermark, trace information, or internal recipient data.
7. Use One Naming Policy Consistently Across a Batch
A batch is easier to audit when every output follows the same naming logic. Changing the pattern in the middle of production can make later reconciliation harder, particularly if some files are generated before a pause, interruption, restart, or resume operation.
Before a large job, lock down the naming pattern together with recipient data, protection settings, output location, and delivery settings. If you intentionally change the naming policy, treat the new run as a clearly separate production set.
8. Check How the Filename Appears During Delivery
The generated filename often becomes the attachment name that the recipient sees when a personalized PDF is sent by e-mail. Before a real distribution, send a test message and confirm that the attachment name is understandable, professional, and correctly associated with the recipient.
This matters for both manual and automated delivery. A well-named file can reduce attachment confusion, while an overly detailed filename can expose information that did not need to be visible outside the protected PDF. If you use Gmail delivery, see [Send Personalized PDFs with Gmail in XERIA](/resources/articles/send-personalized-pdfs-with-gmail-in-xeria/).
9. Troubleshoot Unexpected Output Filenames
If filenames are missing values, duplicated, malformed, or different from the expected pattern, start by checking the recipient data and the current naming configuration. Then generate a small test set before rerunning the entire job.
- Confirm that the intended recipient list is loaded
- Check that the selected naming pattern is the production pattern
- Verify that dynamic values are populated in the recipient records
- Look for recipients with identical values used in the filename
- Test long names and non-Latin characters
- Avoid manually renaming a few files if the underlying batch pattern is wrong
Practical Best Practices
Use a filename policy that is predictable, unique enough, privacy-aware, and easy to validate. Keep the fixed document label stable, use supported dynamic recipient values only when they add real value, test edge cases, and review the final output folder before sending or archiving.
- Use one consistent pattern for the whole production batch
- Keep filenames understandable to both operators and recipients
- Include only the minimum recipient information needed for identification
- Make duplicate names unlikely
- Test the actual generated names before production
- Keep naming logic aligned with recipient, delivery, and archive workflows
How Output Naming Fits into XERIA
Output naming is part of XERIA’s personalized batch workflow. It works alongside recipient lists, imported spreadsheet data, personalized watermarks, trace codes, passwords, PDF permissions, controlled e-mail delivery, cloud-connected outputs, Mail Log, and other document-generation settings.
Its role is operational clarity: making each generated file easier to associate with the intended recipient and downstream workflow without changing the security meaning of the PDF itself. A good filename supports organization and reconciliation; it is not a security control by itself.
Frequently Asked Questions
Can XERIA include recipient information in personalized PDF filenames?
Use the recipient fields or dynamic values that the current XERIA output naming interface explicitly supports. The exact available values can depend on the version and workflow, so do not assume every spreadsheet field or watermark token can be used as a filename variable.
What happens if two recipients generate the same filename?
That creates a collision risk or at least an identification problem. Review the naming pattern and use another supported differentiator so that outputs remain distinguishable. Always test duplicate or similar recipient names before a large batch.
Should I put the recipient’s full e-mail address in the filename?
Only if there is a real operational reason and the privacy tradeoff is acceptable. Filenames can be exposed in many systems outside the protected PDF, so a shorter or less sensitive identifier is often preferable.
Does changing the output filename change the PDF protection?
No. The filename helps identify and organize the file, but it is not the same as encryption, password protection, PDF permissions, watermarking, or trace data. Those protection layers should be configured separately.
Conclusion
Configure personalized PDF filenames in XERIA as part of the production workflow, not as an afterthought. Define what the name needs to communicate, use only the dynamic values supported by the current interface, test representative recipients, prevent duplicate names, protect unnecessary personal information, and confirm the final output before delivery.