#
Filenames
#
Introduction
This section includes information about filenames in general and the different ways they are relevant when integrating with Pagero Network.
#
Unique filenames
Regardless of direction, format and transport protocol; we strongly advise that all filenames be unique.
#
Examples
To illustrate, the following are ❌ BAD examples:
invoiceNumber.xmlinvoiceNumber_date.pdforderType_sellerVatNumber.edi
The following are ✔️ GOOD examples:
uniqueId_invoiceNumber.xmlinvoiceNumber_date_uniqueId.pdforderType_sellerVatNumber_uniqueId.edi
For certain use cases and setups, e.g. for files FROM Pagero delivered via SFTP; all filenames will be set up to be unique, due to the possibility of clashes on the disk system when not doing so.
#
Special characters
The general recommendation is to only use alphanumerical characters in filenames, i.e. alphabetical letters between A-Z or a-z, and/or digits between 0-9.
Non-alphanumerical characters such as ?, %, *, :, |, ", <, >, ., ,, ;, = and (blankspace) are reserved and should never be used.
#
Regular expressions
For inbound files, i.e. to Pagero, we can use regular expressions to "filter out" documents based on a given filename structure. This can be especially valuable in multi-company setups, where all files can be placed in one directory on the server and then filtered out by e.g. VAT-number, GLN, business unit etc. in the filename and then forwarded to the correct entity´s account in Pagero Online.
This mainly works in SFTP setups, but works both when fetching from external servers and when using Pagero´s server.
#
Dynamic content
For outbound files, i.e. from Pagero, we can use document content to construct dynamic filenames.
Examples of this would be to fetch the buyer tax number and set this as a prefix in the filename, set the document subtype as a suffix, set the document date/timestamp etc.