We added multi-factor authentication for non-SSO users and are working on new changes that include reduced latency and security improvements.

Recently Released

🧑‍💻 Platform

(Released 3/24) Multi-Factor Authentication for non-SSO users: To encourage security best practices and help protect data stored in a customer's organization, we have released tooling to make it easy for admins to migrate all non-SSO users to multi-factor authentication. If you do not use SSO or MFA for your organization, please speak to your company admin so they can schedule this migration; details on migration tooling can be found here. This migration is critical to maintaining our excellent security posture; more details can be found in our new journal article.

Upcoming Changes

⭐️ indicates newly introduced upcoming changes

🧑‍💻 Platform

Faster Search: We are releasing broad improvements to search performance in parts of the app.

Updates to Java and Kotlin SDKs: There is an upcoming change in our Java/Kotlin API that will be part of a new version release. In this update, we will be replacing an external library (Guava) with a custom solution for handling query parameters and headers. What this means for users:

• Reduced JAR Size: This change reduces the size of the SDK.
• Opt-In Update: Since this is a version change, users will have the option to upgrade at their own pace. The new version will give users access to the improvements, but it won’t affect users who don't choose to move to it.
• Minimal Impact: There may be a small adjustment required for users who have been working directly with raw headers or query parameters.

Optimized High-Volume Payments: Our systems will be optimized to significantly increase the processing speed for large volumes of ACH payments to JPMC.

Saved Filters: Users will be able to save complex filter combinations for recurring workflows, simplifying navigation back to specific views.

Export Permissions Update: Going forward, users will only have access to exports when they are the creator of the export or when they are assigned access to the report from which the export was created.

Dashboard Clean-Up: Redundant "Status Change" information will be removed from the dashboard, which appears in timeline views for various objects. Similar information can be found in "Events," which are in dashboard views, or retrieved via API and webhooks. Status changes will first be removed for Expected Payments and Payment Orders in November, with additional objects to follow in early 2025. Please contact Support if you have questions or concerns.

💵 Payments

⭐️ Simplified Views and Reduced Latency: Modern Treasury is making changes to some dashboard pages to improve our in-app experience; please contact support if you have any questions.

• We will be removing the Reconciliation Overview page; information on that page will be on the Cash Management page going forward.
• We will no longer surface metrics regarding inflows and outflows of cash. This information can still be found under Cash Management → Analytics.
• Nested accounts will be accessible as a filter in Cash Management → Accounts.

⭐️ Security Enhancements to External Accounts: It will no longer be possible to create Payment Orders using External Accounts that are in the Pending Approval state. This ensures that payments aren’t sent to External Accounts that haven’t been approved. This change will apply to External Account creation and updates.

Payment Templates: Customers will be able to configure Templates for Payment Orders. Templates allow finance and treasury teams to standardize how payment orders are created by defining preset values, required fields, and locked settings. This structure reduces manual errors, ensures compliance, and makes manual payment processing more efficient.

Increased Importer Speeds for High Volumes: We’re optimizing our system to boost the processing speed of our iso20022, ISO Payment Status, NACHA returns, and BAI2 file importers.

Sunday & Holiday Next Day ACH Processing with JPMC: Next day ACH payments submitted after Friday’s cutoff until 9:50 PM PT on Sunday or during bank holidays will clear by 8:30 AM PT the next business day.

Faster Payments Creation for Larger Volumes: To complement our new Bulk Request API and enhanced file origination performance, we are optimizing our Payment Order creation process. This improvement will significantly increase throughput for high-volume payment creation.

Increased Processing Speed for High Volumes: We’ve optimized our systems to significantly boost the processing speed of large-volume ACH payments across all banks, expanding beyond just JPMC.

Request for Payment (RFP) at PNC: Users will be able to utilize Request for Payment (RFP) on the Real Time Payments (RTP) network at PNC.

Expanded Cross-Border Payment Coverage: We are planning to expand our cross-border payment capabilities at Citi via the Worldlink product and traditional SWIFT wires, adding support for new currencies and countries.

Global Payments Validation: Payment Order fields for cross border payments will automatically be validated against the bank’s requirements for each country and currency. This will notify the user about required fields and the correct format for successful payment completion. For example, this can include Purpose Codes, Tax Identifiers, or Addresses. We will support Global Payments Validations at Bank of America, JP Morgan, and Citi.

Support for Local Payment Methods: We will support local payment methods in India, Japan, and Singapore through Bank of America, further expanding our global reach.

New Bank Integrations: New bank integrations will be added for Regions, Web Bank, and Western Alliance, expanding banking options for users.

✅ Reconciliation

⭐️ Side-by-Side Improvements: Users will get access to a variety of quality of life improvements the /reconcile page, including updates to the account picker, new filter shortcuts for large recon operations, horizontal mode, better visibility for large record count and improved UX.

⭐️ PO-Manual Linking: Users will be able to manually reconcile Transactions to Payment Orders in the MT app when needed.

⭐️ Paper Item Deprecation: Users will no longer see Paper Items in the UI; all related functionality will be transitioned to Incoming Payments of type Check. More details to come; please contact support if you have any questions.

Account Favoriting: Reconciliation and payments customers will be able to favorite internal accounts in the app for faster access during reporting and reconciliation.

Improved Filters on the Overview Page: We will make our overview page more intuitive by introducing global filters across both metrics and internal account details.

New Reconciliation Method Filter on Transactions: Users will be able to filter transaction by reconciliation method (automatic or manual).

In-App Journal Entry Builder: Users will be able to create journal entry exports in-app to export to ERPs. This feature is currently in development with design partners. If interested, reach out to your CSM.

Multi-System Reconciliation in App: We are deploying a new page for users to link Expected Payments and Payment Orders using entity linking in the app. This feature allows users to map payments and payment intents across multiple systems. For more information, read our guide here.

1:Many Reconciliation AI Suggestions: Users will receive suggestions for 1 Transaction to many Expected Payment reconciliation use cases, in addition to 1:1 suggestions that are available today.

Journal Entry Exports: Users will be able to create journal entries in the app to send to ERPs.

Many-to-Many Reconciliation: Users will be able to create rules to automatically reconcile many Transactions to many Expected Payments, enabling reconciliation for more complex payment scenarios.

Faster High-Volume Recon: We will launch system improvements to process reconciliations faster when handling high transaction volume.

📚 Ledgers

⭐️ Saved Reporting Views: Ops users will be able to navigate to a Financial Reporting view that will contain saved views of key operational balances, like MTL Reporting or Outstanding Liability balances. Saved views will be configured as subsets of your Ledger Account Category balances.

Unlinked Ledger Entry Details in Account Recon: When viewing historical account variance in the /reconciliation page, users will be able to see where variance is caused by Ledger Transactions that are not linked to payments. Users will be able to investigate by filtering to unlinked Entries on a given Ledger Account.

Linked Ledgerable Details in UI: When viewing a bank transaction, users will be able to see associated Ledger Transactions in the Related Items details. Users will also be able to see linked Ledger Transaction information on Payment Order and Expected Payment objects.

Historical Ledger Statements: Users will be able to generate statements that show a set of Ledger Account or Category balances for each day over a range of dates, to support MTL and other reporting use cases.

More Scalable LACs: Ledger Account Categories will support containing up to 10M Ledger Accounts and up to 7 levels of nesting.

Improved Account Recon View Performance: We will improve performance of the /reconcile page for organizations with large numbers of Expected Payments and Ledger Transactions.

Faster Ledger Queries: Performance improvements will enable faster querying of Ledger Account Category balances; categories with millions of accounts can be fetched in under 200ms.

Filter Enhancements: Users will be able to filter the Ledger Accounts page to view only accounts with nonzero posted balances. We will also fix an issue causing these filters to time out for some users.

Dashboard Design Update: We will update the design of filters and other pages in the dashboard for a cleaner, more intuitive experience.

Unledgered Amount Display: Users will be able to view the Unledgered Amount next to each bank transaction, showing any amount not yet recorded to the ledger.

Preset Payment Amounts: When ledgering a payment from the dashboard, the amount for both credit and debit entries will be preset to the payment amount.

Settlement ID Filter: Users will be able to filter Ledger Transactions in the dashboard by Settlement ID.

Currency Filter Fix: We will fix an issue on the Ledger Account page where a currency filter is ignored in search.

Dropdown Display Fix: We will fix an issue in which the Ledger Account Category dropdown persists on the screen when creating a Ledger Account.

Actions Button Fix: We will fix an issue where users can't access the actions button on Ledger Transactions table rows.

This cycle we made improvements to our ledgers tables and continued to work on upcoming features, including many-to-many reconciliation and payment templates.

Recently Released

📚 Ledgers

(Released 3/10) Balance Sorting on Ledger Accounts UI: Customers can sort the Ledger Accounts table in ascending or descending order based on their Pending, Posted, or Available balances.

Upcoming Changes

🧑‍💻 Platform

Multi-Factor Authentication for non-SSO users: In order to encourage security best practices and help protect data stored in a customer's organization, we will allow admins to migrate all non-SSO users to multi-factor authentication. Tooling to support the migration will be provided. Details on timelines will be shared in the coming weeks.

Faster Search: We are releasing broad improvements to search performance in parts of the app.

Updates to Java and Kotlin SDKs: There is an upcoming change in our Java/Kotlin API that will be part of a new version release. In this update, we will be replacing an external library (Guava) with a custom solution for handling query parameters and headers. What this means for users:

• Reduced JAR Size: This change reduces the size of the SDK.
• Opt-In Update: Since this is a version change, users will have the option to upgrade at their own pace. The new version will give users access to the improvements, but it won’t affect users who don't choose to move to it.
• Minimal Impact: There may be a small adjustment required for users who have been working directly with raw headers or query parameters.

Optimized High-Volume Payments: Our systems will be optimized to significantly increase the processing speed for large volumes of ACH payments to JPMC.

Saved Filters: Users will be able to save complex filter combinations for recurring workflows, simplifying navigation back to specific views.

Export Permissions Update: Going forward, users will only have access to exports when they are the creator of the export or when they are assigned access to the report from which the export was created.

Dashboard Clean-Up: Redundant "Status Change" information will be removed from the dashboard, which appears in timeline views for various objects. Similar information can be found in "Events," which are in dashboard views, or retrieved via API and webhooks. Status changes will first be removed for Expected Payments and Payment Orders in November, with additional objects to follow in early 2025. Please contact Support if you have questions or concerns.

💵 Payments

Payment Templates: Customers will be able to configure Templates for Payment Orders. Templates allow finance and treasury teams to standardize how payment orders are created by defining preset values, required fields, and locked settings. This structure reduces manual errors, ensures compliance, and makes manual payment processing more efficient.

Increased Importer Speeds for High Volumes: We’re optimizing our system to boost the processing speed of our iso20022, ISO Payment Status, NACHA returns, and BAI2 file importers.

Sunday & Holiday Next Day ACH Processing with JPMC: Next day ACH payments submitted after Friday’s cutoff until 9:50 PM PT on Sunday or during bank holidays will clear by 8:30 AM PT the next business day.

Faster Payments Creation for Larger Volumes: To complement our new Bulk Request API and enhanced file origination performance, we are optimizing our Payment Order creation process. This improvement will significantly increase throughput for high-volume payment creation.

Increased Processing Speed for High Volumes: We’ve optimized our systems to significantly boost the processing speed of large-volume ACH payments across all banks, expanding beyond just JPMC.

Request for Payment (RFP) at PNC: Users will be able to utilize Request for Payment (RFP) on the Real Time Payments (RTP) network at PNC.

Expanded Cross-Border Payment Coverage: We are planning to expand our cross-border payment capabilities at Citi via the Worldlink product and traditional SWIFT wires, adding support for new currencies and countries.

Global Payments Validation: Payment Order fields for cross border payments will automatically be validated against the bank’s requirements for each country and currency. This will notify the user about required fields and the correct format for successful payment completion. For example, this can include Purpose Codes, Tax Identifiers, or Addresses. We will support Global Payments Validations at Bank of America, JP Morgan, and Citi.

Support for Local Payment Methods: We will support local payment methods in India, Japan, and Singapore through Bank of America, further expanding our global reach.

New Bank Integrations: New bank integrations will be added for Regions, Web Bank, and Western Alliance, expanding banking options for users.

✅ Reconciliation

Account Favoriting: Reconciliation and payments customers will be able to favorite internal accounts in the app for faster access during reporting and reconciliation.

Improved Filters on the Overview Page: We will make our overview page more intuitive by introducing global filters across both metrics and internal account details.

New Reconciliation Method Filter on Transactions: Users will be able to filter transaction by reconciliation method (automatic or manual).

In-App Journal Entry Builder: Users will be able to create journal entry exports in-app to export to ERPs. This feature is currently in development with design partners. If interested, reach out to your CSM.

Multi-System Reconciliation in App: We are deploying a new page for users to link Expected Payments and Payment Orders using entity linking in the app. This feature allows users to map payments and payment intents across multiple systems. For more information, read our guide here.

1:Many Reconciliation AI Suggestions: Users will receive suggestions for 1 Transaction to many Expected Payment reconciliation use cases, in addition to 1:1 suggestions that are available today.

Journal Entry Exports: Users will be able to create journal entries in the app to send to ERPs.

Many-to-Many Reconciliation: Users will be able to create rules to automatically reconcile many Transactions to many Expected Payments, enabling reconciliation for more complex payment scenarios.

Faster High-Volume Recon: We will launch system improvements to process reconciliations faster when handling high transaction volume.

📚 Ledgers

Unlinked Ledger Entry Details in Account Recon: When viewing historical account variance in the /reconciliation page, users will be able to see where variance is caused by Ledger Transactions that are not linked to payments. Users will be able to investigate by filtering to unlinked Entries on a given Ledger Account.

Linked Ledgerable Details in UI: When viewing a bank transaction, users will be able to see associated Ledger Transactions in the Related Items details. Users will also be able to see linked Ledger Transaction information on Payment Order and Expected Payment objects.

Historical Ledger Statements: Users will be able to generate statements that show a set of Ledger Account or Category balances for each day over a range of dates, to support MTL and other reporting use cases.

More Scalable LACs: Ledger Account Categories will support containing up to 10M Ledger Accounts and up to 7 levels of nesting.

Improved Account Recon View Performance: We will improve performance of the /reconcile page for organizations with large numbers of Expected Payments and Ledger Transactions.

Faster Ledger Queries: Performance improvements will enable faster querying of Ledger Account Category balances; categories with millions of accounts can be fetched in under 200ms.

Filter Enhancements: Users will be able to filter the Ledger Accounts page to view only accounts with nonzero posted balances. We will also fix an issue causing these filters to time out for some users.

Dashboard Design Update: We will update the design of filters and other pages in the dashboard for a cleaner, more intuitive experience.

Unledgered Amount Display: Users will be able to view the Unledgered Amount next to each bank transaction, showing any amount not yet recorded to the ledger.

Preset Payment Amounts: When ledgering a payment from the dashboard, the amount for both credit and debit entries will be preset to the payment amount.

Settlement ID Filter: Users will be able to filter Ledger Transactions in the dashboard by Settlement ID.

Currency Filter Fix: We will fix an issue on the Ledger Account page where a currency filter is ignored in search.

Dropdown Display Fix: We will fix an issue in which the Ledger Account Category dropdown persists on the screen when creating a Ledger Account.

Actions Button Fix: We will fix an issue where users can't access the actions button on Ledger Transactions table rows.

We released updated logic for transaction types and are continuing to make progress on upcoming features, including payment templates, to streamline your workflow.

Recently Released

🧑‍💻 Platform

(Released 2/6) Updated Logic for Transaction Types: We released updated logic for how we define the type field in our transaction object. This change will lead to greater accuracy as we support additional payment rails and geographies.

• Transaction type will now be inferred using an updated mapping between vendor codes, bank and currency;
• Upon reconciliation, transactions will now inherit the type of their reconciled payment order;
• Historical transaction records will be updated under this new logic. This will affect transactions available via UI, API and push to warehouse.

Payment Order Type and Expected Payment Type are unaffected. Additional documentation on this change can be found here. Please reach out to the support team if you have any concerns or questions.

Upcoming Changes

⭐️ indicates newly introduced upcoming changes

🧑‍💻 Platform

Multi-Factor Authentication for non-SSO users: In order to encourage security best practices and help protect data stored in a customer's organization, we will allow admins to migrate all non-SSO users to multi-factor authentication. Tooling to support the migration will be provided. Details on timelines will be shared in the coming weeks.

Faster Search: We are releasing broad improvements to search performance in parts of the app.

Updates to Java and Kotlin SDKs: There is an upcoming change in our Java/Kotlin API that will be part of a new version release. In this update, we will be replacing an external library (Guava) with a custom solution for handling query parameters and headers. What this means for users:

• Reduced JAR Size: This change reduces the size of the SDK.
• Opt-In Update: Since this is a version change, users will have the option to upgrade at their own pace. The new version will give users access to the improvements, but it won’t affect users who don't choose to move to it.
• Minimal Impact: There may be a small adjustment required for users who have been working directly with raw headers or query parameters.

Optimized High-Volume Payments: Our systems will be optimized to significantly increase the processing speed for large volumes of ACH payments to JPMC.

Saved Filters: Users will be able to save complex filter combinations for recurring workflows, simplifying navigation back to specific views.

Export Permissions Update: Going forward, users will only have access to exports when they are the creator of the export or when they are assigned access to the report from which the export was created.

Dashboard Clean-Up: Redundant "Status Change" information will be removed from the dashboard, which appears in timeline views for various objects. Similar information can be found in "Events," which are in dashboard views, or retrieved via API and webhooks. Status changes will first be removed for Expected Payments and Payment Orders in November, with additional objects to follow in early 2025. Please contact Support if you have questions or concerns.

💵 Payments

⭐️ Payment Templates: Customers will be able to configure Templates for Payment Orders. Templates allow finance and treasury teams to standardize how payment orders are created by defining preset values, required fields, and locked settings. This structure reduces manual errors, ensures compliance, and makes manual payment processing more efficient.

Increased Importer Speeds for High Volumes: We’re optimizing our system to boost the processing speed of our iso20022, ISO Payment Status, NACHA returns, and BAI2 file importers.

Sunday & Holiday Next Day ACH Processing with JPMC: Next day ACH payments submitted after Friday’s cutoff until 9:50 PM PT on Sunday or during bank holidays will clear by 8:30 AM PT the next business day.

Faster Payments Creation for Larger Volumes: To complement our new Bulk Request API and enhanced file origination performance, we are optimizing our Payment Order creation process. This improvement will significantly increase throughput for high-volume payment creation.

Increased Processing Speed for High Volumes: We’ve optimized our systems to significantly boost the processing speed of large-volume ACH payments across all banks, expanding beyond just JPMC.

Request for Payment (RFP) at PNC: Users will be able to utilize Request for Payment (RFP) on the Real Time Payments (RTP) network at PNC.

Expanded Cross-Border Payment Coverage: We are planning to expand our cross-border payment capabilities at Citi via the Worldlink product and traditional SWIFT wires, adding support for new currencies and countries.

Global Payments Validation: Payment Order fields for cross border payments will automatically be validated against the bank’s requirements for each country and currency. This will notify the user about required fields and the correct format for successful payment completion. For example, this can include Purpose Codes, Tax Identifiers, or Addresses. We will support Global Payments Validations at Bank of America, JP Morgan, and Citi.

Support for Local Payment Methods: We will support local payment methods in India, Japan, and Singapore through Bank of America, further expanding our global reach.

New Bank Integrations: New bank integrations will be added for Regions, Web Bank, and Western Alliance, expanding banking options for users.

✅ Reconciliation

Account Favoriting: Reconciliation and payments customers will be able to favorite internal accounts in the app for faster access during reporting and reconciliation.

Improved Filters on the Overview Page: We will make our overview page more intuitive by introducing global filters across both metrics and internal account details.

New Reconciliation Method Filter on Transactions: Users will be able to filter transaction by reconciliation method (automatic or manual).

In-App Journal Entry Builder: Users will be able to create journal entry exports in-app to export to ERPs. This feature is currently in development with design partners. If interested, reach out to your CSM.

Multi-System Reconciliation in App: We are deploying a new page for users to link Expected Payments and Payment Orders using entity linking in the app. This feature allows users to map payments and payment intents across multiple systems. For more information, read our guide here.

1:Many Reconciliation AI Suggestions: Users will receive suggestions for 1 Transaction to many Expected Payment reconciliation use cases, in addition to 1:1 suggestions that are available today.

Journal Entry Exports: Users will be able to create journal entries in the app to send to ERPs.

Many-to-Many Reconciliation: Users will be able to create rules to automatically reconcile many Transactions to many Expected Payments, enabling reconciliation for more complex payment scenarios.

Faster High-Volume Recon: We will launch system improvements to process reconciliations faster when handling high transaction volume.

📚 Ledgers

Unlinked Ledger Entry Details in Account Recon: When viewing historical account variance in the /reconciliation page, users will be able to see where variance is caused by Ledger Transactions that are not linked to payments. Users will be able to investigate by filtering to unlinked Entries on a given Ledger Account.

Linked Ledgerable Details in UI: When viewing a bank transaction, users will be able to see associated Ledger Transactions in the Related Items details. Users will also be able to see linked Ledger Transaction information on Payment Order and Expected Payment objects.

Historical Ledger Statements: Users will be able to generate statements that show a set of Ledger Account or Category balances for each day over a range of dates, to support MTL and other reporting use cases.

More Scalable LACs: Ledger Account Categories will support containing up to 10M Ledger Accounts and up to 7 levels of nesting.

Improved Account Recon View Performance: We will improve performance of the /reconcile page for organizations with large numbers of Expected Payments and Ledger Transactions.

Faster Ledger Queries: Performance improvements will enable faster querying of Ledger Account Category balances; categories with millions of accounts can be fetched in under 200ms.

Filter Enhancements: Users will be able to filter the Ledger Accounts page to view only accounts with nonzero posted balances. We will also fix an issue causing these filters to time out for some users.

Dashboard Design Update: We will update the design of filters and other pages in the dashboard for a cleaner, more intuitive experience.

Unledgered Amount Display: Users will be able to view the Unledgered Amount next to each bank transaction, showing any amount not yet recorded to the ledger.

Preset Payment Amounts: When ledgering a payment from the dashboard, the amount for both credit and debit entries will be preset to the payment amount.

Settlement ID Filter: Users will be able to filter Ledger Transactions in the dashboard by Settlement ID.

Currency Filter Fix: We will fix an issue on the Ledger Account page where a currency filter is ignored in search.

Dropdown Display Fix: We will fix an issue in which the Ledger Account Category dropdown persists on the screen when creating a Ledger Account.

Actions Button Fix: We will fix an issue where users can't access the actions button on Ledger Transactions table rows.

This cycle we released internal account linking for ledgers and improved validations on the reconciliation side-by-side tool. We have quite a few new upcoming features in the works, including expansions to MFA login, improvements to file importer speed for payments, and UI improvements for reconciliation tools.

Recently Released

📚 Ledgers

Link Internal Account to Ledger Account: Users can link their internal accounts with ledger accounts in order to perform Account Recon and compare balances.

Edit Ledger Accounts in UI: Users can now update Ledger Accounts in the dashboard.

✅ Reconciliation

Tentatively Reconciled Event Documentation: We released updated documentation on how tentatively reconciled events work at MT..

Improved Validations on the Side-by-Side: Users now receive streamlined error messages for invalid reconciliation states in the side-by-side.

Upcoming Changes

⭐️ indicates newly introduced upcoming changes

🧑‍💻 Platform

⭐️ Multi-Factor Authentication for non-SSO users: In order to encourage security best practices and help protect data stored in a customer's organization, we will allow admins to migrate all non-SSO users to multi-factor authentication. Tooling to support the migration will be provided. Details on timelines will be shared in the coming weeks.

⭐️ Updated Logic for Transaction Types: On 2/6 Modern Treasury will release updated logic for how we define the type field in our transaction object. This change will lead to greater accuracy as we support additional payment rails and geographies.

• Transaction type will now be inferred using an updated mapping between vendor codes, bank and currency;
• Upon reconciliation, transactions will now inherit the type of their reconciled payment order;
• Historical transaction records will be updated under this new logic. This will affect transactions available via UI, API and push to warehouse.

Payment Order Type and Expected Payment Type are unaffected. Additional documentation on this change can be found here. Please reach out to the support team if you have any concerns or questions.

⭐️ Faster Search: We are releasing broad improvements to search performance in parts of the app.

Updates to Java and Kotlin SDKs: There is an upcoming change in our Java/Kotlin API that will be part of a new version release. In this update, we will be replacing an external library (Guava) with a custom solution for handling query parameters and headers. What this means for users:

• Reduced JAR Size: This change reduces the size of the SDK.
• Opt-In Update: Since this is a version change, users will have the option to upgrade at their own pace. The new version will give users access to the improvements, but it won’t affect users who don't choose to move to it.
• Minimal Impact: There may be a small adjustment required for users who have been working directly with raw headers or query parameters.

Optimized High-Volume Payments: Our systems will be optimized to significantly increase the processing speed for large volumes of ACH payments to JPMC.

Saved Filters: Users will be able to save complex filter combinations for recurring workflows, simplifying navigation back to specific views.

Export Permissions Update: Going forward, users will only have access to exports when they are the creator of the export or when they are assigned access to the report from which the export was created.

Dashboard Clean-Up: Redundant "Status Change" information will be removed from the dashboard, which appears in timeline views for various objects. Similar information can be found in "Events," which are in dashboard views, or retrieved via API and webhooks. Status changes will first be removed for Expected Payments and Payment Orders in November, with additional objects to follow in early 2025. Please contact Support if you have questions or concerns.

💵 Payments

⭐️ Increased Importer Speeds for High Volumes: We’re optimizing our system to boost the processing speed of our iso20022, ISO Payment Status, NACHA returns, and BAI2 file importers.

Sunday & Holiday Next Day ACH Processing with JPMC: Next day ACH payments submitted after Friday’s cutoff until 9:50 PM PT on Sunday or during bank holidays will clear by 8:30 AM PT the next business day.

Faster Payments Creation for Larger Volumes: To complement our new Bulk Request API and enhanced file origination performance, we are optimizing our Payment Order creation process. This improvement will significantly increase throughput for high-volume payment creation.

Increased Processing Speed for High Volumes: We’ve optimized our systems to significantly boost the processing speed of large-volume ACH payments across all banks, expanding beyond just JPMC.

Custom Payment Order Templates: Users will be able to create custom templates for different Payment Order use cases to make it easier to initiate payments. Users will be able to control which fields on the Payment Order form are visible, required, optional, and preset. Contact our team to schedule a demo.

Request for Payment (RFP) at PNC: Users will be able to utilize Request for Payment (RFP) on the Real Time Payments (RTP) network at PNC.

Expanded Cross-Border Payment Coverage: We are planning to expand our cross-border payment capabilities at Citi via the Worldlink product and traditional SWIFT wires, adding support for new currencies and countries.

Global Payments Validation: Payment Order fields for cross border payments will automatically be validated against the bank’s requirements for each country and currency. This will notify the user about required fields and the correct format for successful payment completion. For example, this can include Purpose Codes, Tax Identifiers, or Addresses. We will support Global Payments Validations at Bank of America, JP Morgan, and Citi.

Support for Local Payment Methods: We will support local payment methods in India, Japan, and Singapore through Bank of America, further expanding our global reach.

New Bank Integrations: New bank integrations will be added for Regions, Web Bank, and Western Alliance, expanding banking options for users.

✅ Reconciliation

⭐️ Account Favoriting: Reconciliation and payments customers will be able to favorite internal accounts in the app for faster access during reporting and reconciliation.

⭐️ Improved Filters on the Overview Page: We will make our overview page more intuitive by introducing global filters across both metrics and internal account details.

⭐️ New Reconciliation Method Filter on Transactions: Users will be able to filter transaction by reconciliation method (automatic or manual).

⭐️ In-App Journal Entry Builder: Users will be able to create journal entry exports in-app to export to ERPs. This feature is currently in development with design partners. If interested, reach out to your CSM.

⭐️ Multi-System Reconciliation in App: We are deploying a new page for users to link Expected Payments and Payment Orders using entity linking in the app. This feature allows users to map payments and payment intents across multiple systems. For more information, read our guide here.

Audit Trails for Categorization Rules: Users will be able to see versions and history for Transaction categorization rules.

1:Many Reconciliation AI Suggestions: Users will receive suggestions for 1 Transaction to many Expected Payment reconciliation use cases, in addition to 1:1 suggestions that are available today.

Entity Linking Page: Users will be able to create links between Expected Payments and Payment Orders on a single unified page.

Journal Entry Exports: Users will be able to create journal entries in the app to send to ERPs.

Multi-System Reconciliation: Users will be able to define multi-legged payments to automatically reconcile data across multiple systems and financial institutions to confirm success or failure states.

Many-to-Many Reconciliation: Users will be able to create rules to automatically reconcile many Transactions to many Expected Payments, enabling reconciliation for more complex payment scenarios.

Faster High-Volume Recon: We will launch system improvements to process reconciliations faster when handling high transaction volume.

📚 Ledgers

Unlinked Ledger Entry Details in Account Recon: When viewing historical account variance in the /reconciliation page, users will be able to see where variance is caused by Ledger Transactions that are not linked to payments. Users will be able to investigate by filtering to unlinked Entries on a given Ledger Account.

Linked Ledgerable Details in UI: When viewing a bank transaction, users will be able to see associated Ledger Transactions in the Related Items details. Users will also be able to see linked Ledger Transaction information on Payment Order and Expected Payment objects.

Historical Ledger Statements: Users will be able to generate statements that show a set of Ledger Account or Category balances for each day over a range of dates, to support MTL and other reporting use cases.

More Scalable LACs: Ledger Account Categories will support containing up to 10M Ledger Accounts and up to 7 levels of nesting.

Improved Account Recon View Performance: We will improve performance of the /reconcile page for organizations with large numbers of Expected Payments and Ledger Transactions.

Faster Ledger Queries: Performance improvements will enable faster querying of Ledger Account Category balances; categories with millions of accounts can be fetched in under 200ms.

Filter Enhancements: Users will be able to filter the Ledger Accounts page to view only accounts with nonzero posted balances. We will also fix an issue causing these filters to time out for some users.

Dashboard Design Update: We will update the design of filters and other pages in the dashboard for a cleaner, more intuitive experience.

Unledgered Amount Display: Users will be able to view the Unledgered Amount next to each bank transaction, showing any amount not yet recorded to the ledger.

Preset Payment Amounts: When ledgering a payment from the dashboard, the amount for both credit and debit entries will be preset to the payment amount.

Settlement ID Filter: Users will be able to filter Ledger Transactions in the dashboard by Settlement ID.

Currency Filter Fix: We will fix an issue on the Ledger Account page where a currency filter is ignored in search.

Dropdown Display Fix: We will fix an issue in which the Ledger Account Category dropdown persists on the screen when creating a Ledger Account.

Actions Button Fix: We will fix an issue where users can't access the actions button on Ledger Transactions table rows.

Our first Release Notes of 2025 includes updates to file transfer functionality and unreconciled transaction categorization. We also added new upcoming items for reconciliation.

Recently Released

🧑‍💻 Platform

(Released 1/3) File Transfers: File transfers make it easier for customers with systems that output files or work in batches to get data into Modern Treasury by eliminating the need for writing “glue code” to translate data into API calls, which requires engineering resources. Learn more here.

📚 Ledgers

(Released 1/15) Bulk Ledger Account Creation: The bulk requests API now supports the creation of up to 1,000 Ledger Accounts in a single request.

💵 Payments

(Released 1/20) New Event for Originating Return: A return timeline will now include an event for when an originating return is created. This will only be an event; a webhook will not be triggered for this action.

✅ Reconciliation

(Released 12/10) Transaction Categorization for Unreconciled Transactions: Customers will be able to create rules that apply metadata tags when transactions are created in the platform, in addition to when they are reconciled. This will unlock tagging for transactions users don’t need to reconcile, such as bank charges, fees, and interest.

(Released 12/20) Vendor Codes in the UI: We will expose vendor codes for transactions as filters and give users the ability to create reconciliation and categorization rules using vendor codes.

Upcoming Changes

⭐️ indicates newly introduced upcoming changes

🧑‍💻 Platform

Deprecating Old Roles: As part of the RBAC system upgrade old roles that are marked as 'To Be Deprecated' will be removed. Any groups that are still associated with these roles will lose access.

Updates to Java and Kotlin SDKs: There is an upcoming change in our Java/Kotlin API that will be part of a new version release. In this update, we will be replacing an external library (Guava) with a custom solution for handling query parameters and headers. What this means for users:

• Reduced JAR Size: This change reduces the size of the SDK.
• Opt-In Update: Since this is a version change, users will have the option to upgrade at their own pace. The new version will give users access to the improvements, but it won’t affect users who don't choose to move to it.
• Minimal Impact: There may be a small adjustment required for users who have been working directly with raw headers or query parameters.

Optimized High-Volume Payments: Our systems will be optimized to significantly increase the processing speed for large volumes of ACH payments to JPMC.

Saved Filters: Users will be able to save complex filter combinations for recurring workflows, simplifying navigation back to specific views.

Export Permissions Update: Going forward, users will only have access to exports when they are the creator of the export or when they are assigned access to the report from which the export was created.

Dashboard Clean-Up: Redundant "Status Change" information will be removed from the dashboard, which appears in timeline views for various objects. Similar information can be found in "Events," which are in dashboard views, or retrieved via API and webhooks. Status changes will first be removed for Expected Payments and Payment Orders in November, with additional objects to follow in early 2025. Please contact Support if you have questions or concerns.

💵 Payments

Sunday & Holiday Next Day ACH Processing with JPMC: Next day ACH payments submitted after Friday’s cutoff until 9:50 PM PT on Sunday or during bank holidays will clear by 8:30 AM PT the next business day.

Faster Payments Creation for Larger Volumes: To complement our new Bulk Request API and enhanced file origination performance, we are optimizing our Payment Order creation process. This improvement will significantly increase throughput for high-volume payment creation.

Increased Processing Speed for High Volumes: We’ve optimized our systems to significantly boost the processing speed of large-volume ACH payments across all banks, expanding beyond just JPMC.

Custom Payment Order Templates: Users will be able to create custom templates for different Payment Order use cases to make it easier to initiate payments. Users will be able to control which fields on the Payment Order form are visible, required, optional, and preset. Contact our team to schedule a demo.

Request for Payment (RFP) at PNC: Users will be able to utilize Request for Payment (RFP) on the Real Time Payments (RTP) network at PNC.

Expanded Cross-Border Payment Coverage: We are planning to expand our cross-border payment capabilities at Citi via the Worldlink product and traditional SWIFT wires, adding support for new currencies and countries.

Global Payments Validation: Payment Order fields for cross border payments will automatically be validated against the bank’s requirements for each country and currency. This will notify the user about required fields and the correct format for successful payment completion. For example, this can include Purpose Codes, Tax Identifiers, or Addresses. We will support Global Payments Validations at Bank of America, JP Morgan, and Citi.

Support for Local Payment Methods: We will support local payment methods in India, Japan, and Singapore through Bank of America, further expanding our global reach.

New Bank Integrations: New bank integrations will be added for Regions, Web Bank, and Western Alliance, expanding banking options for users.

✅ Reconciliation

⭐️ Audit Trails for Categorization Rules: Users will be able to see versions and history for Transaction categorization rules.

⭐️ 1:Many Reconciliation AI Suggestions: Users will receive suggestions for 1 Transaction to many Expected Payment reconciliation use cases, in addition to 1:1 suggestions that are available today.

⭐️ Entity Linking Page: Users will be able to create links between Expected Payments and Payment Orders on a single unified page.

⭐️ Journal Entry Exports: Users will be able to create journal entries in the app to send to ERPs.

Multi-System Reconciliation: Users will be able to define multi-legged payments to automatically reconcile data across multiple systems and financial institutions to confirm success or failure states.

Many-to-Many Reconciliation: Users will be able to create rules to automatically reconcile many Transactions to many Expected Payments, enabling reconciliation for more complex payment scenarios.

Faster High-Volume Recon: We will launch system improvements to process reconciliations faster when handling high transaction volume.

📚 Ledgers

Unlinked Ledger Entry Details in Account Recon: When viewing historical account variance in the /reconciliation page, users will be able to see where variance is caused by Ledger Transactions that are not linked to payments. Users will be able to investigate by filtering to unlinked Entries on a given Ledger Account.

Linked Ledgerable Details in UI: When viewing a bank transaction, users will be able to see associated Ledger Transactions in the Related Items details. Users will also be able to see linked Ledger Transaction information on Payment Order and Expected Payment objects.

Historical Ledger Statements: Users will be able to generate statements that show a set of Ledger Account or Category balances for each day over a range of dates, to support MTL and other reporting use cases.

More Scalable LACs: Ledger Account Categories will support containing up to 10M Ledger Accounts and up to 7 levels of nesting.

Improved Account Recon View Performance: We will improve performance of the /reconcile page for organizations with large numbers of Expected Payments and Ledger Transactions.

Faster Ledger Queries: Performance improvements will enable faster querying of Ledger Account Category balances; categories with millions of accounts can be fetched in under 200ms.

Filter Enhancements: Users will be able to filter the Ledger Accounts page to view only accounts with nonzero posted balances. We will also fix an issue causing these filters to time out for some users.

Dashboard Design Update: We will update the design of filters and other pages in the dashboard for a cleaner, more intuitive experience.

Unledgered Amount Display: Users will be able to view the Unledgered Amount next to each bank transaction, showing any amount not yet recorded to the ledger.

Preset Payment Amounts: When ledgering a payment from the dashboard, the amount for both credit and debit entries will be preset to the payment amount.

Settlement ID Filter: Users will be able to filter Ledger Transactions in the dashboard by Settlement ID.

Currency Filter Fix: We will fix an issue on the Ledger Account page where a currency filter is ignored in search.

Dropdown Display Fix: We will fix an issue in which the Ledger Account Category dropdown persists on the screen when creating a Ledger Account.

Actions Button Fix: We will fix an issue where users can't access the actions button on Ledger Transactions table rows.

We added transaction IDs to reversal webhook events. We also planned improvements to ACH processing and complex reconciliation scenarios.

Recently Released

💵 Payments

(Released 12/12) Transaction ID in Reversals Webhook: We added transaction IDs to the completed reversals webhook event; reversals.completed response will now contain the associated transaction_id. This will make it easier to reference the reversed transaction.

Upcoming Changes

⭐️ indicates newly introduced upcoming changes

🧑‍💻 Platform

Deprecating Old Roles: As part of the RBAC system upgrade old roles that are marked as 'To Be Deprecated' will be removed. Any groups that are still associated with these roles will lose access.

Updates to Java and Kotlin SDKs: There is an upcoming change in our Java/Kotlin API that will be part of a new version release. In this update, we will be replacing an external library (Guava) with a custom solution for handling query parameters and headers. What this means for users:

• Reduced JAR Size: This change reduces the size of the SDK.
• Opt-In Update: Since this is a version change, users will have the option to upgrade at their own pace. The new version will give users access to the improvements, but it won’t affect users who don't choose to move to it.
• Minimal Impact: There may be a small adjustment required for users who have been working directly with raw headers or query parameters.

File Sharing via SFTP: Users will be able to perform recurring data uploads by sharing files via SFTP. Users will be able to create Payment Orders, Expected Payments, Transactions, and Ledger Transactions.

Optimized High-Volume Payments: Our systems will be optimized to significantly increase the processing speed for large volumes of ACH payments to JPMC.

Cycle Through Approvals: After approving a Payment Order, users will be able to move to the next item without returning to the approval list.

Payment Approvals by Currency: Users will be able to filter payment approvals by currency on the approvals list.

Saved Filters: Users will be able to save complex filter combinations for recurring workflows, simplifying navigation back to specific views.

Export Permissions Update: Going forward, users will only have access to exports when they are the creator of the export or when they are assigned access to the report from which the export was created.

Dashboard Clean-Up: Redundant "Status Change" information will be removed from the dashboard, which appears in timeline views for various objects. Similar information can be found in "Events," which are in dashboard views, or retrieved via API and webhooks. Status changes will first be removed for Expected Payments and Payment Orders in November, with additional objects to follow in early 2025. Please contact Support if you have questions or concerns.

💵 Payments

⭐️ Sunday & Holiday Next Day ACH Processing with JPMC: Next day ACH payments submitted after Friday’s cutoff until 9:50 PM PT on Sunday or during bank holidays will clear by 8:30 AM PT the next business day.

Faster Payments Creation for Larger Volumes: To complement our new Bulk Request API and enhanced file origination performance, we are optimizing our Payment Order creation process. This improvement will significantly increase throughput for high-volume payment creation.

Increased Processing Speed for High Volumes: We’ve optimized our systems to significantly boost the processing speed of large-volume ACH payments across all banks, expanding beyond just JPMC.

Custom Payment Order Templates: Users will be able to create custom templates for different Payment Order use cases to make it easier to initiate payments. Users will be able to control which fields on the Payment Order form are visible, required, optional, and preset. Contact our team to schedule a demo.

Request for Payment (RFP) at PNC: Users will be able to utilize Request for Payment (RFP) on the Real Time Payments (RTP) network at PNC.

Expanded Cross-Border Payment Coverage: We are planning to expand our cross-border payment capabilities at Citi via the Worldlink product and traditional SWIFT wires, adding support for new currencies and countries.

Global Payments Validation: Payment Order fields for cross border payments will automatically be validated against the bank’s requirements for each country and currency. This will notify the user about required fields and the correct format for successful payment completion. For example, this can include Purpose Codes, Tax Identifiers, or Addresses. We will support Global Payments Validations at Bank of America, JP Morgan, and Citi.

Support for Local Payment Methods: We will support local payment methods in India, Japan, and Singapore through Bank of America, further expanding our global reach.

New Bank Integrations: New bank integrations will be added for Regions, Web Bank, and Western Alliance, expanding banking options for users.

✅ Reconciliation

⭐️ Multi-System Reconciliation: Users will be able to define multi-legged payments to automatically reconcile data across multiple systems and financial institutions to confirm success or failure states.

Transaction Categorization for Unreconciled Transactions: Customers will be able to create rules that apply metadata tags when transactions are created in the platform, in addition to when they are reconciled. This will unlock tagging for transactions users don’t need to reconcile, such as bank charges, fees, and interest.

Vendor Codes in the UI: We will expose vendor codes for transactions as filters and give users the ability to create reconciliation and categorization rules using vendor codes.

Expanded Support for Bulk Reconciliation. We will support additional edge cases for many-1 bulk reconciliation in the UI.

Many-to-Many Reconciliation: Users will be able to create rules to automatically reconcile many Transactions to many Expected Payments, enabling reconciliation for more complex payment scenarios.

Faster High-Volume Recon: We will launch system improvements to process reconciliations faster when handling high transaction volume.

📚 Ledgers

Unlinked Ledger Entry Details in Account Recon: When viewing historical account variance in the /reconciliation page, users will be able to see where variance is caused by Ledger Transactions that are not linked to payments. Users will be able to investigate by filtering to unlinked Entries on a given Ledger Account.

Linked Ledgerable Details in UI: When viewing a bank transaction, users will be able to see associated Ledger Transactions in the Related Items details. Users will also be able to see linked Ledger Transaction information on Payment Order and Expected Payment objects.

Historical Ledger Statements: Users will be able to generate statements that show a set of Ledger Account or Category balances for each day over a range of dates, to support MTL and other reporting use cases.

More Scalable LACs: Ledger Account Categories will support containing up to 10M Ledger Accounts and up to 7 levels of nesting.

Improved Account Recon View Performance: We will improve performance of the /reconcile page for organizations with large numbers of Expected Payments and Ledger Transactions.

Faster Ledger Queries: Performance improvements will enable faster querying of Ledger Account Category balances; categories with millions of accounts can be fetched in under 200ms.

Filter Enhancements: Users will be able to filter the Ledger Accounts page to view only accounts with nonzero posted balances. We will also fix an issue causing these filters to time out for some users.

Bulk Ledger Account Creation: The bulk requests API will support the creation of up to 1,000 Ledger Accounts in a single request.

Dashboard Design Update: We will update the design of filters and other pages in the dashboard for a cleaner, more intuitive experience.

Unledgered Amount Display: Users will be able to view the Unledgered Amount next to each bank transaction, showing any amount not yet recorded to the ledger.

Preset Payment Amounts: When ledgering a payment from the dashboard, the amount for both credit and debit entries will be preset to the payment amount.

Settlement ID Filter: Users will be able to filter Ledger Transactions in the dashboard by Settlement ID.

Currency Filter Fix: We will fix an issue on the Ledger Account page where a currency filter is ignored in search.

Dropdown Display Fix: We will fix an issue in which the Ledger Account Category dropdown persists on the screen when creating a Ledger Account.

Actions Button Fix: We will fix an issue where users can't access the actions button on Ledger Transactions table rows.

This cycle we rolled out improvements like enhanced metadata search and real-time payment confirmations. Upcoming updates include transaction categorization for unreconciled transactions, vendor code filters, faster high-volume reconciliations, and more.

Recently Released

✅ Reconciliation

(Released 12/9) Adjust Metadata Search Behavior: Metadata search in the UI can now take on multiple values in a single query.

(Released 12/2) Custom Identifiers in the UI: Users can filter by custom identifier in the UI.

(Released 11/19) CSV Exports in the Side-by-Side View: Users can export CSV files from transactions in the /reconcile page.

(Released 11/19) Exhaustive Drop-Downs for Metadata Search: When searching for metadata in Expected Payments and Transactions, users can now navigate through all of their available keys in the UI.

💵 Payments

(Released 11/27) Real-Time Payment Confirmation: Users can receive real-time confirmation of RTP or FedNow payments at Bank of America, Cross River, JP Morgan, US Bank, and Wells Fargo via the confirmed event in Payment Order webhooks.

(Released 11/27) Create Legal Entities at Cross River Bank: Users can create legal entities at Cross River Bank to ensure compliance with regulatory requirements.

Upcoming Changes

⭐️ indicates newly introduced upcoming changes

🧑‍💻 Platform

Deprecating Old Roles: As part of the RBAC system upgrade old roles that are marked as 'To Be Deprecated' will be removed. Any groups that are still associated with these roles will lose access.

Updates to Java and Kotlin SDKs: There is an upcoming change in our Java/Kotlin API that will be part of a new version release. In this update, we will be replacing an external library (Guava) with a custom solution for handling query parameters and headers. What this means for users:

• Reduced JAR Size: This change reduces the size of the SDK.
• Opt-In Update: Since this is a version change, users will have the option to upgrade at their own pace. The new version will give users access to the improvements, but it won’t affect users who don't choose to move to it.
• Minimal Impact: There may be a small adjustment required for users who have been working directly with raw headers or query parameters.

File Sharing via SFTP: Users will be able to perform recurring data uploads by sharing files via SFTP. Users will be able to create Payment Orders, Expected Payments, Transactions, and Ledger Transactions.

Optimized High-Volume Payments: Our systems will be optimized to significantly increase the processing speed for large volumes of ACH payments to JPMC.

Cycle Through Approvals: After approving a Payment Order, users will be able to move to the next item without returning to the approval list.

Payment Approvals by Currency: Users will be able to filter payment approvals by currency on the approvals list.

Saved Filters: Users will be able to save complex filter combinations for recurring workflows, simplifying navigation back to specific views.

Export Permissions Update: Going forward, users will only have access to exports when they are the creator of the export or when they are assigned access to the report from which the export was created.

Dashboard Clean-Up: Redundant "Status Change" information will be removed from the dashboard, which appears in timeline views for various objects. Similar information can be found in "Events," which are in dashboard views, or retrieved via API and webhooks. Status changes will first be removed for Expected Payments and Payment Orders in November, with additional objects to follow in early 2025. Please contact Support if you have questions or concerns.

💵 Payments

⭐️ Faster Payments Creation for Larger Volumes: To complement our new Bulk Request API and enhanced file origination performance, we are optimizing our Payment Order creation process. This improvement will significantly increase throughput for high-volume payment creation.

Increased Processing Speed for High Volumes: We’ve optimized our systems to significantly boost the processing speed of large-volume ACH payments across all banks, expanding beyond just JPMC.

Custom Payment Order Templates: Users will be able to create custom templates for different Payment Order use cases to make it easier to initiate payments. Users will be able to control which fields on the Payment Order form are visible, required, optional, and preset. Contact our team to schedule a demo.

Request for Payment (RFP) at PNC: Users will be able to utilize Request for Payment (RFP) on the Real Time Payments (RTP) network at PNC.

Expanded Cross-Border Payment Coverage: We are planning to expand our cross-border payment capabilities at Citi via the Worldlink product and traditional SWIFT wires, adding support for new currencies and countries.

Global Payments Validation: Payment Order fields for cross border payments will automatically be validated against the bank’s requirements for each country and currency. This will notify the user about required fields and the correct format for successful payment completion. For example, this can include Purpose Codes, Tax Identifiers, or Addresses. We will support Global Payments Validations at Bank of America, JP Morgan, and Citi.

Support for Local Payment Methods: We will support local payment methods in India, Japan, and Singapore through Bank of America, further expanding our global reach.

New Bank Integrations: New bank integrations will be added for Regions, Web Bank, and Western Alliance, expanding banking options for users.

✅ Reconciliation

⭐️ Transaction Categorization for Unreconciled Transactions: Customers will be able to create rules that apply metadata tags when transactions are created in the platform, in addition to when they are reconciled. This will unlock tagging for transactions users don’t need to reconcile, such as bank charges, fees, and interest.

⭐️ Vendor Codes in the UI: We will expose vendor codes for transactions as filters and give users the ability to create reconciliation and categorization rules using vendor codes.

⭐️ Expanded Support for Bulk Reconciliation. We will support additional edge cases for many-1 bulk reconciliation in the UI.

Many-to-Many Reconciliation: Users will be able to create rules to automatically reconcile many Transactions to many Expected Payments, enabling reconciliation for more complex payment scenarios.

Faster High-Volume Recon: We will launch system improvements to process reconciliations faster when handling high transaction volume.

📚 Ledgers

⭐️ Unlinked Ledger Entry Details in Account Recon: When viewing historical account variance in the /reconciliation page, users will be able to see where variance is caused by Ledger Transactions that are not linked to payments. Users will be able to investigate by filtering to unlinked Entries on a given Ledger Account.

⭐️ Linked Ledgerable Details in UI: When viewing a bank transaction, users will be able to see associated Ledger Transactions in the Related Items details. Users will also be able to see linked Ledger Transaction information on Payment Order and Expected Payment objects.

⭐️ Historical Ledger Statements: Users will be able to generate statements that show a set of Ledger Account or Category balances for each day over a range of dates, to support MTL and other reporting use cases.

⭐️ More Scalable LACs: Ledger Account Categories will support containing up to 10M Ledger Accounts and up to 7 levels of nesting.

⭐️ Improved Account Recon View Performance: We will improve performance of the /reconcile page for organizations with large numbers of Expected Payments and Ledger Transactions.

Faster Ledger Queries: Performance improvements will enable faster querying of Ledger Account Category balances; categories with millions of accounts can be fetched in under 200ms.

Filter Enhancements: Users will be able to filter the Ledger Accounts page to view only accounts with nonzero posted balances. We will also fix an issue causing these filters to time out for some users.

Bulk Ledger Account Creation: The bulk requests API will support the creation of up to 1,000 Ledger Accounts in a single request.

Dashboard Design Update: We will update the design of filters and other pages in the dashboard for a cleaner, more intuitive experience.

Unledgered Amount Display: Users will be able to view the Unledgered Amount next to each bank transaction, showing any amount not yet recorded to the ledger.

Preset Payment Amounts: When ledgering a payment from the dashboard, the amount for both credit and debit entries will be preset to the payment amount.

Settlement ID Filter: Users will be able to filter Ledger Transactions in the dashboard by Settlement ID.

Currency Filter Fix: We will fix an issue on the Ledger Account page where a currency filter is ignored in search.

Dropdown Display Fix: We will fix an issue in which the Ledger Account Category dropdown persists on the screen when creating a Ledger Account.

Actions Button Fix: We will fix an issue where users can't access the actions button on Ledger Transactions table rows.

Recent updates include advanced ledger account settlements and FedNow routing number validation. Looking ahead, we will deprecate old RBAC roles and enhance processing speeds for high-volume ACH payments.

Recently Released

📚 Ledgers

• (Released 11/15) Custom Ledger Account Settlements: Ledger Account Settlements can be used to represent payouts and itemized Ledger Entries. You can now create a Settlement in drafting status and include any group of entries on a Ledger Account, without needing to specify a settlement time period.
• (Released 11/15) Redrafted Payment Order Ledgering: When a Payment Order is redrafted, it is is automatically linked to a new Ledger Transaction that retains the description and metadata from the original transaction.
• (Released 11/14) Ledger Timestamp in Dashboard: When creating a Ledger Transaction in the dashboard, users can now set an effective_at timestamp.
• (Released 11/18) Editing Embedded Ledger Transactions: Users can now edit the associated Ledger Transaction directly when modifying a Payment Order or Expected Payment in the dashboard.

💵 Payments

• (Released 11/19) FedNow Routing Number Eligibility Check: We have added support for FedNow to our routing number eligibility API. This API validates whether a counterparty can receive a particular payment type. If a counterparty has the ability to receive a FedNow payment, we will return fednow on the supported_payment_types field. We separated fednow into its own type in the eligibility API because an originating bank may only support one network. This distinction helps users determine whether their counterparty can receive payments via a specific network and decide whether to proceed with the payment. While Modern Treasury identifies network eligibility, it’s important to note that most banks do not allow customers to explicitly select a specific instant payment network. Instead, banks route the payment automatically between FedNow and RTP based on factors like cost and availability. As a result, the Payment Order API only accepts rtp as the value for the payment_type parameter when creating an instant payment. If a routing number’s supported_payment_types includes either fednow or rtp, users can initiate an instant payment by creating a Payment Order with payment_type set to rtp. This ensures that the bank will determine the appropriate network to use based on their routing logic.

Upcoming Changes

⭐️ indicates newly introduced upcoming changes

🧑‍💻 Platform

⭐️ Deprecating Old Roles: As part of the RBAC system upgrade old roles that are marked as 'To Be Deprecated' will be removed. Any groups that are still associated with these roles will lose access.

Updates to Java and Kotlin SDKs: There is an upcoming change in our Java/Kotlin API that will be part of a new version release. In this update, we will be replacing an external library (Guava) with a custom solution for handling query parameters and headers. What this means for users:

• Reduced JAR Size: This change reduces the size of the SDK.
• Opt-In Update: Since this is a version change, users will have the option to upgrade at their own pace. The new version will give users access to the improvements, but it won’t affect users who don't choose to move to it.
• Minimal Impact: There may be a small adjustment required for users who have been working directly with raw headers or query parameters.

File Sharing via SFTP: Users will be able to perform recurring data uploads by sharing files via SFTP. Users will be able to create Payment Orders, Expected Payments, Transactions, and Ledger Transactions.

Optimized High-Volume Payments: Our systems will be optimized to significantly increase the processing speed for large volumes of ACH payments to JPMC.

Cycle Through Approvals: After approving a Payment Order, users will be able to move to the next item without returning to the approval list.

Payment Approvals by Currency: Users will be able to filter payment approvals by currency on the approvals list.

Saved Filters: Users will be able to save complex filter combinations for recurring workflows, simplifying navigation back to specific views.

Export Permissions Update: Going forward, users will only have access to exports when they are the creator of the export or when they are assigned access to the report from which the export was created.

Dashboard Clean-Up: Redundant "Status Change" information will be removed from the dashboard, which appears in timeline views for various objects. Similar information can be found in "Events," which are in dashboard views, or retrieved via API and webhooks. Status changes will first be removed for Expected Payments and Payment Orders in November, with additional objects to follow in early 2025. Please contact Support if you have questions or concerns.

Adjust Metadata Search Behavior: Metadata search in the UI will be case insensitive and take in multiple values in a single query.

💵 Payments

⭐️ Increased Processing Speed for High Volumes: We’ve optimized our systems to significantly boost the processing speed of large-volume ACH payments across all banks, expanding beyond just JPMC.

Custom Payment Order Templates: Users will be able to create custom templates for different Payment Order use cases to make it easier to initiate payments. Users will be able to control which fields on the Payment Order form are visible, required, optional, and preset. Contact our team to schedule a demo.

Real-Time Payment Confirmation: Users will be able to receive real-time confirmation of RTP or FedNow payments at Bank of America, Cross River, JP Morgan, US Bank, and Wells Fargo via the confirmed event in Payment Order webhooks.

Request for Payment (RFP) at PNC: Users will be able to utilize Request for Payment (RFP) on the Real Time Payments (RTP) network at PNC.

Expanded Cross-Border Payment Coverage: We are planning to expand our cross-border payment capabilities at Citi via the Worldlink product and traditional SWIFT wires, adding support for new currencies and countries.

Global Payments Validation: Payment Order fields for cross border payments will automatically be validated against the bank’s requirements for each country and currency. This will notify the user about required fields and the correct format for successful payment completion. For example, this can include Purpose Codes, Tax Identifiers, or Addresses. We will support Global Payments Validations at Bank of America, JP Morgan, and Citi.

Support for Local Payment Methods: We will support local payment methods in India, Japan, and Singapore through Bank of America, further expanding our global reach.

New Bank Integrations: New bank integrations will be added for Regions, Web Bank, and Western Alliance, expanding banking options for users.

Create Legal Entities at Cross River Bank: Users will be able to create legal entities at Cross River Bank to ensure compliance with regulatory requirements.

✅ Reconciliation

Many-to-Many Reconciliation: Users will be able to create rules to automatically reconcile many Transactions to many Expected Payments, enabling reconciliation for more complex payment scenarios.

Faster High-Volume Recon: We will launch system improvements to process reconciliations faster when handling high transaction volume.

Custom Identifier Filters: Users will be able to find, search and filter on Expected Payment Custom Identifiers in the Reconciliation UI.

📚 Ledgers

Faster Ledger Queries: Performance improvements will enable faster querying of Ledger Account Category balances; categories with millions of accounts can be fetched in under 200ms.

Filter Enhancements: Users will be able to filter the Ledger Accounts page to view only accounts with nonzero posted balances. We will also fix an issue causing these filters to time out for some users.

Bulk Ledger Account Creation: The bulk requests API will support the creation of up to 1,000 Ledger Accounts in a single request.

Dashboard Design Update: We will update the design of filters and other pages in the dashboard for a cleaner, more intuitive experience.

Unledgered Amount Display: Users will be able to view the Unledgered Amount next to each bank transaction, showing any amount not yet recorded to the ledger.

Preset Payment Amounts: When ledgering a payment from the dashboard, the amount for both credit and debit entries will be preset to the payment amount.

Settlement ID Filter: Users will be able to filter Ledger Transactions in the dashboard by Settlement ID.

Currency Filter Fix: We will fix an issue on the Ledger Account page where a currency filter is ignored in search.

Dropdown Display Fix: We will fix an issue in which the Ledger Account Category dropdown persists on the screen when creating a Ledger Account.

Actions Button Fix: We will fix an issue where users can't access the actions button on Ledger Transactions table rows.

We introduced custom processing windows, as well as bulk invoice uploads for easier reconciliation. Looking ahead, Platform will add a Java/Kotlin SDK upgrade and introduce SFTP file sharing for recurring data uploads.

Recently Released

💵 Payments

View Custom Processing Windows in Dashboard: Our Modern Treasury dashboard provides full visibility into custom processing windows and enables teams to move money on their own terms.

• Users can request custom processing windows by contacting their support or Sales representative.
• Custom processing windows are set by bank, payment rail, currency, and direction.
• All customers are able to view custom processing under Accounts > Cash Management > Select an Internal Account > Click Processing Windows tab.

🧑‍💻 Platform

Invoice Bulk Upload with Virtual Accounts: When creating bulk uploads of invoices via the web application, users can now specify a Virtual Account for the Counterparty to pay. This helps simplify reconciliation.

Upcoming Changes

⭐️ indicates newly introduced upcoming changes

🧑‍💻 Platform

⭐️ Updates to Java and Kotlin SDKs: There is an upcoming change in our Java/Kotlin API that will be part of a new version release. In this update, we will be replacing an external library (Guava) with a custom solution for handling query parameters and headers. What this means for users:

• Reduced JAR Size: This change reduces the size of the SDK.
• Opt-In Update: Since this is a version change, users will have the option to upgrade at their own pace. The new version will give users access to the improvements, but it won’t affect users who don't choose to move to it.
• Minimal Impact: There may be a small adjustment required for users who have been working directly with raw headers or query parameters.

File Sharing via SFTP: Users will be able to perform recurring data uploads by sharing files via SFTP. Users will be able to create Payment Orders, Expected Payments, Transactions, and Ledger Transactions.

Optimized High-Volume Payments: Our systems will be optimized to significantly increase the processing speed for large volumes of ACH payments to JPMC.

Cycle Through Approvals: After approving a Payment Order, users will be able to move to the next item without returning to the approval list.

Payment Approvals by Currency: Users will be able to filter payment approvals by currency on the approvals list.

Saved Filters: Users will be able to save complex filter combinations for recurring workflows, simplifying navigation back to specific views.

Export Permissions Update: Going forward, users will only have access to exports when they are the creator of the export or when they are assigned access to the report from which the export was created.

Dashboard Clean-Up: Redundant "Status Change" information will be removed from the dashboard, which appears in timeline views for various objects. Similar information can be found in "Events," which are in dashboard views, or retrieved via API and webhooks. Status changes will first be removed for Expected Payments and Payment Orders in November, with additional objects to follow in early 2025. Please contact Support if you have questions or concerns.

Adjust Metadata Search Behavior: Metadata search in the UI will be case insensitive and take in multiple values in a single query.

💵 Payments

Custom Payment Order Templates: Users will be able to create custom templates for different Payment Order use cases to make it easier to initiate payments. Users will be able to control which fields on the Payment Order form are visible, required, optional, and preset. Contact our team to schedule a demo.

Real-Time Payment Confirmation: Users will be able to receive real-time confirmation of RTP or FedNow payments at Bank of America, Cross River, JP Morgan, US Bank, and Wells Fargo via the confirmed event in Payment Order webhooks.

Request for Payment (RFP) at PNC: Users will be able to utilize Request for Payment (RFP) on the Real Time Payments (RTP) network at PNC.

FedNow Routing Number Eligibility Check: We are adding support for FedNow to our routing number eligibility API. This API validates whether a counterparty can receive a particular payment type. If a counterparty has the ability to receive a FedNow payment, we will return fednow on the supported_payment_types field.

Expanded Cross-Border Payment Coverage: We are planning to expand our cross-border payment capabilities at Citi via the Worldlink product and traditional SWIFT wires, adding support for new currencies and countries.

Global Payments Validation: Payment Order fields for cross border payments will automatically be validated against the bank’s requirements for each country and currency. This will notify the user about required fields and the correct format for successful payment completion. For example, this can include Purpose Codes, Tax Identifiers, or Addresses. We will support Global Payments Validations at Bank of America, JP Morgan, and Citi.

Support for Local Payment Methods: We will support local payment methods in India, Japan, and Singapore through Bank of America, further expanding our global reach.

New Bank Integrations: New bank integrations will be added for Regions, Web Bank, and Western Alliance, expanding banking options for users.

Create Legal Entities at Cross River Bank: Users will be able to create legal entities at Cross River Bank to ensure compliance with regulatory requirements.

✅ Reconciliation

Many-to-Many Reconciliation: Users will be able to create rules to automatically reconcile many Transactions to many Expected Payments, enabling reconciliation for more complex payment scenarios.

Faster High-Volume Recon: We will launch system improvements to process reconciliations faster when handling high transaction volume.

Custom Identifier Filters: Users will be able to find, search and filter on Expected Payment Custom Identifiers in the Reconciliation UI.

📒 Ledgers

Faster Ledger Queries: Performance improvements will enable faster querying of Ledger Account Category balances; categories with millions of accounts can be fetched in under 200ms.

Filter Enhancements: Users will be able to filter the Ledger Accounts page to view only accounts with nonzero posted balances. We will also fix an issue causing these filters to time out for some users.

Bulk Ledger Account Creation: The bulk requests API will support the creation of up to 1,000 Ledger Accounts in a single request.

Timestamp Specification: Users will be able to specify an effective_at timestamp when creating a Ledger Transaction in the dashboard.

Dashboard Design Update: We will update the design of filters and other pages in the dashboard for a cleaner, more intuitive experience.

Unledgered Amount Display: Users will be able to view the Unledgered Amount next to each bank transaction, showing any amount not yet recorded to the ledger.

Ledgered Payments: When a Payment Order is redrafted, linked Ledger Transactions will be automatically recreated with inherited details from the original transaction.

Preset Payment Amounts: When ledgering a payment from the dashboard, the amount for both credit and debit entries will be preset to the payment amount.

Settlement ID Filter: Users will be able to filter Ledger Transactions in the dashboard by Settlement ID.

Currency Filter Fix: We will fix an issue on the Ledger Account page where a currency filter is ignored in search.

Dropdown Display Fix: We will fix an issue in which the Ledger Account Category dropdown persists on the screen when creating a Ledger Account.

Actions Button Fix: We will fix an issue where users can't access the actions button on Ledger Transactions table rows.

This cycle brings smoother reconciliation with automated net credit/debit matching, while upcoming updates will speed up payments, enable real-time confirmations, enhance ledger flexibility and performance, and more.

Recently Released

✅ Reconciliation

Transaction Categorization Rule Options: Users can create categorization rules with an expanded list of fields (e.g. Payment Order Purpose Code, Creation Method, Type).

Net Credit and Debit Reconciliation: Users can create reconciliation rules which automatically reconcile a Transaction with a net amount of both credit and debit Expected Payments, instead of only credit or only debit Expected Payments.

Improved Automation: Our systems have been further enhanced to automatically trigger reconciliation based on new or updated Expected Payments data.

Upcoming Changes

🧑‍💻 Platform

Optimized High-Volume Payments: Our systems will be optimized to significantly increase the processing speed for large volumes of ACH payments to JPMC.

Cycle Through Approvals: After approving a Payment Order, users will be able to move to the next item without returning to the approval list.

Payment Approvals by Currency: Users will be able to filter payment approvals by currency on the approvals list.

Saved Filters: Users will be able to save complex filter combinations for recurring workflows, simplifying navigation back to specific views.

File Sharing via SFTP: Users will be able to perform recurring data uploads by sharing files via SFTP. Users will be able to create Payment Orders, Expected Payments, Transactions, and Ledger Transactions.

Export Permissions Update: Going forward, users will only have access to exports when they are the creator of the export or when they are assigned access to the report from which the export was created.

Dashboard Clean-Up: Redundant "Status Change" information will be removed from the dashboard, which appears in timeline views for various objects. Similar information can be found in "Events," which are in dashboard views, or retrieved via API and webhooks. Status changes will first be removed for Expected Payments and Payment Orders in November, with additional objects to follow in early 2025. Please contact Support if you have questions or concerns.

Adjust Metadata Search Behavior: Metadata search in the UI will be case insensitive and take in multiple values in a single query.

💵 Payments

Custom Payment Order Templates: Users will be able to create custom templates for different Payment Order use cases to make it easier to initiate payments. Users will be able to control which fields on the Payment Order form are visible, required, optional, and preset. Contact our team to schedule a demo.

Real-Time Payment Confirmation: Users will be able to receive real-time confirmation of RTP or FedNow payments at Bank of America, Cross River, JP Morgan, US Bank, and Wells Fargo via the confirmed event in Payment Order webhooks.

Request for Payment (RFP) at PNC: Users will be able to utilize Request for Payment (RFP) on the Real Time Payments (RTP) network at PNC.

FedNow Routing Number Eligibility Check: We are adding support for FedNow to our routing number eligibility API. This API validates whether a counterparty can receive a particular payment type. If a counterparty has the ability to receive a FedNow payment, we will return fednow on the supported_payment_types field.

Expanded Cross-Border Payment Coverage: We are planning to expand our cross-border payment capabilities at Citi via the Worldlink product and traditional SWIFT wires, adding support for new currencies and countries.

Global Payments Validation: Payment Order fields for cross border payments will automatically be validated against the bank’s requirements for each country and currency. This will notify the user about required fields and the correct format for successful payment completion. For example, this can include Purpose Codes, Tax Identifiers, or Addresses. We will support Global Payments Validations at Bank of America, JP Morgan, and Citi.

Support for Local Payment Methods: We will support local payment methods in India, Japan, and Singapore through Bank of America, further expanding our global reach.

New Bank Integrations: New bank integrations will be added for Regions, Web Bank, and Western Alliance, expanding banking options for users.

Create Legal Entities at Cross River Bank: Users will be able to create legal entities at Cross River Bank to ensure compliance with regulatory requirements.

✅ Reconciliation

Many-to-Many Reconciliation: Users will be able to create rules to automatically reconcile many Transactions to many Expected Payments, enabling reconciliation for more complex payment scenarios.

Faster High-Volume Recon: We will launch system improvements to process reconciliations faster when handling high transaction volume.

Custom Identifier Filters: Users will be able to find, search and filter on Expected Payment Custom Identifiers in the Reconciliation UI.

📒 Ledgers

Faster Ledger Queries: Performance improvements will enable faster querying of Ledger Account Category balances; categories with millions of accounts can be fetched in under 200ms.

Filter Enhancements: Users will be able to filter the Ledger Accounts page to view only accounts with nonzero posted balances. We will also fix an issue causing these filters to time out for some users.

Bulk Ledger Account Creation: The bulk requests API will support the creation of up to 1,000 Ledger Accounts in a single request.

Timestamp Specification: Users will be able to specify an effective_at timestamp when creating a Ledger Transaction in the dashboard.

Dashboard Design Update: We will update the design of filters and other pages in the dashboard for a cleaner, more intuitive experience.

Unledgered Amount Display: Users will be able to view the Unledgered Amount next to each bank transaction, showing any amount not yet recorded to the ledger.

Ledgered Payments: When a Payment Order is redrafted, linked Ledger Transactions will be automatically recreated with inherited details from the original transaction.

Preset Payment Amounts: When ledgering a payment from the dashboard, the amount for both credit and debit entries will be preset to the payment amount.

Settlement ID Filter: Users will be able to filter Ledger Transactions in the dashboard by Settlement ID.

Currency Filter Fix: We will fix an issue on the Ledger Account page where a currency filter is ignored in search.

Dropdown Display Fix: We will fix an issue in which the Ledger Account Category dropdown persists on the screen when creating a Ledger Account.

Actions Button Fix: We will fix an issue where users can't access the actions button on Ledger Transactions table rows.