DAS2 Reporting for France

Transcription

1 ERP CLOUD DAS2 Reporting for France Oracle Financials for EMEA Table of Contents 1. Purpose of the document Assumptions and Prerequisites Feature specific setup... 3 Legal Entity Registration... 3 Supplier registration... 4 Entering the SIRET number... 4 Enabling an income tax reporting site Transaction entry... 5 Prepayment handling DAS2 Verification Extract for France Manage French DAS210 Information DAS2 Type 210 Updates Report for France Manage French DAS2 Summary UI DAS2 Extract File Report for France DAS2 Contractor Letters Report for France Appendix A Appendix B

2 1. Purpose of the document Companies in France that do business with independent and tax registered contributors must declare to the tax authorities all payments made each year. These third party payments include fees, commissions and rebates. The company submits this information to tax authorities in a formatted, electronic file. This file contains information about the yearly totals paid for each supplier invoice by DAS2 reporting tax category. This document explains the implementation and usage guidelines for the DAS2 functionality for France including the following components: DAS2 Verification Extract for France Generates French DAS2 contractor and income tax information from data entered in Oracle Payables and extracts information into the DAS2 temporary tables automatically submitting the DAS2 Verification Extract Execution Report for France. DAS2 Verification Extract Execution Report for France Generates output file for the information extracted by the DAS2 Verification Extract for France process. DAS2 Type 210 Updates Report for France Generates a list of all changes to the French DAS2 data made since the last run of the verification report. DAS2 Extract File Report for France Generates the DAS2 electronic file that is submitted to the tax authorities. DAS2 Contractor Letter Report for France Generates letters to all French contractors and contributors whose income is reported in the DAS2 extract file for the current year. The document explains the prerequisite setup, transaction entry aspects, report output details and the business flow for the DAS2 feature. 2. Assumptions and Prerequisites Before performing the feature specific setup you have to set up the following entities: 2

3 Data Security Refer to the Fusion Security topical essay available on cloud.oracle.com Geographies Enterprise Structure Balancing segment value (BSV) assignment to the legal reporting unit or legal entity Suppliers Procurement Business Function Common Options for Payables and Procurement You should complete the Implementation Project for your organization before commencing the Feature Specific Setup outlined below. If you require further details, refer to the Analyze and Report section of Oracle Financials Cloud (Get Started) web site. 3. Feature specific setup Legal Entity Registration Navigation: Navigator > Setup and Maintenance Task name: Manage Legal Entity Registration Enter the first party SIREN number on the Manage Legal Entity Registration UI. The SIREN field is country specific and will appear for Legal Entities that are registered in France (Territory = France). Save and go to task Manage Legal Entity Financial Information. Enter the APE (Activite Principale de l'entreprise) or NAF (Nomenclature des Activités Françaises) code that is used in DAS2 reporting. 3

4 Supplier registration Navigation: Navigator > Procurement -> Suppliers For DAS2 reporting purposes, a supplier has to have an address in France and have a contact registered for the site. Entering the SIRET number The SIRET number is a numerical identifier for businesses in France. It proves that a business is registered for the type of work they are offering to do. The SIRET number is stored in the following location: Navigation: Navigator > Procurement -> Suppliers -> Profile -> Income Tax (tab) You have to select France as the taxpayer country and enter the SIRET number in the Taxpayer ID field. There is no system validation on the Taxpayer ID field. Check the Federal reportable checkbox and select an income tax type that is defaulted on every invoice line at the time of invoice entry. You can change the default value or delete it. 4

5 Enabling an income tax reporting site You have to enable a supplier site as income tax reporting site. This site and address is used as the supplier address on the DAS2 reports. 4. Transaction entry Navigation: Navigator > Payables -> Invoices -> Create Invoice Enter basic invoice details like supplier/site, invoice number, amount, invoice and accounting date. Choose an income tax type that is recognized by DAS2 at invoice line level. If the income tax type is entered at supplier level, the value is defaulted to the invoice line level. The default value can be updated on deleted according to the DAS2 reporting category being invoiced. 5

6 Use one of these available French DAS2 codes: AVAN/A Fringe Benefits - Other AVAN/L Fringe Benefits - Housing AVAN/N Fringe Benefits - Food AVAN/V Fringe Benefits - Car DAU/AR Miscellaneous - Other DCO/CO Miscellaneous - Brokerage Fees DCOM/C Miscellaneous - Commissions DDA/DA Miscellaneous - Royalties DDI/DI Miscellaneous - Inventor's Fees DHON/H Miscellaneous - Fees DJE/JP Miscellaneous - Director's Fees DRIS/R Miscellaneous - Rebates INDE/F Indemnities and Reimbursements - Lump Sum INDE/P Indemnities and Reimbursements - Payment by the Employer INDE/R Indemnities and Reimbursements - On Supporting Documents 6

7 RETE/D Withholding Tax Exemption According to International Conventions RETE/R Withholding Tax - Reduced Rate COTIS Contributions to Pension Funds (to be Deducted) TVA/47 VAT on Royalties (to be Deducted) TVA/55 VAT on Royalties (to be Added) The other codes, like MISC2 for example are for United States and not to be used for French DAS2. Validate and pay the invoice. For DAS2 reporting purposes it is not required for the invoice to be accounted. See another example of an invoice bellow with a different income tax type assigned. 7

8 The income tax type entered at line level defaults to distribution level. 8

9 Validate and pay the invoice. 9

10 Prepayment handling There are two different ways prepayment can be handled by DAS2 reporting 1. In some instances you consider payables prepayment transactions as a pre-invoice. In this case you have to enter the prepayment with the income tax type populated and the prepayment is reported on the DAS2 reports after it is paid. As the prepayment transaction is reported when it is paid the prepayment applications are not reported to avoid reporting duplicate amounts. It is especially important when the prepayment is reported in one tax year (i.e. 2014), but the prepayment application happens only during the next tax year (i.e. 2015). Therefore if an invoice is fully paid by a prepayment application, the invoice will not appear on the DAS2 reports (as the full amount of the prepayment has been reported when the prepayment was paid). If the invoice is partially paid by the prepayment application, the portion of the invoice that is paid directly is reported by DAS2 as of the payment date 2. If the prepayment transaction is an advanced payment, the prepayment does not appear on the DAS2 reports until the prepayment is applied to an invoice with a DAS2 related income tax type. As the prepayment transaction is not reported when it is paid the prepayment application is treated as a payment against the invoice and the amount of the prepayment application is reported as of the application date. Some worked use cases are included in the appendix section of this document. 5. DAS2 Verification Extract for France Navigation: Navigator > Tools -> Scheduled Processes When all transactions are entered, validated and paid for the reporting year, submit the DAS2 Verification Extract for France 10

11 The Tax for salaries parameter is used to set a value in the electronic file that cannot be derived from any other source. The DAS2 Verification Extract Execution Report for France is automatically submitted and creates an output file that can be used to review the data extracted. 11

12 The report lists all invoices that are eligible for the reporting year. The report contains only the lines where the income tax type was entered i.e. it excludes transaction tax lines if they have no income tax type specified. The invoices are rounded to integer and listed by reverse chronological order by the payment date. 6. Manage French DAS210 Information Navigation: Navigator > Payables -> Invoices -> DAS2 Information for France -> Manage DAS210 Information for France If you want to access these UIs your user must have access to at least one business unit that is registered under French jurisdiction. You can also review and modify the DAS2 information on the Manage DAS210 Information for France UI. Any modifications on this UI are reported on the Type 210 Updates Report for France. 12

13 Query on extracted information based on the Legal Entity 13

14 The amounts displayed can be modified. 7. DAS2 Type 210 Updates Report for France Navigation: Navigator > Tools -> Scheduled Processes For audit purposes, submit the DAS2 Type 210 Updates Report for France. The report displays any changes you made on the DAS210 Information for France UI. 14

15 The report output shows the old and new values for the updated amounts. 8. Manage French DAS2 Summary UI Navigation: Navigator > Payables -> Invoices -> DAS2 Information for France -> Manage DAS210 Summary for France When all the changes are done, you can review the information to be reported on the Manage DAS2 Summary for France UI. 15

16 9. DAS2 Extract File Report for France Navigation: Navigator > Tools -> Scheduled Processes Submit the DAS2 Extract File Report for France to create the electronic file. 10. DAS2 Contractor Letters Report for France Navigation: Navigator > Tools -> Scheduled Processes Submit the DAS2 Contractor Letter Report for France to create the letters for suppliers. It contains all the information reported to the tax authorities. 16

17 11. Appendix A A reference document about DAS2 legislation can be find here: 17

18 12. Appendix B You can find below some use cases that illustrate how prepayments and their application is reported in DAS2. 1. Prepayment that does not have a DAS2 related income tax type assigned is never reported itself. Case 1 Prepayment PREP01 is created as of 1-Dec-2011 for the amount of EUR 1,196 (Item EUR 1,000, Tax EUR 196). Income tax type is blank or has a non-das2 related value. Prepayment PREP01 is paid as of 5-Jan Prepayment PREP01 is not reported for Prepayment PREP01 is not reported for When a prepayment with no DAS2 related income tax type is partially or fully applied to an invoice that has DAS2 related income tax type, the invoice is reported (partial or full amount depending on the payment status) as per the date of application. Case 2.1 Prepayment PREP02 is created as of 1-Dec-2011 for the amount of EUR 1,196 (Item EUR 1,000, Tax EUR 196). Income tax type is blank or has a non-das2 related value. Prepayment PREP02 is paid as of 5-Dec Invoice INV01 is created as of 2-Jan-2012 for EUR 1,196 (Item EUR 1,000, Tax EUR 196). Invoice INV01 has AVAN/L (fringe benefit housing) assigned as income tax type Prepayment PREP02 is fully applied to invoice INV01 as of 10-Jan-2012 and INV01 is now fully paid Neither transaction is reported for INV01 is reported under code AVAN/L amount EUR 1,000 for 2012 (as per prepayment application date). Case 2.2 Prepayment PREP03 is created as of 1-Dec-2011 for the amount of EUR 1,196 (Item EUR 1,000, Tax EUR 196). Income tax type is blank or has a non-das2 related value. Prepayment PREP03 is paid as of 5-Dec Invoice INV02 is created as of 2-Jan-2012 for EUR 3,588 (Item EUR 3,000, Tax EUR 588). Invoice INV02 has AVAN/L (fringe benefit housing) assigned as income tax type Prepayment PREP03 is fully applied to invoice INV02 as of 10-Jan-2012 and INV02 is now partially paid. Neither transaction is reported for INV02 is reported under code AVAN/L amount EUR 1,000 for 2012 (as per prepayment application date). 18

19 Case 2.3 Prepayment PREP04 is created as of 1-Dec-2011 for the amount of EUR 1,196 (Item EUR 1,000, Tax EUR 196). Income tax type is blank or has a non-das2 related value. Prepayment PREP04 is paid as of 5-Dec Invoice INV03 is created as of 2-Jan-2012 for EUR 3,588 (Item EUR 3,000, Tax EUR 588). Invoice INV03 has AVAN/L (fringe benefit housing) assigned as income tax type Prepayment PREP04 is fully applied to invoice INV03 as of 10-Jan-2012 and INV03 is now partially paid. The outstanding amount of EUR 2,392 is paid by check as of 15-Jan Invoice INV03 is now fully paid Neither transaction is reported for INV03 is reported under code AVAN/L amount EUR 3,000 for Prepayment that has a DAS2 related income tax type assigned is reported by DAS2 after it has been partially or fully paid. In case of partial payment, a proportionate value of the item line(s) is reported. The prepayment is reported in the period when the payment was made. Case 3.1 Prepayment PREP05 is created as of 1-Dec-2011 for the amount of EUR 1,196 (Item EUR 1,000, Tax EUR 196). Income tax type has AVAN/L as income tax type assigned to the item. Prepayment PREP05 is paid as of 5-Jan Prepayment PREP05 is not reported for Prepayment PREP05 is reported under code AVAN/L for Case 3.2 Prepayment PREP09 is created as of 1-Dec-2011 for the amount of EUR 3,588 (Item EUR 3,000, Tax EUR 588). Income tax type has AVAN/L as income tax type assigned to the item. Prepayment PREP09 is partially paid as of 5-Dec-2011, payment amount is EUR 1,196. Prepayment PREP09 is fully paid as of 10-Jan-2012, payment amount is EUR 2,392. Prepayment PREP09 is reported under code AVAN/L with an amount of EUR 1,000 for Prepayment PREP09 is reported under code AVAN/L with an amount of 2,000 for When a prepayment with DAS2 income tax type assigned is applied to an invoice that has DAS2 related income tax type the prepayment application is not reported. If the invoice is fully paid by the prepayment, it does not appear on the DAS2 reports. If the invoice is partially paid, it appears on the DAS2 reports when full payment is received, but the reported amount excludes the prepayment application amount. 19

20 Case 4.1 Prepayment PREP06 is created as of 1-Dec-2011 for the amount of EUR 1,196 (Item EUR 1,000, Tax EUR 196). Income tax type has AVAN/N (Fringe benefit food) as income tax type assigned to the item Prepayment PREP06 is paid as of 5-Dec Invoice INV04 is created as of 2-Jan-2012 for EUR 1,196 (Item EUR 1,000, Tax EUR 196). Invoice INV04 has AVAN/L (fringe benefit housing) assigned as income tax type Prepayment PREP06 is fully applied to invoice INV04 as of 10-Jan-2012 and INV04 is now fully paid PREP06 is reported under code AVAN/N for INV04 is not reported for either 2011 or Case 4.2 Prepayment PREP07 is created as of 1-Dec-2011 for the amount of EUR 1,196 (Item EUR 1,000, Tax EUR 196). Income tax type has AVAN/N (Fringe benefit food) as income tax type assigned to the item line. Prepayment PREP07 is paid as of 5-Dec Invoice INV05 is created as of 2-Jan-2012 for EUR 3,588 (Item EUR 3,000, Tax EUR 588). Invoice INV05 has AVAN/L (fringe benefit housing) assigned as income tax type Prepayment PREP07 is fully applied to invoice INV05 as of 10-Jan-2012 and INV05 is now partially paid. PREP07 is reported under code AVAN/N for 2011 with the amount of 1, INV05 is not reported for either 2011 or Case 4.3 Prepayment PREP08 is created as of 1-Dec-2011 for the amount of EUR 1,196 (Item EUR 1,000, Tax EUR 196). Income tax type has AVAN/N (Fringe benefit food) as income tax type assigned to the item. Prepayment PREP08 is paid as of 5-Dec Invoice INV06 is created as of 2-Jan-2012 for EUR 3,588 (Item EUR 3,000, Tax EUR 588). Invoice INV06 has AVAN/L (fringe benefit housing) assigned as income tax type Prepayment PREP08 is fully applied to invoice INV06 as of 10-Jan-2012 and INV06 is now partially paid. The outstanding amount of EUR 2,392 is paid by check as of 15-Jan Invoice INV06 is now fully paid PREP08 is reported under code AVAN/N for 2011 with the amount of 1, INV06 is reported under code ANAN/L for 2012 with the amount of EUR 2,

21 Oracle Corporation, World Headquarters Worldwide Inquiries 500 Oracle Parkway Phone: Redwood Shores, CA 94065, USA Fax: C O N N E C T W I T H U S blogs.oracle.com/oracle facebook.com/oracle twitter.com/oracle oracle.com Copyright 2017, Oracle and/or its affiliates. All rights reserved. This document is provided for information purposes only, and the contents hereof are subject to change without notice. This document is not warranted to be error-free, nor subject to any other warranties or conditions, whether expressed orally or implied in law, including implied warranties and conditions of merchantability or fitness for a particular purpose. We specifically disclaim any liability with respect to this document, and no contractual obligations are formed either directly or indirectly by this document. This document may not be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without our prior written permission. Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners. Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group White Paper Title October