Skip to main content
The Bill Pay Email inbox gives your company a dedicated forwarding address — <slug>@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.

​
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 flow is still the fastest path. If your vendor invoices already land in a normal work inbox — for example an ap@yourco.com mailbox — connecting that mailbox directly is usually simpler than forwarding each one. See Connected mailboxes.

​
Provision your address

  1. Go to Bill Pay and click New bill → Forwarding address.
  2. In the side-sheet, click Create inbox. Dash.fi reserves a slug under invoices.dash.fi for your organization (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 your organization — 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, Forwarding address stays in the New bill dropdown 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 a user in your organization. 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 organization.
  4. Sender identity — the sender must resolve to a known user in your organization.
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. 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 for the full flow.

​
Read the activity log

Open New bill → Forwarding address to see every email that reached the address, newest first, with pagination at the bottom. Each row shows the sender, subject (when present), when the email was received (to the second), the per-email status, and each attachment with its own outcome. Truncated senders, subjects, and file names reveal the full value on hover. Narrow the log with the Status filter at the top of the activity list — All statuses (default), Received, Processed, Rejected, or Failed. Reopening the drawer always jumps back to page 1.

​
Email status

​
Rejection reasons

​
Attachment outcomes

Expand a row to see every attachment on the email with its own outcome:

​
FAQ

No. The address is frozen when you create the inbox — it never changes for the lifetime of your organization, so it’s safe to save in vendor records.
Not in this release. Dash.fi only accepts forwarded mail from users in your own organization (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 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.
  • Connected mailboxes — the alternative that reads a Gmail or Microsoft 365 mailbox directly
  • Create a bill — including the upload and manual intake methods
  • Manage bills — find and edit drafts created from forwarded emails
  • Bill pay — bill lifecycle, tabs, and exports