Product Updates

Chasing overdue invoices is nobody’s favourite job, so we built something to do it for you.

This week’s release is headlined by automated dunning reminders: overdue invoices are now grouped by risk, wrapped in a branded email your customers will recognise, and sent without anyone on your team lifting a finger. It’s rolling out to our design partners shortly, with a full blog post on how it works to follow next week. For now, here’s everything that shipped.

New features#

1. Automated dunning reminders, the standout release this week, rolling out to our design partners shortly. Overdue invoices are grouped into ageing buckets, such as low, medium and high risk, and customers receive a branded reminder email showing exactly what’s outstanding: line items, amounts and full payment history. Your team spends less time chasing and more time collecting.

2. Branded email templates for every message you send. Alongside dunning, you can now design and preview your own templates for invoices, welcome emails and password resets, and set an organisation-wide default so every email looks like it came from you.

3. A rebuilt contract experience, start to finish. Adding stakeholders, uploading files, setting pricing and milestones, and moving a contract through its lifecycle now happens in one connected flow.

4. Aiko can now build your invoice templates for you. Ask Aiko to create, update or preview an invoice template and it does the work directly, no need to hand-build one yourself.

5. A new foundation for connecting your books. Incoming ledger data is now automatically normalised and matched against your existing customers, products and records, the groundwork for reconciling data from the ERPs.

6. A more personal touch in the sidebar, with your organisation’s name and logo right where your team navigates every day.

Improvements#

1. Template changes are now checked against your organisation before they save, so edits always land in the right place.

2. Contract actions and file uploads now share the same polished components throughout, for a more consistent feel.

3. Backfilled billing data now flows through the same core billing logic as everything else, keeping historical records consistent.

Fixes#

1. Usage-based pricing plans now hold onto their billing frequency correctly and validate against the pricing schema.

2. Aiko’s approval flow is more resilient. Abandoned approvals no longer leave a conversation stuck, and the composer pauses while one is pending.

3. Fixed a bug where clicking duplicate quickly on a contract could silently do nothing.

4. Invoice template tables and configuration now display and save correctly, so partial edits no longer wipe out unrelated fields.

New Features#

1. Model Context Protocol (MCP) OAuth 2.0 authorisation:

   • Added OAuth 2.0 authorisation code sign-in flow for MCP clients (such as Claude Desktop and Cursor AI tools), allowing finance teams to securely connect external AI workspace agents into Enso.
   • Integrated persistent MCP configuration and developer documentation links directly into the product header.

2. Contract milestone audit trails with file attachments:

   • Upgraded contract milestone and payment tracking grids to record complete historical audit trails, support file attachment columns, and track custom attributes.

3. Entity detail audit logs:

   • Enabled entity-level audit logs on organisation detail pages to track structural changes to legal entities and billing rules.

Improvements#

1. Payment summary stat cards:

   • Redesigned payment summary views into bordered stat cards for clearer high-level treasury visibility.

2. Shared authentication forms:

   • Consolidated security credential forms across login and authorisation pages for multi-region teams.

Fixes#

1. Invoice template blank-state validation:

   • Enforced validation to block saving contracts when the invoice template identifier is blank, preventing contract templates from being cleared during background refreshes.

2. Local contract save error handling:

   • Enhanced error handling during contract modification saves to prevent local state loss during network interruptions.

3. Numerical and date value parsing:

   • Corrected field order sorting on payments and prevented numerical metrics from being misclassified as date fields.