SAF-T generation

Setup

Before extracting the SAF-T file for the first time, it is mandatory to set up the transaction origin by tax code.

For each tax level, the origin of the transaction needs to be defined as being either Mainland, Azores, or Madeira. For each tax level, the tax code level needs to be defined for SAF-T purposes.

The tax type can be different from VAT and if it’s settled as Tax stamp, it is mandatory to assign the related tax stamp type.

Process

A dedicated function will enable the generation of the XML file.

In the SAF-T extraction function (FUNSAFTEXT) you can select the type of SAF-T to be exported:

  • SAF-T PT Integrated: The file is only extracted when requested by the government. It also includes common tables, invoices, and the general ledger.
  • SAF-T PT Invoicing: The file is extracted when requested by the government. It only includes invoices.
  • SAF-T PT Accounting: The file is extracted when requested by the government. It only includes the general ledger.
  • SAF-T PT Self-billing: The file includes purchase auto-invoices when requested by the supplier or the government.
  • SAF-T PT AT communication: The file is communicated every month with the invoices of the previous month. The product table is not exported.
  • SAF-T PT Self-billing AT: The file is communicated every month with the auto-invoices from the previous period. The product table is not exported.
  • SAF-T PT Shipping documents AT: This type is used to communicate in advance the transport that will occur. See Transportation communication.

In addition, the supplier filter will only be enabled if the SAF-T type is associated with the supplier auto-invoice (Self-billing and self-billing AT).

The Site and Document fields are only applied if the communication relates to transport notes. See Transport notes.

It is required that the product description has more than two characters. This is responsibility of the user to be careful with the product setup.