PaperPort scan naming is controlled by the scan profile's Output settings, while the general Item options supply related naming defaults. If files are difficult to sort or repeatedly acquire unexpected suffixes, inspect both roles before renaming a large collection manually.
Use disposable scans in a test folder. This guide follows the official PaperPort 14.7 naming controls; it does not recommend altering an archive's existing filenames without the document owner's approval. External references and filing procedures may depend on those names.
Define the naming problem first
Decide whether you need chronological sorting, uniqueness or a human-readable description. Those are related but different requirements. A date alone can describe when scanning occurred, yet several items scanned on that date still need distinct names.
The official Scanning Profile settings describe name, prefix and suffix choices. They also document the sequential numbering requirement in the applicable prefix or suffix. Use the options actually offered by your installed version rather than typing an unsupported token copied from another application's naming system.
Distinguish capture date from document date
An automatic current date describes the scanning event. It does not establish the invoice date, signing date or date of the business transaction. Keep substantive document dates in the approved metadata process when those are needed for retrieval.
Choose enough numeric width
Where the product offers fixed-width numbering, leading zeros can make ordinary filename lists easier to sort. Compare sample names representing single-digit and double-digit counts. The choice should reflect the intended batch size and filing convention, rather than an arbitrary preference for a longer filename.
Inspect the profile actually used
Open Scan Settings, select the active profile and review its Output tab. Record its current name and output format before changing anything. Another profile may use a different convention, so a successful test through one scanning button does not establish that every intake route follows it.
The Item options reference explains naming defaults for combined or stacked PDF items and the suffix scheme. It specifically directs scanned-item naming to the scanning profile. Keep those operations separate while diagnosing the result.
| Operation | Relevant naming check |
|---|---|
| Newly scanned document | Selected profile's Output naming |
| Combined or stacked item | General Item naming defaults |
| Several same-day scans | Sequential element and resulting unique names |
| Files sort unexpectedly | Date representation and numeric width |
Test repeated scans in the same destination
Create several harmless outputs with the proposed convention. Inspect the exact filenames in both PaperPort and the underlying approved folder. Confirm that no extension is hidden in a way that makes two different formats look identical.
Include an existing-name case
Place an approved sample with a potentially matching name in the test folder, then observe the documented naming behavior of a new scan. Do not rely on assumptions about collision handling when important files are involved. Stop if a warning offers replacement and inspect the path and selected operation.
Review the result after changing folders
If staff scan into multiple destinations, repeat the test in a second permitted folder. Record the result instead of assuming a counter behaves as a global business identifier. A filename counter should not be described as a guaranteed unique invoice or client reference across unrelated systems.
Keep names useful without embedding private data
Avoid placing sensitive personal details in filenames simply because they are visible in the document. Names can appear in email subjects, shared-folder listings and support screenshots. Use the organization's approved identifiers and metadata scheme.
For mobile capture, see our OneDrive OCR walkthrough. If both routes feed the same document library, agree a shared filing convention rather than letting each scanner invent a competing one.
After adopting the profile, have another operator make a harmless scan and verify the expected filename. That confirms the procedure is understandable without relying on the person who configured it.
Review the convention with the person responsible for retrieval. A filename that looks tidy to the scanning operator may be confusing to the colleague searching for it later.
Retain a small note with the profile name, date convention, sequential pattern and test result. Leave older archive names intact unless a separate migration has been approved, and distinguish convenient sorting from the authoritative records identifiers used by the business.
