Email Forwarding Setup
Forward receipts and bank alert emails to your two dedicated Satsuma addresses.
Email Forwarding
Satsuma provides two shared email addresses you can forward emails to. Each address routes to a different parser:
| Address | What to send | What happens |
|---|---|---|
receipts@… |
Order confirmations, purchase receipts | Parsed into a Receipt with line items |
txns@… |
Bank transaction alert emails | Parsed into a Transaction |
You'll find both addresses on Settings → Email Sources → Email Forwarding.
Before you can forward
Satsuma only accepts mail from email addresses you've explicitly verified — this prevents anyone from spoofing emails to your account.
To verify a sender address:
- Go to Settings → Email Sources → Email Forwarding
- Enter the email address you'll be forwarding from (your personal address, or your bank's alert address like
alerts@chase.com) in the "Add sender address" field - Click Send code — a 6-digit code is emailed to that address (valid for 30 minutes)
- Enter the code to confirm
Once verified, any email forwarded from that address to either Satsuma address will be processed automatically.
Forwarding receipts
When an order confirmation arrives in your inbox, forward it to the receipts@ address. Satsuma parses the email with a local AI model to extract the merchant, date, total, and individual line items.
Auto-forward filter (recommended): In Gmail or Outlook, create a filter that automatically forwards emails matching "receipt OR order confirmation OR invoice" to the receipts@ address. You'll never have to forward manually.
Forwarding bank alerts
Enable transaction alerts at your bank ("notify me on every purchase") and set the delivery address to your personal email. Then forward — or auto-forward — those alert emails to the txns@ address.
Satsuma detects bank alert emails by looking for phrases like "transaction alert", "charge alert", "debit alert", "new transaction" in the subject. It then extracts the amount, merchant, and tries to route the transaction to the right account based on the card last-four digits mentioned in the alert (e.g. "card ending in 4321").
Security
Forwarded mail must pass SPF/DKIM/DMARC authentication — emails that fail these checks are silently rejected. Parsing happens off the request cycle so the webhook returns immediately.
Checking activity
The Email Forwarding page shows a log of recent inbound emails — whether they were imported successfully, skipped (no recognisable content), or rejected (authentication failure).