Ligne Practice Management

Trust accounting for South African attorneys, with the controls built into the system.

Ligne is a modular practice-management platform built around the financial and operational requirements of South African legal practice. Trust and business funds stay separate, overdrafts are refused by the database, and every financial event leaves a permanent record.

Matter trust ledgerIllustration
EntryAmount (ZAR)Balance
Deposit20 000.0020 000.00
Payment−7 500.0012 500.00
Available in trust12 500.00
Posting rejectedA payment of 15 000.00 would overdraw this matter’s trust balance. The database refuses it before it is committed.
Figures are illustrative.
Functional areas

One platform for the whole practice.

Twenty-four areas share one matter, one ledger and one audit trail. Pick an area to read more.

Trust accounting

Receipts, payments, transfers and per-matter trust ledgers, with overdrafts refused by the database.

User manual

Business accounting

General ledger, VAT, fee notes, creditors and disbursements.

User manual

Bank reconciliation

Reconcile bank statements against the trust and business ledgers.

User manual

Month-end & periods

Trust reconciliations each month, and period close that blocks late postings.

User manual

Clients & matters

A workspace for every matter: parties, notes, deadlines and financial history together.

User manual

Contacts

Contact records with roles per matter and South African address look-up.

User manual

Tasks

Matter tasks and follow-ups in one work queue, including tasks raised from email.

User manual

Documents

Matter file storage, a document type for every file, PDF conversion and a pleading generator driven by Word templates and matter data.

User manual

Email

Matter-linked mailbox and correspondence, with scheduled send.

User manual

Calendar & deadlines

Shared diaries and rule-based litigation and conveyancing deadlines.

User manual

Debtors & collections

Collect money owed to your clients: debtor ledger, payment plans, judgments and enforcement.

User manual

Payroll

South African payroll, payruns and SARS outputs including EMP201, EMP501 and IRP5.

User manual

Conveyancing

A guarded transfer pipeline with dated transfer duty, clearances, guarantees, FICA, purchaser and seller statements and a payout checklist.

User manual

Bills of costs

Compile recoverable costs into a versioned bill for taxation, with tariff codes, taxation results and a printable PDF.

User manual

CIPC & company secretarial

Entity tracking, compliance items and CIPC reports for corporate clients.

User manual

Evidence dossier

A matter-scoped evidence register with timelines and bundles for litigation.

User manual

Reporting

Trust, financial and SARS reports, including LPC reporting for the firm.

User manual

Dashboards

Case analytics with KPI tiles and tabbed reports, and a practice snapshot on the welcome screen.

User manual

Search

One search box in the toolbar across matters, contacts and invoices, extended by each module.

User manual

Import & export

Excel workbooks for contacts, clients and matters, with a dry run before anything is written.

User manual

Opening balances

Capture general ledger and trust opening balances once, as a single transaction, when you go into production.

User manual

Users & access

Roles, permissions and overrides, checked at the window and again in the service layer.

User manual

Windows & workspace

Dock, float and maximise windows across monitors, with your layout remembered.

User manual

Updates

Signed updates delivered module by module from a site the firm controls.

User manual
What it is
A legal practice-management and trust-accounting platform for South African law firms.
Why it differs
The key financial controls sit in the database and posting engine, not in a checklist.
Where data lives
On infrastructure the firm controls. There is no vendor-hosted multi-tenant service.
Control design and assurance

Financial integrity, enforced by design, not assumed through procedure.

Where a generic accounting package relies on users following procedure correctly, Ligne’s primary controls are systemic: they sit in the database and the posting engine, not in a checklist.

The aim is to make certain kinds of accounting error structurally difficult or impossible, rather than merely warning the user about them.

Every financial event is written together to the general ledger, the relevant matter ledger and an immutable audit trail. Corrections are made only by reversing or adjusting entries. Original history is never overwritten.

  1. ScreenCaptures what the user intends
  2. PresenterRoutes the action to one business operation
  3. Use caseValidates and runs a single transaction
  4. Ledger serviceTranslates the command into balanced entries
  5. PostgreSQLTrust overdraft constraint, whichever screen or report called it

The layers above make the application maintainable. The layer below makes it dependable: a constraint trigger rejects any posting that would overdraw a trust matter before it can be committed.

Proof on demand

Check that the books agree, whenever you want to know.

The Trust Bank Audit runs a fixed list of independent checks in seconds: the overdraft safeguard is on, every posted entry balances, each trust entry has the shape its type requires, the bank equals what is owed to clients, and every matter’s trust ledger agrees with the general ledger to the cent. It also looks for overdrawn clients, reservations that are not covered, stored balances that have drifted, reversals that are not paired, bank accounts that have not been reconciled lately, and trust postings that name no matter.

The result is a plain verdict, with the claim each check proves and what it found. Each run is saved unaltered, shown as “last verified” on the dashboard, the matter overview, the client screen and at sign-in, and can be printed as a Trust Integrity Certificate.

The Trust Bank Audit window in Financial Diagnostics: a green verdict reading ‘Your trust account is in balance’, trust assets and the amount owed to clients both R 51 041.99 with a variance of R 0.00, and a list of checks that each show Passed with what they found.
Trust Bank Audit. The verdict, the reconciliation and every check performed, in one window.
Page one of a Trust Integrity Certificate for a sample firm: verdict Verified, physical trust cash and the amount owed to clients both R 1 082 224.75 with a variance of 0.00, and eleven checks each marked PASS.
Trust Integrity Certificate. The printed record of an audit run: the verdict, the reconciliation, every check and the fingerprint that shows the record is unaltered. Sample data.
A trust creditors list as at 31 October 2026 for a sample firm: eight clients and matters with their trust balances, totalling R 1 082 224.75, equal to the trust bank accounts per the general ledger, with a certification block.
Trust creditors list. Every client and matter holding trust money, compared with the trust bank balance before it can be certified. Sample data.
Every entry, every batch

The same plain answer for each transaction and each posting batch.

Transaction Integrity checks every posted entry: its ledger legs balance, its audit header agrees with what was actually posted, and a trust entry reached the matter’s trust ledger. Batch Integrity compares each posting batch’s recorded count and totals with the entries it really holds, and can correct a batch that has drifted.

Both give an outcome you can read at a glance, the figures behind it, and the first problem by name when there is one.

The Transaction Integrity tab: a green banner reading ‘All 677 entries are consistent’, tiles showing 677 entries checked, 677 consistent and none needing attention, and a table of entries with OK markers for the ledger, audit and trust ledger checks.
Transaction Integrity. Every posted entry, with the result of each check beside it.
The Batch Integrity tab: a green banner reading ‘All 426 batches are consistent’, tiles showing 426 batches checked, 2 open and none needing attention, and a table of posting batches with their status, cached and actual entry counts and totals.
Batch Integrity. Each posting batch’s recorded count and totals against the entries it holds.
Worked examples

See how real transactions post.

Every transaction becomes balanced journal entries. These examples show the most common transactions, deliberately simplified.

INVOICE_POST_VAT Simplified

A fee note with VAT

The firm raises a fee note for R10 000.00 plus 15% VAT. Revenue and VAT owed to SARS are separated at the moment of posting, so the VAT return is built from the ledger, not reconstructed afterwards.

Client owes the firm
R11 500.00
Fees recognised
R10 000.00
Owed to SARS
R1 500.00
Journal entries
AccountDebitCredit
1. Fee note FN-2041: fees, excluding VAT
1300 Accounts Receivable10 000.00
4100 Professional Fees10 000.00
2. Fee note FN-2041: VAT
1300 Accounts Receivable1 500.00
2300 VAT Output Account1 500.00
Total11 500.0011 500.00

One check shown. Debits equal credits at R11 500.00. The engine confirms this and far more before anything is committed.

MATTER_CREDITOR_INVOICE Simplified

A creditor invoice linked to a matter

Counsel’s invoice arrives for a specific matter. The firm now owes the creditor, and the cost is held as a recoverable disbursement against that matter until it is billed on.

Owed to creditor
R6 900.00
Recoverable from client
R6 900.00
Trust movement
None
Journal entries
AccountDebitCredit
1. Matter creditor invoice: counsel’s fee
1320 Disbursements Recoverable6 900.00
2200 Accounts Payable6 900.00
Total6 900.006 900.00

One check shown. Debits equal credits at R6 900.00. The engine confirms this and far more before anything is committed.

TRUST_CREDITOR_PAYMENT Simplified

Paying that creditor from the matter’s trust funds

When the client has money in trust for the matter, the creditor can be paid directly from it. The first posting is a real trust disbursement. The second discharges the payable and uses up the recoverable disbursement recorded when the invoice arrived, because the client’s own money bore the cost. Nothing passes through the operating account, and no VAT is added to a cost the client’s trust money has already settled.

Creditor settled
R6 900.00
Operating account
Not touched
Recoverable from client
R6 900.00 → R0.00
Matter trust balance
R20 000.00 → R13 100.00
Journal entries
AccountDebitCredit
1. Trust payment to creditor
2100 Trust Liability (client)6 900.00
1100 Trust Bank Account6 900.00
2. Creditor invoice settled from trust
2200 Accounts Payable6 900.00
1320 Disbursements Recoverable6 900.00
Total13 800.0013 800.00

One check shown. Debits equal credits at R13 800.00. The engine confirms this and far more before anything is committed.

One trust check shown. Available R20 000.00 covers R6 900.00, leaving R13 100.00. The database enforces this independently of the screen.

One billing check shown. If the cost was already billed to the client on an invoice, the payment from trust is refused, because that invoice has already used up the recoverable amount. Pay the creditor from the operating account and apply the client’s trust funds to the invoice instead.

Trust reservation Simplified

Reserving trust funds for an expected cost

Counsel’s account and the sheriff’s fees are still to come, but the money is already in trust. An attorney places a hold on part of the matter’s balance, with a note saying why. The hold posts nothing: the trust balance is unchanged, but the held amount can no longer be spent, swept to the business account or applied to an invoice until it is released or used to pay that cost.

Matter trust balance
R20 000.00 (unchanged)
Reserved
R8 400.00
Available to spend
R11 600.00
Matter trust balance, one trust bank account
ItemAmount
Held in trust for the matter20 000.00
Reserved: counsel’s fee (expected invoice)6 900.00
Reserved: sheriff’s fees1 500.00
Available to spend11 600.00

No journal entries. A reservation changes what is available, never the general ledger, the matter ledger or the bank reconciliation.

One trust check shown. A transfer of R12 000.00 to the business account is refused: only R11 600.00 is available. When counsel’s invoice arrives, paying it from trust can use the reservation, and any remainder can be released in the same step. The database enforces this independently of the screen.

PAYMENT_TRUST Simplified

Transferring trust funds to the business account

The client owes fee note FN-2041 (R11 500.00) and has the funds in trust. The transfer pays the invoice from trust: money leaves trust, arrives in the operating account, and the receivable is cleared in the same transaction.

Invoice balance
R11 500.00 → R0.00
Matter trust balance
R20 000.00 → R8 500.00
Trust and business
Moved in one transaction
Journal entries
AccountDebitCredit
1. Trust to business transfer
2100 Trust Liability (client)11 500.00
1100 Trust Bank Account11 500.00
2. Payment from trust: FN-2041
1200 Operating Bank Account11 500.00
1300 Accounts Receivable11 500.00
Total23 000.0023 000.00

One check shown. Debits equal credits at R23 000.00. The engine confirms this and far more before anything is committed.

One trust check shown. Available R20 000.00 covers R11 500.00, leaving R8 500.00. The database enforces this independently of the screen.

PAYMENT_TRUST (batch) Simplified

A trust sweep across several matters

A sweep finds open invoices whose matters hold trust funds and stages one draft for each in a single batch. Each matter’s available funds, after any reserved amounts, are shared across its invoices and never over-allocated. Nothing posts until a person reviews the batch.

Invoices staged
3 of 4
Total moved
R19 000.00
Review
Before anything posts
Proposed sweep, one trust bank account
InvoiceBalance dueTrust availableStaged
Matter A · INV-A19 200.0015 000.009 200.00
Matter A · INV-A28 050.005 800.005 800.00
Matter B · INV-B111 500.004 000.004 000.00
Matter C · INV-C13 450.000.00Skipped
Batch total19 000.00
Journal entries
AccountDebitCredit
1. Batch total: trust liabilities, three matters
2100 Trust Liability (client)19 000.00
1100 Trust Bank Account19 000.00
2. Batch total: receivables cleared
1200 Operating Bank Account19 000.00
1300 Accounts Receivable19 000.00
Total38 000.0038 000.00

One check shown. Debits equal credits at R38 000.00. The engine confirms this and far more before anything is committed.

PAYMENT_DIRECT Simplified

A client pays an invoice

The client pays fee note FN-2042 by EFT into the firm’s operating account. The bank balance rises and the receivable falls by the same amount, so the debtors’ ledger and the invoice always agree.

Received
R4 600.00
Invoice balance
R4 600.00 → R0.00
Trust movement
None
Journal entries
AccountDebitCredit
1. Direct payment: FN-2042
1200 Operating Bank Account4 600.00
1300 Accounts Receivable4 600.00
Total4 600.004 600.00

One check shown. Debits equal credits at R4 600.00. The engine confirms this and far more before anything is committed.

TRUST_RECEIPT + debtor ledger Simplified

A debtor pays money owed to a client

On a collections matter the debtor pays R8 000.00 into trust. The money is held for the client, and the same transaction mirrors it into the debtor ledger as unallocated suspense. It reduces the debt only when it is allocated, in order, across the ledger buckets.

Debt outstanding
R12 100.00 → R4 100.00
Held in trust for client
R8 000.00
Allocated
Costs, interest, then capital
Debtor ledger: allocating the receipt
BucketOwingAppliedRemaining
Costs1 500.001 500.000.00
Interest600.00600.000.00
Capital10 000.005 900.004 100.00
Total12 100.008 000.004 100.00
Journal entries
AccountDebitCredit
1. Trust receipt from debtor, held for the client
1100 Trust Bank Account8 000.00
2100 Trust Liability (client)8 000.00
Total8 000.008 000.00

One check shown. Debits equal credits at R8 000.00. The engine confirms this and far more before anything is committed.

CREDITOR_PAYMENT Simplified

Paying a creditor from the operating account

When the firm settles the same creditor from its own funds instead, the payable is discharged against the operating bank account. Trust money is never involved.

Creditor settled
R6 900.00
Paid from
Operating account
Trust movement
None
Journal entries
AccountDebitCredit
1. Creditor payment
2200 Accounts Payable6 900.00
1200 Operating Bank Account6 900.00
Total6 900.006 900.00

One check shown. Debits equal credits at R6 900.00. The engine confirms this and far more before anything is committed.

Illustrative amounts and references, simplified for explanation. Real postings are subject to many more checks than are shown, and entries vary with each firm’s setup. Entries follow the platform’s standard posting templates and chart of accounts. VAT is shown at 15%.

Design principles

What the architecture is designed to protect.

Trust overdrafts are rejected at the database level

A constraint trigger refuses any posting that would overdraw a trust matter, whichever screen or report attempted it.

Every financial event is auditable

The general ledger, the matter ledger and the audit trail are written together, so they cannot silently diverge.

Compliance sits in the workflow

Legal and accounting requirements are addressed at the point of transaction, not reconstructed in reports afterwards.

Designed for longevity

Mature technology chosen to stay maintainable, keeping historical records accessible beyond any single release.

Capabilities

The whole practice, organised around the matter.

Each matter is a complete workspace. Select one and every other window follows it.

Financial operations

Trust and business accounting, general ledger, receipts, payments, trust transfers, VAT, fee notes priced from tariff scales and fee-earner rates, disbursements, reserved trust funds, trust interest and bank reconciliation.

Matter management

Clients, related parties, correspondence, documents, financial history, notes, tasks, deadlines, court appearances, evidence and email, all linked to the matter.

Practice administration

Document management, calendaring and shared diaries that can sync to Nextcloud, workflow deadlines, email integration, full-text search, a global search bar (Ctrl+K) with Back, Forward, recently viewed and pinned records, payroll and debt recovery.

Practice-area modules

Bills of costs, conveyancing with its transfer finances, CIPC and company secretarial compliance, and debtor and collections management.

Matter file storage

A synchronised folder chosen per workstation. Nextcloud is preferred and detected automatically. OneDrive, Google Drive, Dropbox or a network share also work.

Document generator

Pleadings generated from Word templates and matter data. The firm’s own templates live in a shared “Document Templates” folder. Word documents convert to PDF with the LibreOffice installed on the workstation.

LPC reporting

Trust creditors list, trust bank reconciliation, trust integrity certificate, Section 86 and Section 78 reports, Fidelity Fund certificate register and annual trust auditor’s reports.

SARS reporting

EMP201, EMP501, IRP5, IT3(a), PAYE, UIF, SDL, Employment Tax Incentive and medical tax credits.

Financial Transactions on the Trust tab: a list of trust batches with receipts, payments and transfers, all posted, and the selected transaction showing its two entries on the right.
Financial Transactions. Trust receipts, payments and transfers in one list, each batch with its entries beside it.
The Deadline Rules window listing 107 rules with jurisdiction, practice area, trigger event, rule type, offset in days, business-day and holiday settings, warning level and an option to exclude 16 December to 15 January.
Deadline rules. The litigation and conveyancing deadlines are rules the firm can read and adjust, including which periods leave out 16 December to 15 January.
A sample tax invoice on the firm’s letterhead: amount due R 8 351.25, six fee and disbursement lines, professional fees R 10 375.00, VAT at 15%, less R 4 000.00 paid from trust, and payment details with a warning that banking details never change by e-mail.
Tax invoice. The firm’s letterhead, the amount due at the top, fees and disbursements, VAT, the trust balance held and how to pay. Sample data.
A sample trust statement for one matter: opening balance R 5 000.00, receipts R 27 000.00, payments R 13 550.00 and a closing balance held in trust of R 18 450.00, with each movement listed.
Trust statement. What the firm holds for the client, receipt by receipt and payment by payment, with the client-money notice. Sample data.
Bills of costs

From the matter file to a bill ready for taxation.

Preparing a bill of costs means finding every recoverable item on the file and presenting it the way a taxing master expects. Ligne compiles the bill from the matter’s own records and keeps your editing separate from the accounting. Compiling a bill never changes the ledgers.

  1. Start the bill. Choose the matter and the type: party and party, attorney and client, amended or supplementary. The header holds the case number, parties, taxing master and taxation date.
  2. Import from the file. Time entries, fee notes and disbursements on the matter come across as copies, with counsel’s fees picked out. Nothing is offered twice, and editing a bill item never touches the original record.
  3. Arrange in sections. Ten standard taxation headings, from Instructions to Counsel Fees and Disbursements, are set up on every bill. Rename them, add your own and reorder items.
  4. Apply the tariff. Search the firm’s tariff fee codes and attach one to an item, with units and rate.
  5. Validate. The bill is checked for missing dates, zero or negative amounts, missing tariff references, unassigned sections and likely duplicates. The warnings are advisory. The bill is the attorney’s document.
  6. Lock and print. Lock the bill, then print it or save it as a PDF with section subtotals and totals.
  7. Record taxation. After taxation, enter the taxed amount and a note against each item. The original amount is never overwritten. If the bill must change, a new version is created and the earlier one stays frozen as the record.
Bill of costs · Version 1 · LockedIllustration
ItemAmountTaxed
Pleadings
Drafting particulars of claim4 200.003 800.00
Consultations
Consultation with client1 800.001 800.00
Counsel Fees
Counsel’s fee for trial15 000.0012 000.00
Disbursements
Sheriff’s fees950.00950.00
Total21 950.0018 550.00
Illustrative items and amounts. The taxed column is recorded beside the original, never over it.
The Fee Codes window with the Magistrates’ Courts fee sheet open and the Edit Fee Code dialog on its Tariff Details tab, showing category, tariff reference, tariff, tariff version, scale, court level, litigation phase, recoverability and who may bill the code.
Fee codes. Each tariff code carries its tariff, version, scale, court level and recoverability, so the bill and the fee note draw on the same source.
Page one of a sample plaintiff’s party and party bill of costs in the High Court, Western Cape Division: items under Instructions and consultations, Pleadings, Discovery, Counsel’s fees and Disbursements, with fees, disbursements and section subtotals.
Bill of costs. Printed with the court heading, the parties as cited, the items in their sections and subtotals carried to the summary. Sample data.
Debtors & collections

Collecting what is owed to your clients.

The debtor module manages the collection of debts owed to the firm or on behalf of its clients, from the first demand through payment plan, judgment and enforcement to settlement or write-off. Every rand is tracked in its own bucket, and money paid into trust by a debtor flows into the debtor ledger without re-keying.

A ledger of seven buckets

Capital, costs, interest, commission, VAT, disbursements and suspense are tracked separately, so you can always show what a payment was applied to.

Trust receipts flow in

When a debtor pays into trust, the receipt is mirrored into the debtor ledger in the same transaction. It reduces the debt only once it is allocated, and reversing the trust receipt unwinds it.

In duplum, applied and recorded

Interest stops accruing at the in duplum cap and the cap is reset on judgment. Every cap event is logged, so the position can be shown to a court.

Payment plans

Instalment schedules with missed payments moving the account into arrears, and a formal default when the arrangement fails.

Judgment and enforcement

Record judgments, issue writs and record their returns. Write off a debt when recovery fails, with the reason on file.

Quotes, ageing and oversight

Settlement quotes with interest brought up to date, age analysis across the book, and debtor and recovery dashboards for supervisors.

Conveyancing

A transfer that cannot skip its prerequisites.

The conveyancing tab on a matter follows a South African transfer from instruction to completion. The stage moves only through a guarded step, the documents that expire are watched, and the money side is kept beside the trust position it depends on.

A pipeline with a history

A stage moves one step at a time, and registration needs the lodgement and registration dates and the title deed number. Anything else — backwards, skipping a stage, or going on with a prerequisite outstanding — needs a specific permission and a reason, and every move is kept in the stage history.

Transfer duty from dated tables

Duty comes from SARS tables held as dated rows and chosen by the sale agreement date, in exact decimal arithmetic. A sale on which VAT is levied carries no duty. A table is marked unverified until an attorney confirms it against SARS.

Clearances and guarantees that expire

Rates and levy clearances, the purchaser’s bank guarantee and the seller’s bond cancellation figures are tracked with their dates. A login alert lists those about to lapse or still not received.

FICA before the FICA stage

The matter can move on when every contact of the client has a verified, unexpired FICA record, or when an attorney records a dated confirmation with a note of what was verified.

Statements for both sides

A statement of account for the purchaser and for the seller is worked out from the figures already on the matter, with any lines added by hand, and prints as a PDF.

A payout checklist tied to trust

The bondholder, the estate agent and the seller’s net proceeds are paid by linking each item to a real trust payment of the matter. A reversed payment re-opens its item, the trust position shows held, reserved and available against what is still to pay, and the matter cannot be completed with a payout outstanding.

A sample purchaser’s statement of account for the purchase of an erf: purchase price R 2 450 000.00, deposit, bank guarantee, transfer duty, conveyancing fee with VAT, Deeds Office fees and a rates adjustment, with a balance due.
Purchaser’s statement of account. Worked out from the figures already on the matter: price, deposit, guarantee, transfer duty, fees and adjustments. Sample data.
Month-end

Month-end with the checks built in.

Closing the month is where trust accounting is proven. Ligne takes you through the steps in order for each trust bank account, and will not close a period while a trust reconciliation is still outstanding.

  1. Import the bank statement. Load the statement as a CSV file. The FNB layout is built in; for any other bank, map its columns once and save the mapping for next month. Lines that cannot be read stop the import instead of being skipped, and a gap in the running balance is flagged.
  2. Clear what matches. Tick matching bank lines and ledger entries together to clear them. A bank line with no ledger entry needs to be entered. A ledger entry not yet on the statement is an outstanding deposit or payment.
  3. Prepare the reconciliation. Choose the trust bank account and the month, and enter the closing balance on the statement. Ligne works out the expected ledger balance and the variance, and creates a draft.
  4. Submit it. A reconciliation with no variance is submitted, which marks the cleared entries as reconciled. A submitted reconciliation cannot be submitted again.
  5. Close the period. An administrator closes the period in Period Management. It cannot close while any trust reconciliation is still a draft. After that, nothing can be posted to the period and backdated entries are rejected.
Trust reconciliation · 2026-09Illustration
LineAmount (ZAR)
Closing balance per bank statement250 000.00
Add outstanding deposits12 000.00
Less outstanding payments−7 500.00
Expected ledger balance254 500.00
Trust ledger balance254 500.00
Variance0.00
Balanced. Status Draft until submitted. Illustrative figures.
A sample trust bank reconciliation at 31 October 2026: bank statement balance, deposits in transit and outstanding payments giving an adjusted bank balance equal to the general ledger and to the matter ledger total, variance 0.00, and the cleared items.
Trust bank reconciliation. The bank statement balance brought to the ledger through deposits in transit and outstanding payments, checked against the matter ledgers. Sample data.
Data in and out

Bring your records in, take your data out.

Existing contacts, clients and matters come into Ligne from Excel workbooks, and the same workbooks can carry your data back out.

Excel templates

Contacts, clients and matters each have a workbook template, in a full or a lite version. Export can include the data already in the system.

Dry run first

Validate a whole workbook without writing anything. Problems are reported by sheet and row number, so they can be fixed in the file.

Updates and skipped rows

Update existing records when identifiers match, or skip rows that fail and carry on. Progress is shown while the import runs.

Opening balances

Go live with the right balances.

Moving onto Ligne means carrying your closing balances over exactly. Opening balances are entered once, checked before anything posts, and posted as a single transaction across the general ledger and the trust ledger.

  1. Enter the general ledger balances. Give each account its debit or credit. Running totals show the difference, and the entries must balance before they can be posted.
  2. Enter trust balances per matter. Record the client, the matter and the trust bank account for each balance, so every matter ledger starts with the right figure. Trust accounts are kept out of the general ledger tab, so nothing is counted twice.
  3. Set the date and reference. The migration date must fall in an open accounting period.
  4. Post once. Only authorised users can post. Everything is written together or not at all, and the screen then locks. Opening balances cannot be posted a second time, and a reversal goes through the system administrator.
Opening balances · 1 March 2026Illustration
General ledgerDebitCredit
1200 Operating Bank Account85 000.00
1300 Accounts Receivable40 000.00
2200 Accounts Payable25 000.00
3400 Partner Capital Account100 000.00
Difference 0.00125 000.00125 000.00
Trust per matterTrust bankAmount
Matter A110020 000.00
Matter B110012 500.00
Total32 500.00
Illustrative accounts, matters and amounts.
Data ownership

Your practice. Your infrastructure. Your records.

Ligne runs on a single workstation, an office server, or private or cloud infrastructure the firm selects. The firm chooses where its data lives. There is no vendor-hosted multi-tenant service.

Continuity of evidence

Historical client and financial records stay available whatever happens to support arrangements.

Independent of hosting

The practice keeps working through an internet outage or a vendor’s service disruption.

Full possession of the record

The firm holds its own database and matter-linked email archive, not a vendor-mediated export.

POPIA & confidentiality

Sensitive client information is not routinely replicated across third-party hosted services.

South African context

Designed around South African legal and financial regulation.

Compliance controls are built into the accounting engine wherever practical.

FrameworkArea addressed
Legal Practice Act 28 of 2014 Trust account separation, Section 86 trust accounting, interest handling, Fidelity Fund reporting
LPC Rules Trust creditors, reconciliations, auditor reporting, trust integrity requirements
Income Tax Act PAYE, UIF, SDL, ETI, IRP5, EMP201, EMP501
Companies Act Corporate client compliance and company secretarial tracking
A sample Fidelity Fund certificate register in landscape: five people with ID, tax and admission numbers, certificate number and expiry, and a status for each: three Valid, one Expiring and one Missing, and a partner certification that asks the signer first to confirm the person with no certificate is not a legal practitioner.
Fidelity Fund certificate register. Each practitioner’s admission, certificate number and expiry, with the ones that need attention marked in words. The partner certification is withheld when a certificate has expired. Sample data.
Security

Security by architecture, not by promise.

Each firm holds its own records. That limits how far any single incident can spread, and leaves the firm in control of how its data is protected.

No central pool of data

Every installation has its own database. There is no shared service holding many firms’ client, estate and trust records.

A breach stays contained

Installations share no database, hosted back end or credentials, so an incident at one firm does not reach another.

The vendor holds no client data

There is no vendor-side data store to subpoena, sell, leak or train on.

A small attack surface

A desktop client talking to a firm-controlled PostgreSQL database has no public web application to probe and no browser session to hijack. The product needs no public internet endpoint.

Roles enforced in the service layer

Permissions are checked in the service layer, not only on screen, and every financial event leaves an immutable audit trail.

Credentials handled carefully

Salted BCrypt password hashes under a 12-character policy, an encrypted database connection password, and optional TLS for connections.

Patching is built in. Releases arrive through the NetBeans Platform’s update mechanism from the firm’s configured update site. Only changed modules are downloaded, and updates are digitally signed. No system is immune to attack, and a firm remains responsible for securing its own servers, workstations, backups and staff access.

Users & access

Access control built into every layer.

Who may do what is decided by roles and permissions held in the database, and it is checked where the work is done, not only where the button is.

Permissions in one registry

Every permission the application checks is declared in a single registry. A permission that is not declared does not exist, and startup checks the database for any unknown ones.

Roles, with overrides

Users hold roles, from system administrator to paralegal, and individual grants and denies can sit on top. A deny wins, and anything not granted is refused.

Checked twice

A window needs permission to open and checks again as it opens. Every sensitive action is checked again in the service layer, so hiding a button is never the only control.

Sessions and administration

A firm-set inactivity timeout warns before signing a user out. Password resets issue temporary passwords, and user administration is logged.

Workspace

Arrange the practice the way you work.

Ligne is a true desktop application. Every screen is a window you can dock beside others, drag into a new position, float on its own or maximise to fill the screen, and your layout is remembered between sessions.

Every window follows the matter you have selected. Keep the matter workspace on one monitor and float the trust ledger, email or documents on another, and they stay in step as you move between matters.

  • Dock windows side by side or in tabs.
  • Float any window on a second monitor.
  • Maximise a window when you need the whole screen.
Two monitorsIllustration
Monitor 1: docked
Matters
Matter workspace
Notes and tasks
Monitor 2: floating
Trust ledger
Email
Layout shown is an example.
Updates

Updates, one module at a time.

Ligne is built from independent modules, and it is updated the same way. A fix to one module reaches every workstation as that module alone, without reinstalling the application or handling installers by hand.

  1. The firm hosts the update site. It can be a shared folder or a web location the firm controls.
  2. Each workstation checks it. The modules that have changed are listed for installation.
  3. Only what changed is downloaded. Everything else on the workstation stays as it is.
  4. Updates are signed. A workstation installs only updates signed by a certificate it has been told to trust.
The Plugins window listing the installed modules, such as the calendar, CIPC compliance, email, bank reconciliation and bills of cost modules, each with an active marker, over the Database Maintenance screen with backup and restore buttons.
Installed modules. Every module is listed, activated or deactivated on its own. Database maintenance, with backup and restore, is behind it.
Extensibility

Extend, don’t fork.

Ligne is not meant to be forked for each firm’s requirements. It is meant to be extended, and its module architecture enforces that: independent modules with controlled dependencies.

Shared services, database migrations and integration points give new modules a stable surface to build against, so new capabilities do not destabilise the ledger.

Core platform

Trust accounting, general ledger, matter accounting, client and matter management, document and email integration, workflow, compliance reporting, the immutable audit trail, security and database infrastructure.

Additional modules

Bank reconciliation, debt and collections, bills of costs, conveyancing, CIPC and company secretarial, payroll, evidence and dossier management.

Bespoke firm modules

Firm-specific workflows, custom reports, specialised billing models, document automation, AI-assisted functionality, banking and accounting integrations, custom import and export, third-party APIs.

Technology

A professional desktop application, built on proven foundations.

Ligne is built on the Apache NetBeans Platform, a mature modular desktop framework, so Ligne’s own code can concentrate on legal practice, accounting and trust compliance.

The result is a workstation application for sustained daily use: responsive, efficient to navigate and independent of a browser tab. Technology is chosen for stability and long-term support rather than passing trends.

  • Java 25
  • NetBeans Platform
  • Swing + FlatLaf
  • JavaFX (Windows and Linux)
  • PostgreSQL
  • jOOQ
  • Flyway migrations
  • Automated regression testing
40integrated application modules
83version-controlled database migrations

Module and migration counts as at 11 November 2026.

Built and continuously developed

Software that is still being engineered.

Ligne is actively developed. Each month’s merged changes are summarised in a public development log, covering trust accounting, reporting, payroll, email and the document generator.

Licensing

Ligne is proprietary, closed-source software, commercially licensed. A controlled platform keeps one consistent financial architecture and supported releases, and lets firm-specific work arrive as extensions rather than forks. Use, copying, modification and redistribution are subject to the applicable licence and contractual terms.

Professional services

Implementation, integration and bespoke development.

Installation, configuration and database setup, migration of existing records, onboarding, integrations with email, calendars, banking and document systems, and firm-specific modules delivered alongside the core platform rather than by modifying it. Customer requirements can feed into the core roadmap, an optional module, or a private extension.

ligne@krugerengelbrecht.co.za

To provide South African legal practitioners with a transparent, auditable and professionally engineered trust accounting and practice management platform, where financial integrity is enforced by design rather than assumed through procedure.

— Ligne Financial Software