An upload is how your loan data gets into Vintage. You choose one or more files exported from your core system, Vintage removes personal information from them in your browser, the cleaned files are sent and read, you confirm what each column means, and you review what the upload will do to your portfolio before you accept it. What follows is the map of that journey; each stage has its own page with the detail.
Only admins and editors can upload. A member with the viewer role does not see the Upload entry in the navigation, and Upload History is closed to them. See Roles and permissions.
What one upload is
Section titled “What one upload is”One pass through the uploader is one upload. However many files you add in that pass, they travel together: they are processed together, reviewed together, and accepted together. Upload History lists each upload as one row.
Files are added in file groups, which you declare by choosing the card a file belongs under:
| File group | What it carries |
|---|---|
| Loan Snapshots | Your portfolio at a point in time, one row per loan (a monthly, quarterly, or yearly picture) |
| Origination Files | Each loan’s facts at the time it was made, such as origination date and original amount |
| Transaction Files | Individual loan events: charge-offs, recoveries, payoffs, prepayments |
An upload can hold any combination of the three: a single snapshot file, an origination file on its own, or a long run of monthly snapshots plus an origination file and a transaction file. Vintage accepts useful partial data and tells you, at Review, what it can and cannot model from what you sent. Preparing your data covers what to export.
Most of the work happens once per file group, not once per file. Every file in a group shares one set of columns, so you decide which columns hold personal information once for the group, and you map its columns once for the group. Choosing files explains the one-set-of-columns rule.
An upload is a draft until you accept it, and accepted afterwards. Only accepted uploads feed your portfolio.
The five stages
Section titled “The five stages”A progress rail down the right side of the uploader shows where you are: Choose Files → Remove PII → Upload → Column Mapping → Review. On a narrow screen it collapses to a band above the step that reads, for example, “Step 2 of 5 · Remove PII”. The rail stays in view as you scroll.
| Stage | What you do | What Vintage does |
|---|---|---|
| Choose Files | Add files under the Loan Snapshots, Origination Files, or Transaction Files card | Reads each file’s columns in your browser. Nothing is sent yet. |
| Remove PII | Pick the Loan ID column and, if your file has one, the Tax ID column, and tick any other columns that hold personal information | Suggests the identifier columns and flags likely personal information for you to confirm |
| Upload | Keep the page open while files are sent, then leave if you like | Removes the ticked columns, scrambles the identifiers, sends the cleaned files, reads them, and suggests a mapping |
| Column Mapping | Confirm what each column means | Pre-fills its suggestions and remembers your answers for next time |
| Review | Read what the upload will do, then accept it | Joins the upload to your existing portfolio and reports what can be modeled |
Choose Files. You add files by type. Vintage refuses file types it cannot read and files with no data at the moment you choose them, and it flags a file whose columns do not match the rest of its group and holds Continue until you deal with it, so a problem never surfaces two screens later. See Choosing files.
Remove PII. This is the last step before anything leaves your browser. You choose which column is the Loan ID (required) and which is the Tax ID (optional). Both are replaced by protected IDs, one-way scrambled values, before upload. Any column you tick as personal information is removed and never sent. When an upload has more than one file group, you confirm each group in turn. See Removing personal information.
Upload. This stage covers two screens. On Uploading, the cleaned files are sent from your open tab, so you stay on the page until every file has finished. The moment the last file lands, the screen changes to Processing: Vintage reads the files and prepares a suggested mapping on its own, and you can close the tab. See Uploading and processing.
Column Mapping. For each file group, you map every column to a Standard field (one Vintage understands, such as Current Balance) or keep it as a Custom attribute. Nothing is dropped. Mapping opens only once the whole upload has finished processing. See Mapping columns.
Review. A single screen states whether the upload can be accepted, how its rows reconcile into loans, and what each modeled output (credit loss, payoff, prepayment) can be measured for. Continuing past Review accepts the upload. There is no separate Finalize screen. See Reviewing before you finalize and Finalizing and what happens next.
Raw values from your files never reach Vintage until after Remove PII. After that step, your browser sends only the cleaned files.
When to stay on the page and when you can leave
Section titled “When to stay on the page and when you can leave”The uploader is built so you can walk away for most of it. The one window where you cannot is while files are leaving your browser.
| Where you are | Can you leave? |
|---|---|
| Choose Files and Remove PII | Your files exist only in this browser tab. Nothing has been uploaded, so leaving or refreshing starts over from Choose Files. |
| Uploading | Stay. Files can only be sent from an open tab. If you move elsewhere in Vintage while any file has not reached Vintage, a warning names how many files would have to be chosen and sent again; closing the tab shows your browser’s own generic warning instead. Files that have already finished are kept. |
| Processing | Yes. Your files are with Vintage, which keeps working without your tab. You are emailed when they are ready for column mapping. |
| Column Mapping | Yes. Resume from Upload History at any time. Mapping edits you have not saved are not kept across a refresh: you return to the mapping as it was last saved. |
| Review | While the Review is prepared, the screen shows the size of the job and an elapsed clock. If you leave, Upload History reopens the upload at Review. |
| After you accept | Yes. If your portfolio is still being updated, the confirmation says so and you are emailed when it is ready. |
Once every file has reached Vintage, the browser’s address bar names the upload, so refreshing the page returns you to that same upload rather than starting a new one.
A draft waits for you
Section titled “A draft waits for you”A draft is kept until you accept it or delete it. There is no expiry and Vintage never removes an unfinished upload on its own. Every draft in Upload History carries a Resume action (or Fix upload, when a file needs your decision) that reopens it at the right step. Because your original files are never stored (they carry personal information), a resumed upload never goes back to Choose Files or Remove PII.
The three emails about an upload
Section titled “The three emails about an upload”Because you can leave partway through, Vintage emails you at the three moments that call for it. These emails go to the person who started the upload.
| When it is sent | Button | |
|---|---|---|
| Your upload is ready to review | Every file in the upload has been processed, and the upload contains data | Review upload |
| Your upload needs attention | Something is blocking the upload: a file could not be processed, the files turned out to contain no data rows, or the Review could not be prepared | Open upload |
| Your portfolio is updated | An upload you accepted has finished being folded into your portfolio, and Portfolio and Modeling now reflect it | View portfolio |
Some details about when each is and is not sent:
- An upload with no data rows is never “ready to review”. If the files finish processing but contain no data rows (an empty export, or one with column headings only), you get Your upload needs attention instead, with a sentence saying why, and the Upload History row reads Needs attention as well.
- “Your portfolio is updated” is sent only when the update outlasts the confirmation. If your portfolio is already up to date by the time you see the confirmation after accepting, the confirmation says so and no email follows.
- Several uploads finishing together produce one email. When more than one of your accepted uploads lands at the same time, you receive one email that says how many it covers. Two uploads started by two different people still produce one email each.
- No email when Vintage reprocesses your portfolio on its own initiative, for example after it improves how it reads data. Nobody asked for that work, so nobody is notified.
- During your organization’s first-upload setup, the “portfolio updated” email is held, and the email that every member receives when setup is complete takes its place. See Your first upload.
Email is a convenience, never the only way to know where an upload stands. Each row in Upload History shows its live stage, and the uploader’s progress rail shows it too. Emails Vintage sends lists every email the product sends, including the account emails.