Cashiering Cloud 2026.3.4
Production Release: August 26, 2026
What's New
Print Totals now respects settlement visibility permissions
The Print Totals button on the Balance Drawer page and the Ready to Deposit pop-up is now disabled for users who don't have permission to view expected settlement amounts, preventing cashiers from bypassing blind balancing safeguards.
(CSH-18433)
Settlement reports show who created and settled each batch, plus over/short variance
Settlement reports now display "Batch created by" and "Settled by" on every page header, along with a new option to show settlement variance as "Over," "Short," or "None" instead of a dollar amount. Users can set a default display preference, and the settlement report screen offers a toggle to override that preference when generating a report.
(CSH-18509, CSH-18508, CSH-18507)
Consolidated transaction status API for AnywhereCashier integrators
The GetTransactionStatus API now returns credit card tender details, a unique transaction identifier, and the transaction amount directly in its response, eliminating the need for a second API call to retrieve credit card details.
(CSH-18502)
Partial void support for single-payment AnywhereCashier transactions
Integrators using AnywhereCashier can now partially void a transaction consisting of a single payment and a single tender via API, rather than only being able to void the full transaction amount.
(CSH-18523)
New permission for resolving unreceipted credit card transactions
Administrators can now control which users are allowed to resolve unreceipted credit card transactions via a new "Resolve unreceipted credit card transactions" setting in Transaction Security, with options for None, Same department, or All. Cashiers can still view unreceipted card tenders for their batches regardless of this setting.
(CSH-18537)
Transaction date now available on the Item Payment Report
A new "Include transaction date" toggle adds the transaction creation date as the first column on the Item Payment Report and sorts results by that date, making it easier to reconcile counter activity by day.
(CSH-18553)
More control over voiding complex transactions with external systems
A new "Complex payment" toggle for external systems lets administrators control whether voids on transactions with multiple payments and tenders are sent to the external system. The previous restriction blocking voids on complex transactions spanning multiple external systems has also been removed, so a single payment type can now be voided independently.
(CSH-18597)
Fixed Issues
| Jira issue # | Detailed description | What changed | Expected results | Requestor |
|---|---|---|---|---|
| CSH-18027 | The Payment Type and Tender Type hot key dropdowns in Administration > Department > Preferences did not include a blank option, so once a hot key was assigned it could not be disabled. | This fix added a blank option to the Payment Type and Tender Type hot key dropdowns. Selecting the blank option disables the hot key, and hot keys are also disabled while the spinner is active or when the associated dropdown itself is disabled. | When this fix is applied, a blank option appears for hot key options under Administration > Department > Preferences. When the blank option is selected, the hot key performs no action. Hot keys are disabled while the spinner is active or when the payment/tender type dropdown is disabled. | Pierce County, WA |
| CSH-18534 | After the 2026.3.1.0 update, Virtual Tape transaction cards on cloud sites did not render correctly at 100% browser zoom — the total amount and kebab menu were clipped, requiring users to zoom out to access them. | This fix corrected the Virtual Tape transaction card layout so all fields and the kebab menu render correctly at 100% zoom, and long "Paid by" names are now truncated (21-character limit) with the full name available in a tooltip. | When this fix is applied, on a cloud site, Virtual Tape batches display Number, Paid by, and Total amount fully visible with the kebab menu accessible on every row at 100% browser zoom, with no clipping. Long Paid by names are truncated with a tooltip showing the full name. | Freeborn Co MN |
| CSH-18613 | When a check tender requiring endorsement was selected and then changed to a non-check tender (such as cash), users could not complete the transaction — the Complete button showed a warning that check scan must be completed. | This fix corrected the transaction completion check so it no longer requires check endorsement/scan when the selected tender is not a check tender. | When this fix is applied, after selecting a check tender that requires endorsement and then switching to a non-check tender, the user can select "Complete" and successfully complete the transaction. | NJ MVC |