5/1/2025 Release (41.15)
May 1st, 2025
Introduction of the Wave Migration, a new payment processor, and template rules.
New Features/Enhancements
Imports
- Wave: Introduction of accounting migration from Wave in embedded UI and API.
- 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
- Qualpay: Integration with new payment processor, Qualpay.
- Transaction Sync: Ability to pause/unpause transaction ingestion for linked Stripe and Unit accounts directly on Banks & Integrations screen.
Analytics
- Lifecycle Events: Added lifecycle events for transaction rules.
Bank Transactions
- Last Synced Date UI: Bank accounts now reflect their “Last Synced Date” on the Banks & Integrations screen.
- Advanced Search: Ability to filter by status in the advanced search in Expense and Income Dashboards.
Invoicing
- Bulk deletion: Ability to bulk delete invoice payments from transaction dashboards and via API.
- Recurring Invoice Emails: Option to toggle automatic emails for future recurring invoices.
Embedded UI
- Expense Rule Templates: Exposed template rules in API and embedded UI for bookkeepers and users to review.
- Monthly Closings: Updated validation to prevent the creation of monthly closings in closed years.
API
- Attachments: API enhancement to filter attachments to a given entity.
- Bank Accounts: Minor API update to return the
integrationId
on pertinent bank accounts.
Bug Fixes
API
- Fixed an issue that prevented manual journal entries from being submitted when line item descriptions were omitted.
- Resolved a bug that reset a business’s invoice prefix when the field was omitted from API requests.
- Fixed a bug where bank account changes on recurring expenses were not being properly saved.
Integrations
- Fixed an error preventing the auto-charge payment method from working with relinked Stripe accounts.
- Stripe integrations and associated bank accounts are now correctly marked as archived when disconnected.
- Ensured historical Plaid transactions are consistently pulled, regardless of webhook delivery order.