A debt portfolio bid tape is the buyer's first structured view of the accounts offered for sale. It should let a qualified bidder group accounts consistently, test completeness, identify exclusions, connect totals to the sale population, and record every assumption used in a bid. A spreadsheet with many columns is not automatically decision-grade data.

This article is educational and does not provide investment, valuation, accounting, legal, or compliance advice. Buyers and sellers should use qualified professionals and the controlling sale documents for each transaction.

Define the offered population before defining columns

Give the tape a sale identifier, portfolio cut date, source-system snapshot time, currency, account-count definition, and stated face-value definition. Explain whether sold balance, current balance, principal, interest, fees, and credits are separate. The cover sheet should reconcile the tape to the portfolio described in the offering materials.

List excluded or specially handled populations, such as active disputes, bankruptcy, deceased accounts, pending payments, recalled placements, litigation, fraud claims, or accounts outside the permitted geography. An exclusion must be implemented in the data, not only described in prose.

Include fields that support cohort analysis

Use the minimum consumer information needed for evaluation. Direct identifiers should be protected and withheld from general bidder access unless the transaction, controls, and applicable requirements justify release.

• unique anonymous account key and portfolio key;
• product and creditor or originator category;
• placement, charge-off, default, and last-payment dates where applicable;
• principal, interest, fee, credit, payment, and total balance fields;
• state or approved geographic level;
• prior placement, contact, payment, dispute, and legal-status indicators;
• documentation and data-availability flags;
• restriction, recall, and post-cutoff update indicators.

Publish a field-level data dictionary

For every column, state its name, business definition, type, permitted values, null meaning, unit, source, derivation, and effective date. Distinguish zero from unknown, not applicable, and not provided. Define whether dates describe an event date, posting date, or file-load date.

Version the dictionary with the tape. A label such as last payment is ambiguous unless the seller explains which payment types qualify, how reversals are treated, and whether the value came from the creditor, a prior agency, or a later servicer.

Run machine and business quality tests

Do not silently repair seller data in the valuation copy. Preserve the received file, record transformations, and keep exceptions visible so the bid owner knows where estimates depend on uncertain inputs.

• unique-key and duplicate-account checks;
• required-field and permitted-value validation;
• date sequence and future-date tests;
• component balances that reconcile to totals;
• negative, zero, and extreme-value review;
• population totals by product, geography, vintage, and status;
• cross-field conflicts such as paid status with a positive balance;
• sample tracing from tape row to available source evidence.

Control questions and revisions

Route bidder questions through a numbered Q&A log. When an answer changes a definition or population, issue a new tape and dictionary version, explain the delta, and require the valuation team to rerun affected checks. Email attachments with the same filename are not reliable version control.

The OCC's current consumer debt-sales guidance emphasizes accurate, comprehensive information, due diligence, and quality control for OCC-supervised sellers. Transaction owners should determine which expectations and requirements apply to their roles.

Create a bid-readiness output

Summarize accepted rows, excluded rows, unresolved exceptions, material missing fields, definition changes, and the cohorts safe to model. Attach the exact tape checksum, dictionary version, query or transformation version, and review approvals to the bid record.

Connect the result to the existing portfolio segmentation framework and buyer due-diligence checklist rather than rebuilding population logic in separate workbooks.

Conclusion

A useful bid tape is a controlled dataset with a reconciled population, explicit definitions, repeatable tests, governed revisions, and traceable assumptions. Kaizen's debt portfolio marketplace provides a place for qualified participants to evaluate auction opportunities; each participant remains responsible for its own diligence and decisions.

Frequently asked questions

Should a bid tape include consumer names and full account numbers?

Not by default. Use anonymous stable keys and release only the minimum data justified by the evaluation stage, transaction controls, confidentiality terms, and applicable requirements.

What should happen when the tape changes after bids begin?

Issue a new version with a clear change log, reconcile the population, identify affected assumptions, and define whether bidders must resubmit under the controlling auction instructions.