We use a third party cloud based reporting solution for preparing and filing our SEC reports,and up until the middle of last year,we primarily relied upon the XBRL customer support team from thethird party vendor to plete the XBRL tagging for our filings.We decided it would be best at that point in time as we were learning how to use the new reporting solution and wanted to stay focused on making sure the edgar piece of the filings were set up appropriately.

After we became more fortable working with the reporting solution,we decided to start working on our own tagging.The tagging was already set up from prior periods in the reporting solution so it was much easier to work on than if we would have had to set up the tagging pletely on our own.But still,it was challenging understanding the setup of the detailed taxonomy.

The reporting solution has a training program that we pleted prior to working on our XBRL.In my own personal experience,i think i went through the training twice,and felt pretty fortable,but still lacked the practical experience.I learned all the ncepts ahead of time,but when i started tagging there was still a steep learning curve.There are many tables that have different levels of ncepts layered in specific patterns,and i wanted to make sure that i was understanding the set up and using the right ncepts.Initially,i relied on the advice of the XBRL customer support team,but over time i became increasingly fortable.Our reporting solution made it easy for me to look at the XBRL ncepts and where they fall into the outline,as well as an easy way to view the document tagging i was working on.

On the SEC web there is a helpful XBRL Previewer tool that reads tagged data and provides a nice,readable format of the XBRL tagging.Using this tool makes it easy to understand exactly what has been tagged,as opposed to trying to prehend unformatted XBRL ding,which is very difficult to learn and hard to read.Within our reporting solution is an SEC viewer tool,similar to the SEC web previewer tool,which we use extensively to ensure that our tagging is appropriate.The reporting solution also has a summary report to check all of our calculations,as well as a validation tool to scan for errors.Our reporting solution can generate various different reports that can be used to ensure our tagging is rrect;however,we mostly rely on the SEC previewer tool,calculation summary reports and validation tools because they pretty much tell the whole story.

Over time we have gained a better understanding of the various levels of the XBRL structure,which set up the overall framework for the tagging.The structure nsists of level one tagging,which is the tagging for the basic financial statements,block tagging of notes and schles and document/entity information.Level two is the acunting policy tagging,level three is the block tagging of the tables throughout the footnotes,and level four is the detail tagging in the notes and schles.Additionally,all ncepts must at least have an abstract (or parent)and child.This can be further subdivided and detailed into three types of patterns;basic,dimensional,or roll-forward.

After we got a good handle on the XBRL structure we started to develop internal ntrol checklists to ensure we were nsistent with reviewing our tagging before we filed.There are many helpful materials available on the web,but we used mainly template checklists within our reporting solution and the AiCPA’s June 1,2011“Proposed Principles and Criteria for XBRL-Formatted information”to help us determine the appropriate items to include.After we prepared the checklist we went through various stages,printing out and documenting more than was necessary.since then,we have been able to refine this process to allow for a more reasonable level of documentation which basically nsists of the following:each individual financial statement or footnote includes an XBRL ntrol checklist to ensure that the tagging is reviewed at all angles and saved for support,and an overall document review checklist is pleted and saved prior to filing.Finally,a print out of the entire document tagging is saved in the SEC previewer format and kept as a permanent hard py.

Despite our tagging experience,we still run into new challenges.My pany recently acquired another financial institution which required us to tag a new business bination footnote,as well as rearrange one of the largest footnotes in our 10Q.Even though our XBRL is pleted in-house,we asked the XBRL customer support team with our reporting solution to review our tagging to make sure that the outline was set up in the best manner possible.The challenge with XBRL ours whenever there is change –a change in USGAAP,a change in your pany’s acunting policies or a change to your actual pany –as it requires a lot of additional work.Having that extra fort level of a third party specialist is very helpful.

One thing that is also very helpful to us is to review our tagging during the process of preparing our filing,as opposed to waiting until the end.One of the challenges with XBRL is to make sure that you stay on of changes to the footnotes or financial statements after it has been tagged.Changes can go through at any given time and it is necessary to develop a process to make sure that someone is designated to go back in and review prior to filing to ensure nothing is missed.

The first time we migrated taxonomies was from 2011 to 2012,and it was a major task with which we were unfamiliar.However,the migration to the 2013 taxonomy was much simpler because we were familiar with the process.Overall it took half an hour for the actual migration.The rest of the process,which is ensuring that the nverted tags are rrect or new tagging is pleted,can be done at a later time before you file.

CERTIFICATION PROGRAM

Our Assistant ntroller and i are currently working on pleting an AICPA XBRL Certification urse to gain credentials,as well as build on our knowledge of XBRL.I’ve only pleted two modules so far but the urse seems pretty prehensive.I am hoping that the urse has actual hands on exercises to help solidify ncepts,as this seems to be the main thing that is lacking in most of the other urses or study materials i have researched.

I think that the program provides an extraqualification aspect to XBRL by requiring the participant to be tested to ensure ncepts are understood.Right now i am working on a piece of the urse that emphasises extension ncepts,and focuses in on the appropriate use of them,which i find very helpful.

UNIVERSAL STANDARDS

The expectation that the us GAAP taxonomy will ver every nuance of every pany is unrealistic.There probably will always be special types of products or instruments that are unique to some panies,or similar products within the panies that have to be differentiated.A pany may have a product that is similar to many other industries,but there uld be specific nuances to them that make them unique.For example,our pany has certain investments that are broadly vered in the USGAAP taxonomy,but require specific detailed information to differentiate them from other similar investments within our portfolio.It is very hard to get down to the fine grain of every product for every pany within the taxonomy.

I think if you understand the overall structure and how the tables are set up you are well on your way to being proficient at XBRL.You should also research other panies’taxonomies,as well as your own prior filings,and make sure you can properly navigate the us GAAP taxonomy.This will allow you to choose the appropriate ncepts and create extensions on a limited basis –when needed.

SBR

Technically it sounds like a great idea to have all SEC and regulatory filings machine readable,but when you are involved in the actual tagging process you see just how much time is involved in setting up and maintaining the tags.Requiring more types of documents to be XBRL tagged nceptually sounds like a good idea,but is it really feasible?right now only the SEC financial statements and footnotes are required to be tagged,and i am hoping it stays that way for a while.Our pany has a well-defined process in place for tagging our seC financial statements and footnotes.If additional tagging is required in other areas of our seC filings,or if it became a requirement in other regulatory filings,it will require additional time and internal resources.

中文新闻：XBRL财务报告报送者的学习曲线

原文链接：