> ## Documentation Index > Fetch the complete documentation index at: https://help.dash.fi/llms.txt > Use this file to discover all available pages before exploring further. # Email inbox > Forward vendor invoices to a dedicated Dash.fi address and we'll turn each attachment into a draft bill. The Bill Pay **Email inbox** gives your company a dedicated forwarding address — `@invoices.dash.fi` — that turns inbound invoices into draft bills. Forward an email and Dash.fi reads each attachment, prefills a draft bill with AI, and logs the email in the activity feed. The email inbox is rolling out behind the `billPayEmailInbox` feature flag. If you don't see the **Email inbox** button in the Bill Pay toolbar yet, contact [support@dash.fi](mailto:support@dash.fi) to enable it. ## When to use it Use the email inbox when invoices already arrive in your inbox and you'd rather forward them than upload each file by hand. It's especially useful for: * Routing vendor emails into Bill Pay without manual downloads * Letting multiple teammates funnel invoices into the same draft queue * Capturing a single audit log of every email that reached Bill Pay, whether it imported, was skipped, or was rejected For one-off invoices you already have on disk, **Upload an invoice** in the [Create a bill](/bill-pay/create-a-bill) flow is still the fastest path. ## Provision your address 1. Go to **Bill Pay** and click **Email inbox** in the toolbar. 2. In the side-sheet, click **Create inbox**. Dash.fi reserves a slug under `invoices.dash.fi` for your customer (for example, `acme@invoices.dash.fi`). 3. Copy the address with the copy button and share it with anyone who forwards invoices. The address is **frozen for the life of the customer** — once created it never changes, so it's safe to save in vendor records or contact lists. Creating an inbox requires the **Bill: write** permission. After provisioning, the **Email inbox** button stays in the toolbar for everyone with access to Bill Pay, and the side-sheet shows the address plus the activity log. ## Who can send to it Dash.fi accepts forwarded mail only when the sender is one of your own users. Each inbound email is checked against, in order: 1. **Spam and virus verdicts** — emails AWS SES flags as spam or virus are rejected. 2. **SPF authentication** — the envelope sender must pass SPF. DKIM alone isn't enough. Make sure the mailbox you forward from has SPF correctly configured. 3. **Sender domain** — the envelope sender's domain must match one of the email domains of users in your Dash.fi customer. 4. **Sender identity** — the sender must resolve to a known user in your customer. Mail that fails any of these checks is recorded in the activity log with a rejection reason (see below) and never creates a draft bill. Direct-from-vendor delivery is not supported yet — forward from your own mailbox. ## Supported attachments Dash.fi sniffs the attachment bytes rather than trusting the file extension, so renaming a file won't change how it's processed. | Status | What it means | | --------------- | --------------------------------------------------------------------------------------------------------------- | | **Supported** | PDF, JPEG, PNG, and WebP attachments — each becomes its own draft bill. | | **Unsupported** | Other file types (Word docs, spreadsheets, ZIP archives, logos in unsupported image formats, etc.) are skipped. | | **Unreadable** | The attachment couldn't be decoded — for example, a corrupt PDF. | | **Oversized** | The attachment exceeds the per-attachment size cap and is skipped. | Inline images that are part of the email signature (CID-referenced HTML assets) are ignored. There's a per-email cap on the number of attachments processed; emails with more than that have their remaining attachments skipped. If an email arrives with **no** supported attachment at all, the whole email is rejected with `noUsableAttachment` and no draft bill is created. ## Where draft bills land Every imported attachment becomes a **draft** bill, prefilled by Dash.fi's AI just like **Upload an invoice** — vendor, invoice number, currency, invoice date, due date, total amount, and line items. The original attachment is stored on the bill. You can find the new draft in the **Drafts** tab in Bill Pay, or open it directly from the activity log using **View bill**. Review the prefilled fields, fix anything the AI got wrong, set payment details, and submit just like any other bill. See [Create a bill](/bill-pay/create-a-bill) for the full flow. ## Read the activity log Open the **Email inbox** side-sheet to see every email that reached the address, newest first, with pagination at the bottom. Each row shows the sender, when the email was received, the per-email status, and any attachments. ### Email status | Status | Meaning | | ------------- | ------------------------------------------------------------------------------------------------------- | | **Processed** | The email was accepted and at least one attachment was handled. | | **Received** | Dash.fi is still working on the email — refresh the sheet shortly. | | **Rejected** | The email failed a guardrail check; see the rejection reason. | | **Failed** | Processing errored unexpectedly. Reach out to [support@dash.fi](mailto:support@dash.fi) if it persists. | ### Rejection reasons | Reason | What happened | | -------------------- | --------------------------------------------------------------------------------- | | `unknownSlug` | The address the email was sent to doesn't match a provisioned inbox. | | `domainMismatch` | The sender's domain isn't one of your customer's user domains. | | `authFail` | The sender failed SPF authentication. | | `spam` | SES flagged the email as spam or carrying a virus. | | `unknownSender` | The sender's domain matches, but the address isn't a known user in your customer. | | `volumeExceeded` | The address received too many emails in a short window. | | `noUsableAttachment` | The email had no supported, readable attachment. | ### Attachment outcomes Each attachment in the row carries its own status: | Status | Meaning | | ------------- | ------------------------------------------------------------------------------- | | **Importing** | The attachment is being parsed into a draft bill. | | **Imported** | A draft bill was created. Click **View bill** to open it. | | **Skipped** | The attachment was unsupported, unreadable, or oversized — see the skip reason. | | **Failed** | Import errored unexpectedly. | ## FAQ No. The address is frozen when you create the inbox — it never changes for the lifetime of your customer, so it's safe to save in vendor records. Not in this release. Dash.fi only accepts forwarded mail from users in your own customer (validated by SPF and your user email domains). Have someone on your team forward the vendor's invoice. Forwarding can rewrite the envelope sender in ways that break SPF, or move the message under a domain that isn't one of your user domains. Try forwarding from a primary work mailbox, or use **Upload an invoice** in [Create a bill](/bill-pay/create-a-bill) as a fallback. They're recorded in the activity log with a skip reason (`unsupported`, `unreadable`, or `oversized`) and no draft bill is created. Any other supported attachments on the same email still import normally. ## Related * [Create a bill](/bill-pay/create-a-bill) — including the upload and manual intake methods * [Manage bills](/bill-pay/manage-bills) — find and edit drafts created from forwarded emails * [Bill pay](/bill-pay) — bill lifecycle, tabs, and exports