How do companies manage first-party and third-party collection licensing together?

Companies that run both first-party and third-party collections manage them by mapping each activity separately, because states draw the line differently. Third-party collection is licensed almost everywhere. First-party servicing under a client's brand is licensed in some states and exempt in others, and the answer can change with whose name is on the letter. Running both models well means keeping two maps and one combined inventory, so that adding a program in a new state is a lookup rather than a research project.

The mistake companies make in both directions

The first-party question is the one companies get wrong most often, and they get it wrong both ways. Some assume that servicing accounts in the creditor's name never needs a license, and get caught in the states that do license first-party activity. Others over-file, paying for first-party licenses in states that exempt the activity entirely, which wastes money and adds renewal obligations for nothing. Both errors come from applying a single national assumption to a question that is answered state by state.

The facts that decide the question are usually whose name appears to the consumer, whether the accounts are in default, and how the state statute defines a collection agency. Those facts have to be checked against each state, not assumed from the company's internal label. The classification reasoning is covered in depth in first-party versus third-party collections licensing; this answer focuses on running the combined portfolio once the classifications are set.

Whose name is on the letter

A single factor shifts many first-party determinations: the name presented to the consumer. When a servicer collects in the creditor's name, some states treat it as first-party and exempt. When the same activity is done under a different name, that can make it licensable. So a company running first-party servicing has to know, per program, which name appears on communications, because a client that wants collections done under a separate brand can move that program from exempt to licensable in some states without any change in ownership of the debt.

• Third-party placements: assume a third-party collection agency license is required and confirm the exceptions.
• First-party servicing in the creditor's name: exempt in many states, licensable in some; the first-party collection licensing map has to be built per state.
• First-party servicing under a separate brand: re-check, because the name can change the answer.
• Default status: whether the accounts are delinquent can affect the classification in some states.

One inventory, licenses tagged by activity

A company running both models, which is common in ARM as agencies add first-party servicing lines, should keep one inventory with each license tagged to the activity it covers. Tagging matters because the same state may require a third-party license and exempt first-party activity, or vice versa, and the inventory has to make clear which authority covers which program. With that tagging in place, onboarding a new client program in a new state becomes a lookup: check whether the program is first- or third-party, check the state, and see whether an existing license covers it or a new one is needed. Without it, every new program is a fresh research project.

This is the combined-portfolio version of the single source of truth for licensing principle: one inventory that answers which license covers which activity in which state.

Showing clients and examiners the coverage

A practical benefit of the tagged inventory is that it answers the questions clients and examiners actually ask. A client onboarding a first-party servicing program wants to know the servicer is licensed where it needs to be for that program. An examiner wants to see which authority covers the activity in their state. A tagged, current inventory answers both from one place, rather than forcing the compliance team to reconstruct the coverage from scattered records under time pressure during an audit.

Onboarding a client program as a lookup

The payoff of a tagged dual map shows up when a new client program arrives. A client wanting first-party servicing in a set of states, or third-party placements across a region, poses a licensing question that should be answerable in minutes, not weeks. With the map in place, onboarding becomes a lookup: classify the program as first- or third-party, list the states it will run in, and check whether existing authority covers each state or a new filing is needed. Where a filing is needed, the timeline for that state's review sets the program's realistic start date. Without the map, every new program becomes a research project, and the client feels the delay. Running onboarding this way is the operational version of the readiness described in state coverage for a new debt buyer, applied to servicing and collection programs.

The lookup also surfaces the honest answer when a program cannot start immediately in a state because authority is missing. Telling a client up front that a given state needs a filing first, with a realistic timeline, is far better than starting the program and discovering the gap during an examination. The tagged map makes that conversation quick and specific rather than vague.

Renewals and bonds across a combined portfolio

A combined first- and third-party portfolio carries renewals and bonds on both legs, and those obligations do not pause because the company is focused on the other leg. Each license, whichever activity it covers, has its own renewal cycle and, where required, its own Surety bond to keep current. Managing the two activities from one inventory means the renewal calendar covers both, so a first-party license does not lapse while attention is on third-party growth or vice versa. Coordinating the bonds with the license renewals across the combined set is the same discipline as coordinating surety bonds and license renewals, just applied to a portfolio spanning two classifications. A single calendar for both legs is what prevents the quiet lapse on whichever side is getting less attention at the moment.

Building and maintaining the dual map

Because the two activities are classified differently and the programs change as clients come and go, the dual map is a maintained thing, not a one-time build. Cornerstone Licensing builds that dual map, files the licenses each leg requires, and keeps the record in Atlas so the compliance team can show any client or examiner exactly which authority covers which program. The ARM and debt buying licensing page covers the adjacent buying and management activities, and ongoing compliance with Atlas is how the combined inventory stays current as programs and footprint change. With both maps in one place, adding a client program becomes a quick lookup and an examination becomes a matter of showing the record, rather than a scramble to reconstruct which authority covers which activity in which state.