Custom File Naming for Treasury Exports

For custom Treasury CSV and original file exports, you have the option to to define the names of outbound files.

Configure custom file names for export files

You can use customized naming for your export files, beyond the Coupa default of simple string and time stamp conventions.

Use the following steps to create custom file names when you create or update outbound CSV and original file integrations:

  1. From the File Naming Mode field for an integration, click Custom. The File Naming Convention section opens.

  2. Click +Insert Token to add naming components. You can also enter free text as a simple string, and the logic validates your entries. You see a preview of the custom name in the File Naming Convention field.

  3. Click Create or Save to apply the custom name.

Figure 1.

When generating the file on the Treasury side, the system reads the specified pattern from the integration configuration and transforms it into a real string by replacing the pattern placeholders (for example, EntityAbbreviation) with the actual corresponding data (the entity abbreviation or name).

The system also ensures that the generated custom file name does not exceed the technical maximum length limit of 255 characters. If the name is longer than this, the following happens:

  • Flat file integrations: You get a system error and can't save the the integration unless you go back and shorten the name.

  • Original file formats: The integration is saved but is given the standard naming.

Note: For flat files, you should make sure that file names are not duplicated, or they will be overwritten when the integration runs.

The supported naming patterns depend on the business object that is exported and whether the export results in a zipped file:

Supported custom file naming patterns

Naming componentAvailabilityDetails
Simple stringAll object typesHover over the information icon (i) to see the valid characters and values.
Date and time stamp:{Date}{Time}All object types

Use common and understandable formats for all exports, for example:

Date: yyyyMMdd (example: 20251117)

Time: HHMMSSSSS (example 063012345)

Business Object: {Object}All object typesEvery integration has a business object, and this can be used for file naming as well. This is the name shown for Business Object in the Integrations table after the Treasury:: prefix.
Specific patternsCurrently only for original file types (see Specific custom file naming patterns table)Available for objects where a single integration run produces multiple files, each unique by identifier.

Specific custom file naming patterns

Business ObjectPattern file namePattern file extension
Original Account Statement{StatementNo}{StatementFormat} {AccountId} {EntityAbbreviation}{BankAbbreviation} {AccountName}{ExportAccountNumber){StatementId}N/A
Original Bank File {ContractIdentifier}{FileIdentifier}{FileFormat}{FileName}{FileIdentifier} or string*

The files are exported with the custom names during the integration run. For zipped files, the files in the ZIP are exported with your custom naming at the integration level, while the ZIP file itself is given the standard Coupa naming convention used for Standard Exports or Original File Exports.

For more information, see the configuration steps at Custom exports for objects from new Treasury interface: Automation Views.