April 2010
22 April 2010
Changes and updates to existing components
A number of changes and updates to existing components have occurred. These are articulated below:
- SBR AU taxonomy due to the addition of an numeration to the lodgment status Code element, and changing the data type of three elements needed for the ACT monthly return
Updated AU Report, Sample instances, Message Implementation Guide (MIG) and message responses due to adding of ‘GroupMember’ type to the list of available Report Party Dimension values to be used in the annual return to distinguish between reporting party context and group member context.
Software developer impacts: This change will require software developers to review work undertaken to date to get a correctly working solution.
Updated AU Report, Sample instances and MIG due to:
- Changes to the cardinality of the Direct Debit element from mandatory to optional.
- Update form element attributes for wage components and wage totals data elements in the FA/IA and add business rules and relevant error repository references in the MIG for the Revenue SA Payroll tax monthly return.
- Add business rule for Direct Debit Authorisation Indicator data element in the Revenue SA Payroll tax monthly return.
- Add enumeration for Lodgment.Status.Code data element in the Revenue SA Payroll tax monthly return.
- Add Period.Unique.Identifier to the Revenue SA Calculate Periodic Payroll Tax request message.
- Changes to the cardinality of the PaymentRecord.AgencyGeneratedReference.Number element to specify that it is optional.
- Rename the Get service to Prefill in the Revenue SA Payroll tax monthly return.
- Addition of an additional element to indicate whether an electronic or paper based assessment is issued.
Software developer impacts: To correct several critical defects identified in testing will require software developers to review any work undertaken to date to get a working solution.
Updated AU Report, Sample instances and MIG due to updated payment tuple within MIG and updated Message Type Text values for reports as defined in NT Revenue Office Payroll tax MIG.
Software developer impacts: No significant impact on software developers. Changes align the payment mechanism structure in the NT Revenue Office Payroll Tax Monthly Return with that of the NT Revenue Office Payroll Tax June and Annual Adjustment Return and ensure the MIG provides an accurate representation of system behaviour.
Updated AU Report, Sample instances, MIG and message responses due to:
- The introduction of Designated Group Employer based payroll tax legislation.
- Includion of additional data elements: estimated group ACT taxable wages, estimated group Australia wide wages and estimated Australia wide wages and updated contexts.
- The remove redundant data elements for period start and end dates to align with annual MIG.
Software developer impacts: Will require software developers to amend/remap any work undertaken to date to get a working solution.
- Following final review against AU Report and ATO system, MIGs and Schematrons have been updated.
- Software developers should note the testing environment for these three forms plus the Activity Statement are now stable and open for testing.
- MIG's updated to incorporate detailed review and final reconciliation against the AU Report.
Losses schedule – In addition to the above, the AU Report and MIG are to be updated due to the incorrect version of the ReportingPartyType dimension being used.
Software developer impacts: To ensure delivery of messages from SWDs to ATO will require software developers to review any work undertaken to date to get a working solution. Change will benefit software developers by providing implementation information that aligns more accurately with the taxonomy.
Australian Securities and Investments Commission (ASIC) - Notification of half yearly reports (7051), Statement to verify financial statements of a Foreign Company (405)/Annual return of a foreign company (406) and Profit and loss statement and balance sheet (FS70)
- Updated MIG, Schematrons and message responses are the result of identifying errors in code and documentation during internal and conformance testing.
Software developer impacts - Software developers will need to re-align their software products with the new version of the reporting taxonomy and require an updated MIG for guidance.
Relocation of Sample Instances
Sample instances have been removed for the forms listed below and can now be accessed via the relevant conformance suites issued as part of Software Developer testing.
- FBT Return
- Tax File Number Declaration
- Notification of half yearly reports (7051)
- Statement to verify financial statements of a Foreign Company (405)/Annual return of a foreign company (406)
- Profit and loss statement and balance sheet (FS70)
- ASIC Copy of Financial Statements and Reports coversheet - Form 388
If you would like more information about SBR’s test plans, including how software developers can get involved, please email SBRServiceDesk@ato.gov.au.
Identity management client (IMClient) and Reference client
Following further testing, the Software developer kit has been updated with revised versions of the Identity management client (IMClient) and Reference Client. The re-release fixes the following defects:
- Updated class diagram in the user guide
- WCF Client is not closed in exceptional circumstance.
The update to the Reference Client also includes the provision of strongly named dlls for dotNet application developers.
To obtain a copy of the IMClient, Reference Client and associated documentation please contact SBRServiceDesk@ato.gov.au.
AUSkey
- AUSkey – SBR’s single secure authentication credential, originally scheduled for April, is now scheduled for public access in May, after the Australian Taxation Office (ATO) peak lodgement period for the March Activity statement (BAS).
