Show the state before the next action
The walkthrough begins with a registered test device and an open fiscal day. Those screens give the operator context before a receipt is submitted. A generic success message would conceal which step had actually completed.
The website keeps the TEST environment label beside this walkthrough. A successful test submission does not establish that production fiscalisation is available.
Keep receipt preparation and confirmation distinct
The sequence shows a receipt before fiscalisation, a payment-method choice and then a fiscalised test receipt with verification details. The receipt PDF provides a second view of the resulting document.
A useful integration review checks the difference between preparing a document and receiving confirmation from the external service. If a request fails or times out, the operator needs a status they can act on.
A pending closure is still pending
The final screens show a close-day confirmation and a closure-processing status. The interface should keep that pending state visible until the external service confirms the outcome.
A practical acceptance scenario is to interrupt the connection after the close request. Check whether the app can recover the current day status before allowing another action. This is a review scenario to test, not a claim that every recovery path has been verified in the public beta.
Report the state, with safe sample records
For beta feedback, include the build version, Android version, action taken and the state shown afterwards. Use a screenshot with customer details removed, and never share a PIN or password.
This gives the team a reproducible issue while keeping the feedback about the workflow itself. Production availability, offline behaviour and backup guidance still need separate confirmation.
