Named access instead of exports and shared passwords
Enterprise finance teams share books with accountants securely by giving each external accountant a named login to the accounting system with only the permissions they need, instead of emailing exports or lending a staff password. Access is checked at the start of each engagement and removed when the person leaves the firm or the engagement ends.
Whether the firm is preparing statutory accounts, tax computations or audit support, it needs to see the ledger and the documents behind it. The decision for finance is how that viewing happens, and what record it leaves.
In an enterprise, the number of external people involved adds up quickly. The audit firm sends a partner, a manager and several associates; the tax agent has its own team; an outsourced payroll provider may need journal access. Each of them is a separate access decision, and each should be traceable to an engagement letter.
What goes wrong when ledgers travel by email
An emailed trial balance or ledger export is a snapshot. If finance posts an adjustment the next day, the accountant is working on stale figures and the two versions drift apart. Year-end then involves reconciling the accountant's working file back to the company's books.
Exports also leave sensitive data in places the company does not control: the accountant's inbox, a personal laptop, a shared folder at the firm. Customer lists, supplier bank details and payroll-related entries are exactly the information a company would not choose to scatter.
Shared logins are worse. If the accountant signs in with a finance staff member's credentials, every change they make appears as that employee's work, and the audit history no longer shows who did what. The employee also cannot change their password without breaking the firm's access, so the password tends never to change at all.
Access rules to agree with your accounting firm
Put these in writing when the engagement starts, so neither side is surprised later.
- Each accountant gets their own named account, never a shared one
- Permissions match the engagement, with review-only access for audit support and posting rights only where the firm prepares adjustments
- Adjustments made by the firm show under the accountant's name in the audit history
- Multi-factor authentication, or the strongest sign-in option the system offers, is switched on
- A named finance owner inside the company approves every new external user
- External access is reviewed at each year end and whenever the firm's team changes
Personal data inside the ledger and the PDPA
Ledgers hold personal data: names and contact details of individual customers, staff claim records, sometimes salary-related postings. Malaysia's Personal Data Protection Act (PDPA) governs how that information is handled, including disclosure to a third party such as an accounting firm. Ask your legal adviser or data protection lead what your obligations are, and check current guidance from the Personal Data Protection Department.
In practice, limit what the accountant can see to what the engagement needs, and make sure the engagement letter covers confidentiality and data handling. If payroll is processed in a separate system, consider posting summary payroll journals to the general ledger rather than one line per employee. Detailed payroll records can then stay in the payroll system, with access granted separately and only to those who need it.
Removing access when people or firms change
Access tends to be granted carefully and removed carelessly. An audit senior who worked on last year's file moves to another client, but the login still works. The company appoints a new firm, and the previous partner can still see the books.
Tie removal to events: the end of an engagement, notice that a firm employee has left, or a change of auditor. Ask the firm to tell you when its team changes, and make that notice a written term of the engagement rather than a courtesy. Every quarter, pull a list of external users and confirm each name with the firm.
Supporting documents need the same care. If the accountant asks for contracts or bank statements, share them through a controlled folder with expiring links rather than as email attachments, and keep a log of what was sent. At the end of the engagement, ask the firm to confirm in writing what it has retained and on what basis, which your engagement letter should already describe.
Accountant access built into the accounting system
BukuCloud lets a company give its accountant a free firm-staff seat, or connect through the Practice console that accounting firms use to work across their clients. Either way, the accountant works in the live books under their own login rather than on an emailed copy. See bukucloud.com.
Frequently asked questions
Is a password-protected export good enough?
A password reduces the risk of interception, but once opened the file is a copy outside your control. It can be forwarded, saved to a personal device, or kept long after the engagement ends. It also goes stale as soon as you post another entry. Named access to the live system avoids both problems and records what the accountant did.
Should our auditor have the same access as our tax agent?
Not necessarily. Auditors generally need to review records and evidence, while a tax agent or outsourced bookkeeper may need to prepare and post adjustments. Give each the permissions their work requires and nothing more. If one firm performs several roles, agree with them which individuals need which level of access, and record it.
What should we do if an accountant's login is compromised?
Disable the account at once, then review the audit history for anything posted or changed since the suspected compromise. Tell the accounting firm, reset credentials, and work out whether personal data may have been exposed. Ask your data protection lead whether any notification duties apply under current PDPA requirements, and document what happened and how it was resolved.
Next step
Explore BukuCloud or tell Fasttrade what your team needs.
These articles explain enterprise process design. Product availability and detailed scope are confirmed in conversation.