This release improves Red’s cash receipt workflows, including how receipt details, routing and ledger values are handled. It also includes some smaller usability and presentation improvements across Red. Cursor support is also now documented.
Cash Receipts
Cash receipt detail handling
FIXED: Red now preserves cash receipt detail lines correctly when creating or updating cash receipts.
Previously, in some cases, supplied detail text could be replaced by the receipt note instead of being kept as separate receipt details.
Red now:
- preserves supplied
detailCollectionvalues when creating a cash receipt; - preserves supplied detail lines when updating an existing cash receipt;
- supports detail lines correctly when creating cash receipts in a batch;
- leaves existing receipt details unchanged when an update does not include new detail lines.
This allows users to keep receipt notes and detailed reference information separate.
Improved cash receipt ledger values
FIXED: Red now handles cash receipt ledger values more reliably.
In some cases, the Big Red Cloud single-receipt response could return a ledger value of 0 even when the corresponding receipt list showed the correct value.
Red now performs an additional safe check against the matching cash receipt where necessary before presenting the ledger value.
This means users should now see the correct ledger value when asking Red to retrieve a cash receipt or when Red verifies a receipt after an update.
Red does not calculate or estimate the ledger value from other fields. It only uses a value from the exact matching Big Red Cloud receipt.
Improved cash receipt routing
FIXED: Requests to create a customer cash receipt are now routed more reliably.
Some phrases containing both customer and cash receipt could previously be interpreted as a request to create a new customer.
Red now gives the cash receipt action priority when the user clearly asks to create or preview a customer cash receipt.
For example:
“Create a customer cash receipt for RTT001.”
will now remain in the cash receipt workflow rather than being interpreted as a customer-creation request.
Cash receipt reference validation
UPDATED: Red now gives clearer guidance when an unsupported reference field is used with a cash receipt.
The Big Red Cloud cash receipt API does not support a separate reference field.
Red now rejects this locally before anything is sent to Big Red Cloud and tells the user to use receipt detail lines instead.
This provides clearer feedback and avoids sending unsupported fields to the accounting API.
Improved cash receipt previews and validation
UPDATED: Cash receipt previews now more closely reflect what will actually be sent to Big Red Cloud.
Improvements include:
- clearer handling of entry and processing dates;
- better preservation of supplied receipt details;
- clearer validation when required customer information is missing;
- improved handling of unsupported cash receipt filters;
- clearer distinction between a Red validation failure and an upstream Big Red Cloud API request.
These changes make it easier to review a cash receipt before confirming a write.
Improved post-update verification
UPDATED: Red now performs stronger verification after cash receipt updates.
After an update, Red checks the resulting cash receipt again and distinguishes between:
- a successfully verified ledger value;
- a verified value that does not match the expected result;
- a result that cannot be verified conclusively.
This helps Red avoid presenting an ambiguous value as though it had been confirmed.
Cursor support
NEW: Red can also be configured for use with Cursor through Cursor’s MCP support.
Users can add Red’s production MCP endpoint to Cursor and then use the normal Red company-connection flow before asking questions about their Big Red Cloud companies.
No Big Red Cloud API key or company credentials should be entered directly into Cursor. Company credentials should only be entered on Red’s secure connection page.
A separate knowledge-base article is available with the Cursor setup steps.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article