Debt Portfolio Sales Briefing
A practical field-by-field framework for preparing a clearer, more reviewable portfolio data package.
A loan tape data dictionary defines each field in a portfolio file—its meaning, source, format, date basis, and acceptable values. For debt portfolio sales, it helps a seller present balances, performance, documentation, and risk flags consistently so prospective buyers can conduct diligence without guessing how the data was assembled.
Key Takeaways
- A dictionary is more than a column list: it records definitions, calculation logic, source systems, timing, and exceptions.
- Account identifiers, balance components, delinquency or charge-off dates, payment history, and documentation status are core diligence fields for most sale processes.
- Data quality is part of marketability. Reconciliations, null-value rules, and population controls should be established before a tape is distributed.
- Field requirements vary by asset class, jurisdiction, transaction structure, and buyer mandate; a generic template should not replace transaction-specific review.
What a Loan Tape Data Dictionary Does
A loan tape is a row-level file describing accounts offered for review. Its dictionary makes the file interpretable: it states whether current balance includes interest, fees, or adjustments; whether a date is original delinquency or a derived aging date; and whether an empty field means “not applicable,” “unknown,” or “not supplied.”
Buyers use a seller’s data package to evaluate documentation, servicing effort, and operational risk. When similar labels carry different definitions, reviewers may make different assumptions or request clarification. A clear dictionary does not determine price or ensure a transaction, but it provides a more disciplined basis for diligence.
Core Required Fields for a Debt Portfolio Sale
The table below is a practical baseline for an account-level consumer or commercial debt tape. “Required” here means commonly useful to a buyer’s review, not universally mandated. A seller should adapt the field set to the asset type and the governing sale agreement.
| Field group | Examples of fields | Why reviewers use it | Dictionary should specify |
|---|---|---|---|
| Account identity | Seller account ID, portfolio ID, anonymized borrower or obligor reference | Links rows to supporting schedules and prevents duplicate-account ambiguity. | Whether identifiers are unique, stable, masked, or remapped for diligence. |
| Original terms | Origination date, original balance or credit limit, product type, term, interest rate where relevant | Establishes the account’s basic economic and contractual profile. | Product taxonomy, currency, source record, and treatment of modified terms. |
| Balance composition | Principal, accrued interest, fees, payments, adjustments, current balance | Allows reviewers to reconcile the amount being offered and understand its components. | Calculation formulas, signs, rounding, cutoff date, and whether components net to total balance. |
| Performance and aging | Last payment date and amount, delinquency date, charge-off date, days past due, payment-plan status | Supports segmentation by recency, payment behavior, and account status. | Business definitions, calendar basis, event precedence, and how missing dates are represented. |
| Documentation and chain | Contract availability, account statements, assignment history, document image flags | Helps scope document review and understand transfer history. | What “available” means, storage location, completeness standard, and known exceptions. |
| Risk and exclusions | Dispute, bankruptcy, deceased, military, fraud, settlement, cease-contact, or legal-status flags | Enables buyers to screen accounts against their mandates and servicing policies. | Source, effective date, permitted codes, update lag, and whether a blank is a negative or unknown result. |
Keep source columns distinct from analytical fields. For example, label “months since last payment” as calculated from the cutoff date and underlying last-payment field. Derived fields should be reproducible and should not be presented as source facts.
Build Definitions That Survive Diligence
A useful dictionary is concise enough to navigate yet specific enough to test. Each entry should include the field name, definition, data type, format, source, population rule, as-of date, permitted values, null treatment, and transformation notes. Where business judgment is involved, add an owner and brief exception note.
Balance fields deserve particular care. State whether a “current balance” is a ledger, contractual, charge-off, or calculated sale balance, and whether payments, credits, settlements, interest, fees, and reversals through the cutoff are included. Preserve exclusion codes and reconcile the offered population to the master extract.
Recommended control checks before delivery
- Confirm each offered account has one unique tape row.
- Reconcile row count and aggregate balances to the approved sale population.
- Test date formats, currency fields, sign conventions, and decimal precision.
- Define the meaning of blanks, zeroes, “N/A,” and unknown values.
- Validate that status flags use the dictionary’s allowed codes.
- Identify fields sourced after the tape cutoff or subject to update lag.
- Check that account-level documents can be linked to the correct identifier.
- Maintain a change log for versioned tapes and corrected fields.
Separate the Sale Tape From the Supporting File Set
The tape should not carry every fact needed for diligence. It is the index for a broader data room that may include the dictionary, a summary reconciliation, supporting documents, and an exceptions schedule. This structure lets reviewers trace portfolio totals to tape rows and, where appropriate, source documents.
Use an exceptions schedule for known limitations rather than silently omitting them. Examples include missing agreements for a subset, a conversion affecting a historical field, legacy document storage, or a risk flag not captured before a stated date. Transparency is not legal or compliance analysis, but it makes the scope of the package clearer.
A Practical Workflow for Preparing the Dictionary
- Define the offered population. Fix the portfolio cutoff date, inclusion criteria, and exclusion rules before finalizing field logic.
- Inventory source data. Map each proposed field to a source system, report, document repository, or calculation. Identify fields that cannot be reliably populated.
- Draft field-level definitions. Establish formats, permitted values, date bases, balance logic, and null rules. Mark derived fields clearly.
- Reconcile and test. Compare counts and totals with internal control reports; test samples for identifier matching and date or amount consistency.
- Document exceptions and version control. Give the tape and dictionary a version, cutoff date, and change log so updates can be tracked during diligence.
- Align delivery to the process. Share only the appropriate level of information through the agreed diligence channel and tailor the package to the prospective transaction.
Common Mistakes That Create Avoidable Questions
Common problems are operational: “DOB” is undefined; amounts lack a cutoff date; status codes arrive without a code table; records duplicate after migration; or documents cannot be matched to the tape identifier. Each issue can slow review while basic facts are established.
A summary schedule is not a substitute for row-level controls. Totals may reconcile while a subset has inconsistent statuses, dates, or balance components. The appropriate package is proportionate: sufficient normalized detail for the initial review, with further support delivered through the agreed process.
Frequently Asked Questions
Is a loan tape data dictionary the same as the loan tape?
No. The tape contains the account-level data. The dictionary explains what the tape’s columns and values mean, how they were sourced, and how exceptions should be interpreted.
Which field is most important in a debt sale tape?
There is no single universal field. Buyers commonly need a coherent combination of account identity, balance composition, timing and performance data, documentation indicators, and risk or exclusion flags. The materiality of each field depends on the portfolio.
How should missing values be shown?
Define them explicitly. A blank, a zero, “not applicable,” “not available,” and “unknown” can carry different meanings. The dictionary should state which representation is permitted for each field and why.
Should derived fields be included in a loan tape?
They can be useful for review if they are labeled as derived and the underlying inputs, calculation method, and cutoff date are documented. Derived fields should not obscure the original source data.
When should a seller update the tape?
Update timing depends on the sale process and agreed cutoff. When a refreshed tape is provided, label the version, disclose the new cutoff date, reconcile material changes, and retain a clear change log.
Transparent Limitations
A data dictionary improves clarity; it cannot repair incomplete records, determine legal enforceability, establish compliance, or predict buyer appetite, price, recovery, or closing. Fields may differ for performing loans, charged-off receivables, judgments, secured obligations, commercial credits, and portfolios subject to different requirements. Sellers should coordinate appropriate data, legal, compliance, servicing, and accounting review.
Educational disclaimer: This article provides general educational information about data preparation for debt portfolio sales. It is not legal, tax, accounting, investment, debt-collection, servicing, or compliance advice, and it does not create a broker-client relationship. Transaction participants should obtain advice tailored to their portfolio and applicable requirements.
Educational disclaimer: This article is general educational information and is not legal, tax, accounting, investment, debt-collection, servicing, privacy, or compliance advice.
Prepare the Portfolio Before the Market Sees It
Discuss a confidential, process-focused review of your debt portfolio sale materials with Fitzgerald Advisors.
