How practice management and document management systems actually connect

A new client calls a mid-size firm on a Monday morning. By Tuesday, a partner has opened a matter, a paralegal has created a folder, and an associate is already emailing a draft NDA. Three systems just fired in sequence: practice management, document management, and email. If the matter number generated in the first system does not match what shows up in the second, the firm has a filing problem that will surface eighteen months later during a malpractice audit or a client billing dispute. This lesson traces exactly where that handoff succeeds and where it quietly breaks.

The core systems, defined

Before tracing the flow, fix the vocabulary:

• PMS (Practice Management System): the system of record for matters, clients, conflicts checks, and often billing. Examples: Elite 3E, Aderant, Clio (smaller firms), Intapp.
• DMS (Document Management System): where documents and emails actually live, versioned and indexed. Examples: iManage, NetDocuments, OpenText.
• Matter number: the unique identifier assigned to a piece of client work, usually structured as client code plus matter code (e.g., 10234-0007).
• ACL (Access Control List): the permission structure determining who can see a file or folder. In law firms this is how ethical walls (information barriers required when a lawyer has a conflict of interest) get enforced technically.

Tracing matter opening: step by step

Step 1: Intake and conflicts. A new matter request enters the PMS or a dedicated conflicts and intake module (often part of Intapp or a standalone tool like Elite's Conflicts Manager). This triggers a conflicts check against the firm's historical client and adverse-party database, a process governed by professional responsibility rules like the ABA Model Rule 1.7 on conflicts of interest.

Step 2: Matter number assignment. Once cleared, the PMS generates the matter number. This number is the spine of the entire tech stack: billing codes, timekeeping entries, and document folders all key off it.

Step 3: DMS folder creation. Here is the first real fork in the road. In a well-integrated stack, the DMS listens for new-matter events from the PMS via an APIAPIApplication Programming Interface: eine standardisierte Schnittstelle, über die Anwendungen kommunizieren und Daten austauschen, ohne die interne Funktionsweise der jeweils anderen zu kennen.Vollständige Definition ansehen → or a middleware connector (common vendors: BigHand, Litera, or custom integrations built on iManage's REST APIREST APIApplication Programming Interface: eine standardisierte Schnittstelle, über die Anwendungen kommunizieren und Daten austauschen, ohne die interne Funktionsweise der jeweils anderen zu kennen.Vollständige Definition ansehen →) and auto-creates a matching workspace, using the identical matter number as the folder ID.

In a poorly integrated stack, a paralegal manually creates the DMS folder and types the matter number in by hand. Typos happen. A folder gets created as 10234-007 instead of 10234-0007. Now search, billing reconciliation, and e-discovery collection for that matter will silently miss documents sitting in the mistyped folder.

Step 4: Access permissions inherit (or don't). The PMS knows who is staffed on the matter and whether an ethical wall applies. If integration is real, that staffing list pushes to the DMS and sets the folder ACL automatically. If it is not, someone has to replicate the permission list by hand in a second system, and “by hand” is exactly where information barriers fail.

Where drift actually happens

Three failure patterns show up repeatedly in real firm environments:

1. Timing lag. The PMS matter opens Monday; the DMS integration batch job runs overnight and doesn't sync until Tuesday. Anyone drafting a document Monday afternoon saves it into a generic "unfiled" folder, which then never gets reconciled.
2. Renames and transfers. A matter gets renumbered after a client billing entity change, or transferred to another office. PMS updates the number. DMS folders, especially older ones, often keep the legacy ID because renaming a folder with thousands of nested documents and preserved version histories is operationally risky, so IT teams frequently choose not to.
3. Permission creep. A lawyer rotates off a matter. The PMS staffing record updates immediately (it's just a database row). The DMS access list often does not get revoked on the same schedule, because removing DMS access requires a separate workflow, sometimes a manual ticket to IT. Result: former team members retain document access for months.

Why this matters beyond neatness

This is not filing hygiene for its own sake. Matter-level access control is how firms operationalize privilege (the legal protection against disclosure of attorney-client communications) and ethical walls. A drifted permission is a potential conflicts breach, and it is discoverable: opposing counsel in litigation can subpoena access logs to show who could see privileged material and when.

It also breaks billing. Time entries in the timekeeping system (often built into the PMS, or a bolt-on like Intapp Time) are tagged to the matter number. If a document sits under a mismatched folder ID, e-discovery exports or billing audits done by matter will simply not find it, and the firm cannot bill for work product it cannot locate.

A simple technical view of the sync

Most PMS-DMS integrations today work as event-driven webhooks rather than nightly batch jobs, though batch still exists at smaller firms. A simplified event payload looks like this:

{
  "event": "matter.opened",
  "matter_number": "10234-0007",
  "client_id": "10234",
  "staffed_attorneys": ["j.smith", "a.chen"],
  "ethical_wall": false,
  "billing_type": "hourly"
}

The DMS connector listens for matter.opened, creates the workspace with matter_number as the folder key, and applies an ACL built from staffed_attorneys. If ethical_wall is true, it also excludes named individuals regardless of staffing. The integrity of the whole system depends on this payload firing reliably and on both systems treating matter_number as an immutable primary key, which, as noted above, is often violated in practice during renumbering events.

AML, conflicts, and billing: the systems around the core two

The PMS and DMS do not operate alone. Two more systems commonly plug into the same matter number:

• AML (Anti-Money Laundering) and KYC (Know Your Customer) checks: required in many jurisdictions before client onboarding, particularly under the EU's Anti-Money Laundering Directives and, in the US, under state bar guidance plus Bank Secrecy Act obligations for certain transactional work. These checks typically happen in the intake module before the matter number is even issued.
• Billing systems, sometimes the same PMS module, sometimes separate (e.g., Aderant's billing engine), pull time entries and disbursements by matter number to generate invoices, often formatted to e-billing standards like LEDES (Legal Electronic Data Exchange Standard) for corporate clients who require structured invoice data.

Every one of these systems assumes the matter number is stable and unique. When it drifts between PMS and DMS, reconciliation across all four systems (intake, DMS, time, billing) becomes a manual, error-prone exercise, usually surfaced only when a client auditor or a lateral partner's due diligence team goes looking.

Where a data warehousedata warehouseEin zentrales Repository, das Daten aus vielen Quellsystemen in einem strukturierten, abfrageoptimierten Speicher zusammenführt, ausgelegt für Analytics, Reporting und Business Intelligence.Vollständige Definition ansehen → fits without breaking privilege

Modern firms increasingly pull PMS, DMS metadata (not full document content), and billing data into a central warehouse or lakehouselakehouseEine hybride Architektur, die die Flexibilität eines Data Lake mit den analytischen Fähigkeiten eines Data Warehouse auf einer einzigen Storage-Schicht verbindet.Vollständige Definition ansehen → for analytics, profitability reporting, and pricing decisions. The critical design constraint: document *content* rarely moves into the warehouse layer because of privilege risk; only structured metadata (matter number, hours, practice group, realization rate) typically does. Row-level security in the warehouse must still mirror the ethical wall logic from the source PMS, or the analytics layer becomes the weak link that leaks who is working on what.

Key Takeaways

• The matter number is the single identifier that must stay synchronized across PMS, DMS, time, and billing; treat any renumbering event as a high-risk operation requiring manual verification.
• Real-time APIAPIApplication Programming Interface: eine standardisierte Schnittstelle, über die Anwendungen kommunizieren und Daten austauschen, ohne die interne Funktionsweise der jeweils anderen zu kennen.Vollständige Definition ansehen → or webhook integration between PMS and DMS (not nightly batch or manual folder creation) is what prevents matter numbers and folder structures from drifting apart.
• Access permissions and ethical walls set in the PMS must propagate to DMS ACLs on the same timeline as staffing changes; delayed revocation is a genuine conflicts and privilege risk, not just an IT hygiene issue.
• AML/KYC and conflicts checks happen upstream of matter number assignment and gate the entire downstream flow; billing systems downstream depend on the same number staying intact.
• Warehouse and lakehouselakehouseEine hybride Architektur, die die Flexibilität eines Data Lake mit den analytischen Fähigkeiten eines Data Warehouse auf einer einzigen Storage-Schicht verbindet.Vollständige Definition ansehen → layers built on top of this stack should carry structured metadata only, with row-level security replicating source-system ethical walls, keeping privileged document content out of the analytics layer entirely.