Process Documentation CUSTOMER

Electronic VAT Register Books with SII (Spain)

Document Version: 1.5 – 2017-06-22

Electronic VAT Register Books with SII (Spain)

Typographic Conventions

Type Style Description

Example Words or characters quoted from the screen. These include field names, screen titles,
pushbuttons labels, menu names, menu paths, and menu options.
Textual cross-references to other documents.

Example Emphasized words or expressions.

EXAMPLE Technical names of system objects. These include report names, program names,
transaction codes, table names, and key concepts of a programming language when they
are surrounded by body text, for example, SELECT and INCLUDE.

Example Output on the screen. This includes file and directory names and their paths, messages,
names of variables and parameters, source text, and names of installation, upgrade and
database tools.

Example Exact user entry. These are words or characters that you enter in the system exactly as
they appear in the documentation.

<Example> Variable user entry. Angle brackets indicate that you replace these words and characters
with appropriate entries to make entries in the system.

EXAMPLE Keys on the keyboard, for example, F 2 or E N T E R .

This document is delivered with SAP note 2485757 and corresponds to

the tax agency’s version 0.7 of Suministro Inmediato de Informacion del
IVA (SII).

CUSTOMER Electronic VAT Register Books with SII (Spain)

2 © 2016 SAP SE or an SAP affiliate company. All rights reserved. Typographic Conventions
Document History

Version Date Change

1.1 2017-05-10 First version delivered with SAP Note 2448460

1.2 2017-05-15 Add last sentence in 1.1. Prerequisite: Installation

Add note paragraph in 1.2.2. Customizing Activities Specific for Electronic
VAT Register Books with SII solution

1.3 2017-05-24 Remove the note in the section 1.2.1. Customizing Activities Related to
eDocuments

1.4 2017-06-12 Added new Customizing activities in section 1.2.2. Customizing Activities
Specific for Electronic VAT Register Books with SII Solution
Changed a paragraph and a new note in section 2.2. Tax Reporting Date and
Accounting Entry Date.
Changed paragraphs under note in section 2.3 Summary Invoice: Begin and
End Number
Removed last paragraph in section 2.4 Tax codes
Added the names of the transactions corresponding to the Create
eDocuments for VAT Register Books with SII (Spain)
(RPFIES_SII_EDOCCREATE) and Create eDocument Lists for VAT Register
Books with SII (Spain) (RPFIES_SII_EDOCLIST) reports.
Added the last paragraph in section 1.2.3 Other Customizing
Added a paragraph about tax ID type 07 (Not Registered) for outgoing
invoices in section 2.1 Invoice ID.

1.5 2017-06-22 Extended note paragraph about VAT date in section 2.2 Tax Reporting Date
and Accounting Entry Date

Electronic VAT Register Books with SII (Spain) CUSTOMER

Document History © 2016 SAP SE or an SAP affiliate company. All rights reserved. 3
Contents

1 ELECTRONIC VAT REGISTER BOOKS WITH SII ................................................................................................... 5

1.1 PREREQUISITES: INSTALLATION .......................................................................................................................... 5
1.2 PREREQUISITES: CUSTOMIZING ......................................................................................................................... 5
1.2.1 Customizing Activities Related to eDocuments .................................................................................... 5
1.2.2 Customizing Activities Specific for Electronic VAT Register Books with SII solution ............................... 6
1.2.3 Other Customizing.............................................................................................................................. 8
1.2.4 Authorization Objects ......................................................................................................................... 8
1.3 GENERAL PROCESS DESCRIPTION OF ELECTRONIC VAT REGISTER BOOKS WITH SII ......................................................... 9
1.3.1 Creating eDocuments ....................................................................................................................... 10
1.3.1.1 Creating eDocuments From Reversal Documents ...................................................................................... 11
1.3.2 Creating Lists of eDocuments ........................................................................................................... 13
1.3.2.1 Correcting Data Before Submitting the Lists to the Tax Agency .................................................................. 14
1.3.3 Submitting the Lists to the Tax Agency.............................................................................................. 14
1.3.4 Receiving Messages from the Tax Agency ......................................................................................... 14
1.3.4.1 Correcting Errors After Submitting the Lists to the Tax Agency .................................................................. 15
1.3.5 Description of Statuses ..................................................................................................................... 16
1.3.5.1 Statuses of eDocuments Within the SII Document Process ........................................................................ 16
1.3.5.2 Statuses of Lists within the SII Lists Process ............................................................................................... 18
1.3.5.3 Statuses of Reversal Documents in the Reversal Documents Process ......................................................... 19

2 CONCEPTS ..................................................................................................................................................... 21
2.1 INVOICE ID ................................................................................................................................................ 21
2.1.1 Correcting the invoice ID .................................................................................................................. 22
2.2 TAX REPORTING DATE AND ACCOUNTING ENTRY DATE ......................................................................................... 22
2.3 SUMMARY INVOICE: BEGIN AND END NUMBER ................................................................................................... 23
2.4 TAX CODES ................................................................................................................................................. 23
2.5 VAT ON CASH ............................................................................................................................................ 24

4
1 Electronic VAT Register Books with SII

The Electronic VAT Register Books with SII solution allows you to prepare, analyze and submit your data to the tax
agency in Spain using the Immediate Supply of Information System (SII).

The Electronic VAT Register Books with SII solution uses the eDocument Framework, which requires the
implementation of the following:

 SAP ERP, option for e-document processing add-on. This add-on has a limited runtime usage right for the
Application Interface Framework (AIF)

 SAP Cloud Platform Integration to handle the communication with external systems as well as notification
messaging.

Note
You need a separate license for the above add-on and to subscribe to SAP Cloud integration platform. For
more information, contact your SAP Account Executive.

1.1 Prerequisites: Installation

Refer to the SAP note 2448460 (SII - Prerequisite Notes for Installation and Use of SAP Solution for Suministro
Inmediato de Informacion del IVA) and SAP note 2485757 (SII (Version 0.7) – Overview).
You can find the required integration package and the implementation guide in your SAP Cloud Platform
Integration’s tenant. Go to Discover and search for eDocument: VAT Register Books for Spain.

1.2 Prerequisites: Customizing

Before you start working with the Electronic VAT Register Books with SII solution, you must check or perform
some Customizing activities:

1.2.1 Customizing Activities Related to eDocuments

You need to perform the following customizing activities to use eDocument Framework for the Electronic VAT
Register Books with SII solution. You find these activities in the Customizing for Cross-Application Components
under General Application Functions -> eDocument -> General Settings:
1. Activate Source Type Documents for Company Code (EDOCOMPANYACTIV view) (mandatory)

CUSTOMER
Electronic VAT Register Books with SII © 2016 SAP SE or an SAP affiliate company. All rights reserved. 5
 In this customizing activity, you have to activate the source type FI_INVOICE for each relevant company code.

2. Define Interface Type for eDocument (EDOINTTYPEV view) (mandatory)

In this customizing activity, you have to create the following 8 entries for each relevant company code:

Company Code eDocument Type Type Description Interface Type

1000 ES_SII_DII SII Deregister Incoming Invoice AIF proxy (for web services)

1000 ES_SII_DOI SII Deregister Outgoing Invoice AIF proxy (for web services)

1000 ES_SII_IIV SII Incoming Invoice AIF proxy (for web services)

1000 ES_SII_OIV SII Outgoing Invoice AIF proxy (for web services)

1000 ES_SII_OPY SII Outgoing Payment VoC AIF proxy (for web services)

1000 ES_SII_UII SII Add/Modify Incoming Invoice AIF proxy (for web services)

1000 ES_SII_UOI SII Add/Modify Outgoing Invoice AIF proxy (for web services)

1000 ES_SII_UOP SII Add Outgoing Payment VoC AIF proxy (for web services)

1.2.2 Customizing Activities Specific for Electronic VAT

Register Books with SII solution

In order to submit your data to the tax agency using the Electronic VAT Register Books with SII solution, you must
identify the types of documents and tax codes that are relevant for the SII processes. These are two mandatory
requirements to prepare and send your data to the Immediate Supply of Information System (SII) of the tax
agency.
To do so, refer to the Customizing settings for eDocument under Cross-Application Components -> General
Application Functions -> eDocument -> Spain -> Settings for Electronic VAT Register Books With SII.

Note
The customizing activities will be delivered with support packages as stated in the note 2448369. If you have
not installed the corresponding support package, you have to use the Edit Table Views (SM30) transaction
to display and edit views and the the BAdI Builder (SE18 or SE19) transaction to create BAdI
implementations.

The settings you make using the activities Assign SII Attributes to Accounting Document Types and Assign SII
Attributes to Tax Codes are mandatory to process your data correctly.

1. Assign SII Attributes to Accounting Document Types (FIESSII_DOCTYPEV view) (mandatory)

In this Customizing activity, you have to define which of your accounting document types are relevant for
Electronic VAT Register Books for SII.
You assign then specific attributes to each of these documents types.

2. Assign SII Attributes to Tax Codes (FIESSII_TAXCODEV view) (mandatory)

CUSTOMER Electronic VAT Register Books with SII (Spain)

6 © 2016 SAP SE or an SAP affiliate company. All rights reserved. Electronic VAT Register Books with SII
 In this Customizing activity, you have to select the relevant tax procedure and enter the tax codes that are
relevant for Electronic VAT Register Books for SII.
You assign then specific attributes to each of these tax codes.

3. Determine Dates for Incoming Invoices (FIESSII_COCODEV view) (optional)

In this Customizing activity, you can indicate which date you want for:
o Reporting Date: The date you indicate here influences the Tax Reporting Period
o Accounting Entry Date: The date you indicate here is used by the Tax agency to calculate the deadline
to submit incoming invoices to the Tax agency (fecha de registro contable).

4. Determine Reporting Dates for Outgoing Invoices (FIESSII_DATEOUTV view)

In this customizing activity you can choose which reporting dates you want to use for new outgoing invoices,
correction outgoing invoices and outgoing invoices used for deregistrations.

5. Determine Accounting Keys for Equalization Tax (FIESSII_TAXPROCV view)

In this Customizing activity, you indicate which accounting key you use to define the equalization tax rate for a
certain tax procedure. Note that this is only possible for outgoing invoices.

6. Change the Handling of Reversal Documents (FIESSII_REVOUTV view)

In this customizing activity you can determine for each of your document types that you use for outgoing
invoices how you want to handle your reversal documents while sending them to the tax agency.

7. Determine Real Estate Information (Business Add-In FIESSII_REAL_ESTATE)

In case you are renting out business properties, you must submit information about the reference and
location of these properties, if you do not collect withholding taxes for them. You use this BAdI to include this
information in the XML you send to the Spanish tax authority.

8. Change Business Partner Information (Business Add-In FIESSII_MASTER_DATA)

In the SAP standard system, the fields Name1 and Name2 in the business partner master data are used to fill
the tag <NombreRazon> of the file you send to the tax agency. With this BAdI you can determine another way
to fill this tag.

9. Change Invoice Details (Business Add-In FIESSII_INVOICE_DETAILS)

The SAP standard system fills the tags that refer to some invoice details in a certain way. With this BAdI you
can change the way the system fills these tags. To do so, you use the following methods:
 CHANGE_INCOMING_INVOICE: Change Incoming Invoice Details for SII Mapping
In the SAP standard system the tag <DescripcionOperacion> of the file you send to the tax agency is filled
with the description of the document type plus the document header text.
You can use this method to fill the above mentioned tag with another description .
 CHANGE_OUTGOING_INVOICE: Change Outgoing Invoice Details for SII Mapping
In the SAP standard system the tag <DescripcionOperacion> of the file you send to the tax agency is filled
with the description of the document type plus the document header text.
You can use this method to fill the above mentioned tag with another description.
In case of sales of business properties, you can use this method to fill the tag
<ImporteTransmisionSujetoAIVA>.

CUSTOMER
Electronic VAT Register Books with SII © 2016 SAP SE or an SAP affiliate company. All rights reserved. 7
10. Change Invoice ID for Invoice Summary (Business Add-In FIESSII_INVOICE_ID)
The SAP standard system fills some of the tags referring to invoices summaries (invoice type F4) in a certain
way. You can use this BAdI to change the way the system fills these tags. To do so, you use the
CHANGE_INVOICE_SUMMARY: Change SII Invoice Summary method:
In the SAP standard system, the tags <NumSerieFacturaEmisor> and
<NumSerieFacturaEmisorResumenFin>for invoice summary (invoice type F4) are filled according to the
entries in the Assign SII Attributes to Accounting Document Types Customizing activity (view
FIESSII_DOCTYPEV). You use this method to change the way to fill the above mentioned tags.
Note that this method applies only to invoices classified with invoice type Invoice Summary (F4).

1.2.3 Other Customizing

You may have already performed the following customizing activities. Now you need to check that the company
codes that are relevant for this process have a 9-digit Spanish tax identification number and a declarer maintained
in the address data:
 If the country of your company code is Spain (ES) and your company is not part of a VAT group, check in
Customizing for Financial Accounting (New) under Financial Accounting Global Settings (New) -> Global
Parameters for Company Code -> Enter Global Parameters.
 If the country of your company code is Spain (ES) and your company is part of a VAT group, check in
Customizing for Financial Accounting (New) under General Ledger Accounting (New) -> Periodic Processing ->
Report -> Sales/Purchases Tax Returns -> Assign Company Codes to Tax on Sales/Purchases Groups.
 If the country of your company code is not Spain (ES), check in Customizing for Financial Accounting (New)
under Financial Accounting Global Settings (New) -> Tax on Sales/Purchases -> Basic Settings -> Plants
Abroad -> Enter VAT Registration Number for Plants Abroad.
 If the currency of the company code is not EUR, you need to activate the Plants Abroad function. To do so,
refer to Customizing for Financial Accounting (New) under Financial Accounting Global Settings -> Tax on
Sales/Purchases -> Basic Settings -> Plants Abroad -> Activate Plants Abroad.

If you have input tax codes with non-Spanish rates, required for EU VAT Refund, maintain the entries in the
Customizing for Financial Accounting (New) under Financial Accounting Global Settings -> Tax on
Sales/Purchases -> Basic Settings -> VAT Refund -> Define Tax Code as Refund-Relevant Value Added Tax (view
cluster VC_TAX_RFD_CODES with the View Cluster Editing (SM34) transaction).

1.2.4 Authorization Objects

In order to run the Create eDocuments for VAT Register Books with SII (RPFIES_SII_EDOCCREATE) report or the
Create eDocuments for SII (Spain) (ESSII_EDOCCREATE) transaction, the system checks if you have the
following authorizations:

CUSTOMER Electronic VAT Register Books with SII (Spain)

8 © 2016 SAP SE or an SAP affiliate company. All rights reserved. Electronic VAT Register Books with SII
 Authorization Object Description Authorization Field Value

F_BKPF_BUK Accounting Document: BUKRS <as required>

Authorization for ACTVT 03 (Display)
Company Codes

EDO_BUK eDocument: BUKRS <as required>

Authorization for
Company code

EDO_PROC eDocument: EDO_PROC ESSIIDOC, ESSIIDEREG

Authorization for EDO_PRSTEP *
Process & Process Step

In order to run the Create eDocument Lists for VAT Register Books with SII (Spain) (RPFIES_SII_EDOCLIST) report
or the Create eDoc Lists for SII (Spain) (ESSII_EDOCLIST) transaction, the system checks if you have the
following authorizations:

Authorization Object Description Authorization Field Value

EDO_PROC eDocument: EDO_PROC ESSIIDOC, ESSIIBUN,

Authorization for ESSIIDEREG
Process & Process Step *
EDO_PRSTEP

EDO_BUK eDocument: BUKRS <as required>

Authorization for
Company code

For performing actions in the EDocument Cockpit (EDOC_COCKPIT) transaction you need to have corresponding
authorizations in the authorization objects EDO_BUK and EDO_PROC.

1.3 General Process Description of Electronic VAT Register

Books with SII

With the Electronic VAT Register Books with SII solution, you can submit data to the tax agency coming from the
following books:
o Incoming Invoices
o Outgoing Invoices
o Outgoing Payment to vendors on VAT Cash Accounting Scheme

This data has to be submitted as a "bundle", that is, in the form of lists mapped to XML messages.
These lists contain specific information about your company’s invoices.
Once the tax agency receives this information from you, it performs some checks and sends the information
about the results of these checks back to you in form of messages. These messages, however, give the status not
only to the lists but also to the invoices contained in the list

CUSTOMER
Electronic VAT Register Books with SII © 2016 SAP SE or an SAP affiliate company. All rights reserved. 9
In order to fulfill this requirement in the SAP system, you must first prepare the data you want to send. This
includes:
1. Creating eDocuments from the invoices that have to be included in the lists.
2. Creating the lists.

After performing these two steps, you submit the lists to the tax agency. For this, the lists are first sent to the SAP
Application Interface Framework (AIF), then to the SAP Cloud Platform Integration and finally the SAP Cloud
Platform Integration sends them to the system of the tax agency
After receiving the messages from the tax agency, you can view the response XML or correct possible errors and
send the information back to the tax agency again.

1.3.1 Creating eDocuments

In order to submit your data and receive messages from the tax agency, you must create eDocuments from your
different applications, for example, from accounting documents, SD documents or documents coming from MM.
In all cases, the eDocuments are created from the accounting documents. Therefore, if you create outgoing
invoices from SD, you must transfer the SD Billing to Accounting.
Reversal documents represent a special kind of eDocuments for this solution. For more information, refer to
Chapter 1.3.4.1.1 Creating eDocuments From Reversal Documents.

CUSTOMER Electronic VAT Register Books with SII (Spain)

10 © 2016 SAP SE or an SAP affiliate company. All rights reserved. Electronic VAT Register Books with SII
After you have checked the Customizing activities mentioned under Chapter 1.2 Prerequisites: Customizing, you
run the Create eDocuments for VAT Register Books with SII (Spain) (RPFIES_SII_EDOCCREATE) report or use the
Create eDocuments for SII (Spain) (ESSII_EDOCCREATE) transaction.
This report selects the accounting document types that are relevant for SII processes according to Customizing
and creates eDocuments from these.

For more information about this report, refer to the system documentation.

After you have created your eDocuments, you can display them and their eDocument type using the EDocument
Cockpit (EDOC_COCKPIT) transaction. To do so, select the following processes:

Process eDocument Type

Spain SII Documents SII Incoming Invoice

SII Outgoing Invoice

SII Outgoing Payment VoC

Spain SII Reversal Documents SII Incoming Invoice

SII Outgoing Invoice

You can check the eDocuments that have been created using the EDocument Cockpit (EDOC_COCKPIT)
transaction:
1. On the left hand side of the transaction’s first screen select the process Spain -> Spain SII Documents.
2. Select the eDocument you want to check. The eDocument has the status Created.
3. You can view the Invoice ID (that is the ID Number, Invoice Number, Invoice Date).
In case of foreign vendors, also the ID Type and ID Country
4. As an optional step, you can press Check eDocument. The system checks if the eDocument can be
inserted in a list. You can also check the information that is displayed in the different columns of your
eDocument.
For more information about the EDocument Cockpit (EDOC_COCKPIT) transaction refer to the documentation of
the transaction itself.
For more information about the actions you can perform within each process, press the Help icon.

1.3.1.1 Creating eDocuments From Reversal Documents

In some cases, an error cannot be fixed in the source document (for example when the wrong vendor, wrong date
was used). In these cases, the source document has to be reversed. To do so:
1. Reverse your source document using the corresponding transaction. For example, if it is originated from
SD, use the Cancel Billing Document (VF11) transaction. If it is originated from MM-IV, use the Cancel

CUSTOMER
Electronic VAT Register Books with SII © 2016 SAP SE or an SAP affiliate company. All rights reserved. 11
 Invoice Document (MR8M) transaction. If it is from FI, use the Reverse Document Header Data (FB08)
transaction.
2. Run the Create eDocuments for VAT Register Books with SII (Spain), (RPFIES_SII_EDOCCREATE) or the
Create eDocuments for SII (Spain) (ESSII_EDOCCREATE) transaction
and select the reversal documents. The report creates one eDocument for the reversal document. The
invoice ID of this eDocument is the same as the one of the eDocument of the reversed invoice.
3. Run the Create eDocument Lists for VAT Register Books with SII (Spain) (RPFIES_SII_EDOCLIST) report or
the Create eDoc Lists for SII (Spain) (ESSII_EDOCLIST) transaction again to include the eDocuments in a
list.
4. Submit the corresponding list again.

If the process is successful, as an answer from the tax agency, the list of the corresponding eDocument receives
the status Accepted, The corresponding eDocuments of the reversed and the reversal document receive the
status Deregistered. This means that the tax agency has accepted the reversal of the accounting document and
has accepted the deregistration request..
To correct the original error, you have to create a new accounting document (following our example, with the
correct vendor, date), create an eDocument for this, include it in a list and submit the list again.
If the eDocument of reversed document has not been sent to the tax agency (and it has, for example, the status
Created or Not Valid for Lists), the creation of the eDocument out of the reversal document will set the status of
both documents to Cancelled.

Note
 To check the eDocument of the reversed accounting document, you have to select the Spain SII Documents
process within the eDocument Cockpit transaction.
To check the eDocument of the reversal document, you have to select the Spain SII Reversal Documents
process within the eDocument Cockpit transaction.
 An eDocument will be created for a reversal document, only if the reversed document already exists as an
eDocument, or is selected in the same run of the Create eDocument Lists for VAT Register Books with SII
(Spain) (RPFIES_SII_EDOCLIST) report or the Create eDoc Lists for SII (Spain) (ESSII_EDOCLIST)
transaction.
 If only reversal documents are selected in the run of the Create eDocument Lists for VAT Register Books with
SII (Spain) (RPFIES_SII_EDOCLIST) report or the Create eDoc Lists for SII (Spain) (ESSII_EDOCLIST)
transaction and no eDocuments have been created yet for the reversed documents, no eDocuments will be
created.
 With the Change the Handling of Reversal Documents (FIESSII_REVOUTV view) Customizing activity you
can determine for each of your outgoing document types how you want to handle the corresponding reversal
documents when sending them to the tax agency. For more information, see Chapter 1.2.2 Customizing
Activities Specific for Electronic VAT Register Books with SII solution

CUSTOMER Electronic VAT Register Books with SII (Spain)

12 © 2016 SAP SE or an SAP affiliate company. All rights reserved. Electronic VAT Register Books with SII
1.3.2 Creating Lists of eDocuments

After you have created eDocuments from your relevant Accounting document types, you run the Create
eDocument Lists for VAT Register Books with SII (Spain) (RPFIES_SII_EDOCLIST) report or the Create eDoc Lists
for SII (Spain) (ESSII_EDOCLIST) transaction .
This report selects the eDocuments you have created and integrates them in lists, according to:
 the types the eDocuments belong to (Incoming, Outgoing or Outgoing Payments VoC), and
 the request type (that, is the reason) of communication you are establishing with the tax agency, that is a
registration, a modification or a deregistration of your data.

After you have created your lists, you can display them and their eDocument type using the EDocument Cockpit
(EDOC_COCKPIT) transaction. To do so, select the following process:

Process eDocument Type

Spain SII Lists SII Add/Modify Outgoing Invoice

SII Add/Modify Incoming Invoice

SII Deregister Outgoing Invoice

SII Deregister Incoming Invoice

SII Add/Modify Outgoing Payment VoC

You can check the lists that have been created using the EDocument Cockpit (EDOC_COCKPIT) transaction:
1. On the left hand side of the transaction’s first screen select the process Spain -> Spain SII Lists.
2. For example, you can select one list and press Display to show a preview of the corresponding XML file that
you will submit to the tax agency. You can also check the information that is displayed in the different
columns of your list.
3. You can check the eDocuments that are contained in a list by double clicking the eDocument Source Key
column of the list. On the next screen, double click the eDocument Source Key column to navigate to the
source document.

Once you create a list, the eDocuments included in it get the status Included in a list.
An eDocument with the status Included in a list is integrated in only one list. No double entries are possible.

You have the option to cancel a list before submitting it.

For more information about this report, refer to the online documentation.
For more information about the actions you can perform, press the Help icon.

CUSTOMER
Electronic VAT Register Books with SII © 2016 SAP SE or an SAP affiliate company. All rights reserved. 13
1.3.2.1 Correcting Data Before Submitting the Lists to the
Tax Agency

Before you submit your lists to the tax agency, you may have to correct some errors that were generated while
creating your lists. These errors refer to the eDocuments that the system tried to include in a list. These
eDocuments have then the status Not valid for a list.
In this case, you have to analyze the errors using the application log and correct them in the source accounting
document of the eDocument, master data or Customizing.
In some cases, the error can only be corrected by creating a reversal document of the source document.
For more information, refer to Chapter 1.3.1.1.1 Creating eDocuments From Reversal Documents
Then, when you submit the list where the eDocument is included, the system automatically uses the most current
data of the corresponding accounting document, so that you do not need to create this eDocument again. This is
the case, for example, when you have to correct the external invoice number of an accounting document.

1.3.3 Submitting the Lists to the Tax Agency

After you have created eDocuments and lists, you have to submit the lists to the tax agency.

You can submit the lists that you created in two ways:
 By selecting the Submit eDocument Lists check box on the selection screen of the Create eDocument Lists for
VAT Register Books with SII (Spain) (RPFIES_SII_EDOCLIST) report or the Create eDoc Lists for SII (Spain)
(ESSII_EDOCLIST) transaction. In this case, the lists are automatically submitted during the report’s run.
 Using the EDocument Cockpit (EDOC_COCKPIT) transaction. In this case, you have to select the Spain SII
Lists process, select your list and press Submit.

As the communication is synchronous, the lists get the final status based on the response from the Tax Agency.

Note
There might also be errors that occur before the list reaches the tax agency. In this case, the list receives the
status Communication error.

1.3.4 Receiving Messages from the Tax Agency

After you submit a list, the tax agency performs some checks on this list and sends back a message to you. The
list receives then one of the following statuses:

Accepted: This means that the tax agency found that the list and all its content are correct. The tax agency
registered all the items in the list.

CUSTOMER Electronic VAT Register Books with SII (Spain)

14 © 2016 SAP SE or an SAP affiliate company. All rights reserved. Electronic VAT Register Books with SII
Rejected: This means that the tax agency found that your entire list is incorrect.
Partially accepted: This means that the tax agency found some errors in some items of your list.

The corresponding eDocuments receive the following statuses accordingly:

Registered: The eDocument has no errors and has been registered by the tax agency
Rejected: The eDocument has errors and has not been accepted by the tax agency
Registered with errors: The eDocument has been accepted by the tax agency (and therefore registered) but it has
some errors that have to be corrected. The tax agency expects that you send a modification request.

For more information about the statuses, refer to 1.2.5 Description of Statuses

1.3.4.1 Correcting Errors After Submitting the Lists to the

Tax Agency

If your list shows the status Communication error:

1. Check for possible errors within the Application Interface Framework (AIF) and/or SAP Cloud
Platform Integration.
2. Analyze and correct these errors,
3. Submit your list again (press Submit button) or cancel it (choose More -> Cancel eDocument).

If your list gets the status Rejected (and the corresponding eDocuments get also the status Rejected):
1. Analyze the application log of the rejected eDocument within the eDocument Cockpit transaction.
2. Correct the errors in the source accounting document, master data or customizing.
3. In the eDocument Cockpit transaction select the rejected eDocument and press Change Status Manually.
This resets the status of the eDocument back to Created and your document can now be included in a list
again.
4. Run the Create eDocument Lists for VAT Register Books with SII (Spain) (RPFIES_SII_EDOCLIST) report or
the Create eDoc Lists for SII (Spain) (ESSII_EDOCLIST) transaction again to include the eDocument in a
list. Check that your eDocument has the status Included in a List.
5. Submit your list again.

If your list gets the status Partially accepted (and the corresponding eDocuments get the status Registered with
errors):
1. Analyze the application log of the erroneous eDocument within the eDocument Cockpit transaction.
2. Correct the errors in the source accounting document.
3. In the eDocument Cockpit transaction select the erroneous eDocument and choose More -> Edit. This
will set the status of the eDocument in Modification requested and your document is ready to be
included in a list again.

CUSTOMER
Electronic VAT Register Books with SII © 2016 SAP SE or an SAP affiliate company. All rights reserved. 15
 4. Run the Create eDocument Lists for VAT Register Books with SII (Spain) (RPFIES_SII_EDOCLIST)
report or the Create eDoc Lists for SII (Spain) (ESSII_EDOCLIST) transaction again to include the
eDocument in a list. The eDocument is included in a list of type Modification.
5. Submit your list.

In some cases, the error can only be corrected by creating a reversal document of the source document. For more
information, refer to chapter 1.3.1.1.1. Creating eDocuments From Reversal Documents.

For information about correcting the invoice ID, refer to Chapter 2.1.1 Correcting the invoice ID

1.3.5 Description of Statuses

1.3.5.1 Statuses of eDocuments Within the SII Document

Process

Status Meaning Possible Further Actions

Created (CREA) This is either:  You can include this eDocument

 The first status of an eDocument in a list using the Create
after it has been created. eDocument Lists for VAT Register
Books with SII (Spain)
 The status an eDocument gets
(RPFIES_SII_EDOCLIST) report or
when it had first the status Rejected
the Create eDoc Lists for SII
or Error and you chose Change
(Spain) (ESSII_EDOCLIST)
Status Manually in the eDocument
transaction.
Cockpit transaction.
 If you changed the status of the
 The status an eDocument recovers
eDocument manually and it gets
after being included in a list and
the status Created, you can
then being deleted from it.
include it in a list.

Included in a List (in proc.) The eDocument has been included in a Submit the corresponding list.
(BUND) list.

Cancelled (CANC) The source document has been You may want to create a new
reversed before the eDocument is eDocument instead.
submitted.

Registered (REGIS) The tax agency has sent a message
confirming that the eDocument has
been registered successfully.
This is the final status of an
eDocument, Usually no further actions
are requested. However, there can be
two possible follow-ups:
 You can request a modification.

CUSTOMER Electronic VAT Register Books with SII (Spain)

16 © 2016 SAP SE or an SAP affiliate company. All rights reserved. Electronic VAT Register Books with SII

Registered with Errors The tax agency has sent a message
(RERR) confirming that the eDocument has
been registered, but there are errors in
it. The tax agency therefore expects that
you send a modification request for this
eDocument.
Rejected (REJE) The tax agency has sent a message
informing that the eDocument has not
been accepted.
Modification requested You have corrected errors in the source
(RMOD) document and then chose More -> Edit
eDocument.
Not valid for Lists Before an eDocument is put in a list, the
(NVALID) system validates, for example, if the
invoice ID is complete. If it is not, it sets
the status of the Document to Not valid
for Lists
Deregistration Requested You have corrected an eDocument in
(RDREG) such a way, that you want it to be
deregistered on the system of the tax
agency. For example, you have changed
the invoice ID of your source document
and you want to deregister the
eDocument with the "old" invoice from
the system of the tax agency. The
Electronic VAT Register Books with SII © 2016 SAP SE or an SAP affiliate company. All rights reserved.
 You can request a deregistration
on the system of the tax agency.
 After you correct the errors, you
select the eDocument in the
eDocument Cockpit transaction
and choose More -> Edit
eDocument. The eDocument gets
then the status Modification
requested and is ready to be
included in a list.
 Another alternative is to request a
deregistration.
 If the error can be corrected
without reversing the document:
after correcting the error, you
select the eDocument in the
eDocument Cockpit transaction
and choose Change Status
Manually. The eDocument gets
the status it had before (either
Created or Modification
requested) and is ready to be
included in a list.
 If the error requires the source
document to be reversed, refer to
the chapter 1.3.1.1.1.
Your eDocument is ready to be
included in a list again. Run the Create
eDocument Lists for VAT Register
Books with SII (Spain)
(RPFIES_SII_EDOCLIST) report or the
Create eDoc Lists for SII (Spain)
(ESSII_EDOCLIST) transaction and
submit the list.
You can display the application log to
see the reason. Correct the error, and
submit the list.
You can include this eDocument in a
list using the Create eDocument Lists
for VAT Register Books with SII
(Spain) (RPFIES_SII_EDOCLIST)
report or the Create eDoc Lists for SII
(Spain) (ESSII_EDOCLIST)
transaction.
CUSTOMER
17
 eDocument is included in a list of the
type Deregistration.

Deregistered (DREG) The tax agency has sent a message You may want to create a new
confirming that it has accepted the eDocument.
deregistration request. Both the
reversed and the reversal documents
get this status.

New Invoice ID Detected You have corrected the invoice ID of an
(NEWID) original document, selected the
corresponding eDocument in the
eDocument Cockpit transaction and
chose More -> Edit eDocument. The
system detects that the Invoice ID has
changed.
Run the Create eDocument Lists for
VAT Register Books with SII (Spain)
(RPFIES_SII_EDOCLIST) report or the
Create eDoc Lists for SII (Spain)
(ESSII_EDOCLIST) transaction. The
eDocument is included in a list of the
type Deregistration and shows the old
invoice ID in the eDocument Cockpit
transaction.

1.3.5.2 Statuses of Lists within the SII Lists Process

Status Meaning Possible Further Actions

Created (CREA) This is the first status after You can display (get a preview) of the XML
creating a list. message that is to be submitted.
You can submit the list.

Accepted (ACCEP) The tax agency confirms that the No further actions needed. You can download
list has been accepted. the XML response that the tax agency sent back
to you.

Cancelled (CANC)
You selected the list and chose
More -> Cancel eDocument. You
may have done it, for example, to
avoid sending the list to the tax
agency.
You may want to create a list again.
Note
The eDocuments that existed in the list are not
deleted. But their status is changed back to the
previous status (for example, Created or
Modification Requested)

Communication Error There is a SOAP error in the Analyze the application log and the interface log.
(ERROR) communication. Correct the errors in both applications and
submit your list again.

Partially Accepted The tax agency confirms that the
(PACP) list has been accepted but some of
the items contain errors.
Correct the errors of the corresponding
eDocuments and run the Create eDocument
Lists for VAT Register Books with SII (Spain)
(RPFIES_SII_EDOCLIST) report or the Create
eDoc Lists for SII (Spain) (ESSII_EDOCLIST)
transaction. Submit your list again.

CUSTOMER Electronic VAT Register Books with SII (Spain)

18 © 2016 SAP SE or an SAP affiliate company. All rights reserved. Electronic VAT Register Books with SII
 Rejected (REJE) The tax agency did not accept your
list because it contains errors.
Analyze the errors in the eDocuments, correct
them, run the the Create eDocument Lists for
VAT Register Books with SII (Spain)
(RPFIES_SII_EDOCLIST) report or the Create
eDoc Lists for SII (Spain) (ESSII_EDOCLIST)
transaction and submit your list again.

1.3.5.3 Statuses of Reversal Documents in the Reversal

Documents Process

Status Meaning Possible Further Actions

Created (CREA) This is the first status of a reversal eDocument. You have to submit this
reversal eDocument to
Caution deregister the corresponding
reversed eDocument.
An eDocument of a reversal document is created
only if there is already an eDocument of the
corresponding reversed document or both
eDocuments are created during the same run of
the Create eDocument Lists for VAT Register
Books with SII (Spain) (RPFIES_SII_EDOCLIST)
report or the Create eDoc Lists for SII (Spain)
(ESSII_EDOCLIST) transaction.
The reversal eDocument has the same invoice ID
as the reversed eDocument.

Included in a List (in Proc.) The reversal eDocument has been successfully Submit the corresponding
(BUND) included in a list. list.

Not Valid for Lists The reversal eDocument contains errors that Analyze the application log of
(NVALID) prevent the system to include it in a list. the reversal eDocument and
correct the errors.

Cancelled (CANC) This is the status when an eDocument from a Final status. No further
reversal document is created for an eDocument actions required.
that has not been submitted to the tax agency.
Both eDocuments will get the status Cancelled
and will not be submitted to the tax agency.

Deregistered (DREG) The tax agency has accepted the deregistration Final status. No further
request. actions required.

Rejected (REJE) The tax agency did not accept the deregistration Analyze the application log
request and correct the errors. You
then select the eDocument in
the eDocument Cockpit
transaction and choose

CUSTOMER
Electronic VAT Register Books with SII © 2016 SAP SE or an SAP affiliate company. All rights reserved. 19
 Change Status Manually.
The eDocument can then be
put in a list again

CUSTOMER Electronic VAT Register Books with SII (Spain)

20 © 2016 SAP SE or an SAP affiliate company. All rights reserved. Electronic VAT Register Books with SII
2 Concepts

2.1 Invoice ID

The invoice ID is the key that the Tax agency uses to ensure the uniqueness of a document in their database within
the SII processes.
The invoice ID consists of the tax identification number of the issuer, the invoice number and the invoice date.
The invoice number can be determined in different ways, according to the source field we select to determine it.
For more information, refer to Customizing under Cross-Application Components -> General Application
Functions -> eDocument -> Spain -> Settings for Electronic VAT Register Books with SII -> Assign SII Attributes to
Accounting Document Types.
The invoice date is the one stored in the Document Date field (BKPF-BLDAT field) of the invoice.

Caution
The document date of incoming invoices should be the same as the date the vendor states in the invoice.
Otherwise, the tax agency cannot match your information with the information of your vendor.

For outgoing invoices, the issuer identification is your own tax number as entered in Chapter 1.2.3 Other
Customizing.
For incoming invoices, the issuer identification is the one of your vendor, as maintained in the master data.
It is very important to maintain the tax numbers and the names of your business partners.
In case of domestic business partners, the tax agency checks that the tax number and the name exist in their
registration database.
If an outgoing invoice to a domestic business partner is rejected by the tax agency because the tax number (NIF)
of the business partner is not registered (no censado), enter ‘X’ in the Tax Number 2 field of the master data of
the corresponding business partner. When the XML is submitted again to the tax agency, the system sets the tax
ID type to ‘07’ (Not Registered) for this business partner.

Caution
Because of the importance of the invoice ID for the tax agency, invoices with an incomplete invoice ID are rejected
by it. Therefore, the SAP system does not include eDocuments created from an invoice with an incomplete invoice
ID in a list. During the list creation, such eDocuments are identified and written into the application log. The
eDocument gets then the status Not included in a list.

CUSTOMER
Concepts © 2016 SAP SE or an SAP affiliate company. All rights reserved. 21
2.1.1 Correcting the invoice ID

Correcting the invoice ID of a source document means correcting all or some of the components of the invoice ID,
that is, its tax identification number of the issuer, its invoice number and/or its invoice date.
If you correct the invoice ID of a source document for which an eDocument already exists and this eDocument is
not included in a list yet, while including this eDocument in a list the system uses the most recent invoice ID of this
eDocument. This means, the system submits the already corrected invoice ID.
If you or the tax agency realizes that the invoice ID is incorrect or incomplete after you have sent your list:
1. Correct the invoice ID of the source document : In case of incoming invoices, you may also need to correct the
issuer tax identification number in the vendor master data
2. In the eDocument Cockpit transaction, select the Spain SII Document process.
3. Select the incorrect eDocument and choose More -> Edit eDocument. The eDocument gets the status New
Invoice ID detected. In the eDocument Cockpit transaction, you can still see the "old" (incorrect) invoice ID.
4. Run the Run the Create eDocument Lists for VAT Register Books with SII (Spain) (RPFIES_SII_EDOCLIST)
report or the Create eDoc Lists for SII (Spain) (ESSII_EDOCLIST) transaction. The eDocument is included in a
list with communication type Deregistration and gets the status Included in a List.
5. Submit your list. Your eDocument is submitted with the "old" (incorrect) invoice ID.
6. The list gets the status Accepted from the tax agency. This means, the tax agency confirms the deregistration
of this eDocument. In the eDocument Cockpit transaction, the eDocument gets again the status New invoice
detected, but it shows the new invoice ID.
7. Run the Create eDocument Lists for VAT Register Books with SII (Spain) (RPFIES_SII_EDOCLIST) report or
the Create eDoc Lists for SII (Spain) (ESSII_EDOCLIST) transaction again. The eDocument is now included in
a list of communication type Registration and gets the status Included in a List.
8. Submit your list.
9. The tax agency confirms this registration. The list gets the status Accepted and the eDocument gets the
status Registered with the "new" (corrected) invoice ID.

Caution
This procedure applies also if, after sending your list, you change any master data or Customizing settings that
influence the determination of the tax identification number, the invoice number and/or the invoice date.

2.2 Tax Reporting Date and Accounting Entry Date

In the case of incoming invoices, it is important to consider two different dates:

 The tax reporting date: this is the date that the system uses to determine the tax reporting period in the XML
message sent to the Tax Authorities.
 The accounting entry date: this is the date that the tax agency uses to determine the deadline to submit the
information about this invoice. The accounting entry date is also required in the XML message.

CUSTOMER Electronic VAT Register Books with SII (Spain)

22 © 2016 SAP SE or an SAP affiliate company. All rights reserved. Concepts
The SAP system uses as default for the reporting date, the posting date of the invoice; and as default for the
accounting entry date, the date stated in the Entry Date field of the invoice. However, for both cases, you can
also use the date you entered in the Entry Date field of your invoices instead.
To do so, refer to Customizing under Cross-Application Components -> General Application Functions ->
eDocument -> Spain -> Settings for Electronic VAT Register Books with SII -> Determine Dates for Incoming
Invoices. Note also that the customizing settings regarding these dates are valid for a whole company code.

Note
The reporting period/year is derived from the VAT date instead, if the following conditions are fulfilled:
 the tax code is a deferred tax code,
 VAT on Cash does not apply for your vendor, and
 VAT is due in the future (VAT date in the document is later than the posting date).

In the case of outgoing invoices, the SAP standard system uses the posting date to report them to the tax agency.
However, you can determine the reporting dates you want to use for new outgoing invoices, correction outgoing
invoices and outgoing invoices used for deregistrations. This influences the reporting year (tag <Ejercicio> and
the period (tag <Periodo> of the file you send to the tax agency. For more information, see Chapter 1.2.2
Customizing Activities Specific for Electronic VAT Register Books with SII solution .

2.3 Summary Invoice: Begin and End Number

In the case of summary invoices, you have to indicate a begin and an end number.
You can determine which begin and end number you use to submit this kind of invoices. For this, refer to
Customizing under Cross-Application Components -> General Application Functions -> eDocument -> Spain ->
Settings for Electronic VAT Register Books with SII -> Assign SII Attributes to Accounting Document Types.

Note
The Change Invoice ID for Invoice Summary (Business Add-In FIESSII_INVOICE_ID ) allows you to change
only the way the system fills some of the tags (<NumSerieFacturaEmisor> and
<NumSerieFacturaEmisorResumenFin> ) that refer to the begin and end number of invoices of the
invoice type Invoice Summary (F4) in the file you send to the tax agency. For more information, see
Chapter 1.2.2 Customizing Activities Specific for Electronic VAT Register Books with SII solution .

2.4 Tax codes

You have to identify which of the tax codes you use are relevant for SII. You also have to assign some attributes to
these tax codes. To do so, refer to Customizing under Cross-Application Components -> General Application

CUSTOMER
Concepts © 2016 SAP SE or an SAP affiliate company. All rights reserved. 23
Functions -> eDocument -> Spain -> Settings for Electronic VAT Register Books with SII -> Assign SII Attributes to
Tax Codes.

Note
An eDocument can only be created if the tax codes used for the source document are identified as relevant for SII.
All tax codes within a document must have the same type: either input or output tax codes. No eDocument is
created if the source document contains a mixture of input and output codes

2.5 VAT on Cash

The system creates an eDocument for a (deferred tax) transfer document only when the vendor is on Cash
Accounting Scheme (Voc). This eDocument represents then the outgoing payments for VoC scenarios.
The system does not create eDocuments for transfer documents for non VoC vendors.

CUSTOMER Electronic VAT Register Books with SII (Spain)

24 © 2016 SAP SE or an SAP affiliate company. All rights reserved. Concepts
www.sap.com/contactsap

© 2016 SAP SE or an SAP affiliate company. All rights reserved.

No part of this publication may be reproduced or transmitted in any
form or for any purpose without the express permission of SAP SE
or an SAP affiliate company.
SAP and other SAP products and services mentioned herein as well
as their respective logos are trademarks or registered trademarks of
SAP SE (or an SAP affiliate company) in Germany and other
countries. All other product and service names mentioned are the
trademarks of their respective companies. Please see http://www.
sap.com/corporate-en/legal/copyright/index.epx#trademark for
additional trademark information and notices.

Material Number: