EFR 2.16.1
What's new?
Improvements
- Enhanced Security: Security keys for EFR logins now refresh by themselves
Fixes
- Czech Republic: Fixed rejection of
NFS="PAY"withoutRFN. These pay-ins/pay-outs are now accepted, journalled and not sent to EET 2.0. - France: Removed
readme.txtfrom local NF525 journal exports (@jou), matching portal exports. Field mapping is available only in the EFR documentation. - Italy: Fixed rejected printer voids returning
RC:OK. EFR now returnsRC:NOwith the printer error code. Unconfirmed voids generate a warning without a fiscal number (FN). - Spain: Fixed TicketBAI invoice chaining during offline or rapid invoice generation, which could reference the same predecessor (
EncadenamientoFacturaAnterior) and cause rejection with009-149.
What this means for our users?
Enhanced Security: The EFR uses a secret key to protect logins, and this key used to stay the same from installation onward. It now renews automatically at regular intervals. Customers and partners don’t need to do anything, and logins keep working as before.
Czech pay-ins/pay-outs: Cash movements no longer need an invoice reference. Invoice settlements still require RFN to identify the invoice being paid.
French journal exports: Consult the EFR documentation for field mapping. Journal data and verification tools remain unchanged.
Italian voids: Your POS can distinguish printer refusals from success. If confirmation is missing after a void is sent, EFR retains RC:OK with a warning: check the printer before retrying.
TicketBAI: Offline or rapidly issued invoices now chain to the correct predecessor, addressing rejections caused by this chaining defect.