Transcript Presentación de PowerPoint

How to integrate XBRL technology in your company
with a minimal impact (José Vilata, EDICOM)
Objectives
• To show how we can integrate incoming and outgoing XBRL
documents in existing systems with a minimal impact on
current applications.
• We will develop a mapping that will convert data from two
related tables in Microsoft Access to an XBRL instance
document using drag-and-drop techniques.
• Also, we will show EDICOM XBRL tools, web based user tools
for managing XBRL instance documents and XBRL taxonomies
with a lot of friendly wizards.
The scenario
• Normally we’ll have some existing applications that store the
data in some customised format and we will need to transform
that data to XBRL documents with minimal impact and cost
INTERNAL
SYSTEM WITH
OWN DATA
DO SOMETHING
TO OBTAIN XBRL
DOCUMENTS
XBRL
DOCUMENTS
How can we make this transformation
with a minimal impact on our existing
systems ?
The solution: a mapper
• A solution to the previous problem is to use a mapping tool
like EDICOM EBIMAP XBRL to do that:
INTERNAL
SYSTEM WITH
PROPRIETARY
DATA
XBRL
DOCUMENTS
EBIMAP will access the existing data in
any format and will convert it to any
other format such as XBRL
How does the Mapper work ?
• A Mapper performs data transformations
• Each transformation consist of :
– a source data schema,
– a destination data schema
– and a set of rules that enables us to convert the original structure
into the target (the map).
SOURCE DATA
STRUCTURE
(TEXT,DB,XML,…)
TRANSFORMATION
RULES
TARGET DATA
STRUCTURE
(XBRL,XML,TEXT,
DB,ETC.)
What is a data schema ?
• A data schema represents the structure of the data that:
– We use as the source for the transformation, usually the
representation of the company data structure in their own format
– We use as the target of the transformation.
An example: We have created the
schema of this Access table in EBIMAP
Another schema example: an XBRL taxonomy
• We will use an example taxonomy that represents the
accounting movements of the company: AccountMov
XBRL taxonomy as a schema in EBIMAP
• The XBRL taxonomy is loaded automatically as a data schema
Transformation (mapping)
• The mapping is a set of rules that enables us to convert the
original structure into the target
• To do the mapping we only need to specify the source and target
data schema
Transformation (mapping) (II)
• Usually the mapping is constructed without any coding
• We link the elements with drag-and-drop techniques
• Also, we can use a complete scripting language for more complex
transformation
Result
• We only need to run the “map” to see the results of the
transformation
Integration with current systems
• One we have seen how we can transform our internal data to
XBRL documents, we need to integrate this process in our
applications
• We can choose between:
– Using API: JAVA, WINDOWS (implements Web Services).
– Using line commands
Public Function ExecuteEBIMAP(strSourceData As String, strTargetData As String,
strMapping As String, strFilter As String)
For example:
ExecuteEBIMAP (“”, “c:\targetDir\,”AccountingToXBRL.ma4”, “”)
In this case we only need to fill in the name of the mapping (“AccountingToXBRL”) and
the target directory where the files resulting from the transformation will be written. The
source data comes from data base and so it is configured in the map.
Taking XBRL integration one step forward
• Once our company can manage incoming and outgoing XBRL
documents we need to give access to company users of these
reports in an easy way
• EDICOM provides the EBI XBRL EDITION suite to do that.
• It is composed of:
–
–
–
–
An XBRL taxonomy editor and repository
An XBRL instance and taxonomy parser and validator
An XBRL instance document data base repository
A communication server with multiple protocols (Web services, HTTP,
FTP, SMTP, etc.)
– A specialised security module that enables digital signature and
encryption
– A Web based user interface to easily manage and deploy the XBRL
technology in our company
EBI XBRL EDITION overview
• A common EBI XBRL EDITION installation could be as follows:
INTERNAL
MANAGEMENT
SYSTEM
INTERNAL XBRL
COMPANY USERS
WEB
SERVICES
UNIVERSAL
VALIDATOR AND
REPOSITORY
MANAGER
SECURITY AND
COMMUNICATION
MODULE
WEB USER
INTERFACE
REPOSITORY
OTHER PARTNERS
WEB INTERFACE EXAMPLE
• The users will access an environment like this:
• The user can “import”, “export”, “print”, “delete” and “edit” all the documents
depending on the permission he has
•He can see and review all the documents that the system is processing
automatically
• All the environment can be customised (colours, folders, buttons, etc.)
XBRL TAXONOMY EDITOR overview
• The suite provides a web based XBRL TAXONOMY EDITOR
The editor has a lot of user helps and wizards to aid in the creation of taxonomies
CONCLUSION
• We have seen how we can integrate incoming and outgoing XBRL
documents in existing systems with a minimal impact on current
applications.
• We have seen that there are existing tools like EBI XBRL EDITION
that help us to do that
• We have seen that we have tools to deploy XBRL technology in
our company in an easy way
SO,
It is time to roll out XBRL technology in our companies,
there is no technical reason not to do it !!!
Many thanks !!!
José Vilata
[email protected]
www.edicomgroup.com