-
-
Notifications
You must be signed in to change notification settings - Fork 1
FAQ
Q: My P&L doesn't match what TastyTrade shows. Why?
TastyTrade's native dashboard uses mark-to-market values that include unrealised gains and losses on open positions. TastyMechanics uses cash-flow based P&L — only money that has actually cleared your account is counted. Open share positions are not included until sold. This is intentional and gives a more conservative, auditable number.
Q: Why does the date on a trade show as one day earlier than in TastyTrade?
TastyTrade stores transaction timestamps in UTC. A trade placed at 9pm US Eastern time is stored as 2am the next day in UTC. TastyMechanics uses the UTC date directly. The difference is always exactly one day and is consistent across all trades — it does not affect any calculations.
Q: The campaign premiums for my ticker look wrong. It's including options I sold before I bought the shares.
This should not happen — pre-purchase options are excluded from campaign premiums by design. If you see this, check whether the share purchase date in your CSV is correct. Options sold on the exact same date as the share purchase are classified as pre-campaign (outside window). If this is causing an issue, please open a GitHub issue with your scenario.
Q: My Capture % is over 100% or deeply negative. Is that a bug?
No. Capture % = Net P&L ÷ Premium Received × 100. It can exceed 100% if you received a credit and the option expired worthless but you had also collected additional credits from rolls. It can be deeply negative if you bought back the option for much more than you received — a large loss trade. Both are mathematically correct.
Q: What does "Ann Return %" mean and why is it capped at 500%?
Ann Return % annualises the per-trade return based on capital at risk and days held:
Ann Return % = (Net P&L ÷ Capital Risk) × (365 ÷ Days Held) × 100
A 1-day trade that returns 1% in a day would annualise to 365%. The cap of ±500% prevents extreme single-day trades from dominating charts and averages. The raw calculation is correct — the cap only affects display.
Q: I exported only 90 days of history. Will it work?
Yes, but equity P&L will be wrong for any shares purchased before the export window. If you bought SOFI in January and sold in March but only exported February onwards, the cost basis for that sale will be missing and the FIFO calculation will be incorrect. Always export your full account history.
Q: Can I use this with a paper trading account?
Yes — the CSV format is the same. Just export from your paper trading history.
Q: Does it work with TastyTrade Australia / UK / Canada?
Unknown. The app was built and tested on a US TastyTrade account only. CSV format and field differences for other regions are not known. It may work, it may not. If you try it and it works (or doesn't), open a GitHub issue and let us know.
Q: I have a spin-off and my P&L looks wrong.
Go to the sidebar and enable the zero-cost exclusion toggle for the affected ticker. Shares received at $0 cost (spin-offs, ACATS transfers) have an inflated cost basis that distorts Realized ROR and Capital Efficiency. The toggle excludes those tickers from all P&L metrics.
Q: How do I run this locally instead of on Streamlit Cloud?
See the Getting Started page.
Q: Is my data sent anywhere?
No. All processing happens in your browser session (Streamlit Cloud) or on your local machine. Your CSV is never transmitted to any server other than the Streamlit session running the app. The Streamlit Cloud session is isolated and ephemeral.
Q: I found a bug. How do I report it?
Open an issue on GitHub. Include your TastyTrade account region, a description of the trade or scenario that produces the wrong result, and the expected vs actual values if possible. You do not need to share your full CSV.