Recent releases include many-to-many reconciliation and faster imports and file payments at scale.

Recently Released

🧑‍💻 Platform

(Released 4/1) Multi-Factor Authentication Enabled by Default: As part of our phased rollout, MFA is now enabled by default for all newly created organizations that do not use SSO. This strengthens our security posture and helps ensure sensitive financial data remains protected. Existing organizations should continue working with their admins to complete their MFA migration ahead of the June 2025 enforcement deadline; details on migration tooling can be found here.

💵 Payments

(Released 4/30) Legal Entities at Increase: We now allow customers to programmatically create entities and attribute them to their Increase accounts. As part of this change, we will sunset the vendor_attributes[entity_id] key when creating Increase Internal Accounts and instead enable the ability to associate these Internal Accounts to Legal Entities by passing in a legal_entity_id.

(Released 5/1) Faster Imports at Scale: All importers now run significantly faster, improving ingestion speed, reliability, and reducing support escalations.

(Released 5/1) Triple Duplicate Payment Protection: File-based payments now have three layers of safeguards to prevent duplicate payments being sent.

(Released 5/1) Faster File Payments at Scale: System optimizations now support significantly higher throughput for large file-based payment volumes.

✅ Reconciliation

(Released in Early Access 5/9) Many-to-Many Reconciliation: Users can now manually reconcile many Transactions to many Expected Payments in the Reconcile side-by-side tool, enabling reconciliation for more complex payment scenarios. Some details to keep in mind regarding use of this feature:

• Expected Payments that are included in many-to-many reconciliation must use exact amount (vs. amount range) and be reconciled wholly (vs. partially)
• Transaction and Expected Payments groups must all have the same direction, either credit or debit

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.

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

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 Batch Metadata via API & Webhooks: We will expose batch-level context in the Payment Order API and webhook events to improve transparency. This will enable faster troubleshooting outside of the UI.

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

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.

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.

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

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.