Collection-Master firms: the questions to ask Vertican

Vertican's February 2025 deck is titled Collection-Master Is Here To Stay, and the same deck describes the product's future as converging with its enterprise platform: "Transition to Q-LawE on your terms." Both statements are the vendor's own. This guide turns them into the diligence questions a firm running Collection-Master should ask, and get answered in writing.

What Vertican has said, in full

The primary document is Vertican's own February 2025 Mastermind deck, Collection-Master Is Here To Stay. Read whole, it says two things at once, and both deserve quoting. The reassurance: the deck opens "Collection-Master Lives!", lists recent enhancements — "Regulation F 7-in-7 enhancements", "Debt itemization Infinity Fields", in-app PaymentVision integration, new File and Serve tools, a Vertican Support App — describes a growing Collection-Master team, and asks its own users to affirm that the product "is fully supported and enhanced to meet industry needs for the foreseeable future". The direction: the slide titled "What is the future of Collection-Master?" answers itself with "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" — and the deck names what it wants to soothe: "We want to minimize your concerns. Budgeting for platform changes when you're ready. Data conversion downtime and user learning curve." In print ten months later, Vertican's CEO described the modernization strategy as an "API layer built on top of our existing on-prem applications like Collection-Master" and called moving firms between platforms "extremely challenging and often unnecessary". All of it is the vendor speaking about its own product.

Why both halves can be true at once

A supported, actively enhanced product and a published convergence path to the vendor's enterprise platform are not contradictory, and this guide does not treat them as a contradiction. Mature software companies run exactly this posture for years, sometimes decades, and Vertican's continued Regulation F work on Collection-Master is evidence the support statement is currently operational, not decorative. What the posture does create is a set of questions with firm-specific answers — when features converge "to work with" Q-LawE, which product gets them natively; what "on your terms" includes; what the transition costs — and a firm signing a renewal is entitled to those answers in writing rather than in a training deck. That is the whole premise here: no suspicion, just the ordinary discipline of turning a vendor's published direction into contractual clarity.

Support commitments

The deck's support statement is a slide, and a slide is not a term. Ask for the contractual version: what are the committed support terms for Collection-Master itself — the licensing deck describes support as a plan with terms, "Plan Type (SLA)", incidents, license term and users — and through what date does your agreement commit them? Account management is "included in Diamond & Platinum Support" per the same deck; ask which tier your firm is on and what the lower tiers commit to in writing. And ask the question the poll slide invites: is "fully supported and enhanced ... for the foreseeable future" something Vertican will state with a horizon — a date, a term, a notice period for any end-of-enhancement decision? A vendor that means it can usually write it down.

Roadmap: what does convergence mean for your configuration

The convergence list is specific — VTFS, PaymentVision, Regulation F — so the questions can be specific too. For each capability your firm depends on, ask: does it continue to be developed in Collection-Master natively, or does it arrive "to work with" Q-LawE in a form that assumes the enterprise product? What does the NextGen "API layer built on top of our existing on-prem applications" mean for Collection-Master screens your staff use today? And ask for the transition offer in writing even if you have no intention of taking it: what does "Transition to Q-LawE on your terms" include — data conversion, training, parallel running — and what does "Less expensive" mean in dollars for a firm of your shape? The deck names "Data conversion downtime and user learning curve" as the fears; the useful response is to ask the vendor to quantify both for your configuration, because a vendor that has done the transition it advertises has those numbers.

Pricing

Collection-Master's published pricing shape is modular: licenses administered across vPortal and the Vertican License Manager, named users in one system and EDI/DTP interfaces and modules in the other, client interfaces individually priced ("Filter by Price 119 to see the DTP's with a Charge"), and jurisdictions unlocked per state ("Click to Buy – Multistate for each state", included with the TotalPlan subscription). Vertican's own deck tells its customers to audit this: "Pro TIP, review your subscription, don't pay for what you don't need!" — so take the vendor's advice literally. Ask for the current line-item list of everything your firm licenses, by name; reconcile it against the interfaces and states you actually run; and ask what the renewal policy is on each class of line item. No dollar figures appear here because Vertican publishes none that we have found, which is itself worth knowing: your own invoice is the only price sheet you can compare anything against.

Data export rights

Three stores matter, and all three are named in Vertican's own materials. The working data, which SQL-Sync copies out — "transferring all Collection-Master data to a SQL server in near real-time" — meaning a documented, queryable copy of your own records may already be within your license; ask whether it is, and what it costs if not. The media in vMedia, with whatever provenance the store holds. And the forms library your firm has built county by county over years, which is configuration rather than data and rarely travels anywhere. The questions, the same ones any vendor should answer: what does a complete export contain, in what documented format, at what cost, on what turnaround, and is any of it conditioned on the state of your account? Settle the answers at renewal time, when they are cheap. The migration page at /migrating/from-collection-master/ holds the full inventory of what a move carries, whichever destination a firm ever chooses, including none.

The exchange network

Collection-Master firms usually also depend on Vertican's exchange network: vExchange, the successor to You've Got Claims, whose migration guidance states that "Collection-Master, Q-LawE, and Q-Law users will be able to continue using the YGC DTP (version 3.3) to communicate with other Senders outside of vExchange." The published documents do not address what happens to a firm's vExchange connectivity if it moves its case management elsewhere, and this page will not guess. Ask directly: is network participation tied to running a Vertican case-management product, contractually or practically? The answer affects any future platform decision in either direction, and it is a fact only the vendor can state. The format itself is explained at /guides/ygc-vexchange-file-format-explained/.

Ask the same questions of any replacement vendor

Every question above generalizes, and a firm evaluating alternatives should put each one — support terms with a horizon, roadmap in writing, line-item pricing, export rights, network dependencies — to any vendor at the table, including us. A vendor's answers to another vendor's hard questions are marketing; its answers to its own are diligence. Hold Otto to this page's standard before holding Vertican to it.

If you are evaluating alternatives

Otto is one, said once: a hosted platform whose rules are evaluated before the action and whose audit record is append-only. The comparison against Collection-Master, sourced to Vertican's own documents, is at /compare/collection-master/; the head-to-head of the two incumbents is at /compare/collection-master-vs-collectmax/; and the migration guide is at /migrating/from-collection-master/.

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.