structure and what will this process file formats containing all the segment be. information for sample selection. SCOA implementation would be one of the considerations the auditors test in checking the classification inherent to the transactions they audit. The relevance of prior period corrections in the context of a multi-dimensional chart of accounts is unclear as the correction will be done to make the required changes to all the segments. The regulation provides for the transaction to be captured and at this point classified within the multiple segments. There is no difference from the current classification being undertaken by municipalities as at least 3 segments are currently relevant (item, municipal standard classification and function). WC PT Witzenberg For SCOA to be standard NT have to The account numbers will be available in [3.4.4] provide the numbering as well. Version 5 to be released early in 2014. Nigel Graves [6] Has any consideration been to Comment noted. Code structure does this type of code structure? I believe I support the accounts codes to be wrote something on this for you many included in Version 5. The basis of years ago. An input code is the compiling the code structure will be organisational unit that does the work included in the PSD. The proposal and an output code is the target made is valid provided the systems have project. For example, the waste the functionality. management unit might collect the refuse from the power station. The waste management unit would use their input code and the output code would be the power station expenditure. Very useful for transfer pricing and activity-based costing. Downside is that it increases size of chart and complexity. It could be an option for the larger municipalities? Overstrand The absence of a complete coding The account numbers for the posting Municipality [3.1] structure for all the segments, levels level detail per segment will be provided and sub-levels within the segments as in Version 5 of the SCOA Tables. A 6 part of the regulations does limit digit code had been designed that practitioners and service providers identifies the segment, group of account from commenting on the SCOA as a and posting level account. Provision is whole. A coding structure would have made in the SCOA Tables for accounts enabled a schematic lay-out to identify to be "breakdown allowed" providing for possible risk areas. This also impacts further detail to be added by the
structure and what will this process be. file formats containing all the segment information for sample selection. SCOA implementation would be one of the considerations the auditors test in checking the classification inherent to the transactions they audit. The relevance of prior period corrections in the context of a multi-dimensional chart of accounts is unclear as the correction will be done to make the required changes to all the segments. The regulation provides for the transaction to be captured and at this point classified within the multiple segments. There is no difference from the current classification being undertaken by municipalities as at least 3 segments are currently relevant (item, municipal standard classification and function). WC PT Witzenberg [3.4.4] For SCOA to be standard NT have to provide the numbering as well. The account numbers will be available in Version 5 to be released early in 2014. Nigel Graves [6] Has any consideration been to this type of code structure? I believe I wrote something on this for you many years ago. An input code is the organisational unit that does the work and an output code is the target project. For example, the waste management unit might collect the refuse from the power station. The waste management unit would use their input code and the output code would be the power station expenditure. Very useful for transfer pricing and activity-based costing. Downside is that it increases size of chart and complexity. It could be an option for the larger municipalities? Comment noted. Code structure does support the accounts codes to be included in Version 5. The basis of compiling the code structure will be included in the PSD. The proposal made is valid provided the systems have the functionality. Overstrand Municipality [3.1] The absence of a complete coding structure for all the segments, levels and sub-levels within the segments as part of the regulations does limit practitioners and service providers from commenting on the SCOA as a whole. A coding structure would have enabled a schematic lay-out to identify possible risk areas. This also impacts The account numbers for the posting level detail per segment will be provided in Version 5 of the SCOA Tables. A 6 digit code had been designed that identifies the segment, group of account and posting level account. Provision is made in the SCOA Tables for accounts to be "breakdown allowed" providing for further detail to be added by the