Use these guidelines when setting up Standard or custom Treasury CSV and original file exports:

• Always build your integrations using file headers instead of column positions, as positions are subject to change.
• Exported data cannot exceed the supported limit of 150,000 rows.
• For more information on the elements for the CSV exports, refer to the API documentation in the Treasury application. See View Treasury API Documentation.

For more information, see Using the Flat File Format.

Available Standard exports

File names contain the object name, date, timestamp, and an integer to prevent overwriting existing files. For example: AccountBalance_20250402_104107+0.

sFTP folders are located under /Outgoing followed by a dedicated folder per object. For example: /Outgoing/AccountBalances. The folders are automatically created once the export triggers.

For examples of exports, download the example export files ZIP.

Custom Treasury export integrations

Custom Treasury export integrations are based on automation views that you configure on the respective menu items in Treasury Management.

This is supported for all objects in the new Treasury Management interface. For example, Cash Flows is supported, while Netting Items Classic is not. The Automation View field is only visible if this feature is supported for the selected object.

For more information, see Automation Views in Treasury Management.

To use the self-service to create or edit outbound Treasury integrations, use the following steps:

1. Go to Setup > Integrations > Integrations to configure your Treasury process.
2. Select Create or use the pencil icon to open an existing custom integration.
3. For Integration, select Flat file or Original format (see Treasury Original File Export Types).
4. For Direction, select From Coupa.
5. For Business Object, select the name of the Treasury object. The Automation View field appears when the object supports an integration that you can customize using self-service.
   Note: If the Automation View field does not appear for an object, then you must request a Statement of Work (SOW) from Coupa to customize the integration.
6. Select a defined view from the Automation View field. This defines the filter parameters for your custom integration.
7. You must also select your End System Type and End System.
   Important: Don't enter Internal for End System, since this setting prevents you from editing an integration.
8. You can use the optional Subfolder field to specify a string that is valid to be a subfolder. If you don't enter a string for the subfolder, nothing is specified and the sFTP folder for the business object is used without a subfolder.
   Note: If you do not enter a value for Subfolder when you save the integration, you cannot add it later. This means you have to create a new integration to specify a string for the subfolder. Also note that when you specify a subfolder name, the system automatically pluralizes the last segment of the folder name using a standard pluralization library. For example, if you enter a path like bankfile/PDF, the last segment is pluralized, resulting in bankfile/PDFS.
9. You can select Enable Encryption if you use a PGP key on the sFTP account level and need the export of this integration to be encrypted.
10. It's best practice to activate the Mark as Exported option where available, for example for bank files, account statements, and general ledger (GL) entries. Then you can exclude the exported data from the menu items in Treasury Management when you save new automation views. This helps ensure your automation views only capture items not yet exported and reduces the risk of duplicate exports. For more information, see Use automation views for custom Treasury outbound integrations.
    Note: For CSV export integrations that do not support the option Mark as Exported, it's best practice to set the option Delta filter to Recent changes. You can do this after you save an integration by using the Edit action from the table. This ensures that only data is exported that was created or updated since the last integration run.
11. Save the integration.

For more information, see Standard Flat File Export Configurations.

After you save an integration, you schedule integration runs from the Integrations data table. To schedule integration runs, use the following steps:

1. Use the pencil icon to open and edit the integration from the data table.
2. In the Edit dialog, activate Enable Scheduler.
3. For Schedule, configure an available setting, for example Every 30 minutes.
4. Save your configuration.

For more information, see Manage Treasury integrations.