To check the MCA audit trail in BUSY, confirm four things for the whole year.
The option was on, the edit log has entries in every period, the edits match the vouchers and the files are kept. Rule 3(1) asks for an audit trail that cannot be disabled, for financial years starting on or after 1 April 2023. A copy of the data folder lets you count the entries.
The audit asks about the audit trail, and the company hands over a screen print. You want more than that. The sections below set out what the rule wants, the four tests an auditor can run and how the data files help with each.
Who Should Check the MCA Audit Trail in BUSY?
Pick the role closest to yours.
You must report on the audit trail and want evidence beyond a screen print.
See the four tests →You want to know what the auditor will ask before the audit starts.
Run the check yourself →BUSY is not on this PC and you still need to review the log.
Read the files →The rule is about software, but the evidence sits in data. A statutory auditor who accepts a screen print is trusting the screen. A review of the data files adds a second view that does not depend on one report. This guide shows what to test and how the files help.
What Does the Audit Trail Rule Ask For?
The ICAI journal's article on audit trail duties sums up the proviso to Rule 3(1) under the Companies (Accounts) Rules, 2014. A company using accounting software must use software that records an audit trail of every transaction, keeps an edit log of changes with their dates and cannot have the trail disabled. It covers financial years beginning on or after 1 April 2023.
The auditor's side sits in Rule 11(g) of the audit rules. The article adds three limits worth knowing. Records kept by hand or in Excel outside the software are outside Rule 3(1), though entries posted from them are covered. Only books of account are covered, not every paper. If a third party keeps the books on its own software, the requirement reaches that software.
Which Four Tests Does an Auditor Run on the Audit Trail?
The same article suggests testing whether the trail was on all year, whether it could be switched off, whether anyone changed the database directly and whether the logs were kept. Each test below is paired with what BUSY shows and what the data file adds.
| Test | What BUSY shows | What the data file adds |
|---|---|---|
| On for the whole year | The Audit Trail Report, with its first and last dates | The same entries, so you can count them month by month |
| Cannot be switched off | The setting screen, and the vendor's note on the detailed option | Nothing about the setting, so ask management how it is protected |
| No direct changes to the database | Nothing, because the report is written by the program | Vouchers that look edited or renumbered, to compare with the log |
| Logs are kept | Reports that can be re-run | Copies of year files that you can keep and date |
The third row is the one a screen cannot answer. A voucher that shows an edit but has no matching log entry is a question for management. It is not proof of anything, because several harmless reasons exist, such as an edit made before the option was switched on.
How to Review the Audit Trail From a Copied Data Folder
These steps suit a review done away from the client's PC. Do them on a copy and never on the live books.
- Get a dated copy of the whole company folderAsk the company to close BUSY and copy the full COMP folder. Note the date and who handed it over.
- Note the year and the switch-on dateWrite the financial year under review. Ask when the Audit Trail option was turned on and compare that with 1 April.
- List the audit entries month by monthCount the Add, Modify and Delete entries for each month of the year. A month with none is a question to ask.
- Set the entries against the voucher labelsList vouchers marked as edited, renumbered or deleted. Look for the audit entry behind each one.
- Read the users, computers and reasonsNote who made the changes and from which computer. Count the edits that carry no reason.
- Write the working paperRecord the counts, the open questions and the copy you tested. Keep the extract with the audit file.
What Can You Read From the BUSY Data Files?
BUSY keeps each company year in database files. The newer revisions of the BUSY 21 files we examined hold the audit trail in tables of their own, recording the action and its time, who did it, from which computer, the amount and any reason typed. A detailed setting adds a saved copy of the voucher. An older revision in our sample had no such table, so an empty log can reflect the file version and not a clean year.
Univik BUSY Data Forensic Analyzer reads these entries and the activity log with no BUSY on the PC. It also labels vouchers as edited, renumbered, deleted or missing a header, so you can set the two lists side by side. It is read-only and sends nothing off the PC. It cannot show who sat at the keyboard, and it cannot see a change made outside BUSY that left no trace.
Univik BUSY Data Forensic Analyzer puts audit entries next to voucher labels, with the name of the user and the computer.
Download Free Trial Buy Now - $99The free build saves ten items per section on Windows 11 and 10, and a Personal licence is $99 for two PCs. Forensic Analyzer page
The log shows what BUSY wrote. An empty month, a late start or an edit with no entry is a reason to ask. It is not a verdict. Write the question down and let management answer it.
What Belongs in the Working Paper?
- The copy
- Folder name, copy date, who supplied it and the financial year.
- Switch-on date
- When the Audit Trail option was enabled, and where you got that date.
- Monthly counts
- Add, Modify and Delete entries for each month of the year.
- Open questions
- Gaps, edits without entries and blank reasons, each with management's reply.
- Every month of the year is accounted for in the counts
- Each edited or renumbered voucher has an entry or a written reply
- The working paper names the copy you tested
- A second person has re-run one count
Fix Common Problems in an Audit Trail Review
Do this: Check the file version and ask when the option was switched on. An older file revision may hold no log table at all.
Do this: The last session may not have been saved. Ask the company to close BUSY properly and send a fresh copy.
Do this: Several people may share a login. Note it as an observation and ask how users are separated.
Want a second pair of eyes on a log extract? Contact our support team with the question, not the client's data.
Questions About the MCA Audit Trail in BUSY
The Univik staff added the product notes. The rule summary follows an ICAI journal article and BUSY's audit trail page, read on October 11, 2026. Univik does not give legal advice, so confirm any point of law with your professional adviser. Our file notes come from our own reading of BUSY 21 folders.
Pages we read: ICAI journal article · BUSY audit trail page