Audit readiness is not a project you do once in the weeks before an external audit. It is a set of habits that make every audit, every bank or investor review, and every change of leadership easier. The cheapest time to build those habits is while the company still has twenty users and one ERP, not after it has eighty users, several branches, and nobody who remembers why a certain account has admin rights.
Auditors call this area IT general controls. The name sounds formal, but for a growing company it comes down to four questions. Who can get into your systems, and who decided that? How do changes reach the live system? Can you restore your data if something goes wrong? What happens when there is an incident? If you can answer each one with evidence instead of memory, you are most of the way there.
Start with user access. Every system that touches money or stock, usually the ERP, the accounting software, the banking portal, and email, needs a current list of who has an account and which role it carries. New accounts should be requested and approved in writing, even if that is just an email or a ticket. When someone leaves, their access should be removed on their last day, and someone should record that it was done.
Then review that list every quarter. Export the users and roles from each system, send the list to each department head, and ask them to confirm every account or mark it for removal. Keep their reply as evidence. The first review almost always turns up shared logins, accounts for people who left months ago, and staff with admin rights they never needed. Fix those, then keep the rhythm going.
Change management is the second area. Changes to the live ERP, such as a new approval rule, a custom report, or a data correction made directly in the database, should not happen because someone asked in a WhatsApp group. Write down who requested the change, who approved it, who made it, and whether it was tested before going live. Limit direct edits to production data to a small, named group, and keep a log of what they changed.
Segregation of duties matters even in a small team. The person who creates a new supplier should not be the same person who approves payments to that supplier. The person who builds a customization should not move it into the live system without someone else checking it. When the team is too small to split roles properly, add a compensating control, for example the owner reviewing a monthly list of new suppliers and changed bank account details.
Backups are the third area, and auditors want evidence, not reassurance. Write down what is backed up, how often, where the copies are kept, and for how long. Then test a restore: take a folder or a copy of the database, restore it to a separate location, and record the date, what was restored, and whether it opened correctly. A backup that has never been restored is only an assumption.
The fourth area is incident handling. One or two pages are enough: what counts as an incident, who to call first, who may decide to shut a system down, and how management gets informed. Keep a simple log of incidents and what was done about them, including small ones such as a lost laptop or a phishing link someone clicked. Auditors look for that log as proof the process is actually used.
Put all of this on a calendar. Each quarter, review user access, test at least one restore, and update any document that changed. Give each control a named owner: who approves new ERP users, who may change production data, who checks the backup logs. The roles do not need to be elaborate, but they need to be written down. Companies that keep this rhythm rarely scramble before an audit, because the evidence is already sitting in a folder.
If an audit is coming up, or you want your IT set up so the next one is not a scramble, contact Kerja Itu Mudah. We can review your current controls, list the gaps an auditor is likely to raise, and help you put the quarterly routine in place. If you want someone to keep it running, IT governance and audit oversight is part of our monthly retainer, starting from IDR 5 million per month.