5/1/2025 Release (41.15)

Introduction of the Wave Migration, a new payment processor, and template rules.

New Features/Enhancements

Imports

  1. Wave: Introduction of accounting migration from Wave in embedded UI and API.
  2. CoA Mapping API: New endpoint for mapping a user's CoA from their legacy accounting system into the Tight API for more complex migrations.

Integrations

  1. Qualpay: Integration with new payment processor, Qualpay.
  2. Transaction Sync: Ability to pause/unpause transaction ingestion for linked Stripe and Unit accounts directly on Banks & Integrations screen.

Analytics

  1. Lifecycle Events: Added lifecycle events for transaction rules.

Bank Transactions

  1. Last Synced Date UI: Bank accounts now reflect their “Last Synced Date” on the Banks & Integrations screen.
  2. Advanced Search: Ability to filter by status in the advanced search in Expense and Income Dashboards.

Invoicing

  1. Bulk deletion: Ability to bulk delete invoice payments from transaction dashboards and via API.
  2. Recurring Invoice Emails: Option to toggle automatic emails for future recurring invoices.

Embedded UI

  1. Expense Rule Templates: Exposed template rules in API and embedded UI for bookkeepers and users to review.
  2. Monthly Closings: Updated validation to prevent the creation of monthly closings in closed years.

API

  1. Attachments: API enhancement to filter attachments to a given entity.
  2. Bank Accounts: Minor API update to return the integrationId on pertinent bank accounts.

Bug Fixes

API

  1. Fixed an issue that prevented manual journal entries from being submitted when line item descriptions were omitted.
  2. Resolved a bug that reset a business’s invoice prefix when the field was omitted from API requests.
  3. Fixed a bug where bank account changes on recurring expenses were not being properly saved.

Integrations

  1. Fixed an error preventing the auto-charge payment method from working with relinked Stripe accounts.
  2. Stripe integrations and associated bank accounts are now correctly marked as archived when disconnected.
  3. Ensured historical Plaid transactions are consistently pulled, regardless of webhook delivery order.