Retroactive Reporting

Use retroactive reporting to report VAT transactions in any given range for which the company has not already submitted VAT data online.

Retroactive reporting includes required and optional setups.

Setup Required for Retroactive Reporting

Here is the setup list required for retroactive reporting:

• Lookup Type: ORA_JEES_SII_RETROACTIVE_DATES

• Lookup Codes: The default lookup code is ORA_EFFECTIVE_DATES, with the start date as January 1, 2017 with the Retroactive option enabled. The application automatically assumes June 30, 2017 as the end date. You can change the dates, or disable the original line and add a new range.

  Note: Enable only one lookup code before you run retroactive reporting.

• Application and Party Level Lookups: The application and party level default value are the same for normal and retroactive reporting.

• Global Descriptive Flexfields: You don't need additional transaction level global descriptive flexfields for Online VAT Reporting for Spain. Changes in global descriptive flexfields are only for the retroactive data that has been reported through Modelo reporting. These Modelo contexts are predefined:

  • JE_ES_MODELO347

  • JE_ES_MODELO347PR

  • JE_ES_MODELO349

  • JE_ES_MODELO415_347

  • JE_ES_MODELO415_347PR

Optional Setup

Consider these actions before you run retroactive reporting:

• To assign user-defined attributes to any of the invoices in the retroactive date range, such as document type override, query the transactions and update the necessary changes in the Regional Information tab with Online VAT Reporting for Spain. Don't make any other SII changes to your transactions.

• Ensure the application and party level defaults are complete.

• If you have excluded supplier or customer accounts or sites from selection and if you have exceptions for these third parties and sites, query the corresponding transactions in both Payables and Receivables and select E in the Regional Information field.