LS Express version 28.2.x

Updated Features

Fixed Float Shown on X and Z Reports and the Posted Close Out Summary

  • The X and Z reports now show the Starting Fixed Float. The Net float cash line now shows the Ending Fixed Float balance, where it previously showed the net of the cash manually added to or removed from the drawer. The posted Close Out Summary now shows the Starting and Ending Fixed Float and the cash removed at close out.

Bug Fixes

Close Out Summary - Fixed Float Wrong or Left Unsettled

  • Fixed several issues where the drawer total did not match the counted amount at Close Out because of how Fixed Float was calculated and settled:
    • Fixed Float is now tracked per drawer only, instead of also being filtered by store, which could hide real float when the store on historical entries was inconsistent.
    • The view with a blank Drawer now adds up the Fixed Float of all drawers instead of showing 0. Posting is blocked until you select a specific drawer if there is outstanding float.
    • A drawer with outstanding Fixed Float but no cash sales in the period (for example, a card-only day) no longer leaves that float unsettled. A cash line is now created so the float can be settled and counted.
    • The Close Out Wizard now runs the same Fixed Float validation as the Close Out Summary, instead of letting you continue with an unresolved drawer.
  • Fixed Float requires a cash payment method to be selected on the POS Exact Payments tab in LS Express Administration, or a payment method flagged for Fiskaly. Without one, the feature is inactive.

Swedish X and Z Reports - Wrong Label for Number of Sales Transactions

  • Fixed an issue where the Swedish translation of the sales transaction count on the X and Z reports read "Antal returnerade försäljningstransaktioner" (number of returned sales transactions). It now reads "Antal försäljningstransaktioner".

X Report Missing Posted Customer Account Returns

  • Fixed an issue where the Swedish X Report did not include returns posted to customer accounts in its totals. The X Report now includes them, matching the Z Report.

Staff Login Prompt After Adding or Removing Cash in the Drawer

  • Fixed an issue where the staff login prompt appeared after you chose OK when adding cash to or removing cash from the drawer, even though you were already signed in. The prompt no longer appears.

Refund to Customer's Account Failed With Infrasec Error

  • Fixed an issue, specific to Sweden, where refunding a payment to a customer's account failed with the error "The Infrasec Sales Transaction does not exist. Identification fields and values: Entry No.='0'" when the original payment had never been registered with Infrasec. The refund now completes and shows an informational message that no original fiscal record was found.

Bug Fixes

Cash Point Closing Failed With "No Drawer Entry Found for Origin Sale"

  • Fixed an issue, specific to Germany, where finalizing a cash point closing could fail with the error "No drawer entry found for origin sale (sale reference). Cannot fiscalize settlement." This affected a Pay to Customers Account payment whose Fiskaly transaction had been created by the 28.2.2 fiscalization fix, where the original invoice or credit memo it settled did not yet have the drawer entry marker that the cash point closing process needs to build its fiscal reference list. A one-time upgrade step now backfills the missing marker for affected documents so their cash point closing completes.

Unsettled Fixed Float Leaked Between Drawers Sharing a Payment Method

  • Fixed an issue where the Unsettled Fixed Float shown while counting a drawer at Close Out could include fixed float left in a different drawer of the same store when both use the same cash payment method, producing an inflated drawer total and an incorrect Difference (and, where a Counting Difference G/L account is set up, a spurious posting). This is a companion to the 28.2.1 fix that scoped the same field to the correct store — the calculation is now also scoped to the correct drawer on the Close Out Summary and Close Out Verify screens. The Close Out Wizard's Count step is not yet covered by this fix and will be addressed in a future release.

Error Creating a New Store

  • Fixed an issue where creating a new store could fail with the error "The record in table Store already exists. Identification fields and values: ID='NEW'," because saving the new store inserted the store record twice. Creating a store now completes normally.

Appl.-from Item Entry Not Set on Return Items Credit Memo Lines

  • Fixed an issue where posting a Return Items transaction could fail with the error "Appl.-from Item Entry must have a value in Sales Line..." because the field linking a return line back to the original sale's item ledger entry was not carried over when the return was converted from a credit memo to an invoice and back again during posting. Return Items now posts successfully with the field populated, matching Reverse Sale.

Bug Fixes

Pay to Customers Account Not Fiscalized When No Invoice Selected

  • Fixed an issue where using Pay to Customers Account without selecting an invoice did not create a Fiskaly transaction for the payment, so the day's cash point closing sent to Fiskaly for the German DSFinV-K export was missing that payment. The payment now generates its own Fiskaly transaction with the correct VAT treatment and is included in the cash point closing totals. A one-time upgrade step also backfills the missing transaction for existing payments that are not yet part of a closed cash point summary.

Bug Fixes

Lost Cashier and Sales Profile When Error

  • Fixed an issue where returning to the POS New UI from Sales History with a saved filter applied could show the error "The Staff does not exist. Identification fields and values: Staff ID=''" and leave the cashier and sales profile blank on the status bar. The status bar now falls back to the current sales profile's store and staff instead of failing when the sale's staff ID is briefly empty during the page refresh. The same fix was applied to the Change Password action.

Close Out Summary - Fixed Float From All Drawers Posted into Difference Account

  • Fixed an issue where the Unsettled Fixed Float amount on the Close Out Summary could include fixed float from drawers belonging to other stores, resulting in an incorrect cash difference. The calculation is now limited to the store and summary being closed out.

Post to Customer Blocked for Negative Value (credit customer)

  • Fixed an issue where the Post to Customer action rejected negative amounts (crediting a customer account) with the error "Select a normal payment method to complete the refund" in every market. This restriction is now applied only where German or Austrian Fiskaly fiscal reporting is enabled; posting negative amounts to a customer account works again in all other markets.

Unable to Reassign a Fiskaly Client to Correct TSS After De-Registration

  • Once a Client ID was generated and registered for a store, there was no supported way to detach it from its TSS, so linking the correct TSS afterward failed with "Client ID is attached to TSS ID and it has been registered in Fiskaly server. The TSS ID is not allowed to change." The Fiskaly Client page now has Deregister Client and Refresh Client Status actions to safely release a Client ID so it can be reassigned. See Manage a Fiskaly Client.

Bug Fixes

Delete Sale Action Failing on New UI

  • Fixed an issue where deleting the current sale from the POS New UI failed with the error "The Sales Header does not exist." After the sale and its payment lines are deleted, the POS now starts a new sale for the current staff member instead of trying to refresh the page against the sale that was just removed.

New UI - Item Search Did Not Match Description 2

  • The POS item search now also matches an item's Description 2 field, in addition to the item number and Description. This applies to the item search box in the POS New UI as well as the standard POS. Matching results also show Description 2 in the search dropdown/result list.

LM - Error Activating License Key After an Environment Upgrade or Restore

  • Fixed an issue where activating the LS Express license could fail with a License Manager error stating the license was already activated with the environment's instance ID, after a Business Central environment upgrade or a restore that left the environment's local activation record out of sync with the License Manager's registration. Activation from the Subscription Setup page now detects this condition automatically, registers a new instance with the License Manager, and completes activation without manual intervention.
  • Separately, if the local API key needed for a license action (for example, Deactivate License) cannot be found, LS Express now shows a clear message that the API key is missing locally, instead of a generic authentication failure.