Collection-Master vs CollectMax: ownership, architecture and pricing model

Collection-Master and CollectMax are the two longest-serving creditor-side collections platforms. Collection-Master, developed from 1977, belongs to Vertican Technologies, which also runs the vExchange network; CollectMax, sold since 1987, belongs to JST, acquired by Embrace Software in early 2026. This page compares them from their vendors' own published materials, with Otto at the end.

How this comparison is sourced

Every claim about either product is quoted from a document its vendor published — product pages, system requirements, help files, licensing and training decks, and the vendors' own press announcements — re-fetched and re-checked against the quotation on 26 August 2026, and linked in full below. The family rules on /compare/ apply with no exception in either direction: no review scores, no pricing without a published source and a link, and silence recorded as silence rather than converted into a missing feature. One thing makes this page different from the other three in the family: neither product compared here is ours. Otto appears in one clearly marked section at the end, and the rest of the page is written to be useful to a firm that will never consider us. The deeper single-product treatments are at /compare/collection-master/ and /compare/collectmax/; this page is the head-to-head.

Who owns what, and since when

Collection-Master belongs to Vertican Technologies. Trade press covering the 2013 merger that created Vertican records that the product was developed "while working in his father's New Jersey based collection law firm beginning in 1977" and had been "Continually enhanced for over 35 years" by then; Vertican was formed when CLS and Q-Soft, the makers of Collection-Master and Q-Law, combined. In 2014 Vertican also acquired YGC Solutions in a stock-for-stock merger, stating the combination would "synergize the YouveGotClaims technology with case management software from CLS and Q-Soft" — which is how the industry's placement-exchange network came under the same roof. Its successor, vExchange, is a Vertican product today.

CollectMax belongs to JST — JS Technologies — which states its own history plainly: "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." The second sentence is JST's claim about its own market position and is quoted as theirs. At the end of January 2026, Embrace Software — whose own site reads "We Buy & Build World-Class Software Businesses" and counts "35+ acquisitions" — acquired JST. Both companies' announcements state that JST "will continue to operate as an independent business within Embrace's portfolio, maintaining its brand, team, and customer relationships" and that "Kurt Baese continues to lead JST as President". So as of 2026, one incumbent is a division of the company that also runs the exchange network, and the other is the legal-vertical entry of a software holding company. Both facts come from the parties themselves, and what each means for a buyer is a question for the roadmap section below, not a conclusion this page draws.

What each vendor says its product is

Vertican's product page opens with "The undisputed leader in debt collection technology and automation" and describes an integrated system whose published assets include "Over 400 bidirectional working client interfaces for the largest national and local credit grantors", "Hundreds of pre-built reports", forms generation for law firms nationwide, and "Smart built-in if-this-than-that technology" for automation. JST's about page leads with longevity — software sold to collections law firms and nothing else since 1987 — and its features page describes workflow automation through MaxPlans, account-level access tracking through MaxSecurity, SSN and account-number masking, and document suppression for do-not-contact, represented and bankruptcy accounts. Both are mature products whose depth in the awkward cases — the co-counsel split, the forwarder reconciliation, the cost advance recovered from the next remittance — is the accumulated asset a buyer is actually pricing. The single-product pages in this family quote both feature sets at length; this page will not repeat them.

Architecture, from the published documents

JST publishes the more detailed deployment picture, in its CollectMax System Requirements PDF (specifications updated December 2023): "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." Windows Server is required, "Wide Area Network (WAN) configurations are not supported" — Citrix or Microsoft Remote Desktop Services are the recommended answer for remote access — and each workstation needs Microsoft Word or Corel WordPerfect installed. Reporting outside the application reads from "JST SmartData, a secondary MS-SQL data set that is updated incrementally", which "can be read and queried by the Customer".

Vertican publishes less about Collection-Master's internals. What is published: its CEO describes the company's NextGen modernization as an "API layer built on top of our existing on-prem applications like Collection-Master", which places the core on-premises in the vendor's own words; reporting outside the application runs through SQL-Sync, "transferring all Collection-Master data to a SQL server in near real-time"; and the February 2025 licensing deck notes the license manager's own database is a .dbf file, with "a 30-day grace period allowing for a lack of a connection to the licensing server". Where the documents are silent — supported server versions, backup duties, remote topologies for Collection-Master — this page is silent too, and the question belongs to the vendor. The honest summary is that these are two on-premises Windows products of similar vintage, and the operational duties their documents assign to the firm are the real line of comparison with any hosted alternative, ours included.

Pricing model, as published

JST publishes a number: "JST offers monthly subscription programs starting at $300 a month", alongside its own advice that "The total cost of collections software is more than just the initial price to get started" — support, maintenance and version upgrades sit on top, as do the third-party licenses the requirements document names, from ADS to an MS-SQL license for SmartData. Modules are separate: of MaxPlans, the workflow automation, JST's help file says "This feature is an add-on. For pricing information, please contact Sales."

Vertican publishes no dollar figure for Collection-Master that we have found, and we print none. What it does publish is the shape: licenses are administered across two systems — "vPortal – manages licenses for Vertican products" alongside VLM, with "Named Users managed by VLM" and EDI/DTP and modules managed by vPortal; client interfaces are individually priced line items ("Filter by Price 119 to see the DTP's with a Charge", with the vendor's own advice, "Pro TIP, review your subscription, don't pay for what you don't need!"); and jurisdictions are unlocked per state ("Click to Buy – Multistate for each state", included at the TotalPlan tier). So the comparison available from public documents is of shapes, not of numbers: a published starting subscription with add-on modules, against an unpublished modular subscription with per-state and per-interface line items. Neither shape is cheaper in the abstract. Price your own configuration — your states, your interfaces, your modules, your support tier — on both, and treat any per-user figure someone quotes you for either product as unsourced unless they can show you where it is published.

Compliance tooling, as each vendor describes it

JST's features page names the control we have called out elsewhere in this family as better than our own: "To prevent a common mistake, the consumer's phone number is not viewable when it is not within allowable time call parameters." It also describes access auditing, data masking, print restriction and document suppression for flagged accounts. Vertican's page names "Call Screen ensures compliance with Mini-Miranda and Regulation F requirements", and its February 2025 deck lists recent "Regulation F 7-in-7 enhancements" and "Debt itemization Infinity Fields". We have not run either product and have no basis to characterize how any of these controls behave in practice; both lists are the vendors' own words, and a demonstration against your own accounts is worth more than both.

The exchange network belongs to one of them

A structural fact worth stating neutrally, because a buyer mapping dependencies should know it: the YGC data standard that moves placements, statuses and money records between creditors and firms is operated by Vertican. You've Got Claims joined Vertican in the 2014 merger; the YGC web application was retired in April 2022 and vExchange is its successor, publishing "5,000+ unique fields and 130+ record types". Both products speak it — Vertican's own migration guidance states that "Collection-Master, Q-LawE, and Q-Law users will be able to continue using the YGC DTP (version 3.3)", and CollectMax documents its YGC interface in its public help files, down to the reminder that "it is your responsibility to transfer the files to You've Got Claims using your Mailman Account." Nothing here implies the network favors anyone; we have no evidence of that and do not suggest it. It is simply a dependency both columns of this comparison share, and one of the two vendors operates it. The format itself is unpacked in plain English at /guides/ygc-vexchange-file-format-explained/.

The two roadmaps, in the vendors' own words

Each vendor has told its installed base where it is going, and both statements deserve to be read whole. Vertican's February 2025 deck is titled Collection-Master Is Here To Stay, opens "Collection-Master Lives!", and lists the product's future as "Converging features (VTFS; PaymentVision; Reg F) to work with our enterprise Q-LawE", "Transition to Q-LawE on your terms", and "Less expensive and an easier transition when you're ready to upgrade". JST, announcing its first conversion of a CollectMax customer to its cloud platform in July 2025, wrote: "There is a future where collection firms are no longer tethered to a network server environment" — and after the acquisition, its president cited "Embrace's track record of continued product investment and long-term ownership approach" as grounds for "confidence in the future of Accis, CollectMax, and ongoing success of our customers." The symmetry is the finding: both incumbents continue to sell and support the product this page compares, and both have named a successor platform in their own publications. Neither has published a timeline. A firm signing a multi-year agreement with either is entitled to ask what the convergence or conversion plan means for its own configuration, in writing — the two guides linked below hold the specific questions.

The questions that decide between them

If you are genuinely choosing between these two, the published record suggests four questions matter more than any feature list. Which client interfaces do you actually run, and which vendor can show yours working — Vertican publishes the larger claimed inventory, and either claim should be tested against your own two largest clients before signing. What can your firm operate — both requirements documents assign real duties to your IT, and the honest way to compare them is to hand both to whoever will carry the pager. What does your configuration cost — a published $300 starting point and an unpublished modular price sheet both end in a firm-specific number, and only that number is comparable. And what does the successor-platform plan mean for you — "transition to Q-LawE on your terms" and Accis conversion are both real published directions, and both vendors should be asked the questions at /guides/collection-master-firms-questions-for-vertican/ and /guides/collectmax-after-the-embrace-acquisition/ respectively.

Where Otto sits, at the end as promised

Otto is a hosted third option, and this page is not where it gets argued for. Three mechanisms, stated once: rules are evaluated before an action and can refuse it, with the refusal naming the rule; the record is append-only and an export package is sealed with a SHA-256 over its contents; and the client reads the same working record through Glass rather than receiving a periodic extract. Whether that outweighs decades of interface breadth and forms depth is a fact about your firm, not about the software. The migration pages at /migrating/from-collection-master/ and /migrating/from-collectmax/ describe what a move actually carries and are written to be useful whichever destination you choose.

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.