XERIA can import a prepared Excel recipient list into its recipient database so that the same people and recipient data can be reused in later batch workflows. The spreadsheet is an import source, not a permanent requirement: after the records are written to XERIA, future personalized jobs can use the saved recipient list directly.
The safest way to import is to treat the spreadsheet as structured data rather than as a visual document. Review the source columns first, map each column deliberately to the corresponding XERIA field, inspect sample rows, remove test or empty records, and only then write the mapped data to the recipient database. This reduces the risk of producing personalized files with the wrong name, e-mail address, organization, password, filename, or trace-related value.
The Short Answer
Prepare a clean Excel recipient list, open the recipient import workflow in XERIA, select the spreadsheet, review the detected columns, map each spreadsheet column to the intended XERIA recipient field, check required data and sample rows, exclude unwanted records, and then write the mapped records to the XERIA database.
After the import, work from the saved recipient list inside XERIA. You do not need to keep selecting the Excel spreadsheet for every future batch. The imported list can be used as the recipient source for personalized PDF generation and related batch operations.
1. Prepare the Excel Recipient List Before Import
A clean source file makes the import much easier to review. Keep one recipient per row and use a consistent meaning for each column. Avoid mixing unrelated values in the same column. Remove explanatory rows, temporary test recipients, duplicate headers, and blank rows that are not intended to become recipient records.
- Use one row per intended recipient
- Keep each data type in a consistent column
- Use clear column headings that make mapping easy to recognize
- Remove test rows and empty records before import when possible
- Review duplicate recipients and reused recipient identifiers
- Check for unexpected spaces or characters that could change a value
2. Decide Which Recipient Fields You Actually Need
XERIA recipient data can include values such as name, e-mail address, organization, department, recipient code, trace-related values, password information, output filename information, and delivery-related fields. You do not need to populate every possible field. Include only the data required by the personalization, protection, naming, trace, or delivery workflow you plan to run.
- Name or full name for recipient identification
- E-mail address when the workflow uses e-mail delivery
- Organization or company-related information when needed
- Department or other grouping information when relevant
- Recipient code or other unique reference used by your workflow
- Password, output filename, trace, or delivery values only when the workflow requires them
3. Import the Spreadsheet into XERIA
Step 1: Open the Recipient Import Workflow
Start from the recipient-list area in XERIA and open the Excel import workflow. The goal is to bring the spreadsheet data into XERIA's recipient database, where the resulting list can be reused later. If you already maintain recipients directly in XERIA, Excel import remains optional rather than mandatory.
Step 2: Select the Prepared Excel File
Choose the prepared recipient spreadsheet. XERIA reads the source so that the available columns can be reviewed before the database is changed. At this stage, verify that you selected the intended file and that the first data rows look like the list you expect to import.
Step 3: Review the Detected Columns
Inspect the columns detected from the spreadsheet before mapping them. This is the point to catch accidental extra columns, shifted values, blank headings, or a source structure that does not match the intended recipient data. Correct the spreadsheet first if the layout is ambiguous.
Step 4: Map Excel Columns to XERIA Fields
Map each relevant Excel column to the corresponding XERIA recipient field. A column containing names should map to the name field, an e-mail column to the e-mail field, organization data to the appropriate organization field, and so on. Leave unrelated source columns unmapped rather than forcing them into an incorrect field.
Step 5: Check Required Data and Sample Rows
Before committing the import, review sample rows and confirm that the important fields contain the expected values. Pay particular attention to names, e-mail addresses, recipient codes, passwords, output filenames, and trace-related data because an error in one of these fields can propagate into personalized output.
Step 6: Exclude Unwanted Records and Write to the Database
Exclude test records, empty rows, or other entries that should not become active recipients. When the mapping and sample data are correct, complete the import so the mapped records are written to the XERIA recipient database. Review the import result before using the list for production work.
4. Choose the Appropriate Import Target
When the import workflow offers a recipient import target, choose it according to what should happen to the recipient list. The available workflow can distinguish between creating a new list, adding records to the current list, or replacing the current list. Treat replacement as a deliberate operation because existing list contents may be removed before the new records are written.
- Create a new list when the spreadsheet should become a separate recipient set
- Append to the current list when the new records should be added to existing recipients
- Replace the current list only when the spreadsheet is intended to become the complete new list
- Review the previous and resulting record counts after the operation
5. Review the Import Result Before Running a Batch
A successful import should still be reviewed before document generation. XERIA can report import-result information such as the target list, previous records, deleted records, inserted records, updated records, and skipped records. Use those counts as a reasonableness check and then inspect the recipient grid or list itself before starting production.
- Look for shifted rows or values appearing under the wrong field
- Check duplicate recipients and reused recipient codes
- Review empty names or missing values that matter to your template
- Verify e-mail addresses before using e-mail delivery
- Check for unexpected spaces and unsupported characters
- Confirm that the imported list contains the recipients you intended
6. Use the Saved Recipient List in Future Batches
Once the data is in XERIA, the database recipient list becomes the working source for later batch operations. This is important because Excel is not required every time you generate personalized PDFs. You can maintain and reuse recipient lists in XERIA instead of repeatedly importing the same spreadsheet.
From there, the saved recipient data can participate in list-based batch production: recipient-specific watermark values, trace-related identifiers, passwords, filenames, and delivery information can be applied according to the workflow you configure. If you are new to the general watermarking process, [How to Watermark a PDF](/resources/articles/how-to-watermark-a-pdf/) provides the broader foundation.
Common Import Mistakes to Avoid
Most import problems originate in the source data or the mapping step rather than in the act of writing records. A few minutes of review before import is usually safer than discovering an error after dozens or hundreds of personalized files have already been produced.
- Importing a sheet that still contains sample or test recipients
- Mapping an e-mail column to the wrong XERIA field
- Using inconsistent values in the same spreadsheet column
- Leaving duplicate or obsolete recipients in the source list
- Reusing a recipient code that should be unique in your workflow
- Starting a production batch without reviewing the imported records first
Practical Best Practices
For repeatable operations, treat the recipient list as controlled production data. Keep a clean source spreadsheet, use stable identifiers where appropriate, review mappings whenever the spreadsheet structure changes, and verify the imported list before generating files. If the list is already maintained correctly in XERIA, update the database list directly rather than importing Excel again without a reason.
- Keep the source spreadsheet simple and purpose-specific
- Use consistent field meanings from one import to the next
- Review the import target before committing the operation
- Verify sample rows before writing to the database
- Check the resulting recipient list before production
- Keep recipient data aligned with the watermark, trace, filename, and delivery workflow that will use it
How This Fits into the XERIA Workflow
XERIA's Excel import is a recipient-data onboarding step, not the document-processing engine itself. Its purpose is to bring structured recipient information into the recipient database so later list-based batch production can use those saved records consistently.
After import, XERIA can use recipient records for personalized PDF workflows that may include visible recipient-specific watermarks, trace codes, password and permission settings, output naming, controlled e-mail delivery, cloud-connected outputs, Mail Log records, and other configured distribution steps. Use only the fields needed for the workflow you actually intend to run.
Frequently Asked Questions
Do I need an Excel file every time I run a batch in XERIA?
No. Excel is an optional import source for bringing recipient data into XERIA. After the records are stored in the recipient database, later batches can use the saved recipient list directly.
Does every spreadsheet column have to be imported?
No. Map only the source columns that correspond to recipient fields your workflow needs. Unrelated columns should be left unmapped rather than assigned to an incorrect XERIA field.
What should I check before completing the import?
Review the detected columns, mapping, required fields, and sample rows. Look for duplicate recipients, empty names, invalid-looking e-mail addresses, reused recipient codes, unexpected spaces, unsupported characters, shifted rows, and any field that appears under the wrong column.
Can I replace an existing recipient list with an Excel import?
The import workflow can support a replace-current-list target as well as creating a new list or appending to the current one. Use replacement deliberately and review the import result so you understand what was deleted, inserted, updated, or skipped.
Conclusion
Importing an Excel recipient list into XERIA is best treated as a controlled data-mapping process. Prepare a clean spreadsheet, review detected columns, map only the fields you need, inspect sample rows, choose the correct import target, and review the result before production. Once the recipients are stored in XERIA, the spreadsheet is no longer required for every batch—the saved database list can drive future personalized PDF workflows.