Can a Law Firm Use AutoCount, SQL Account or ABSS for Trust Accounting?

Law firms rely on accounting software every day to manage finances, issue invoices, track expenses, and produce financial reports. In Malaysia, many firms use solutions such as AutoCount, SQL Account or ABSS (MYOB).

But when it comes to trust accounting, a common question arises:

Can a law firm use AutoCount, SQL Account, or ABSS to manage client trust money?

The short answer is:

Yes, they can be used for a firm’s general accounting. However, they are generally not designed to meet the specialised requirements of trust accounting on their own.

Understanding why requires looking at the fundamental difference between accounting for your own money and accounting for money that belongs to your clients.

The Critical Difference: Firm Money vs Client Money

A law firm’s operating account contains money that belongs to the firm:

  • Professional fees
  • Disbursement recoveries
  • Office income
  • Firm expenses

Trust accounting, however, deals with money that belongs to someone else.

Examples include:

  • Litigation deposits
  • Stakeholder funds
  • Conveyancing monies
  • Settlement proceeds
  • Estate administration funds
  • Client retainers held pending work completion

The law firm is merely holding these funds on behalf of clients until they can be legally disbursed.

As a result, trust accounting requires a much higher level of tracking, transparency, and control.

What Traditional Accounting Software Does Well

Products such as AutoCount, SQL Account, and ABSS are excellent business accounting solutions.

They typically provide:

  • General ledger management
  • Accounts receivable
  • Accounts payable
  • Bank reconciliation
  • Financial statements
  • Budgeting and analysis
  • Tax reporting
  • Invoice and payment processing

For managing a law firm’s business operations, these capabilities are more than sufficient.

The challenge appears when trust funds enter the picture.

Why Trust Accounting Is Different

Trust accounting is not simply another bank account in the general ledger.

A trust account may contain funds belonging to dozens, hundreds, or even thousands of different clients simultaneously.

For example:

Client

Trust Balance

Client A

500,000.00

Client B

50,000.00

Client C

15,000.00

Client D

3,000.00

The bank statement may show RM568,000.

The trust accountant’s job is not merely to reconcile the bank balance.

They must also know:

  • Exactly how much belongs to each client
  • Which matter each balance relates to
  • Whether funds are restricted for specific purposes
  • Which transactions have been authorised
  • Whether a withdrawal would cause a client ledger to go negative

This is where trust accounting becomes significantly more specialised than traditional accounting.

The Problem with Using General Accounting Software Alone

A common approach is to create:

  • A trust bank account
  • Individual client accounts
  • Various sub-ledgers

While this can work for small volumes, it quickly becomes difficult to manage as the number of matters grows.

Some common challenges include:

1. Matter-Level Tracking

A single client may have multiple cases or transactions.

For example:

ABC Holdings Sdn Bhd

  • Property Purchase – Damansara
  • Property Sale – Johor Bahru
  • Commercial Lease Agreement
  • Litigation Matter

Trust funds for one matter cannot automatically be used for another matter.

Traditional accounting systems generally focus on customer accounts rather than matter-specific trust ledgers.

2. Client Ledger Reconciliation

In trust accounting, it is not enough for the bank balance to match the general ledger.

The following must also agree:

Trust Bank Balance = Total of All Client Matter Ledgers

This additional layer of reconciliation is typically performed outside traditional accounting systems using spreadsheets or manual reports.

3. Prevention of Overdrawn Client Balances

Suppose:

  • Client A holds RM20,000
  • A user attempts to withdraw RM25,000

A trust accounting system should immediately prevent the transaction.

Many general accounting systems only verify the overall bank balance, not the balance available within a specific client matter.

This increases the risk of inadvertently using one client’s funds to pay expenses relating to another client.

4. Trust-to-Office Transfers

One of the most common trust transactions occurs when legal fees become payable.

The process generally involves:

  1. Client funds held in trust
  2. Invoice issued
  3. Client authority obtained
  4. Transfer from trust account to office account

A trust accounting solution should create a clear audit trail linking these events together.

In many traditional accounting solutions, this process often requires separate manual entries and supporting documentation.

5. Complete Audit Trails

Trust funds are highly regulated because they belong to clients.

Auditors frequently want to know:

  • Who performed a transaction
  • When it was entered
  • Who approved it
  • Which matter it relates to
  • Supporting documents and authorisations

General accounting systems provide audit logs, but they are not necessarily designed around trust-accounting workflows and controls.

What Many Firms End Up Doing

A common arrangement is:

AutoCount/SQL Account/ABSS

Used for:

  • Office accounting
  • Billing
  • Financial statements
  • Accounts receivable
  • Accounts payable

Separate Trust Records

Managed via:

  • Excel spreadsheets
  • Manual ledgers
  • Custom databases
  • Trust accounting software

The problem is that maintaining information across multiple systems creates duplication, increases administrative effort, and introduces opportunities for error.

What Should a Trust Accounting System Provide?

An effective trust accounting solution should include:

Matter-Based Ledgers

Every transaction is linked to a specific client matter.

Real-Time Trust Balances

Instant visibility of available funds for each matter.

Automated Trust Reconciliations

Ensuring:

Bank Balance = Trust Ledger Control Balance = Total Matter Balances

Withdrawal Controls

Preventing transactions that would create negative trust balances.

Trust-to-Office Transfers

Supporting controlled movement of money from client funds to firm revenue once authorised.

Complete Audit Trails

Recording every adjustment, transfer, and approval.

Regulatory Reporting

Producing reports often required during audits and compliance reviews.

So, Can AutoCount, SQL Account or ABSS Be Used?

The answer is yes, but with limitations.

If a law firm only needs:

  • Billing
  • Financial reporting
  • General accounting

then AutoCount, SQL Account, and ABSS are excellent solutions.

However, if the firm is responsible for managing client trust money, these systems typically do not provide the specialised matter-based controls, trust ledger management, compliance workflows, and reconciliation capabilities that trust accounting requires.

As trust balances increase and the number of matters grows, managing trust funds through general accounting software alone can become increasingly complex and risky.

Where Fiducia Fits In

Fiducia was designed specifically for organisations that hold money on behalf of others.

Rather than treating trust funds as ordinary accounting transactions, Fiducia focuses on:

  • Matter-based trust accounting
  • Client trust ledgers
  • Trust receipts and payments
  • Trust-to-office transfers
  • Reconciliation controls
  • Audit-ready reporting
  • Complete transaction history

This allows firms to continue using their preferred accounting software for business accounting while managing trust funds in a system built specifically for trust accounting requirements.

After all, successful trust accounting is not simply knowing how much money is in the bank. It is knowing exactly who that money belongs to, what it can be used for, and ensuring every transaction can withstand scrutiny when an audit occurs.

Learn more about Fiducia and how it helps organisations manage client funds with confidence.