> ## Documentation Index
> Fetch the complete documentation index at: https://docs.stelle.co/llms.txt
> Use this file to discover all available pages before exploring further.

# Bulk upload

> Drop a pile of investor PDFs into one batch, let Stelle read and match each one, fix what's wrong, then publish them to the right investors.

Bulk upload files many investor documents at once: a quarter's NAV statements, a closing's subscription agreements, a year's tax slips. Stelle reads each PDF with AI and matches it to a fund and an investor. You don't rename files. You correct any mistakes, then publish.

**Who can do this:** Subscriptions & Documents (Write), across every fund and investor. GP Admins can do everything.

## Key concepts

* **Batch** — one pile of files sharing one document type, category and visibility.
* **Document type** — **Subscription agreement**, **Limited partnership agreement**, **Unit certificate**, **NAV statement**, **Capital call notice**, **Tax slip**, **Account statement** or **Other investor document**. It sets the default category, date meaning and name.
* **Alias** — another name your documents use for a fund or investor, such as a short name or a recurring typo.

## Start a batch

1. Go to **Records** → **Bulk upload** and click **New bulk upload**.
2. Choose the **Document type** and **Category**.
3. Optionally pick a **Fund (optional)** to file every document to that fund, whatever the PDFs say.
4. Choose whether the batch is **Visible to LPs**. Nothing else about the batch can change later.
5. Create the batch, then drop PDFs on it.

Keep the page open while files upload. Leaving stops files not yet sent.

## How matching works

Stelle matches the fund (the batch's fund, or by name or alias), then the investor among that fund's investors: by exact name, alias, close-enough name (at least 80% similar and clearly ahead), or, failing those, an email belonging to exactly one investor. Two similar investors both go to review rather than being guessed.

The **Match type** column shows how each file matched: **Exact**, **Alias**, **Fuzzy**, **Email**, **Batch** or **Manual**.

## Item statuses

| Status | Meaning | What to do |
| - | - | - |
| **Waiting** / **Reading** | Being read | Nothing |
| **Needs review** | Fund or investor didn't match | Pick them by hand |
| **Could not read** | The file couldn't be read | Pick by hand, or **Process** it again |
| **Ready to publish** | Fund and investor are set | Check fuzzy matches, then publish |
| **Published** | It's a document on the investor | — |

## Correct a match

1. Click a row to open its side panel beside the PDF.
2. Change the **Fund**, **Investor**, **Date**, **Language** or **Name**.
3. Under **Save as alias**, save names Stelle read that didn't match, so they match next time.
4. Save.

Later matching never overwrites your manual picks. An investor with no investment in the fund gets a warning but can still be published.

**Find Matches** re-matches using new aliases without re-reading files. **Process** re-reads files (by default those that **Need review** or **Could not read**). Both act on ticked rows, or the whole batch.

Manage aliases firm-wide under **Records** → **Bulk upload** → **Aliases**. A name can belong to only one fund or investor.

## Rename documents

1. Click **Rename…**.
2. Write a name template with `{fund_name}`, `{investor_name}`, `{quarter_year}` and `{year}`, for example `{fund_name}, {quarter_year} - {investor_name}`. At a bilingual firm, write the French one too.
3. Check the preview, then apply.

Only ready documents are renamed. Duplicate names get "(2)", "(3)" and so on.

## Publish a batch

1. Tick the rows to publish, or none to publish every ready document.
2. Click **Publish**.
3. Check the fuzzy matches the dialog lists. Ready doesn't mean a person checked it.
4. If the batch is visible, choose whether to tick **Email investors**.
5. Click **Publish *n* documents**.

Tax slips and account statements go on the investor's profile only. Every other type goes on the investor and their investment in the fund. A hidden batch shows investors nothing until you switch on **Visible to LPs**.

> [!WARNING]
>
> With **Email investors** ticked, each investor profile gets one **New documents** email, copied to its secondary emails. It starts unticked. The same choice appears when you later make a published batch visible.

## Unpublish or delete

* **Unpublish** archives the published documents and returns each item to **Ready to publish**.
* **Visible to LPs** on the batch shows or hides everything it published, overriding profile-level changes.
* **Remove from batch** takes one file out. A published one stays with its investor.
* **Delete batch** deletes the batch and its unpublished files. Published documents stay.

None of these emails investors.

## Good to know

* **PDF only, up to 100 MB each.** Files over 100 pages are read from their first and last 50 pages.
* **One PDF is one document for one investor.** Split multi-investor packs first.
* **One type per batch.**
* **Stelle reads who and when, never amounts**, and writes nothing to the ledger.
* **A published file stays tied to its batch.** Change its category and as-of date on the batch.

## What your investors see

* Each published, visible document appears under **Documents**, in the fund's group, or under **Other documents** for profile-only types. New files show **Unread**.

See [Document library](https://docs.stelle.co/documents/library.md).

## Related

* [Document library](https://docs.stelle.co/documents/library.md)
* [Automatic notifications](https://docs.stelle.co/communications/notifications.md)
* [Rollout checklist](https://docs.stelle.co/get-started/rollout-checklist.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.