AOMS Intelligence
Bridging the gap between legal operations and technical architecture. This dashboard provides a live view into the Advocates Office Management System.
Key System Capabilities
-
01
Unified Case Lifecycle
End-to-end management of Suits, E.P. (Execution Petition), and I.A. (Interim Application) within a single workflow.
-
02
Accounting/GL Sync
Auto-generation of ledgers for every new client/suit ensuring financial accuracy.
-
03
Multi-Bill Receipting
Distribute single payments across multiple cases and active invoices.
-
04
Hierarchical Tracking
Parent-child relationship management for complex litigation chains (Suits → E.P. → I.A.).
-
05
Multi-Office Architecture
Configurable branch management for multi-location legal firms.
-
06
Automated Court Diary
Centralized calendar for hearings, postings, and case status updates.
-
07
Financial Integrity Engine
Point-in-time Balance Sheets and P&L statements built directly into the DB.
-
08
Advanced Reporting
Over 40+ specialized reports for performance and due tracking.
-
09
Role-Based Security
Granular access control for clerks, advocates, and senior partners.
-
10
Registry & Archives
Tracking of certified copies, decree debt, and historical registers.
System Overview
Legal Lifecycle
End-to-end management of Suits, Execution Petitions, and Interim Applications.
Accounting Bridge
Double-entry GL system linked directly to client interactions and case filing.
Multi-Office Support
Configurable for multiple branches or distinct legal offices with parent-child hierarchy support.
Analytical Engine
Over 40+ specialized reports for case tracking, dues, and office performance.
Database Explorer
System Architecture
The DAL Helper (DatabaseController.vb)
A static management layer that abstracts MySQL operations. It handles global connection pooling, manual transaction starts/commits, and raw SQL execution.
Active Record Entities
Each business object (Suit, Client, Bill) carries its own persistence logic. When you call suit.Save(), the entity itself constructs and executes the required SQL statements.
Accounting Synchronization
System triggers ensure that creating a Client or Suit automatically generates an Accounting Ledger, maintaining a perfect 1:1 link between legal cases and financial tracking.
MDI Presentation Layer
A classic Windows Forms interface providing multi-document navigation, organized into Masters (Setup), Activities (Operations), and Reports.
System Relationship Map
Visual map of the AOMS core entity relationships. (Native CSS rendering for maximum reliability)
Parties
Clients & OpponentsSuits
Core Legal CaseCourts
JurisdictionsI.A. / E.P.
Interim Application / Execution PetitionAccounting
Ledgers & GroupsHearings
Court DiaryBills
InvoicesReceipts
CollectionsStatements
Case SummaryThe system operates on a Hub-and-Spoke model where the Suit is the central anchor. All other modules (Financials, Accounting, Registry) are synchronized in real-time to the Suit's lifecycle.
App Gallery
Visual reference of the core application forms and menus. Click an image to expand.
Business Rules & Form Logic
Client-Accounting Lock
No client can exist without an associated Ledger Code. This ensures that every bill generated has a valid debit point in the accounting system.
Intelligent Receipt Allocation
Receipts are not just "entry records". They allow a single Gpay/Cash payment to be distributed across multiple active bills and multiple cases for the same client.
EP & EA Hierarchy
Execution Petitions (EP) act as parent containers for Execution Applications (EA). Each level maintains its own independent court posting diary.
Operational Workflows
1. Intake Phase
Define Client -> Assign Ledger -> Set Accounting Group -> Finalize Party Master.
2. Litigation Phase
File Suit -> Automatic Ledger Creation -> Post Hearing Dates -> Manage IAs.
3. Financial Phase
Generate Bill -> Allocate Receipt (Multi-Bill) -> Close Transaction -> Statement Generation.