Remittance Email Import

When a supplier pays out a commission, they typically send a remittance advice — a PDF or plain-text email that lists what was paid, which bookings it covers, and any reference numbers. Instead of manually hunting down each entry in your ledger, you can forward that email directly to JourneyFuse and let AI parse it and match it to your open commission records automatically.

The system creates a draft import for you to review. You confirm or dismiss it in about 10 seconds. That's it.

Setup: Find Your Import Address

Each workspace has a unique import address. To find yours:

1. Go to Settings → Email
2. Look for the Commissions Import Address section
3. Copy the address — it looks like commissions+{your-workspace-id}@mail.journeyfuse.com

That's the only setup required. No API keys, no integrations to configure.

Tip: Add the address to your contacts or create a forwarding rule in your email client so you never have to look it up again.

Forwarding a Remittance

When a supplier sends you a commission payment remittance:

1. Open the email in your inbox
2. Forward it (with any PDF attachments) to your import address
3. JourneyFuse processes it in the background — usually within a minute
4. A new draft appears in Commissions → Imports for you to review

You can forward from any email client — Gmail, Outlook, Apple Mail, whatever you use. The system accepts the email body and any attached PDFs.

How Matching Works

After parsing the remittance, JourneyFuse attempts to match the payment to your open commission entries in two phases:

Phase 1 — Reference Number Match (High Confidence)

The AI extracts any booking reference numbers, confirmation codes, or invoice numbers from the remittance. It then searches your open commission entries for exact matches. When a reference number aligns with an entry, the match is flagged as high confidence — it's almost certainly the right record.

Phase 2 — Fuzzy Amount + Supplier Match (Medium Confidence)

If no reference number match is found, the system falls back to comparing the payment amount and supplier name against your open entries. An amount within a small tolerance of an expected commission, from a supplier that matches, is flagged as a medium confidence match.

Medium confidence imports still need your review — a near-match could be correct, or it could be a coincidence. Either way, you stay in control before anything is committed to your ledger.

Unmatched Imports

If the system can't find any matching entry (no reference numbers, amount doesn't align with any open entry), the import is still created as a draft — it just won't be pre-linked to a specific commission entry. You can review the parsed details and manually reconcile from there.

Review & Confirm

All pending imports appear under Commissions → Imports.

Each import card shows:

• Supplier name extracted from the remittance
• Payment amount and payment date
• Reference numbers found (if any)
• Matched commission entry (if a match was found) with the confidence level
• The raw parsed data so you can spot any extraction errors

From there you have two actions:

Confirm — Accepts the import and links it to the matched commission entry. The entry is updated with the remittance details and marked accordingly in your ledger.

Dismiss — Discards the draft. Use this if the import is a duplicate, the match is wrong, or the email wasn't actually a remittance (e.g., a supplier newsletter that happened to mention a dollar amount).

Confirmed and dismissed imports are removed from the pending list — only actionable drafts are shown.

Tips for Better Results

PDFs get better extraction. When a supplier attaches a PDF remittance statement, JourneyFuse uses GPT-4o to analyze it — the most capable model for structured document extraction. If a supplier only sends a plain-text email body, it uses GPT-4o-mini, which still works well but may miss edge cases in unusual formats.

Forward the original, don't copy-paste. Forwarding preserves the full email structure and any attachments. Pasting text into a new email loses the PDF and reduces extraction accuracy.

Include the PDF if you have it. Some suppliers send a brief plain-text email with a PDF attachment that has all the detail. Make sure the PDF is attached when you forward — the AI will prioritize the structured data in the PDF over the plain-text body.

Use booking references whenever possible. If your supplier includes booking confirmation numbers on their remittances, those Phase 1 matches are far more reliable than amount-based matching. Consider asking suppliers to include references if they don't already.

Duplicates are safe to forward. If you accidentally forward the same remittance twice, the second import will appear as a separate draft. Just dismiss it.

FAQ

Which suppliers does this work with? Any supplier that sends remittance emails — there's no predefined list. The AI reads the email content and extracts whatever details it finds.

What if the supplier name is extracted incorrectly? You'll see the extracted name on the import card before confirming. If it looks wrong, dismiss the import and manually update the commission entry. You can also forward the email again after confirming your import address is correct.

Can multiple agents in my workspace use the same import address? Yes. The import address is workspace-wide — any agent can forward remittances to it, and the imports appear in the shared Commissions → Imports queue for any authorized agent to review.

What if the payment covers multiple bookings? The current import creates one draft per email. If a remittance covers several bookings, it will match to the closest single entry. Future updates will support multi-entry remittance matching.

Is there a limit on how many remittances I can forward? No hard limit for normal agency usage. If you're bulk-importing historical remittances, spread them out over a few minutes rather than forwarding dozens at once.

What happens to imports I dismiss? Dismissed imports are permanently removed from the queue. They don't affect your ledger or any commission entries.