XBRL Text Block Tagging; Easy as 1, 2, 3

June 3rd, 2009 by Brian Larson, CPA - Software Quality Engineer

With the SEC’s final ruling on XBRL issued earlier this year, the commission made a decision that a filer’s first year filing shall include the footnotes and financial statement schedules tagged in blocks of text (http://www.sec.gov/rules/final/2009/33-9002fr.pdf pg 7, but labeled as pg 6781). This decision greatly simplifies the tagging process in the first year. In subsequent years, each filer will be required to create a more detailed filing but that’s a subject for another day. Let me show you how easy it is to create text blocks for your notes using Rivet Dragon Tag and CrossTag software.

Read the rest of this entry »




Rivet’s Summary of the 2009 US GAAP XBRL Taxonomy

June 2nd, 2009 by Christy Rohrs, CPA - Director of Corporate Compliance and Reporting

A Quick User’s Guide for Preparers

There are a lot of questions going around right now about when companies should be using the 2009 US GAAP Taxonomy for their XBRL filings. Per the Edgar Filer Manual located on the SEC website (http://www.sec.gov/info/edgar/edmanuals.htm), Edgar is anticipating being able to handle the 2009 Taxonomy in the third quarter of their fiscal 2009 year which is 6/30/09:

It is anticipated that in the third quarter of Fiscal Year 2009, EDGAR Release 9.15.2 will introduce the following changes: 1) the existing US GAAP Taxonomy will be upgraded to 2009 US GAAP Taxonomy. 2) The US GAAP Beta 2.0 Taxonomy will no longer be supported and 3) Submission Type SH-ER Information Table XML documents will be validated against the schema included in the Submission Type SH-ER Information Table XML Technical Specification posted on http://www.sec.gov/info/edgar.shtml.

Read the rest of this entry »




When it comes to XBRL, you can file it right the first time!

May 13th, 2009 by Brian Larson, CPA - Software Quality Engineer

Technorati Profile
The EDGAR system is now busily accepting live XBRL filings. Last week (week of May 4th) there were 11 new filings. I thought it would be beneficial for those who are new to XBRL to write something about preparing a valid filing. By valid, I mean something that will pass the EDGAR validations and make it into the system.

There’s a lot of talk out there about how difficult XBRL is and how companies should not try to prepare their own filings but instead outsource it. We at Rivet Software work hard to make products that take the complexity out of XBRL so that you can do your filings in-house. One of the ways we do that is by hiring people like me, a CPA who understands financial reporting and how to create tools that are easy for non technical professionals to use.

Read the rest of this entry »




CrossTag – A Matured, Collaborative XBRL Tagging Solution

May 6th, 2009 by Emily Huang - Co-founder & VP, Business Technology

In 2007, CrossTag was born out of the need to create an extremely easy-to-use and highly flexible application to support all kinds of documents (Word, PDF, Excel, RTF, etc.), and most importantly, it was designed to work in a collaborative environment. CrossTag was a mature product from the beginning as it leverages much of the same code used in our Dragon Tag product, where we have already invested over 100,000 hours of development.

So, you can think of CrossTag being on the market for 2 years, but with 5 years of product development behind it.

Read the rest of this entry »




Manage the tagging and filing process with CrossTag User Roles and Workflow

April 15th, 2009 by Brian Larson, CPA - Software Quality Engineer

CrossTag is designed to help you manage the tagging and filing process from start to finish. We’ve put a lot of thought into making it an efficient, yet precise process in which accurate filings are produced every time you file. This post explores what CrossTag can do to help you manage a filing project.

First, the system separates into two roles the template design and data entry tasks that are inherent in an XBRL filing project. In CrossTag, these two user roles are called “Preparer” and “Designer”. Each CrossTag user can be setup as either preparer or designer or both.

The role of the designer is to create templates and modify taxonomies. This user needs to understand the basics of XBRL. The preparer, on the other hand, really does not need to know anything about XBRL. This person just needs to get the data into the templates created by the designer.

Initially, the two user role concept was designed to allow filers to leverage lesser skilled individuals to perform the time consuming data entry duties. However, with our current beta release of the software (CrossTag Spring Release), we’ve solved this problem with technology.

Read the rest of this entry »




The impact of Agile development and what it means to the CrossTag customer PT 2

March 27th, 2009 by Kevin Berens - VP, Products

How product innovation is combined with feedback from customers – the evolution of CrossTag for XBRL tagging

In my last entry, I talked about how customer feedback was incorporated into the product. However, we try to balance feedback from customers in conjunction with product ideas that we think would benefit our users

In the spring release we have several new features that we would like to enhance (based you’re your feedback) over the next 6 to 9 months. We are introducing the following:

Read the rest of this entry »




The impact of Agile development and what it means to the customer PT 1

February 26th, 2009 by Kevin Berens - VP, Products

How feedback from customers get into the product – the evolution of CrossTag for XBRL tagging

What is Agile development (using a Wikipedia reference):

Agile software development is a group of software development methodologies that are based on similar principles. Agile methodologies generally promote a project management process that encourages frequent-

Stop – Stop – Stop

As a customer, you could care less how Rivet Software develops software.

What you do care about (in addition to quality), is how exactly does a product feature get into the product? If you suggest a usability idea or a product enhancement, you want to know when you might expect this feature to get incorporated into the product (assuming that the idea will benefit all customers). If you hope to see this feature be incorporated into the product within 3 to 12 months, then you really do care that Rivet uses agile development.

Read the rest of this entry »