XBRL Explanatory Note: The following section defines the XBRL context declarations which will be used within the messages specified within this MIG. The rules relating to the optionality and cardinality of the context within a specific message will be defined in the relevant message specification section. – The message sender is the organisational entity that submits the specific rollover message. There MUST be only one Message Sender context defined within a business document. If no Message Sender context is declared then error code SUPER.GEN.GEN.6 MUST be returned. If more than one Message Sender context is declared then error code SUPER.GEN.GEN.10 MUST be returned. The message sender context MUST conform with the specifications in the Message Sender Context Specification Table. Message Sender Context Specification Table Context Message Data Requirement Rule Imp. code Concept This is a unique identifier used to link the XBRL Standard data element to a defined XBRL context. Context will validate that Mandatory Recommend a meaningful code combined N/A Identifier this is present and with a sequential number. For this context an unique. example could be SND01. – This field must be set to the ABN of the party that is sending this document. 1. Entity Identifier Mandatory 1. MIG. SBR.GEN.GEN.1 1. Must be a valid ABN in accordance to the ABN algorithm. Entity Identifier This must be set to Mandatory MIG. SBR.GEN.GEN.14 Scheme http://www.abr.gov.au/abn Explicit member dimension ReportPartyType XBRL Standard (“ReportPartyTypeDimension”) must be set will validate Entity Segment Mandatory N/A to dimension domain “MessageSender”. value. Period Date - This is a mandatory item within the XBRL Start Date specification so it must be populated with a XBRL Standard date and this MIG suggests setting both Mandatory will validate that N/A and end date to the current date. The actual this is present. Period Date - value will not be tested only whether it is End Date present. – The message receiving is the organisational entity that receives the specific rollover message for processing.
XBRL Explanatory Note: The following section defines the XBRL context declarations which will be used within the messages specified within this MIG. The rules relating to the optionality and cardinality of the context within a specific message will be defined in the relevant message specification section. – The message sender is the organisational entity that submits the specific rollover message. There MUST be only one Message Sender context defined within a business document. If no Message Sender context is declared then error code SUPER.GEN.GEN.6 MUST be returned. If more than one Message Sender context is declared then error code SUPER.GEN.GEN.10 MUST be returned. The message sender context MUST conform with the specifications in the Message Sender Context Specification Table. Message Sender Context Specification Table Context Data Concept Requirement Rule Imp. Message code Context Identifier Mandatory This is a unique identifier used to link the data element to a defined XBRL context. Recommend a meaningful code combined with a sequential number. For this context an example could be – SND01. XBRL Standard will validate that this is present and unique. N/A Entity Identifier Mandatory This field must be set to the ABN of the party that is sending this document. 1. Must be a valid ABN in accordance to the ABN algorithm. 1. MIG. 1. SBR.GEN.GEN.1 Entity Identifier Scheme Mandatory This must be set to http://www.abr.gov.au/abn MIG. SBR.GEN.GEN.14 Entity Segment Mandatory Explicit member dimension ReportPartyType (“ReportPartyTypeDimension”) must be set to “MessageSender”. XBRL Standard will validate dimension domain value. N/A Period Date - Start Date Mandatory This is a mandatory item within the XBRL specification so it must be populated with a date and this MIG suggests setting both and end date to the current date. The actual value will not be tested only whether it is present. XBRL Standard will validate that this is present. N/A Period Date - End Date – The message receiving is the organisational entity that receives the specific rollover message for processing.
Draft_Rollover_Message_Implementation_Guide_v2.0.docx