SYSTEMATIC QA METHODOLOGY Annual Report & Corporate Document Proofreading ✦ B i l i n g u a l C o n s i s t e n c y R e v i e w • F i n a n c i a l D a t a V e r i f i c a t i o n • R e g u l a t o r y C o m p l i a n c e ✦ Document Type: Methodology Deck Target Documents: Annual Report, Sustainability Report, Corporate Documents Language Pairs: Indonesia ↔ English Version: 1.0 (Professional Standard) 🎯 Objective: To ensure the document is 100% accurate in data, consistent across languages, and fully compliant with applicable regulations (OJK, PSAK, GCG). 1. Overview of the QA System This methodology is a 6 - stage systematic process designed specifically for bilingual corporate documents, particularly annual reports. Unlike standard proofreading (which only checks spelling and grammar), this system performs data reconciliation , regulatory compliance mapping , and cross - version linguistic consistency 💡 Why This System Works: It treats the document as a legal - financial instrument , not just a piece of text. Every number is traced back to the audited financial statements (CALK). Every paragraph is compared across languages. Every section is checked against OJK and PSAK requirements. 📋 Step 1 Mapping & Anchor 🔍 Step 2 Cross - Version 📊 Step 3 Data Recon. ⚖️ Step 4 Regulatory ✏️ Step 5 Formatting 📈 Step 6 Reporting 2. The 6 - Step Detailed Methodology STEP 1 Structural Mapping & "Anchor Data" Identification ⏱️ Effort: ~10% of total project time What I do: Before reading a single word, I prepare the "truth source" for the entire document. • Identify the master document: The Audited Financial Statements (CALK) is the sole source of truth for all financial figures. Every number in the narrative (MD&A) must reconcile to this document. • Extract "Anchor Data": I pull all material figures (Total Assets, Revenue, Profit, Debt, Cash Flow, Dividends, Share Count) from the CALK and save them as a "reference checklist" before reading the text. • Flag bilingual structure: I confirm that the document is bilingual (ID/EN) and plan to read them side - by - side , not separately. 📌 Output: Anchor Data Table (checklist of key financials). STEP 2 Cross - Version Comparative Analysis (ID vs EN) ⏱️ Effort: ~20% of total project time What I do: This is a unique skill that differentiates me from standard proofreaders. • Paragraph segmentation: I read the document in small units (per paragraph/per table). I read the Indonesian version, then immediately read the English version next to it. • Detect "Translation Drift": I look for missing information, added content, or shifts in meaning during translation. • Detect Data Mismatch: I verify that numbers (dates, amounts, percentages) match exactly across versions. (Example found: "September" vs "December", "1 Senior Manager" vs "2 Senior Managers"). 📌 Output: Bilingual Consistency Matrix (list of discrepancies with corrections). STEP 3 Financial Data Reconciliation (CALK Cross - Referencing) ⏱️ Effort: ~30% of total project time (The Most Critical Phase) What I do: This is where I catch critical financial errors that could trigger OJK inquiries or lawsuits. • Narrative vs. Statement: I compare every financial claim in the MD&A (e.g., "debt decreased", "profit increased") against the related lines in the Statement of Financial Position and Income Statement. • Arithmetic Testing: I recalculate differences, percentages, and ratios manually. (Example caught: 2,428 - 1,316 = 1,112, not 3,744. 7,948 / 17,102 = 46.5%, not 75%). • Unit Validation: I check if "Rp 10,893 million" is actually million or billion by cross - referencing the absolute number in CALK. 📌 Output: Financial Data Accuracy Report (spotting misstatements). STEP 4 Regulatory Compliance Mapping (OJK, PSAK, GCG) ⏱️ Effort: ~20% of total project time What I do: I use a "mental regulatory checklist" applicable to Indonesian public companies. • OJK VIII.G.7: Financial statement presentation. I check Rupiah notation, mandatory disclosures, and table structures. • POJK 51/2017: Sustainability reporting. I check if the sustainability report is referenced correctly. • PSAK: Accounting standards. I check if accounting terminology (e.g., "Liabilities" vs "Obligations") is consistent with Indonesian standards. • GCG (Corporate Governance): I check for internal contradictions in policies (e.g., Whistleblowing) or procedures (e.g., GMS/EGM). (Example caught: "No reports" vs "Several cases reported" in the same section). 📌 Output: Regulatory Compliance Checklist (mapping findings to specific regulations). STEP 5 Formatting & Stylistic Audit ⏱️ Effort: ~10% of total project time What I do: I ensure the document looks as professional as its content reads. • Notation Standardization: I unify "Rp. 1,000,000, - " to " Rp1,000,000 ". • Abbreviation Standardization: I expand "sbb" to "sebagai berikut", "dll" to "dan lain - lain". • Digital Artifact Detection: I spot rendering errors like "Ʀ" (replacing "ti") which often appear from PDF conversions. This ensures the final digital version is clean. • Capitalization & Hierarchy: I check for consistent heading styles (H1, H2, H3) and table formatting. 📌 Output: Style Guide Recommendations & Corrected Templates. STEP 6 Issue Prioritization & Reporting ⏱️ Effort: ~10% of total project time What I do: I deliver a clean, actionable report so the client can fix issues without reading the whole document again. • Classification: 🔴 Critical — Data errors, regulatory contradictions, material misstatements. (Fix immediately). 🟠 Medium — Formatting errors, terminology inconsistencies, structural mismatches. 🟢 Low — Typos, capitalization, minor grammar. • Correction Log: I compile a table with ID → Page → Location → Issue → Correction . This allows the client to use "Find & Replace" or assign fixes easily. 📌 Output: Comprehensive QA Report & Correction Log (Word/Excel). 3. Tools & Techniques Used Tool / Technique Application in the Process Side - by - Side Comparison (ID/EN) Used in Step 2. I view both language versions simultaneously to catch "translation drift" and mismatched data. Manual Arithmetic Recalculation Used in Step 3. I do not trust calculated percentages or differences. I always recalculate them against the anchor data. MS Word Track Changes Used in Step 5 & 6. For direct editing, I use Track Changes to show every correction clearly. Regulatory Checklist (OJK/PSAK) Used in Step 4. A mental/checklist framework to ensure all mandatory disclosures are present and correct. Excel Correction Log Used in Step 6. For large documents (200+ pages), I compile all findings in a sortable Excel sheet for the client. PDF Comparison Tools Used to verify the final rendering and catch digital artifacts (like the "Ʀ" character). 4. What You Will Receive Upon project completion, the client receives a comprehensive package of deliverables, ensuring transparency and actionable results. Deliverable Description Comprehensive QA Report Full narrative report summarizing the scope, findings, and recommendations. Bilingual Consistency Matrix Table showing all discrepancies found between Indonesian and English versions, with corrections. Regulatory Compliance Checklist Mapping of findings to specific regulations (OJK, PSAK, POJK) with status indicators. Full Correction Log (Excel/Word) Detailed table of all issues (100+ items) with ID, page, location, issue, and correction for easy fixing. Style Guide / Formatting Standards Recommendations for standardizing Rupiah notation, dates, abbreviations, and capitalization for future documents. Track Changes Document Final corrected document with all changes applied and visible via Track Changes. Executive Summary (for Management) One - page summary of critical findings for the board or compliance team. 5. Why This Methodology Matters to You (Your ROI) 🚫 Risk Mitigation Catching a single misstated figure (e.g., IDR 827 Million vs IDR 827 Billion) prevents OJK inquiries, shareholder lawsuits, and reputational damage. 🕒 Saves Internal Team Time Instead of your internal team spending weeks manually checking numbers and translations, I deliver a ready - to - use correction log that speeds up the final approval process by up to 50%. ⚖️ Regulatory Assurance Gain peace of mind knowing that your document has been reviewed against the latest OJK and PSAK requirements, ensuring full compliance for public filing. 🌐 Bilingual Integrity Ensure that investors and regulators reading either the Indonesian or English version receive the exact same information, avoiding confusion and miscommunication. 6. Process Flow Overview 1. MAPPING → 2. CROSS - VERSION → 3. RECONCILIATION → 4. COMPLIANCE → 5. FORMATTING → 6. REPORTING (Anchor Data) → (ID vs EN) → (CALK Check) → (OJK/PSAK) → (Style Audit) → (Prioritized Log) 7. QA Checklist Applied to Every Document # Checkpoint Status Indicator 1 All financial figures in MD&A reconciled with CALK. ✅ Verified 2 Indonesian and English versions contain identical data. ✅ Verified 3 No internal contradictions in policies or procedures (e.g., GCG). ✅ Verified 4 Rupiah notation is standardized. ✅ Verified 5 Abbreviations are expanded and standardized. ✅ Verified 6 No digital artifacts (e.g., "Ʀ") present in the final rendering. ✅ Verified 7 Table structures are formatted correctly. ✅ Verified 8 Director and Commissioner names are spelled consistently. ✅ Verified 📩 Ready to Ensure Your Document is Flawless? I apply this exact methodology to every annual report, corporate document, and sustainability report I review. Contact me to discuss your project. [ bryanpingkanramadhan @gmail.com ] | [ My Upwork ] Confidential Methodology — Annual Report QA & Consistency Review © 2026 | All rights reserved | This document is part of the professional portfolio