# Debt collection software for law firms: how the category works > What collections case management software has to do — placements, ledgers and trust accounting, compliance gates, court and service integrations, document assembly and client reporting — how the category is structured, and who the established systems are. - Source: https://ottoforfirms.com/collections-software/ - Publisher: Otto — https://ottoforfirms.com - Updated: 2026-07-29 Collections case management software runs a creditor-side law firm's whole file: placements arriving from a client, the ledger and trust accounting underneath them, gates on contact and filing, court and process-server integrations, document assembly, and the reporting that goes back to the client. The long-established systems are CollectMax, Q-LawE and Collection-Master. ## Key facts - This is not general legal case management. The work is placement-driven, ledger-heavy, and it has to hand a file back to the client on a schedule. - Six functions define the category: placements, ledgers and trust, compliance gates, court and service integrations, document assembly, and client reporting. - The long-established products are CollectMax from JST, in this vertical since 1987, and Vertican's Q-LawE and Collection-Master, the latter developed from 1977. We publish no market-share figure. - Deployment is the first fork. CollectMax's own requirements describe a Windows file server; Vertican describes an on-premises core with an API layer built on top. - The number that decides a migration is client interfaces. Vertican publishes "Over 400 bidirectional working client interfaces" for Collection-Master. - Otto is a new entrant here: fewer client interfaces than the incumbents, four configured jurisdictions, and no installed base to point at. ## What is collections software, and how is it different from case management? A creditor-side collections practice does not open its own matters. Files arrive in batches from a bank, a debt buyer, a servicer or a forwarding agency, each with its own file format, its own fee schedule, its own rules about what may be done and when, and its own expectation of what comes back. The software that runs such a firm is therefore shaped by three things a general legal case-management system is not built around: volume, because a file is worked by rule rather than by attention; money, because the firm is holding other people's money in trust and accounting for it per client and per account; and reporting, because the client is entitled to know the state of its own portfolio without asking. A general practice-management product handles matters, calendars, time and billing. A collections platform handles placements, ledgers, work queues, compliance gates, court output and client files. The vocabulary alone tells you they are different categories — placement, recall, remittance, net-back, liquidation rate, disposition code — and a product that does not have those words in it has not been built for this. ## The six things this software has to do First, placements: ingest a client's file, map its fields, apply its fee schedule and its rules, and acknowledge receipt in the format that client expects. Second, ledgers and trust accounting: every payment, cost advance, fee split, remittance and adjustment recorded per account and reconcilable to a bank statement, with client funds segregated. Third, compliance gates: the rules that decide whether an action may happen at all — contact frequency and timing, disputes and cease requests, attorney representation, validation status, time-barred accounts, and whether a filing has the documentation behind it. Fourth, court and service integrations: e-filing, process servers, sheriffs and garnishment answers, all of which vary county by county. Fifth, document assembly: complaints, summonses, writs, letters and validation notices generated from account data in the format a particular clerk accepts. Sixth, client reporting: status files, remittance files and the portfolio picture the client reads. A system that does five of these well and one badly is not five-sixths of a system, because the one it does badly is where the firm's exposure sits. ## Placements, and why the client interfaces are the whole game Everything else in a collections practice can be rebuilt. The client interfaces are the part that must not break for a single day, because a bank whose status file stops arriving does not care what caused it. Each interface is a per-client contract expressed as a file format: what a placement record contains, which codes mean what, when the status file goes out, how a recall is acknowledged, how remittance is reported. The scale of this is not a secret — JST's own documentation of the record types CollectMax uploads to the You've Got Claims network enumerates financial transactions for payments and costs, debtor records, employment, bank and asset information, legal captions, reconciliation records, notes, suit and judgment information, balance and interest, payment plans, bankruptcy, probate and physical assets — and Vertican publishes "Over 400 bidirectional working client interfaces" as a headline feature of Collection-Master. Read either of those as a buyer and the message is the same: ask any vendor which of your client interfaces run in production today, by name, and treat the answer as the schedule for everything else. ## The ledger and the trust account This is the part of the category that is closest to accounting software and furthest from anything a demonstration will show you well. The system holds money that is not the firm's, splits it according to a fee schedule that varies by client and sometimes by account age, advances costs that have to come back out of later collections, and produces a remittance the client can reconcile. Two consequences follow for anyone evaluating. The first is that a trust balance is the one number nobody will accept as approximately right, so a migration that lands consumer records perfectly and lands trust a dollar out is a failed migration. The second is that accounting depth is a real axis of difference between products, and the way to test it is not a feature list but your own worst month: hand a vendor a period with a bounced payment, a partial remittance, a fee adjustment and a cost recovery in it, and ask to see the ledger come out right. ## Compliance gates: the difference between a rule that warns and a rule that refuses Every product in this category has compliance features, and the phrase covers two quite different mechanisms. One is detection: the action happens, and a report or an audit finds it afterwards. The other is prevention: the rule is evaluated before the action and the action does not happen. Both are legitimate and most systems do some of each. The question to ask a vendor is not whether they have compliance features but where in the sequence each rule runs, and what evidence exists when a rule fires. There are good published examples of the preventive pattern in this market that have nothing to do with us — JST describes a control in which "the consumer's phone number is not viewable when it is not within allowable time call parameters", which removes the temptation rather than punishing it, and is a better pattern than blocking a dial after somebody has decided to place it. Otto's own approach is to evaluate before the action and record the refusal with the rule that caused it. None of this is a compliance outcome, ours included: software applies rules that have been written down correctly, which makes writing them down correctly the work. ## Courts, service and documents The document library is the least glamorous and most underestimated part of the category. A complaint that a clerk in one county accepts is not a complaint that a clerk in the next county accepts, and a firm that has been filing in the same forty counties for twenty years is sitting on an institutional asset that does not transfer with its data. This is the axis on which an incumbent's age is a genuine advantage. Vertican describes Collection-Master's forms management as "Fast and flexible word processing that efficiently generates legal forms for law firms nationwide", and a library assembled county by county over decades is exactly what that means. Whatever system you are evaluating, the test is narrow and cheap: hand the vendor your three highest-volume counties and ask to see the complaint, the summons and the writ produced from your own account data, formatted the way that clerk expects, before you sign. ## Client reporting, and who is actually reading it The reporting question in this category has an unusual shape because the audience is not the firm. A bank's oversight team, a debt buyer's vendor manager and a servicer's compliance function all read the output, and increasingly they want to see the firm's own record rather than a package the firm assembled for them. Two structural facts are worth knowing when you compare products. Reporting frequently runs against a copy of the data rather than the data — JST describes SmartData as "a secondary MS-SQL data set that is updated incrementally so building it daily will be quick and easy", and Vertican describes SQL-Sync as "transferring all Collection-Master data to a SQL server in near real-time". And heavy work is often scheduled for a quiet window: JST's own automation guidance is to "eliminate down time during the workday and run all of your larger Batch Processes at night". Neither is a defect; both are ordinary engineering for products of that architecture. They do determine how fresh an answer can be and who has to build the query, which is worth knowing before your largest client asks for something new. ## How the category is structured: installed, hosted, and the layer in between The first fork is deployment. The established products in this market are installed software with an on-premises core. CollectMax's published system requirements describe a dedicated Windows server, a third-party database engine — "A third-party software license called Advantage Database Server (ADS) is required to be installed on your server in order to run CollectMax across your network" — a word processor on every workstation, a daily backup to removable media and a UPS on the server, and state that "Wide Area Network (WAN) configurations are not supported", with Citrix or Remote Desktop Services recommended where remote access is needed. Vertican's modernisation is described by its CEO as "a powerful API layer built on top of our existing on-prem applications like Collection-Master". Both vendors are also moving: JST wrote in 2025, announcing its first customer conversion to a cloud platform, that "There is a future where collection firms are no longer tethered to a network server environment." The second structural fact is how these products are priced, which is modular rather than flat: modules, client interfaces, jurisdictions and support tiers are commonly separate line items. Vertican's own licensing deck instructs administrators to filter their interface list by price and adds "Pro TIP, review your subscription, don't pay for what you don't need!", and describes per-state unlocks bought individually. The practical advice that falls out of this is to price your own configuration rather than a list price, and to ask what the third-party licences underneath the software cost as well. ## Who the established systems are Three products have a documented, decades-long presence in this exact vertical, and it is worth knowing what each one is before comparing any of them. We publish no market-share figure because we have none and have found none published; what follows is each vendor describing itself. CollectMax is JST's product; JST says it has been "providing debt collections software solutions since 1987" with "over 900 installations nationwide", and its published subscription pricing starts at $300 a month. Q-LawE is Vertican Technologies' enterprise platform, built on SQL, with rule-driven automation through DDAS, a multi-threaded job scheduler, attorney review workflows and a deep integration bench; Vertican has moved it to named-user subscription licensing. Collection-Master is Vertican's older platform, developed "beginning in 1977", still supported and enhanced, with "Over 400 bidirectional working client interfaces" and a published path toward Q-LawE — Vertican's own February 2025 deck offers customers "Transition to Q-LawE on your terms". Vertican also runs a free training programme, Mastermind, whose catalogue lists dozens of sessions across the product line. There are adjacent products in the agency market and in general legal case management that firms sometimes evaluate alongside these; they are a different category with a different centre of gravity, and a firm that files suit needs the court and trust machinery above. ## How to evaluate one, in five questions Which of my client interfaces run in production today, by name and by direction? Show me a trust reconciliation from a completed migration, and tell me who did the reconciling. What happens to my change history — after a move, can you reconstruct a file as it stood on a date in the past, and is any part of that history deletable on a schedule? Which jurisdictions are configured, and may I see the configuration on screen rather than on a map? And if you say your system prevents violations rather than reporting them, show me the record a blocked action leaves behind. A vendor who answers all five in writing is describing the system you will actually get. We are not exempt from these; ask us the same ones. ## Where Otto sits, and what we are not claiming Otto is a new entrant in this category and there is no version of this page where pretending otherwise helps anybody. What we do not have: an installed base, decades of county formats, the number of client interfaces a long-established incumbent maintains, or a customer we can point you at. Four jurisdictions ship configured today — Florida, Georgia, Texas and New York. What is different is mechanism rather than outcome: rules are evaluated before an action and can refuse it, with the refusal recorded alongside the rule that caused it; the record is written as the work happens and an export is sealed with a SHA-256 over its contents; the client reads the same record directly rather than waiting for a periodic summary; and automation is authored as a sentence that is drafted into steps a person then edits. We publish no efficiency figures, no liquidation improvements and no compliance outcomes, because we have not measured any and our terms disclaim the last of them. This page exists because the category deserves a plain explanation, and because we would rather be found by someone who then decides an incumbent fits them better than not be found at all. ## Primary sources 1. [About JST](https://www.collectmax.com/about/) — CollectMax's vendor on its own history and installed base (JST CollectMax · retrieved 29 July 2026) > JST has been providing debt collections software solutions since 1987. With over 900 installations nationwide, JST serves more debt collections law firms than any other high-end legal debt collections software provider. 1. [CollectMax Features & Benefits](https://www.collectmax.com/features-and-benefits/) — Published starting price, and a compliance control worth naming (JST CollectMax · retrieved 29 July 2026) > JST offers monthly subscription programs starting at $300 a month, allowing you to grow and expand your practice as you need it. 1. [CollectMax Features & Benefits (call-window control)](https://www.collectmax.com/features-and-benefits/) — An example of a preventive rather than detective control, published by a competitor (JST CollectMax · retrieved 29 July 2026) > To prevent a common mistake, the consumer's phone number is not viewable when it is not within allowable time call parameters. 1. [CollectMax System Requirements](https://www.collectmax.com/downloads/CollectMax%20System%20Requirements.pdf) — PDF, updated December 2023 — what an installed collections platform requires of a firm (JST CollectMax · retrieved 29 July 2026) > A third-party software license called Advantage Database Server (ADS) is required to be installed on your server in order to run CollectMax across your network. 1. [CollectMax System Requirements (networking)](https://www.collectmax.com/downloads/CollectMax%20System%20Requirements.pdf) — PDF, updated December 2023 — supported topologies and remote access (JST CollectMax · retrieved 29 July 2026) > Wide Area Network (WAN) configurations are not supported. Citrix and Microsoft Remote Desktop Services (RDS), also referred to as Microsoft Terminal Services (MSTS), are recommended for those customers requiring an application server environment. 1. [CollectMax System Requirements (reporting copy)](https://www.collectmax.com/downloads/CollectMax%20System%20Requirements.pdf) — PDF, updated December 2023 — the separately built analytics data set (JST CollectMax · retrieved 29 July 2026) > JST SmartData, a secondary MS-SQL data set that is updated incrementally so building it daily will be quick and easy. 1. [CollectMax help — Batch Process Automation Script](https://www.collectmax.com/webhelp/Content/Batch%20Process%20Automation%20Script.htm) — When heavy processing runs on an installed platform (JST CollectMax · retrieved 29 July 2026) > eliminate down time during the workday and run all of your larger Batch Processes at night 1. [CollectMax help — YGC Upload Record Types](https://www.collectmax.com/webhelp/Content/YGC_Upload_Record_Types.htm) — A vendor's own catalogue of what a collections file contains (JST CollectMax · retrieved 29 July 2026) > The following Record Types are uploaded to the You've Got Claims Network. 1. [JST Converts First CollectMax Customer to Accis Platform](https://www.collectmax.com/2025/jst-converts-first-collectmax-customer-to-accis-platform/) — JST's own announcement, 31 July 2025 (JST CollectMax · retrieved 29 July 2026) > There is a future where collection firms are no longer tethered to a network server environment. 1. [Q-LawE product page](https://vertican.com/q-law/) — Vertican's enterprise platform, in its own description (Vertican Technologies · retrieved 29 July 2026) > Q-LawE is Vertican's Enterprise software product. 1. [Collection-Master product page](https://vertican.com/collection-master/) — Client-interface breadth and forms management (Vertican Technologies · retrieved 29 July 2026) > Over 400 bidirectional working client interfaces for the largest national and local credit grantors 1. [Collection-Master Is Here To Stay](https://vertican.com/wp-content/uploads/2025/02/CM-is-Here-to-Stay.pdf) — Mastermind Series presentation, February 2025 — the published path between Vertican's two platforms (Vertican Technologies · retrieved 29 July 2026) > What is the future of Collection-Master? Converging features (VTFS; PaymentVision; Reg F) to work with our enterprise Q-LawE. Transition to Q-LawE on your terms. 1. [Licensing, VLM / vPortal & Collection-Master](https://vertican.com/wp-content/uploads/2025/02/Licensing-VLM-vPortal-Collection-Master.pdf) — Mastermind Series presentation, February 2025 — how modular licensing works in practice (Vertican Technologies · retrieved 29 July 2026) > Filter by Price 119 to see the DTP's with a Charge. Pro TIP, review your subscription, don't pay for what you don't need! 1. [The future is now: why Vertican's technology is more modern than ever](https://www.creditorsbar.org/news/the-future-is-now-why-verticans-technology-is-more-modern-than-ever) — National Creditors Bar Association, 15 December 2025 — the modernisation strategy in the CEO's words (National Creditors Bar Association · retrieved 29 July 2026) > API layer built on top of our existing on-prem applications like Collection-Master. 1. [CLS and Q-Soft Agree to Create Largest Legal Collection Software Company](https://www.insidearm.com/news/00012045-cls-and-q-soft-agree-to-create-largest-le/) — Trade press, 9 December 2013 — where Collection-Master's start date is recorded (insideARM · retrieved 29 July 2026) > Mr. Goldman developed the CLS software, Collection-Master, while working in his father's New Jersey based collection law firm beginning in 1977. 1. [Mastermind training catalogue](https://vertican.com/mastermind/) — Vertican's free training programme across its product line (Vertican Technologies · retrieved 29 July 2026) > All sessions are free to attend and start at 2:00 pm (ET) ## Related - [Compare collections software: CollectMax, Q-LawE and Collection-Master](https://ottoforfirms.com/compare/) — Comparisons of the three long-established creditor-side collections platforms and Otto. Every claim about another product is quoted from a document that vendor published, with a link and the date we read it. - [CollectMax alternatives for collections law firms](https://ottoforfirms.com/compare/collectmax/) — Weighing an alternative to CollectMax: what JST's own system requirements, feature page and help files describe, what CollectMax does well, what a migration off it actually carries, and where Otto differs. - [Q-LawE alternatives: what to check before you switch](https://ottoforfirms.com/compare/q-lawe/) — Q-LawE from Vertican Technologies, read entirely from Vertican's own decks and guides: named-user subscription licensing, GetField expressions, truncatable change tracking, and what a move off it carries. - [Collection-Master alternatives: what a replacement has to carry](https://ottoforfirms.com/compare/collection-master/) — Collection-Master from Vertican Technologies, read from its product page, its 2025 Mastermind decks and its CEO in print: four hundred client interfaces, per-state and per-interface licensing, a published path to Q-LawE, and what leaving actually involves. - [Migrating a collections firm to a new case management system](https://ottoforfirms.com/migrating/) — What actually moves when a creditor-side collections firm changes case management systems: the trust ledger, the media, the client interfaces, and the history. --- This is an informational reference, not legal advice, and using it creates no attorney-client relationship. Limitations periods turn on facts this page cannot know — which state's law governs, the contract type, when the claim accrued, and whether anything tolled or revived it. Confirm against the primary source and your own counsel before acting.