Red 1.4.0 Release Notes 28/07/2026

Modified on Tue, 18 Aug at 2:50 PM

Sales Invoices
UPDATED: Red can now handle sales invoices with multiple lines more safely.

Red now checks that:

each invoice line contains the information it needs,

the net, VAT and total amounts add up correctly,

the invoice totals match the individual lines,

the correct Sales VAT categories are being used,

placeholder or incomplete product details are caught before anything is saved.

When something is wrong, Red gives a clearer explanation of which part of the invoice needs to be corrected.

For example, users can ask:

Create a sales invoice with multiple product lines.

Create an invoice using a generated reference.

Check why this invoice cannot be created.

Preview this invoice before saving it.

Company Readiness
NEW: Red can now perform a more complete check of whether a company is ready to use.

The check looks at areas such as:

the company’s financial year,

whether the transaction date falls within that financial year,

Sales VAT rates,

Sales Analysis categories,

products,

sales representatives,

other setup needed before using sales, purchases and reports.

Red then tells the user whether the company is:

ready;

ready with warnings;

not ready;

having a connection problem.

It also separates important problems from recommendations, so users can see what must be fixed and what is only suggested.

For example, users can ask:

Is this company ready to create sales invoices?

Check whether this company is ready for viewing/editing the sales book, purchases book and reports.

What setup is missing from this company?

Why is this company only "ready with warnings"?

Are all my companies set up in the same way?

Connection Reliability
FIXED

A user could connect successfully and use some Red features, then get an incorrect message saying their API key was invalid or expired when trying to list sales invoices.

The fix means Red now:

keeps the company connection available when Claude retries a request,
only marks an API key as invalid when there is a genuine authentication failure,
does not clear a valid company connection because of a general request.

This should prevent users from being asked to reconnect when their company connected correctly.