Muse Task HubUnofficial guide

Money · Community report

Build a trade journal from confirmation emails

@borrowed_ideas says Muse built a dashboard that reads their trade confirmation emails and benchmarks each trade against SPY since the trade, replacing a trade journal they had given up keeping by hand in a spreadsheet. No broker or error rate is named, so spot-check a few trades against your statements.

What you can get

What it is

Trade journal and dashboard

A trade journal built from your own confirmation emails, with unreadable rows flagged, and any benchmark comparison labelled as a record rather than advice.

It came back right when

  • Each row traces to a specific confirmation email.
  • Rows that could not be read are listed, not guessed.
  • Totals for a sample month match your broker's statement.
  • No brokerage login or trade was made.

The checks are editorial, not from the source.

Illustration — suggested task flow, not an execution result
  1. Point to the emailsStops for your approval

    Broker, mailbox, folder and start date.

  2. Build the table

    One row per confirmation, each traced to its email.

  3. Reconcile a monthStops for your approval

    Compare against the broker's statement.

  4. Add viewsStops for your approval

    Charts or a benchmark, with the method stated.

Editorial, not from the source

Works when

  • You used to keep a trade log and stopped because of the typing.
  • Your broker emails a confirmation for every trade.
  • You will check the log against a statement before relying on it.

Does not work when

  • You need figures for tax filing. Use your broker's tax documents and an adviser.
  • You want advice on what to buy or sell.
  • Your confirmations arrive only inside the broker's app, not by email.

Build a trade journal from confirmation emails: review template

A record-keeping template. It is not investment, tax or financial advice.
ItemWhat it is based onStatus
[Trades found][Confirmation emails, each linked][Count confirmed]
[Sample month][Broker statement][Matches or differs]
[Benchmark method][Your stated choice][Applied as stated]

The source case

On X, @borrowed_ideas reports building a dashboard with Muse that reads their trade confirmation emails and benchmarks each trade against SPY performance since the trade, then charts the aggregate result weighted by notional value over time, with a view for every single trade. They say they used to keep a trade execution journal in a spreadsheet but gave up because every trade had to be typed in by hand. The post does not say how many trades or which broker were involved, or whether any email was misread. Checked on 2026-09-24, it is an individual report of a personal tool, not investment advice and not evidence of what the reader's records will show.

A public report by someone outside this library. Not independently reproduced here.

From the source

Source excerpt

It goes through my trade confirmation emails and then benchmarks all of my trades against SPY performance since the trade. ... I actually used to maintain such a trade execution journal with a spreadsheet, but gave up due to sheer laziness as I had to manually input my trades.

@borrowed_ideas · Read it at the source · checked

Quoted from the original posts. Not written by this guide, and not a result produced here.

Suggested prompt

Bring Broker name and where confirmations arrive, Start date, Columns you want, Benchmark and method, if any. Acts Reads trade confirmation emails in the mailbox you connect. Builds and updates the journal and any chart you ask for. Does not log into a brokerage, place trades or share your records. Source community report, checked 2026-09-24.

Written by this guide as a starting point, not quoted from the source. Your edits stay in this browser.

Other ways to ask

Editorial rewrites of the brief above, for a different emphasis. Copy them separately.

What you need

Editorial, not from the source

You supply

  • Broker name and where confirmations arrive
  • Start date
  • Columns you want
  • Benchmark and method, if any

Connected

  • Read access to the mailbox holding the confirmations
  • A sheet or dashboard for the output

Approved by you

  • Read-only mailbox access
  • No brokerage login
  • No trading authority of any kind

How to try it

Editorial, not from the source

  1. Find where your broker's trade confirmations arrive and how far back they go.
  2. Agree the columns: date, ticker, buy or sell, quantity, price, fees if shown, and notional value.
  3. Have a sample of rows checked against the emails, and against a broker statement, before trusting the whole log.
  4. If you want a benchmark comparison, name the benchmark and the method, and keep it as a record of past trades.
  5. Keep the mailbox access read-only. Nothing here should touch the brokerage account.

Let the emails do the typing

The report behind this page is about a familiar failure: a trade execution journal kept in a spreadsheet and abandoned because every trade had to be entered by hand. Brokers usually send a confirmation for each trade, and those emails already hold most of what a journal needs. Start by finding where they arrive and how far back they go, then agree the columns before anything is built: date, ticker, buy or sell, quantity, price, any fees shown, and the notional value. Keep the access read-only and limited to the mailbox. The journal does not need a brokerage login, and there is no reason to give one. A plain table that fills itself is the core of the task; charts can come later.

Reconcile before you trust it

Emails are a convenient source, not an authoritative one. A confirmation can be corrected or cancelled by a later email, filed in another folder, or formatted differently after a broker changes templates. Ask for every row to point back to the email it came from, and for any email that could not be read to be listed rather than guessed. Then take one month and compare the journal to your broker's statement: the number of trades, the quantities and the totals. If they match, extend the check to another month. If they do not, fix the rows by hand and ask why they differed. The report does not mention errors either way, which is a reason to check rather than a reason to assume there were none.

Keep the benchmark a description

The author's dashboard compares each trade against SPY since the trade and plots the aggregate over time, weighted by notional value. A comparison like that is a way of describing what happened, and it depends heavily on choices: which benchmark, from which date, with or without dividends, weighted how. Write those choices down and ask for them to be applied as stated. Do not read the result as a measure of skill or a signal about what to do next, and do not use it for tax purposes, where your broker's documents and an adviser are the right sources. This page gives no investment advice. It covers turning emails you already receive into a record you can check.

Limits and confirmation points

Limits to confirm

  • One attributed report. It gives no count of trades, no broker and no note of errors.
  • Confirmation emails can be missing, duplicated or corrected later. Your broker's statements are the record of what happened.
  • A comparison against an index is a description of past trades. It is not a measure of skill and not investment or tax advice.
  • Nothing here authorizes placing, changing or cancelling a trade, or logging into a brokerage account.

Stop and check

Editorial, not from the source

  • Before it starts: confirm which mailbox and which broker's emails to read.
  • After the first pass: check sampled rows against the emails and a statement.
  • Before sharing or relying on it: confirm the benchmark method is the one you chose.

If it goes wrong

Editorial, not from the source

A trade is missing or doubled
Check for corrected or cancelled confirmations and emails filed elsewhere. Reconcile against the broker's statement, which is the record.
Prices or quantities look wrong
Ask for the rows that came from each email to be shown with the email date, and correct them by hand against the statement.
The benchmark figure looks too good or too bad
Ask how it was calculated, over what dates and with what weighting. Treat it as a description, not a verdict on your trading.

Common questions

Can Muse build a trade journal from my emails?

One user reports that it built a dashboard from their trade confirmation emails, including a per-trade view and a comparison against SPY. This directory has not reproduced it.

Does it need my brokerage login?

No. The report describes reading confirmation emails. Keep access to the mailbox, read-only, and nothing else.

How accurate will it be?

Unknown. The report does not mention errors. Check a sample month against your broker's statement before relying on it.

Can I use it for my taxes?

Use your broker's tax documents and an adviser for that. A journal built from emails is a personal record.

Does the SPY comparison tell me if I'm a good investor?

It describes past trades against one benchmark under the method you chose. It is not investment advice or a verdict on skill.

Next

Related to this task

More in Money

  • File a class-action claim A list of settlements you may be eligible for, with deadlines and estimated payouts, and claim forms filled out and submitted only after you approve each one individually.
  • Compare bitcoin-backed loan terms A side-by-side comparison of loan-to-value, interest rate, liquidation threshold and fees across lenders, sourced and dated, left for you or a financial professional to evaluate.
  • Check if you used the best rewards card A nightly or periodic check that flags charges where a different card in your wallet would have earned more rewards, plus a running read on which card credits you haven't used yet.

Every money task

Get recurring task recommendations — ask your own agent to check for relevant updates.