• New Console Feature: Card Pages Added
  • We’ve enhanced our console experience by introducing Card List and Card Detail Pages, providing better visibility and management of issued cards.

• Signatory Name Now Available for Printed Checks
  • Description:
    • We’ve added the signatory name to the issued checks table, ensuring that customers who print their own checks have all the necessary information. Previously, this data was generated but not stored, making it inaccessible for those needing to print checks independently.
  • What’s New?
    • Signatory Name Field: Now stored on the checks table for easy retrieval.
    • Read-Only API Access: The signatory name is now exposed as a read-only field in the API, allowing users to access it without modification.

• Improved Webhook Delivery for Incoming ACH Updates
  • We have resolved an issue where some customers were not receiving updated webhooks for incoming ACH transactions. As of today, all incoming ACH update events will now correctly trigger webhook notifications. Previously, while the initial create webhook was successfully sent, subsequent update notifications—such as those indicating a return—were not being delivered.
• Improved Error Messaging for Issued Checks
  • We’ve enhanced our API response for issued checks to provide better visibility into error statuses. Now, the API will explicitly indicate when the issue is related to velocity limits, similar to how ACH returns provide actionable retry guidance.
• Support for Other Delivery Methods
  • Description: Within the field delivery_method The below options will be available.
    • USPS_FIRST_CLASS
    • OVERNIGHT
    • TWO_DAY
    • USPS_CERTIFIED
    • Note: USPS is the default selection if not specified otherwise
  • How to enable
    • The above options are not available for all orgs. Please reach out to your bank partner and/or RM for more details

• Several Documentation Updates. Please see the details listed below
  • Additional Check Deposit Status added to the documentation. See Details of the change below

    • Declined Check could not be processed for collection by the bank

      • NOTE: This status is only available at certain bank

  • Additional Key Points about Invoice Account Numbers. See Details below.

    • Dashboard Display: Additional account numbers appear in an “Additional Account Numbers” field on the account detail page

    • Payment Types: Supports both incoming ACHs (debit/credit) and incoming wires

    • Transaction Appearance: Transactions appear like normal payments, with the account number matching the invoice account number in incoming ACH/wire objects

    • Account Nature: These are not separate accounts, but rather additional account numbers linked to an existing ledger account

    • Bank Controls: Banks can only control whether organizations can create invoice accounts using the invoice_account_allowed flag. There are no limits on payment size or number of account numbers

    • Lifecycle: Can remain active indefinitely and can be disabled/re-enabled as needed\
      

• Enhanced Shipping Methods for Issued Checks
  • Description: A new field has been added:delivery_method. Which will allow orgs and users to pick a shipping method.
    • USPS is the default selection if not specified otherwise
    • PRINT (New option)
      • Note: The PRINT option provides check data only; customers must handle check image generation for printing. This endpoint remains provider-agnostic for seamless integration.
  • Check out our Documentation
    • https://docs.treasuryprime.com/reference/post_check

• Search Filtering Added to the NEW Console
  • Description:
    • Users will now see a filter in the search bar upon entering 3 characters or more. This will enable users to quickly find specific data in the console search engine like filtering for accounts, ACHs, Wires, and more.
  • How to Enable:
    • This is automatically enabled for all organizations using “The Console”

Some of you may have noticed a new banner announcing our new console in your old console/dashboard. Please see that message below

• Enhanced 1099-INTs generation (tax documents)
  • Now, customers/fintechs can use the endpoint POST /account/:account_id/tax_document **** to generate 1099s on demand
    • Customers/Fintechs can generate a 1099 via this endpoint as long as a 1099 doesn't already exist for the account. If a 1099 does exist for the account, customers/fintech can either delete the existing 1099 via the PATCH or DELETE endpoint (if the 1099 has not yet been filed). They can also create a corrected 1099 using the is_correction flag (if the 1099 has already been filed).
  • If a change is needed for the tax document, customers/fintechs can use the PATCH /account/:account_id/tax_document/:id to make the necessary update
    • The PATCH endpoint would allow users to update the status of the 1099 under certain conditions. If the status of the 1099 is ready_for_filing the user could PATCH the status to filing to trigger filing of the 1099. We would trigger the filing of the 1099 and return the entry in filing status. We'll update the status to filed once the filing is completed.
  • Additional endpoints DELETE /account/:account_id/tax_document/:id and GET /account/:account_id/tax_document/:id are available for use
    • For DELETE /account/:account_id/tax_document/:id
      • If the 1099's status is pending or ready_for_filing, we'd use this endpoint to allow deletion of the 1099. At this time, the 3rd party provider doesn't allow changes to unfilled 1099s; instead, customers/fintechs will need to delete the 1099s they want to change and create a new one. When this endpoint is used, we'll delete the associated 1099 and set the status to deleted.
    • For GET /account/:account_id/tax_document/:id
      • Similarly, we've added a GET /account/:account_id/tax_document endpoint that returns the 1099s generated for an account.
  • Documentation
    • https://docs.treasuryprime.com/docs/creating-and-filing-a-1099-int

• Enhanced Statement Generation viaPOST /account/:account_id/statement
  • Now, customers can use the endpoint POST /account/:account_id/statement to generate on-demand statements.
  • When used, Treasury Prime generates a statement and provides a URL link for configuration to be filled out.
  • The endpoint does not use a statement_config, instead, it requires all parameters that will be used when generating the statement to be supplied with the request.
    • Parameters that are required for a statement_config are also required when generating statements via this endpoint.
  • Automatic monthly statements (bulk on the 2nd of the month) will remain available for those not using this feature
• Documentation
  • https://docs.treasuryprime.com/reference/post_account-account-id-statement

• Update to the [Account] Endpoint
  • Now the [Account] endpoint can provide a list of Daily Balances along with the average balance
  • Documentation:
    • https://docs.treasuryprime.com/reference/get_account-id-daily-balance