Downloads Downloads

XBRL Messenger

XBRL Messenger is Fujitsu's product for both Standard Business Reporting and SuperStream

The best way to see how it can assist you with developing XBRL aware applications is to download it and test it out in your own environment. It is available for both Java and .NET and includes a range of sample applications for SBR and SuperStream.

Click here to request a FREE XBRL Messenger evaluation copy


SBR and SuperStream Taxonomies

The SBR Yeti portal is not currently available for viewing and downloading taxonomies.

Taxonomies can be viewed (but not downloaded) from this alternative site:

The SBR generated taxonomies can be downloaded via the Download Taxonomy section in the following page:

The new ATO generated taxonomies are available on the ATO SBR Service Registry site. Go to the View Service Artifacts and select the type of documents you are after. Then select click on the relevant file. Currently only these types of documents have ATO generated taxonomies:

Indvidual Income Tax Returns (IITR)

Non-individual Income Tax Returns (NITR)


Do It Yourself (DIY) XBRL - Is there a better approach

I've been working with  global XBRL implementations over the past eight years and sometimes get into discussions with experienced software developers in regards to the "buy or build" argument. Obviously this argument isn't unique to XBRL and, being a software developer myself, I totally understand developers questioning the need to use a specialised XBRL package to create "a simple XML document".

Typically I hear comments which can be summarised as - "All we need to do is build a simple XML handler which can generate the XBRL instance documents which SuperStream mandates. They're just XML documents which need to conform to a schema. How difficult can that be?"

While understanding such comments, I don't believe that the requirement to create XBRL instance documents consistently and reliably is quite that simple. The document below is my response to the questions which have been raised with me over the last eight years and, I am happy to admit, reflects my personal opinion. I would also like to highlight that I have more than a personal interest in the topic as the company I work for has a set of commercial XBRL offerings!

Pitfalls with DIY XBRL processors