Bulk Expected Payment CSV Template Guidance

Expected Payments can be uploaded into Modern Treasury, or updated, in bulk using a CSV.

When you are creating an Expected Payment in Modern Treasury, you can click on the Bulk Expected Payment button then the Download Template CSV link to access the CSV. 

Once this link is clicked, a CSV file will download and columns can be populated based on the below guidance.

• Column A: Internal Account ID
  • Required, will need to be the ID for the account you expect the funds to land in. You can see the list of IDs on the Bulk Expected Page (under the CSV template link).

• Column B: Amount Lower Bound
  • Required, this will reflect the lowest amount this expected payment may be equal to.
    Value in specified currency's smallest unit. e.g. $10 would be represented as 1000.

• Column C: Amount Upper Bound
  • Required, this will reflect the highest amount this expected payment may be equal to.
    Value in specified currency's smallest unit. e.g. $10 would be represented as 1000.
  • Additional data represented as key-value pairs. Both the key and value must be strings.
  • See more info about Metadata here.

• Column D: Direction
  • Required, you will want to specifycredit, debit
    When you are receiving money, use credit.
    When you are being charged, use debit.

• Column E: Type
  • Optional, you will want to specify one of the following: ach, wire, or check.

• Column F: Currency
  • Optional, this will default to the currency of the internal account.

• Column G: Date Lower Bound
  • Optional, this is the earliest date the payment may come in.
    Format: yyyy-mm-dd

• Column H: Date Upper Bound
  • Optional, this is the latest date the payment may come in.
    Format: yyyy-mm-dd

• Column I: Statement Descriptor
  • Optional but useful information to include. This should reflect the statement description you expect to see on the transaction.
    - For ACH payments, this will be the full line item passed from the bank.
    - For wire payments, this will be the OBI field on the wire.
    - For check payments, this will be the memo field.

• Column J: Metadata
  • Optional, Additional data represented as key-value pairs. Must be formatted as "key:value". If you have multiple sets of key-value pairs, you will want to separate with "key:value|key:value"
  • See Metadata for more details.
  • The information you provide in this section is for internal usage. It does not affect how the expected payment is matched.

• Column K: Counterparty ID
  
  • Optional, as this represents the ID of the counterparty you expect is sending this payment.
  • The information you provide in this section is for internal usage. It does not affect how the expected payment is matched.

• Column L: Description
  • Optional, the information you provide in this section is for internal usage. It does not affect how the expected payment is matched.