# Upload History

**Upload History** is the list of every upload your organization has made, newest first. It is where you pick up an unfinished upload, reopen a finished one to check or adjust its mapping, and delete an upload or a file you no longer want in your portfolio. Open it from **Upload** in the main navigation; the page is headed **Uploads**, and **New upload** starts another.

Upload History is open to admins and editors. Uploads belong to the organization, not to one person, so everyone who can upload sees every upload.

## What each row shows

Each row is one upload, however many files it contains.

| Column | Shows |
|---|---|
| **Uploads** | The date and time: when it was accepted, or when it was started if it is still a draft |
| **Status** | Where the upload stands now (below) |
| **Uploaded by** | The member who started it. Kept even if that person is later removed from the organization. |
| **Loan Snapshots**, **Origination Files**, **Transaction Files** | How many files of each type the upload contains |

The last column holds the row's actions: **Delete upload**, and for a draft, a button to reopen it. A long list loads more rows with **Load more**.

## What the statuses mean

An upload is a **draft** until it is accepted. While a draft is moving, the status shows its live stage, and the list refreshes on its own while any row is still moving.

| Status | What it means | What you do |
|---|---|---|
| **Draft** | Files are still being sent from a browser tab, so no progress can be reported here yet | Nothing, or return to the tab that is uploading |
| **Processing · 3 of 12 files** | Vintage is reading the files in | Nothing. You can reopen it to watch. |
| **Analyzing** | Every file is read; Vintage is analyzing columns and preparing suggestions | Nothing |
| **Mapping** | Processing is finished and a suggested mapping is in place, but nobody has confirmed it yet | **Resume** to confirm the mapping |
| **Ready to review** | The mapping was confirmed and the upload has reached Review | **Resume** to review and accept it |
| **Needs attention** | A file could not be processed, or the upload has no data rows | **Fix upload** to decide what to do with the file |
| **In verification** | With the Vintage team during your organization's first-upload setup. Nothing here needs you. | **Open upload** to look, if you like. See [Your first upload](/uploading/your-first-upload/). |
| **Removing…** | Deleted; its data is being removed in the background | Nothing. The row leaves the list once the data is removed. |
| **Accepted** | Finalized and part of your portfolio | Click the row to reopen it |

A file Vintage has given up on always outranks progress: an upload with one failed file reads **Needs attention**, never as still processing. And an upload whose suggested mapping nobody has confirmed reads **Mapping**, not **Ready to review**, because Vintage never counts its own suggestion as your decision.

## Resuming a draft

Every unfinished draft carries its own reopen button on its row: **Resume**, or **Fix upload** when a file needs your decision. (The list is the only place to resume from, so having two drafts never looks like having one.) Drafts do not expire; a draft waits until you accept it or delete it.

Where a resumed draft opens is decided from what the upload has actually produced:

- **Still being processed:** the same Processing screen the uploader shows, with live progress. Any file that failed is named and removable, so the rest can go on.
- **Processed, mapping not yet confirmed:** Column Mapping.
- **You had reached Review:** Review. This holds even if you left while the Review was still being prepared.

A resumed draft never goes back to Choose Files or Remove PII: your original files are never stored, because they carry personal information. A resumed draft shows every file in the upload with its state, so an interrupted batch is never quietly narrowed to the files that happened to finish. Mapping edits you had not saved are not carried over; you see the mapping as it was last saved.

## Reopening an accepted upload

Click an accepted row to open it. You see the upload's saved column mappings, one block per file, and its Review. You can change a mapping here and press **Save mapping**; the change applies only to that upload's file, and your other uploads are unchanged.

A reopened Review reads at two grains, on purpose, and says so on the screen:

- **Its reconciliation is history.** "120 new loans" means the loans that were new **when this upload was accepted**. That figure is fixed then and never rewritten by anything that happened to the portfolio later.
- **Its readiness is as of now.** What each output can be modeled with reflects your portfolio as of its last completed update, plus this upload's own data.

While your portfolio is still being updated (after another upload or a deletion, for instance), the reopened Review says so, and that its readiness figures **may change when the update finishes**, in either direction. See [Reviewing before you finalize](/uploading/reviewing-before-you-finalize/).

## Deleting an upload or a file

You can delete a whole upload from its row with **Delete upload**, whether it is a draft or accepted. To remove a single file from an accepted upload, reopen the upload and use **Delete file** on that file. A deletion removes the data from your active portfolio: it no longer counts toward readiness, modeling, or pricing.

The confirmation says what will actually happen:

- **For a draft:** the upload was never accepted into your portfolio, so deleting it leaves your existing numbers unchanged.
- **For an accepted upload:** your portfolio is recomputed from the remaining uploaded data, the removal runs in the background, and the upload shows as **Removing…** until it finishes.

The delete takes effect the moment you confirm, however large the upload, and you never wait for the removal itself. From then on the upload cannot be opened, resumed, or deleted again. Its row reads **Removing…** with a note:

- for an accepted upload, that its data is being removed from your portfolio and the portfolio numbers update when that finishes;
- for a draft, that its stored data is being cleared and your portfolio is not affected.

The row leaves the list once the data is removed and, for an accepted upload, the rebuild it needs is under way. The rest of that rebuild shows on the Portfolio and Modeling screens, which display their processing state rather than present the old numbers as current. See [The Portfolio screen](/portfolio/the-portfolio-screen/).

If the answer to a delete never arrives (the connection drops, or the request takes too long), Vintage checks the list again rather than guess. An upload that is gone or reads **Removing…** was deleted. Otherwise you see "We could not confirm the delete. The upload is still listed, so please try again."

**Deleting your earliest months affects the whole portfolio:** If the files you delete carried your portfolio's **earliest snapshot months**, your observed history now starts later. Vintage then re-evaluates every loan in the portfolio, not only the deleted ones, because a loan that looked seasoned only because those early months existed is honestly re-classified once they are gone. Adding older files has the same whole-portfolio effect. See [Origination and term](/concepts/origination-and-term/).

To correct an upload that went in wrong, delete it and upload the corrected file. [Uploading month after month](/uploading/uploading-month-after-month/) covers corrections in more detail.

## What is kept after a delete

A deleted upload stops contributing to your portfolio immediately, but a record is kept for audit:

| What | How long |
|---|---|
| The deleted rows' cell values | Purged **90 days** after deletion |
| The upload's row and column metadata, and the scrubbed file that was uploaded | Kept indefinitely, for audit |
| Data from uploads you have not deleted | Never purged. It is the basis for your portfolio and for recomputing it. |

Keeping audit records is the default, not a condition of using Vintage. Your organization can **request permanent deletion** of its data at any time, and Vintage then removes the retained files and audit records as well. This is a request to the Vintage team rather than a control in the product. See [Security and data protection](/reference/security-and-data-protection/).

## Related

- [How uploading works](/uploading/how-uploading-works/)
- [Uploading and processing](/uploading/uploading-and-processing/)
- [Reviewing before you finalize](/uploading/reviewing-before-you-finalize/)
- [Uploading month after month](/uploading/uploading-month-after-month/)
- [Your first upload](/uploading/your-first-upload/)
- [Security and data protection](/reference/security-and-data-protection/)