Boarding a Portfolio: What Has to Arrive With the Accounts

Per our servicing analysis, errors in consumer lending cluster at the handoff — and the reason is structural rather than careless. Balances and identifiers transfer cleanly, in standard formats, and the context that governs each account frequently doesn't. The arrangement someone is already paying under, the dispute nobody resolved, the request not to be called at work, the note that a relative has authority. Those are the fields most often missing, and they're precisely the ones whose absence produces the worst outcomes for customers and the worst findings in an examination.

What transfers and what doesn't

Field	Usually arrives	Consequence if missing
Balance and identifiers	Yes	—
Payment history	Usually	Can't verify the balance
Arrangement in force	Frequently not	A paying customer is treated as delinquent
Dispute status	Frequently not	Collection on a disputed account
Contact restrictions	Frequently not	Contact after a restriction
Hardship indicators	Rarely	Pressure on a vulnerable customer
Third-party authority	Rarely	Family member turned away
Delinquency start date	Sometimes	Limitation status unknowable

Read the first column top to bottom: reliability falls exactly as consequence rises. The fields that arrive intact are the ones a spreadsheet holds naturally; the ones that go missing live in case notes, flags, and free text — and those govern what you're allowed to do.

Per our limitation periods analysis, the last row is the field most likely to be dropped and least reconstructable, because nobody uses it operationally until they need it.

What to require in the agreement

What arrives is what was contracted for, so the field list belongs in the purchase or servicing agreement, not in a request afterwards.

1. Account and customer identifiers, with full contact history.
2. Original agreement terms and a copy of the agreement.
3. Complete payment and transaction history, per our debt sale analysis — the basis for verifying the balance if it's ever questioned.
4. Balance composition — principal, interest, fees — since a balance that can't be broken down can't be explained to a customer.
5. Date of first delinquency and any events affecting limitation status.
6. Arrangements in force, with terms and payment record against them.
7. Dispute records, open and closed, with outcomes.
8. Contact restrictions, consents, and channel permissions.
9. Hardship, vulnerability, and deceased indicators.
10. Third-party authority records, per our authority guide.
11. Litigation and bankruptcy status, per our bankruptcy guide.
12. What the customer was last told, including any settlement offer outstanding.

Also contract for what happens afterwards: a duty to forward mail, payments, and disputes received post-transfer, a defined contact for questions, and a retention period during which the seller must still be able to produce documents. Per our portfolio sale analysis, these obligations are cheap to negotiate at signing and impossible afterwards.

Validating before you work anything

1. Reconcile counts and totals to the schedule — accounts received against accounts purchased, and balances against the stated total.
2. Check field completeness, and quantify what's missing rather than noting that something is.
3. Sample accounts against source documents — does the balance reconcile to the agreement and payment history?
4. Test for duplicates within the file and against accounts you already hold.
5. Check identity matching, per our matching analysis — over-matching attributes someone else's debt to a customer, which is among the worst errors available here.
6. Scrub against deceased and bankruptcy sources before any contact, per our deceased accounts guide.
7. Verify contact data rather than assuming it's current.
8. Document the results, per our records analysis — what you knew at boarding is what an examination will ask about.

Step three is the one that gets skipped under commercial pressure and matters most. Per our debt sale analysis, a portfolio whose balances can't be evidenced is one you can't defend when a customer disputes — and the sample tells you, before you've contacted anyone, what proportion of the file that describes.

Unknown as a status

The practical mechanism that prevents most boarding failures.

An account whose arrangement, dispute, or restriction status can't be confirmed should not enter the standard sequence. Any of those could make ordinary collection activity inappropriate, and you can't tell which.

• Flag incomplete accounts explicitly at boarding, rather than leaving fields blank — per our limitation periods analysis, a blank field and a confirmed status look identical to every downstream system.
• Route them to a defined path: establish the position, then release.
• Ask the seller, using the contractual channel, and set a deadline.
• Where the position can't be established, treat conservatively — assume the restriction exists rather than assuming it doesn't.
• Report on the suppressed population until it's cleared, since otherwise it quietly leaks into normal treatment.

The conservative default in point four is the whole discipline. The cost of suppressing an account that turned out to be workable is a delay; the cost of working an account that turned out to be disputed, in hardship, or subject to a restriction is a conduct failure.

Honouring what's in force

The most common customer-facing failure after a transfer, and the most avoidable.

Someone agreed a plan, has paid it every month, and receives a demand from a company they've never heard of. From their side the agreement they kept has been ignored; from yours the arrangement field was empty.

What to do:

1. Identify every account with payments in a regular pattern, even where no arrangement is flagged — the payment history reveals arrangements the data didn't carry.
2. Honour the existing terms rather than requiring renegotiation.
3. Carry over the payment method where consent allows, and tell the customer what will change — a direct debit that silently stops is a broken arrangement caused by you.
4. Confirm the arrangement in writing at first contact, restating its terms.
5. Where terms genuinely can't continue, say so clearly and offer something equivalent, per our payment plan analysis.

Item one is the highest-value analysis available at boarding. Per our promise-to-pay analysis, a customer already paying reliably is the most valuable population in any portfolio — and the fastest way to destroy that value is to treat them as a delinquent stranger.

The first contact

An unfamiliar company contacting someone about a debt looks exactly like a scam — because that's a real scam pattern.

What the first communication should do:

• Identify you clearly, and name the original creditor and the product.
• Explain the transfer and when it happened.
• Give the customer a way to verify you independently — a published number they can find themselves, not just one printed in the letter.
• State the balance and its composition.
• Carry any required notices, including validation and dispute rights, which is a matter for compliance.
• Confirm any arrangement continues, prominently.
• Explain how to dispute, per our dispute analysis.
• Avoid demanding tone — per our letters analysis, a first contact that arrives as a threat from an unknown party gets treated as fraud and ignored.

And expect inbound volume. Per our inbound analysis, a boarding notice generates a wave of calls from people asking whether this is real — staff them, and treat the call as the verification opportunity it is.

Reporting after a transfer

• Establish who reports what and from when, so the account isn't reported twice or dropped entirely — per our reporting analysis, duplicate reporting of one debt is a recurring consequence of transfers.
• Carry the delinquency history accurately rather than restarting it.
• Confirm the seller ceases reporting as of the transfer date.
• Handle disputes about pre-transfer periods — you'll receive them, and the records sit with the seller, which is why the retention obligation matters.
• Reflect arrangements in what you report, since an account paying under a plan should not be reported as though nothing were happening.

The first is the one customers notice. The same debt appearing twice on a file is a visible error that takes months to correct and generates a dispute you'll have to handle anyway.

When you're the one transferring out

Briefly, because the obligations don't end at the sale.

• Send the context fields, not just the balances — the list above, in full.
• Exclude what shouldn't be sold — disputed accounts, accounts in hardship, deceased accounts, and anything whose status you can't establish, per our portfolio sale analysis.
• Notify customers that the account has transferred and to whom.
• Forward payments, mail, and disputes that arrive after the date.
• Retain documents for the agreed period and respond to requests.
• Stop your own activity — reporting, contact, and any agency placements.

The last is the one that produces duplicate contact, where both the seller's agency and the buyer are pursuing the same person for the same debt — which is the failure customers complain about most loudly and which per our restrictions analysis is a propagation problem, not a policy one.

Frequently asked questions

---

This guide is educational and does not constitute legal or compliance advice. Requirements governing debt transfers and sales, validation and notice obligations on first contact, documentation standards, credit reporting during and after transfer, and the handling of disputes and restrictions vary by jurisdiction, product, and counterparty. Consult qualified counsel and your compliance function before boarding or transferring a portfolio.