Audit Report For France
Audit Report For France
Audit Report For France
ERP CLOUD
Table of Contents
1
1. Purpose of the document
This document explains the implementation and usage guidelines for the following report:
The document explains the prerequisite setup, report output details and the business flow.
You can use the Audit File for France process to create an electronic audit file to fulfill the legal reporting
requirements.
As of 1st January 2014 new rules require all companies, subject to tax in France and under audit by the
French tax authorities, to produce audit documentation in a prescribed electronic format. This is a
statutory requirement that complements the printed mandatory journals required by law; this
electronic audit file along with journals must be prepared according to the French GAAP (Generally
Accepted Accounting Principles).
The objective of fiscal authorities is to better target companies to be controlled; auditors can verify the
coherence between the audit file and the accounting being reported.
In this document we assume that you have already set up the following entities:
Data Security – Refer to the Fusion Security topical essay available on cloud.oracle.com
Enterprise Structure
Accounting and reporting sequences if used
You should complete the ‘Implementation Project’ for your organization before using the Audit File for
France process. If you require further details, refer to the Analyze and Report section of Oracle
Financials Cloud (Get Started) web site.
3. Reporting
The Audit Report for France process does not require any additional feature specific setup.
You have to enter, process and account all your subledger transactions. Also all manual journals have to
be entered and processed for the reporting period. There are no specific attributes that you have to
enter on the subledger transactions or journals for them to be reported.
The Audit Report for France does not include journal lines entered in STAT currency.
2
To run the process you have to submit the Audit Report for France job on the Scheduled processes UI.
Ledger – enter the ledger name that you are reporting on. The available values are dependent on the
data access set assigned to your user.
Legal Entity – the values are restricted to the legal entities associated with the ledger. Leave it blank to
report on all the data in the ledger regardless of the legal entity.
3
Show adjustment periods – enter ‘Yes’ if you want to include data from adjustment periods in the
report run, otherwise select ‘No’.
From/To Period – specify the range of periods you want to run the report for.
Journal Entry Source – Leave it blank to report on all sources at the same time or specify a single source
(e.g. Payables, Receivables, Assets etc.) to be included in the data file.
Account filter – using this parameter you can restrict the account code combinations that will be
included into the data file.
Accounting Sequence Name – enter the sequence name if you want to restrict what journal lines to
include in the electronic file.
Posting status – select the posting status whether you can to see only posted journals or also journals
that are transferred, but not yet posted from the subledgers.
Report Order by – specify if you want to report to list accounting or reporting sequences.
You can have the output file saved as a text, data or .csv file.
For review purposes you can open the file in an excel spreadsheet.
4
The table below describes the data elements included in the file.
5
Oracle Corporation, World Headquarters Worldwide Inquiries
500 Oracle Parkway Phone: +1.650.506.7000
Redwood Shores, CA 94065, USA Fax: +1.650.506.7200
CONNECT W ITH US
blogs.oracle.com/oracle
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
facebook.com/oracle 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
twitter.com/oracle 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.
oracle.com
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. 1017