A Standard field is a field whose meaning Vintage understands, such as Current Balance or Net Charge-Off Amount. When you map a column in your file to a Standard field, Vintage knows how to use it: to tie rows to a loan, to age the loan, or to measure credit loss and prepayment. Every other column is kept as a Custom attribute, under its own name, so you can still filter on it later. Nothing you upload is dropped.
The tables below are the full, fixed set of Standard fields. You cannot add to it, and you do not need to supply most of it. Loan ID is the only field every file must have. Every other field is your call, and the Review screen tells you what each missing field costs you before you finalize.
How to read the tables
Section titled “How to read the tables”Each table below covers one group of fields, in the order Vintage groups them.
- Field is the display name you see on the Column Mapping and Fields screens.
- id is the field’s fixed key. It appears beside the display name on the Standard Fields tab of the Fields screen. You never need to use it as a column heading; Vintage matches your own headings.
- Files names the file groups the field is recognized on: Origination, Snapshot, or Transaction. When you map a column, the field picker offers only the Standard fields that apply to that file’s group.
- Type is the field’s value type: numeric, date, categorical, or text. A Standard field’s type is fixed.
Universal base
Section titled “Universal base”These three fields are part of every modeling method. A loan cannot be modeled for anything without them, and every method also needs a term (see Payoff, closure, and term).
| Field | id | Files | Type | What it holds |
|---|---|---|---|---|
| Loan ID | loan_id | Origination, Snapshot, Transaction | text (scrambled) | Your identifier for the loan. The only key that ties rows to one loan, across files and across uploads. |
| Snapshot Month | snapshot_month | Snapshot | date | The month a snapshot row describes. |
| Current Balance | current_balance | Snapshot | numeric | Outstanding principal balance at the snapshot. |
Loan ID is a protected identifier: before your file leaves your browser, each value is replaced by a one-way scrambled stand-in called a protected ID. Vintage stores only that, which is enough to recognize the same loan next month. See Removing personal information.
Protected identifier
Section titled “Protected identifier”| Field | id | Files | Type | What it holds |
|---|---|---|---|---|
| Tax ID | tax_id | Origination, Snapshot, Transaction | text (scrambled) | The borrower’s tax identifier (SSN, TIN, or EIN). Scrambled and stored; a fallback join key, never modeled. |
Tax ID is scrambled the same way Loan ID is, and kept when you identify it. It serves as a fallback join key; Loan ID is the primary key that identifies a loan.
Origination
Section titled “Origination”These fields are preferred, not required. When they are missing, Vintage estimates them for some loans and tells you so; see Origination and term.
| Field | id | Files | Type | What it holds |
|---|---|---|---|---|
| Origination Date | origination_date | Origination, Snapshot | date | The date the loan was originated. |
| Original Loan Amount | original_loan_amount | Origination, Snapshot | numeric | The loan amount at origination. |
Credit-loss inputs
Section titled “Credit-loss inputs”| Field | id | Files | Type | What it holds |
|---|---|---|---|---|
| Transaction ID | transaction_id | Transaction | text | Optional. Used to deduplicate transactions when provided. |
| Transaction Date | transaction_date | Transaction | date | The date a transaction or event occurred. Used to time and deduplicate transaction events. |
| Net Charge-Off Amount | net_charge_off_amount | Snapshot, Transaction | numeric | The loss amount after recoveries. |
| Charge-Off Amount | charge_off_amount | Snapshot, Transaction | numeric | The gross amount charged off. |
| Recovery Amount | recovery_amount | Snapshot, Transaction | numeric | The amount recovered after a charge-off. |
| Charge-Off Flag | charge_off_flag | Snapshot, Transaction | categorical | A marker that a charge-off happened. You classify which values mark the event. |
| Charge-Off Date | charge_off_date | Snapshot | date | The explicit date of the charge-off. The strongest timing evidence for a charge-off. |
How each combination of these fields is used is listed on Modeling methods. How charge-offs and recoveries are booked is explained in Charge-offs and recoveries.
Typed transaction ledger
Section titled “Typed transaction ledger”Many core systems export one ledger with a kind code on each row and a single amount column, rather than a separately named amount column for each kind. These two fields read that shape.
| Field | id | Files | Type | What it holds |
|---|---|---|---|---|
| Transaction Type | transaction_type | Transaction | categorical | The kind of each ledger row. You classify each code as Charge-off, Recovery, Payoff, Partial prepayment, Regular payment, or Not a modeled event. |
| Transaction Amount | transaction_amount | Transaction | numeric | The single generic amount column. Its meaning comes from the row’s Transaction Type. |
Each row’s amount is routed into the measure its classified kind names: a charge-off row’s amount is read as a charge-off amount, a recovery row’s as a recovery, a payoff row’s as a payoff amount, a partial prepayment row’s as a partial prepayment amount, and a regular payment row’s as an Actual Payment Amount. A row classified Not a modeled event, or not classified at all, contributes nothing. If the same row also carries a named column for the same quantity, such as a real Charge-Off Amount column, the named column wins. See Classifying values.
Payoff, closure, and term
Section titled “Payoff, closure, and term”| Field | id | Files | Type | What it holds |
|---|---|---|---|---|
| Payoff Flag | payoff_flag | Snapshot | categorical | A marker that the loan was paid off. You classify which values mark the event. |
| Prepayment Flag | prepayment_flag | Snapshot | categorical | A marker of a full prepayment. You classify which values mark the event. |
| Payoff Amount | payoff_amount | Snapshot, Transaction | numeric | The amount paid to retire the loan. |
| Payoff Date | payoff_date | Snapshot | date | The explicit date of the payoff. The twin of Charge-Off Date. |
| Loan Status | loan_status | Snapshot | categorical | The loan’s lifecycle status. You classify each value as Open (still active), Paid off, Charged off, or Exited (other). |
| Closure Reason | closure_reason | Snapshot | categorical | Why the loan was closed. Classified with the same four meanings as Loan Status. |
| Closed Date | closed_date | Snapshot | date | The date the loan closed. It times whichever ending the rest of the data proves; it never says which ending it was. |
| Term (Months) | term_months | Origination, Snapshot | numeric | The loan’s term in months. |
| Maturity Date | maturity_date | Origination, Snapshot | date | The scheduled maturity date. |
Every modeling method needs a term: either Term (Months), or a Maturity Date from which Vintage derives the term as the calendar months from origination to maturity. A loan with neither cannot enter the modeling curves, because its lifetime is undefined and its runoff would be miscounted as prepayment. A maturity date is a term source and nothing more.
How these fields decide when and how a loan ended is explained in How a loan’s ending is decided and Payoffs and exits.
Partial-prepayment inputs
Section titled “Partial-prepayment inputs”| Field | id | Files | Type | What it holds |
|---|---|---|---|---|
| Partial Prepayment Amount | partial_prepayment_amount | Snapshot, Transaction | numeric | The partial prepayment in the period. |
| Unscheduled Principal Amount | unscheduled_principal_amount | Snapshot, Transaction | numeric | Principal paid beyond the schedule. |
| Actual Principal Paid | actual_principal_paid | Snapshot | numeric | The principal actually paid in the period. |
| Scheduled Principal Due | scheduled_principal_due | Snapshot | numeric | The scheduled principal due in the period. |
| Scheduled Principal Paid | scheduled_principal_paid | Snapshot | numeric | The scheduled principal paid in the period. |
| Interest Rate | interest_rate | Origination, Snapshot | numeric (percent) | The loan’s annual note rate. |
| Scheduled Payment Amount | scheduled_payment_amount | Snapshot, Transaction | numeric | The scheduled total payment for the period. |
| Actual Payment Amount | actual_payment_amount | Snapshot, Transaction | numeric | The total payment actually collected in the period. |
Measuring a prepayment speed needs a reported schedule basis: Scheduled Principal Due or Scheduled Principal Paid, or a Scheduled Payment Amount paired with an Actual Payment Amount for the same month. A loan without one gets no speed. See Prepayment speeds.
Interest Rate is read as Percent points by default, so 8.36 means 8.36%. If your core exports rates as fractions (0.0836), you can change the field’s format to Decimal fraction. See Declaring formats.
Recognized non-modeling attributes
Section titled “Recognized non-modeling attributes”These are recognized so your column lands somewhere named, but no modeled output reads them.
| Field | id | Files | Type | What it holds |
|---|---|---|---|---|
| FICO Score | fico_score | Origination, Snapshot | numeric | The borrower’s FICO credit score. |
| Closed Snapshot Month | closed_snapshot_month | Snapshot | date | The month a loan was observed closed. Stored, but feeds no measurement: Vintage takes an ending’s timing from the explicit event dates and marker months instead. |
The amortization inputs
Section titled “The amortization inputs”Term (Months), Maturity Date, and Interest Rate are the amortization inputs: they fix a loan’s term and note rate.
- They feed the projections only: the pricing build-up, the month-by-month cash-flow projection, the projected tail of the credit-loss curve, and the WARM fallback. Those projections assume level payments and say so beside every figure.
- No measurement amortizes with them. No curve Vintage measures from your own history reconstructs a payment schedule. In a measurement, the term has only two roles, both as a gate: a loan needs a term to be modeled at all, and the term marks the final three months within which a loan that vanishes from your file is treated as matured rather than as an inferred payoff.
- Scheduled Payment Amount is not an amortization input. No projection reads it. Its one use is in the prepayment-speed measurement, as the scheduled half of the payment-totals pair.
- An interest rate and a scheduled payment on their own are not a schedule basis for the prepayment speed.
Headings Vintage recognizes
Section titled “Headings Vintage recognizes”Vintage recognizes a column by the field’s own name or a known synonym, so your headings do not need to match the display names exactly, and it pre-fills its suggestion on the Column Mapping screen. Recognition goes beyond this list, and every suggestion is yours to confirm or change. Some common synonyms:
| Field | Headings recognized include |
|---|---|
| Loan ID | Loan Number, Loan No, Acct No, Account Number, Note ID, Note No |
| Tax ID | SSN, TIN, EIN, Social Security Number, Federal Tax ID |
| Snapshot Month | As Of Date, Statement Month, Reporting Month, Period End, Snapshot Date |
| Current Balance | UPB, Current Principal Balance, Principal Balance, Outstanding Balance, Curr Bal |
| Origination Date | Orig Date, Note Date, Funding Date, Booked Date, Open Date |
| Original Loan Amount | Orig Bal, Original Amount, Original Note Amount, Funded Amount |
| Transaction Date | Txn Date, Posted Date, Effective Date |
| Transaction Type | Txn Type, Tran Code, Transaction Code, Entry Type |
| Transaction Amount | Amount, Amt, Txn Amt, Posting Amount |
| Net Charge-Off Amount | NCO Amount, Net Charge Off, Net Loss |
| Charge-Off Amount | Gross Charge Off, Charge Off Amt, CO Amount |
| Recovery Amount | Recoveries, Recovery Amt |
| Charge-Off Flag | Charged Off, CO Flag |
| Charge-Off Date | CO Date, Charged Off Date, Write Off Date |
| Payoff Flag | Paid In Full, PIF Flag, Is Paid Off |
| Payoff Date | Paid Off Date, PIF Date, Paid In Full Date |
| Loan Status | Status, Account Status |
| Closure Reason | Close Reason, Closed Reason |
| Closed Date | Close Date |
| Term (Months) | Term, Loan Term, Amortization Term |
| Maturity Date | Maturity |
| Partial Prepayment Amount | Curtailment, Curtailment Amount |
| Unscheduled Principal Amount | Unscheduled Principal, Extra Principal |
| Actual Principal Paid | Actual Principal, Principal Paid |
| Interest Rate | Rate, Int Rate, Note Rate, APR |
| Actual Payment Amount | Payment Amount, PMT AMT, Actual Payment, Total Payment, Amount Paid |
| Scheduled Payment Amount | Scheduled Payment, Contractual Payment, Regular Payment |
| FICO Score | FICO, Credit Score |
Fields whose values you classify
Section titled “Fields whose values you classify”Six Standard fields carry codes rather than amounts, and a code means something only because you say so. When you map a column to one of them, Vintage lists its distinct values and asks what each one means:
- Loan Status and Closure Reason: Open (still active), Paid off, Charged off, or Exited (other).
- Charge-Off Flag, Payoff Flag, and Prepayment Flag: which values mark the event and which do not. Vintage keeps no built-in list of values such as
Yor1. - Transaction Type: Charge-off, Recovery, Payoff, Partial prepayment, Regular payment, or Not a modeled event.
Your answers belong to your organization, so a later upload with the same values asks nothing. See Classifying values.
Amount fields with a reporting basis
Section titled “Amount fields with a reporting basis”For the flow amounts (Charge-Off Amount, Net Charge-Off Amount, Recovery Amount, Actual Principal Paid, Actual Payment Amount, Scheduled Principal Due, Scheduled Principal Paid, and a ledger’s Transaction Amount), Vintage asks whether the column reports each month’s activity, a life-to-date running total, or a year-to-date total that resets each January. It pre-fills the answer as a suggestion when the column’s own history makes it clear, and asks you outright when it cannot tell. Vintage converts every such column to monthly amounts before any calculation. See Declaring formats.