Technical context

This section provides a high level technical context for a typical software developer implementation. It aims to answer the question "what do I need to do to my product to support SBR?"

technical-context-image

Items in green are the responsibility of the software developer and items in yellow are provided by the SBR program. There is a basic level of support available for all the green functions, in the form of consultation and advice of generic approaches.

The table below identifies the work and functional changes required to interact with the SBR solution, as well as the specific resources available from and expectations of the SBR teams.

Task / Function SBR Support
  1. Work with the SBR taxonomy, and support the related link bases for presentation, business rules,  validation, formula, etc.
  • XBRL and SBR Taxonomy Training services
  • SBR-AU XBRL Taxonomy
  • SBR Taxonomy Architecture Document
  1. Create valid XBRL instance documents from application data.
  • XBRL Processor engine
  • SBR-AU XBRL Taxonomy
  • Message Implementation Guides
  1. Provide access to mapping tools that allow users (accountants, bookkeepers and businesses) to map the taxonomy to the data in their systems.
  1. Provide a user interface which will allow the users to view, check, and edit the forms that are supported.
  1. Consume the Identity Management processes which will provide a key store, credential signing, messages to the VANGuard Trust Broker and return of "secure tokens" and the application of those tokens in the message assembly.
  • Australian Business Register (Credential Issuing)
  • Secure Token Server (authentication)
  • Credential Keystore and authentication API software tools.
  1. Interface with the SBR web services to send the reports/messages to the correct agency.
  • Web Service Implementation Guide
  • WSDL Files
  1. Receive the related error and confirmation messages in response to reports sent, and provide user interfaces to allow these to be read and or stored by the user in a meaningful way.
  • Message Implementation Guides
  • Machine readable validation rules with human readable messages
  1. Provide direction as a result of error messages that will allow a user to contact the right support desk for problem resolution.
  1. Receive Taxonomy updates together with appropriate mapping or software product updates where the taxonomy impacts product functions (eg a new reporting requirement).
  • SBR Knowledge Repository
  • SBR Taxonomy releases and change management policy.
  1. Receive dynamic updates to the SBR Taxonomy where the mapping has not been altered (eg revised tax tables).

Last updated: 11 May 2012
Page ID: 14046