Use the Address Type field to mark this address as the substitution address.

Set the country code to ES.

Based on ID Types, specify the ID type that corresponds with the ID number in the Miscellaneous Tax 2 field.

where <CERTIFICATE_FILENAME1> is the name of the .p12 certificate file and <CERTIFICATE_FILENAME2> is the name of the .pem certificate file.

where <CERTIFICATE_FILENAME1> is the name of the .p12 certificate file and <KEY_FILENAME> is the name of the .pem private key file.

When prompted, enter the password for the .p12 file.

This step results in two new files:

where <FILENAME> is one of the two .pem new files.

Depending on your local IT setup, you can grant access to a group of users.

Specify the entity for which you want to prepare an SII declaration.

Specify the .pem file name for the digital certificate that authorizes your company to connect to the SII Web service.

Specify the private certificate key.

Specify the certificate password, which is required to connect to the AEAT Web service.

Specify the directory in which the digital certificate is stored.

Specify the amount of time in seconds until the system tries to access the Internet address of the AEAT Web service.

cURL is a command line tool used to send files using URL syntax and is used to communicate with the AEAT Web service.

Specify the path to the directory in which XML-format requests are stored. These files are sent to the AEAT Web service electronically using SII Authorization.

Specify the path to the directory in which XML-format responses are stored. The inbound response file names have a specific format; for more information, see Using Spain SII Declaration.

Specify the environment type for which you are adding a URL. Possible values are:

Specify the Web service address for the production or test environment type to which you must transmit files of the type indicated in the Event field.

Specify the SII Declaration version number.

Specify the entity for which you want to set the invoice date types.

Specify the type of date used for issued invoices in SII declarations.

Specify the type of date used for received invoices in SII declarations.

Specify how many invoices to print in each XML file. If there are more invoices than the value specified, another XML file is generated.

Specify a comma-separated list of daybooks for which related invoices should be excluded from the SII declaration.

If selected, the SII declaration prints the Reference field from the supplier invoice. Otherwise, the declaration prints the year, daybook code, and voucher of the supplier invoice.

Specify the Invoice Type Key that you want to use for this daybook.

Set this field to Yes to generate the invoices in this daybook as simplified invoices.

If the invoices generated in this daybook require the identification of the customer or supplier, set this field to Yes.

Specify the tax code for which you want to enter SII-related information.

These fields populate automatically based on the value that you specify in the Tax Code field.

If you select this field, the Not Subjected (NoSujeta) part of the XML with Excluded Tax information is printed. If there is setup with any value for this flag, this tax code will be printed in the SII declaration.

If you have not completed the setup for the Tax Code in Spain SII Tax Rate, the invoice will not be printed.

If this tax code relates to an issued invoice for a correction, use the drop-down menu to identify the particular issued invoice type. Possible values are R1, R2, R3, R4, and R5, which are categories of issued invoices described in SII legislation.

Specify the special regime tax code, as defined by the Spanish Government.

When there is a transaction of Successive Tract (Tracto Sucesivo), defined by the special regime tax code 15, the tax point date is different from the posting date. An extra date with the field title Date of Operation (Fecha de Operación) is declared in the XML file.

To send the invoices dated from January 1 to July 31, 2017, the special regime tax code 14 must be specified for invoices received and the tax code 16 must be specified for invoices issued. Entering the code 14 will create two extra fields in the XML file for accounting date and deductible fee, represented by the value 0. The code 16 will create one extra field in the XML file for non-exempt type, with the value S1 for non-exempt invoices.

If this tax code applies to special intra-Community transactions, select this field.

If this tax code relates to services, select this field. If this tax relates to goods, do not select this field.

If this tax code relates to an equivalence surcharge, select this field.

If you completed the Correction Code field, complete the related Type field. Possible values for this field are S (Substitution) and I (Differences), which are types of corrected invoices described in SII legislation.

If you completed the Special Intra-Community field, complete the related Type field. Possible values for this field are A and B, which are types of special intra-Community transactions described in SII legislation.

Select this field if the tax code is included in SII declarations related to accounts receivable transactions.

If tax is not included, set this field to No and specify a value for one of the following fields, based on SII legislation:

If tax is included, set this field to Yes and redefine the Exempt code.

See the explanation for the Tax Included Exempt field. This field relates to the ImportePorArticulos7_14_Otros XML tag—amount in euros if the attachment relates to art. 7.14, others—and the ImporteTAIReglasLocalizacion XML tag—amount in euros if the attachment is for operations not subject to the TAI rules of location.

If you completed the Tax Included Exempt field, complete the related Included/Exempt field. Possible values for this field are E1–E6, which represent exemption reasons listed in SII legislation.

If you completed the Not Incl./Territory Rules or Not Included/Others (Art. 7, 14, etc) fields, complete the related Included/Non Exempt Code field. Possible values for this field are S1 and S2, which represent Classification of Subject/Non-Exempt transaction type categories listed in SII legislation.

Complete the field in the Accounts Payable section:

Indicate if this tax relates to a reverse charge.

To include entities in the same corporate group as the entity specified in the Entity field, select this field. For more information on relating entities to one another, see Including Entities in a Group.

For original declarations, select Registration. For updates to declarations that you have previously sent, select Amendments.

Specify whether the SII declaration relates to issued (customer) invoices, received (supplier) invoices, or special intra-Community invoices (for transactions within the EU).

If you want to send this SII declaration to the AEAT Web service, set this field to Yes.

If you want to validate the XML content in the generated SII Declaration file, set this field to Yes.

If you are sending a correction invoice for an invoice that was previously marked as Approved (Correcto) or Accepted with Errors (Aceptado Con Errores) by the AEAT Web service, set this field to Yes. This setting instructs the AEAT Web service to discard the version of the invoice that was previously sent, and to record this version of the invoice in the VAT registration book.

The total number of invoices that were not sent due to errors can be viewed in <PREFIX>_EXCEL.csv, as described in Result Files.

The total number of invoices that were approved.

The total number of invoices that were partially approved.

The total number of invoices that were rejected.

If you to update the QAD application based on the AEAT XML response file, select this field.

Specify the type of SII Declaration that this XML response from the AEAT Web service relates to.

This browse allows you to view the status of customer invoices in the declaration that you sent to the Web service. It also includes error columns and a Sequence column that shows you how many times an invoice status was changed. Declarations can be sent for multiple entities, so the browse includes an Entity Code column. The largest sequence value is the most recent invoice status change.

This browse allows you to view the status of supplier invoices in the declaration that you sent to the Web service. It also includes error columns, reference columns, and a Sequence column that shows you how many times an invoice status was changed. Declarations can be sent for multiple entities, so the browse includes an Entity Code column. The largest sequence value is the most recent invoice status change.

This browse allows you to view the status of special intra-Community transactions in the declaration that you sent to the Web service. It also includes error columns and a Sequence column that shows you how many times an invoice status was changed. Declarations can be sent for multiple entities, so the browse includes an Entity Code column. The largest sequence value is the most recent invoice status change.

To submit a correction invoice for a previously accepted invoice, use Spain SII Update Status (36.5.8.10.6) to set the invoice status to Void. You can then submit the correction invoice in Spain SII Declaration, setting the Void field in the selection criteria to Yes.

If an invoice that you previously submitted to the AEAT Web service was rejected, you can resubmit an updated version of the invoice. If the resubmission is accepted, it is important to mark the invoice as an updated invoice. To do so, use Spain SII Update Status.

To update the status of a customer invoice, set this field to Issued Invoices. To update the status of a supplier invoice, set this field to Received Invoices. To update the status of an invoice related to an special intra-community transaction, set this field to Special Intra-Community.

To update the status of a particular invoice, specify the number of the invoice.

These fields populate automatically, based on the invoice number.

If you want to replace the (submitted) invoice with a correction invoice, set this field to Void. The status can only be set to Void when the current invoice status is Approved (Correcto), Accepted with Errors (Aceptado Con Errores), or Updated and when the invoice balance is zero.

If you have updated the invoice to correct an error that caused the initial invoice to be rejected, and you want to keep a record of this action, set this field to Updated.