Custom Treasury Exports

Configure custom Treasury export integrations based on Automation Views or Automation Users in Treasury Management. You can also configure custom file names for exported files, including files in exported ZIP folders.

Custom export integrations for Treasury business objects from Coupa Core

For all objects in the new Treasury Management interface, you can configure custom Treasury export integrations for Treasury business objects that are based on automation views, which you configure from the respective menu items in the application. For example, Cash Flows is supported, while Netting Items Classic is not. When you create an integration in Core, the Automation View field is only visible if this feature is supported for the selected object. For more information, see Custom exports for new Treasury interface: Automation Views.

You can also use custom Treasury export integrations for some classic Treasury business objects. These exports leverage the default Custom Page Views (CPVs) for your automation users to run automated Classic Statement Export and Classic Table Export integrations for menu items in the classic interface. For more information, see Custom exports for classic Treasury business objects: Automation User.

For general guidelines for setting up all Treasury export integrations, see Exports.

Tip: When you create a new integration, it's a good idea to use the name of the Treasury menu item for the integration. You can also add that it is a custom view, for example. This makes it easier to search for custom integrations after you create them. From the Integrations table, you can then set the View filter to All and search for the name of the custom integration you want to edit, for example Settlements, Cash Flows, or just Custom.

Custom exports for objects from new Treasury interface: Automation Views

Figure 1.
Create Integration window for custom Treasury integration for Account Statements

Use self-service to create or edit outbound Treasury integrations based on Automation Views in Treasury Management. To create and configure custom exports, 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 integration. When you edit an existing integration, some of the following fields are disabled and cannot be changed unless you create a new integration.
  3. For Integration Type, 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, you must request a Statement of Work (SOW) from Coupa to customize the integration. However, you can use self-service to configure automated Classic Statement Export and Classic Table Export integrations for some menu items in the classic interface. For more information, see Custom exports for classic Treasury business objects using Automation User.
  6. Select a defined view from the Automation View field. This defines the filter parameters for your custom integration.
  7. Code is auto-generated after you create and save the integration.
  8. 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.
  9. sFTP Account: Select one of the Treasury sFTP accounts you have configured from Coupa Core. You can also select Enable Encryption if you use a PGP key on the sFTP account level and need the export of this integration to be encrypted. For more information, see Set up sFTP accounts for Treasury integrations.
  10. 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.
  11. 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: 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.
  12. Mark as Exported: It's best practice to activate this 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.
  13. File Naming Mode is optional:
    1. Custom lets you add naming tokens and free text for your exported files rather than using default Coupa naming conventions. The available tokens vary based on the specific CSV or original file export. If you do not enter a value, Coupa's standard naming convention is applied to the export files. For more information, see Custom File Naming for Treasury Exports.

    2. Standard applies the default Coupa naming convention to files. For more information, see Available Standard Exports.

  14. Save the integration.

After you save the custom integration, you can enable and configure the Scheduler for your Treasury integration runs. For more information, see Schedule Treasury integration runs.

Custom exports for classic Treasury business objects: Automation User

Figure 2.

You can configure Classic Statement Export and Classic Table Export integrations based on the classic interface. You must have at least one automation user designated in Treasury Management. The custom integrations you configure in Coupa Core then run under this user. For more information, see Designate Automation Users.

Note: Not all CSV settings from the classic menu items in the application may be supported in the export files for the custom integrations, since they are based on the settings for the Automation User in Treasury Management.

To create or configure custom outbound integrations for Classic Statement Export and Classic Table Export objects, 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 Type, select Classic statement export or Classic table export.
  4. For Direction, only From Coupa is available.
  5. For Business Object, select the name of the classic Treasury object.
  6. Select a Treasury automation user from the User field. This defines the filter parameters for your custom integration.
  7. Code is auto-generated after you create and save the integration.
  8. 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.
  9. sFTP Account: Select one of the Treasury sFTP accounts you have configured from Coupa Core. You can also select Enable Encryption if you use a PGP key on the sFTP account level and need the export of this integration to be encrypted. For more information, see Set up sFTP accounts for Treasury integrations
  10. 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: 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.
  11. Save the integration.

After you save the custom integration, you can enable and configure the Scheduler for your Treasury integration runs. For more information, see Schedule Treasury integration runs.