Skip to main content

FAQ

France

Frequently Asked Questions

General​

How are periodic reports (month/year) generated?

Periodic reports are generated automatically based on transaction data and daily closures performed by the POS system. The process ensures that all financial data is consistently recorded and available for reporting purposes.

Daily closure as trigger

The generation of periodic reports is based on regular closing procedures.

  • Trigger the daily closure via the POS software.
  • Use a non-fiscal transaction with NFS="CLO".
  • Ensure the closure process is completed correctly.

This daily closure is required for further reporting steps.

Automatic report generation

After the closure step, the system handles report creation automatically.

  • The EFR generates a closure report automatically.
  • The report is stored in the transaction journal (/EFR/rn/def/jou/.jou).
  • When a new month begins, periodic reports (monthly and yearly) are created automatically.

This process does not require manual intervention.

Export of month/year reports

Periodic reports can be exported using different methods.

  1. Access the web interface:
  2. Use automated access:
  3. Retrieve reports from the efsta cloud portal.

These options allow flexible access depending on the system setup.

Retrieving daily closure records

In addition to periodic reports, daily closure data can also be queried.

Use the following endpoints:


This retrieves daily closure records from the journal.


This returns the current balance totals.

How is 'Return of Goods' registered?

Returns of goods are handled within the transaction data by using negative values. This ensures that the system correctly reflects the financial impact of returned items.

Registration of returns

To register a return, specific fields must be adjusted accordingly.

  • Returns are recorded as positions with a negative sign.
  • This applies to the <Pos> fields:
    • Quantity (Qty)
    • Amount (Amt)

Using negative values ensures that returns are clearly identified as reversing a previous sale.

Handling within transactions

Returns can be processed in different ways, depending on the situation.

  • They can be registered as a separate transaction.
  • This may result in a negative total amount (e.g. in combination with a cash refund).
  • Alternatively, returns can be processed together with the sale of other items.

This flexibility allows businesses to handle returns according to their operational needs.

Impact on totals

Negative values are taken into account in all relevant calculations.

  • Returns are included in Grand Totals.
  • They are also included in the “Grand Total absolute” field according to NF525 rules.

This ensures that overall financial data remains accurate and consistent.

Difference between returns and voids

Returns are not the same as voided transactions.

  • Returns are processed using negative values in position fields.
  • Voids are identified using specific fields:
    • Pos.Void
    • ESR.Void

This distinction is important for correct fiscal reporting.

Transaction examples:

<Tra>
    <ESR D="2021-06-23T09:35:00" TL="001" TT="1" TN="2091" T="-1.99" FR_OperationType="remboursement">
        <PosA>
            <Pos PN="1" IN="4012345678901" Dsc="Test Item" TaxG="A" Qty="-1" Amt="-1.99"/>
        </PosA>
        <PayA>
            <Pay Dsc="Cash" Amt="-1.99"/>
        </PayA>
    </ESR>
</Tra>
<Tra>
    <ESR D="2021-06-23T09:35:00" TL="001" TT="1" TN="2091" T="1.00" FR_OperationType="vente">
        <PosA>
            <Pos PN="1" IN="4012345678901" Dsc="Test Item" TaxG="A" Qty="-1" Amt="-1.99"/>
            <Pos PN="2" IN="1234" Dsc="Exchange Item" TaxG="A" Amt="2.99"/>
        </PosA>
        <PayA>
            <Pay Dsc="Cash" Amt="1.00"/>
        </PayA>
    </ESR>
</Tra>