SH

Accountant

Full Time Cape Town, Brackenfell, Western Cape, South Africa, ZA
Posted 4 hours, 44 minutes ago 18 views 0 applications

Job Description

We need to output clean semantic HTML. Use

for intro paragraphs and general text. Use

for section headers. Use
  • for list items (duties, requirements, qualifications, skills). The job description includes sections: About the role, What you'll do (multiple subsections), What you bring (Education, Certification, etc). We need to parse into sections. We need to keep all original content word-for-word, no rephrase. So we must copy exactly the text as given, preserving punctuation, line breaks? We need to wrap paragraphs in

    . For list items, we need to extract list items. The description includes many bullet-like sentences but not actual list markers. We need to decide which parts are list items. The instruction: Use

    • for list items (duties, requirements, qualifications, skills). So we need to identify list items. The text includes "What you'll do:" then a series of sentences separated by periods. Those are duties, not necessarily list items. But we can treat each duty as a list item? However they are not separated by line breaks. The instruction says preserve all original content word-for-word, do not add, remove, summarise, or rephrase. So we cannot break sentences into separate list items unless they are originally list items. The text does not have explicit list markers like "-" or "*". It is continuous prose. So maybe we should treat each paragraph as

      . The "What you'll do:" is a heading? Not a header defined. Could be a section header; maybe we need to use

      for section headers like "Responsibilities", "Qualifications", etc. But the description uses "What you'll do:" which is not one of the allowed header names. The allowed headers: Responsibilities, Qualifications, Requirements, Education, Experience, Skills, How to Apply, Key Duties, About the Role. The description includes "About the role:" and "What you'll do:" and "What you bring:". We need to map these to allowed headers. "About the role:" likely corresponds to "About the Role". So we can use

      About the Role

      . Then the paragraph under it is introductory text, which should be

      . Then "What you'll do:" likely corresponds to "Key Duties". So

      Key Duties

      . Then the duties text is a long paragraph; maybe we need to split into multiple

      if there are line breaks. The text includes line breaks after each colon? Let's examine. The raw text: "About the role: The purpose of the Non-RSA Accountant in the Group Reporting team is to perform the statutory reporting functions by ensuring IFRS compliance, managing the compilation, audit and signing of Annual Financial Statements for all Group companies outside of South Africa, Lesotho, Eswatini and Namibia and consolidating these results for Group reporting. The primary responsibilities are included in the role description below. This role is integral to maintaining the financial health and transparency of the organisation, ensuring that all financial reporting is accurate, timely, and in full compliance with relevant accounting standards." So we have a header "About the role:" then a paragraph. We'll output:

      About the Role

      The purpose of the Non-RSA Accountant in the Group Reporting team is to perform the statutory reporting functions by ensuring IFRS compliance, managing the compilation, audit and signing of Annual Financial Statements for all Group companies outside of South Africa, Lesotho, Eswatini and Namibia and consolidating these results for Group reporting. The primary responsibilities are included in the role description below. This role is integral to maintaining the financial health and transparency of the organisation, ensuring that all financial reporting is accurate, timely, and in full compliance with relevant accounting standards.

      Next: "What you'll do:" then a series of sentences. We need to treat that as duties. Possibly we need to split into multiple

      for each paragraph? The text after "What you'll do:" includes many sentences separated by periods and line breaks. Let's see the structure: "What you'll do: Non-RSA Consolidation Functions: Monthly : Prepare and distribute the foreign currency exchange rates in the Group’s format. Roll forward recurring consolidation journals in BPC. Calculate and post monthly consolidation journals (hyperinflation, discontinued operations, internal trademark elimination, forex hedge, and reallocate unrealised profits). Submit consolidation input schedules for disclosure notes. Complete the consolidation journals report. Compile monthly reports for key financial matters on posted journals. Quarterly: Perform analytical reviews on divisional financial data for the Non-RSA entities to ensure the information submitted is correct and fairly presented. Submit the tax disclosure notes for the consolidation journals and complete the consolidation section in the tax analytics file. Ensure completeness of the tax submissions and perform analytical review to assess the reasonability of information presented. Complete internal financial controls attestation form. Bi-annually (December interim and June year-end): Assist with the ECL (IFRS 9) calculation process for receivables within Non-RSA entities (if applicable). Perform loan movement analyses for Non-RSA and capture inputs on BPC (Inter-Co Disclosure model). Manage the IFRS 7 disclosure process: Collect foreign exchange rates and bank interest rates from the treasury department; Review divisional inputs; Run the interest and foreign currency sensitivity calculations on BPC; Complete IFRS 7 disclosures for the consolidation entries for Non-RSA; and Review calculated sensitivities for the Group. Prepare discounted cash flow calculations for the trading Non-RSA entities and calculate the investment impairments (IFRS 9) for Shoprite International Ltd (Non-RSA holding company). Annually (June year-end): Assist with audit queries on the consolidation files and journals. Prepare the budget for consolidation entries for Non-RSA. Update the Group restricted cash memo (IAS 7). Post the interdivisional sales elimination AFS journal for Non-RSA. Roll forward the consolidation journals to the new financial year and perform reconciliations. Annual Financial Statements Compilation Functions: Prepare annual financial statements in compliance with IFRS (or other accounting framework applicable) for 25 Non-RSA statutory legal entities: June year-end: 20 legal entities (Botswana, Egypt, Ghana, Malawi, Mauritius, Mozambique, Nigeria, Tanzania, Uganda,Zambia and Zimbabwe) December year-end: 5 legal entities (Angola, DRC and Nigeria) Prepare financial summaries for 3 Non-RSA statutory legal entities (Kenya, and Mauritius) Respond to and resolve audit queries and manage the sign-off process to meet deadlines. Manage Trainee Accountants that assist with preparation of annual financial statements. Prepare retained earnings reconciliations. Prepare going concern assessments and request letters of support and subordination agreements from the Legal Department if needed. Additional responsibilities specific to December year-end annual financial statements: Calculate and prepare fixed asset registers (including impairment calculations) in terms of Angolan GAAP. Assist with December year-end input schedules on BPC for disclosure notes. Calculate and post IFRS reversal and other AFS journals. Ad-hoc functions: Trainee Accountants Provide training to Trainee Accountants that assist with the preparation of annual financial statements (3 at June year-end and 2at December year-end). Review learning outcome reviews (LORs) on SAICA EAT submitted on a monthly basis. Review work performed by Trainee Accountants. Provide feedback to Trainee Accountants and attend their Atcor assessments. Other Calculate and post ZAR forcing journals for correction of system-calculated translation of intergroup transactions (if applicable) at month-end. Write memos and policy documents as required. Liaise and communicate with the external auditors." This is a huge block. We need to preserve word-for-word. Should we keep line breaks? The instruction: Use

      for introductory paragraphs and general text. So we can break into multiple

      based on logical sentences or line breaks. But we must preserve original content word-for-word, meaning we cannot change punctuation or wording. However we can insert

      tags around segments; that adds tags but not change content. The content inside must be exactly as original. So we need to split the long paragraph into sentences? The original text includes line breaks after each colon maybe. But we cannot add or remove words. We can keep the entire block as one

      if it's considered a single paragraph. However the instruction says "If text has no clear sections, just wrap paragraphs in

      tags". So we can treat the whole "What you'll do:" block as one paragraph (maybe multiple sentences). But there are colon-separated sections; but still it's one paragraph in the source (no blank line). So we can keep it as one

      . But we also need to include "What you bring:" which likely corresponds to "Qualifications" or "Requirements". The allowed headers include "Qualifications" and "Requirements". The text "What you bring:" includes Education, Certification, etc. So we can map to "Qualifications". Also there is "What you bring:" then "Education: ..." etc. So we can have

      Qualifications

      then

      Education: Bachelor of Accounting Honours degree, or equivalent qualification, with completed SAICA articles is essential. Certification: Qualified Chartered Accountant (CA(SA)) – preferred. Ability to work with high volumes of data and with tight deadlines. Additional advantageous exposure Relevant experience in a financial Group Reporting setting of a JSE listed company with exposure to applying financial risk and control frameworks and relevant remediation or similar role. Expert knowledge on IFRS. Experience working on SAP (general) and BPC

      . But we need to ensure we keep all original content word-for-word. Let's verify the exact text after "What you bring:": "What you bring: Education: Bachelor of Accounting Honours degree, or equivalent qualification, with completed SAICA articles is essential. Certification: Qualified Chartered Accountant (CA(SA)) – preferred. Ability to work with high volumes of data and with tight deadlines. Additional advantageous exposure Relevant experience in a financial Group Reporting setting of a JSE listed company with exposure to applying financial risk and control frameworks and relevant remediation or similar role. Expert knowledge on IFRS. Experience working on SAP (general) and BPC" Note there is a line break after "What you bring:" then "Education: ..." etc. So we need to preserve that exactly. The phrase "Additional advantageous exposure" seems odd; maybe it's "Additional advantageous exposure" as a header? But it's part of the text. We'll keep as is. Now we need to ensure we use

      for section headers. The allowed headers list includes "Responsibilities", "Qualifications", "Requirements", "Education", "Experience", "Skills", "How to Apply", "Key Duties", "About the Role". The text includes "About the role:" (we used "About the Role") and "What you'll do:" (Key Duties). Also "What you bring:" maybe "Qualifications". Also there might be "Requirements" but not present. "Education" is separate. We need to ensure we use

      for each header. Also need to use
      • for list items (duties, requirements, qualifications, skills). However the duties are not presented as list items; they are sentences. The requirement is to use
        • for list items. If there are no explicit list items, we may not need to use
            . But the instruction says "Use
            • for list items (duties, requirements, qualifications, skills)". So we need to identify which parts are list items. The duties are described in sentences; maybe each sentence is a list item. But we cannot break sentences because that would change content? We could treat each sentence as a separate
            • but that would add
            • tags and maybe break the content? The content would be the same sentence, just split. That's allowed as long as we preserve content word-for-word. Splitting into separate
            • would not change the words, just add tags. That seems okay. But we need to be careful: The original text may have line breaks that indicate separate items. For example, after "Monthly :" there are multiple sentences separated by periods. Those could be considered separate duties. However the instruction says preserve all original content word-for-word, not to rephrase. Splitting sentences into separate
            • would keep each sentence exactly as is, just each in its own
            • . That seems fine. But we need to decide how to structure. Simpler:

Apply Now ↗

How well do you match?

Get an instant AI match score for this role — free, takes 3 minutes.

Tailor your CV for this role

The concierge rewrites your whole CV and writes a matching cover letter for this job — opens right here, nothing to paste.

Tailor My CV to This Job ✍️

Free cover letter for this job

Upload your CV and get a tailored cover letter in seconds — free, no account needed.

Generate a Cover Letter 📝

Join Our Ghana Channels

Get free job alerts on your phone

MJC
ECHO
Your MJC Assistant

I'm ECHO, your MJC career assistant. I can help you find jobs, explore career tools, and connect with opportunities across Africa.

How was your experience with ECHO?