A written companion to Bryan Cheong’s original video or pictures. Updated by Syntax Technologies on 28 September 2026.
Start an LHDN tax audit preparation file with the officer’s actual document request, then retrieve the relevant reports separately for each requested year. In SQL Accounting, check the date range, preview the report and export a clearly named copy before moving to the next item.
Bryan Cheong’s video walks through a specific request covering 2022, 2023 and 2024. Those years and the eleven items belong to that example; they are not a universal checklist or a limit on how long records should be retained.
1. Read the request and organise one folder per year
Identify the entity, periods, requested documents and response arrangements. Create a checklist that maps each requested item to a report or supporting document. Keep each year separate, as Bryan demonstrates, and name exports clearly—for example, 2024-General-Ledger.pdf.
Use the dates requested for your case. Bryan temporarily removes a date filter because his demonstration database lacks the historical data; that is not an instruction to remove the filter from a real audit report.
2. Retrieve general ledger, journals and sales/purchase ledgers
- General ledger: open GL → Print Ledger Report, set the period, select General Ledger, apply and preview.
- Journals: use GL → Print GL Document Listing and select the journal listing.
- Sales and purchase ledgers: use the corresponding ledger selections and export the results for each requested year.
Check filters before exporting. A report restricted to one account or party will not answer a request for a complete ledger.
3. Prepare bank, cash and transaction evidence
The video shows filtering the ledger to individual bank and cash accounts. Prepare the corresponding bank statements as supporting evidence. Where the request includes cash in hand or petty cash, retrieve those accounts too.
For subcontractor payments, Bryan demonstrates the supplier payment listing and filters for the relevant subcontractors. For contractual receipts or payments, select the relevant customer or supplier records. The correct report depends on how the transaction was recorded.
4. Include item details where they are requested
For material purchases, Bryan opens the purchase invoice listing. He then changes from the summary view to a format showing item details. A total-only report may be insufficient when the request is for purchased items.
Review sales invoices, purchase invoices, customer receipts, supplier payments and cash-book receipt/payment voucher listings against the request. A listing helps locate transactions, but it does not replace the underlying invoice, contract or receipt when that evidence is requested.
5. Use payroll records for employee-level salary details
A single salary expense account in SQL Accounting may show only a total. If employee-level annual details are requested, Bryan switches to SQL Payroll and uses Payroll → Print Yearly Individual Reports.
The data must exist for the requested period. Installing payroll software today does not recreate missing historical payroll. Locate the original records or backups if the system was not used during those years.
6. Check stock cards and closing stock values
Use Stock → Print Stock Card, select the relevant dates and preview the movement report. Bryan explains that the stock-card value should be checked against the stock value recorded or reported in the accounts.
Investigate differences with the person responsible for the accounts. Do not change historical entries merely to make two reports match.
7. Review the pack and arrange support
- Confirm the company, report period and applied filters.
- Open each exported PDF and check that all required pages are included.
- Match reports to the request checklist and attach supporting documents.
- Explain missing records or differences to your accountant or tax adviser.
- Confirm software support availability in advance if report retrieval help may be needed.
Bryan highlights the value of arranging dealer support before an officer’s visit. Confirm the scope and availability under your own support agreement. Software support helps retrieve information; it does not determine the tax treatment or guarantee an audit outcome.
Frequently asked questions
Does the three-year example mean I can discard older records?
No. The requested audit periods and statutory retention requirements are different. Keep records for the applicable period and check any additional requirements with your adviser. Refer to LHDN’s Tax Audit Framework.
Are SQL reports alone enough?
Use the actual request as your guide. Reports need accurate underlying entries, and officers may also require original documents or other evidence.
Can Syntax help locate a report?
Contact us with the requested report name, year and software version. Do not post employee details or confidential audit documents in public comments.
Primary source: Bryan Cheong’s embedded SQL Accounting and SQL Payroll walkthrough. Menus and formats may vary by version. Follow the audit notice and your tax adviser’s guidance for the actual submission.
Need help with SQL Accounting or SQL Payroll?
Syntax Technologies provides software sales, training and support. Contact 012-663 9318 or info@syntech.com.my with your software version and the reports or workflow you need help with.