WARNING: Severe Ledger Calculation Flaw on FYERS - 1 Trade, 3 Completely Different P&L Numbers

Hi everyone. I’m sharing a catastrophic backend calculation error I’ve uncovered on the Fyers platform. If you actively trade options and ever mix intraday and carry-forward positions, you need to audit your official Global P&L reports immediately.

Fyers is currently operating a system where your true exchange settlement, your live dashboard P&L, and your official tax P&L report all show completely different numbers. In my case, it turned a legitimate ₹14k profit into a fabricated ₹70k loss on my official ledger.

I’ve escalated this, but Fyers support is actively defending the math. I’d love to hear from other brokers or developers here on how a system’s architecture could be failing this badly.

Here is the exact, clear timeline of my NIFTY 22900 CE trades based on my order books and P&L reports:

1. Date of the First Orders (Initial Entry): Friday, March 27, 2026

  • Morning Scalp: Bought 520 qty at ₹508.38 and Sold 520 qty at ₹513.70. This was a purely intraday trade, completely squared off for a +₹2,766 realized profit.
  • Carry-Forward: Later that afternoon, I bought the initial 260 quantity at ₹462.25 to carry forward over the weekend.

2. Date of the Averaged Orders (Scaling Up): Monday, March 30, 2026

  • I scaled into the position further, executing four additional buy orders of 260 quantity each (at ₹287.17, ₹248.65, ₹220.82, and ₹171.75).
  • Total Open Carry-Forward: 1,300 quantity.
  • True Average Buy Price (FIFO): ₹361,566.40 total capital / 1300 qty = ₹278.13.

3. Date of the Exit Order (Final Square Off) & Dashboard Glitch: Wednesday, April 1, 2026

  • I sold the entire 1,300 quantity position at ₹289.48, closing the swing trade.
  • My True Realized Profit for the swing trade: +₹14,755.00.
  • However, upon exit, my Fyers portfolio dashboard displayed a total realized profit of only +₹6,756.75. The UI was using a flawed “blended average” that aggregated some, but not all, of the closed Friday trades.
  • When I complained about the dashboard discrepancy, Fyers support replied: “Please note that your P&L will not be affected at this moment. Once you close the position, your P&L will be updated accordingly.”

4. The Global P&L Report (Back-End Fabrication): Fyers support lied. When I downloaded my official Global P&L report to verify the final settlement, the +₹6,756.75 dashboard profit disappeared entirely.

Instead, the official Fyers ledger reported a massive realized loss of -₹70,770.18 for this exact contract.

How did they do this? Their Global P&L report fabricated my buy average as ₹343.92.

I reverse-engineered their software’s math: The Fyers backend simply took every single buy order I ever placed for that contract across all dates (including the 520 qty from the fully closed morning scalp, totaling 1,820 qty) and divided the total capital by 1,820. It completely deleted the 520-qty sell order that squared off the intraday leg from the mathematical equation.

By applying a global buy average that ignores paired intraday sell legs, Fyers artificially inflated my buy price by over 60 points and wiped out roughly ₹85,000 of my actual capital on their ledger.

5. The Support Response: When escalated again, Fyers support replied stating that “if you have both carry-forward positions and intraday positions… calculations will be based on a weighted average.” They are blindly defending a system that generates three completely different P&L numbers for the exact same trade and prints fake ₹70k losses on legally binding tax documents.

Questions for the community:

  1. Have any other Fyers users noticed massive discrepancies between their Dashboard P&L and their Global P&L reports when scaling positions?
  2. For the brokers and platform devs in this forum: How can a broker legally generate an end-of-day P&L report that ignores matched intraday legs and blatantly violates exchange FIFO reconciliation?

Please double-check your ledgers, everyone. Fyers’ backend math is fundamentally broken.

AI Summary for Quick Readers:

A user has reported a significant issue with a trading platform’s backend calculation system, causing discrepancies between the live P&L dashboard, global P&L reports, and tax reports. The problem occurs when mixing intraday and carry-forward positions. The system incorrectly calculates profits and losses by applying a flawed weighted average that overlooks intraday sell orders.

As a result, a legitimate ₹14k profit was reported as a ₹70k loss on the official tax report. Despite raising the issue, platform support continues to defend the inaccurate calculation method.

The user is concerned about the potential legal and tax implications and is seeking feedback from other traders or developers about similar issues or proper reconciliation methods.

What the OP Forgot to Clarify:

  1. Impact on Ledger: Has the ₹14k profit been credited and materialized in your actual ledger balance?

( This is the critical point in determining whether the calculation error affects real funds.)

  1. Tax Report Discrepancy: Is the ₹70k loss only appearing as a virtual figure in your tax report, or is it affecting your actual ledger balance?

Mine isn’t the same issue, but I’ve noticed a similar concern. For the same period, my Regular P&L, Tax P&L, and Verified P&L reports at Zerodha show discrepancies of ₹6–7 lakhs.

Zerodha’s explanation is that, for the Verified P&L report, the cost price of transferred Reliance shares has been treated as zero, whereas in the Regular P&L and Tax P&L reports, the cost price has not been treated as zero.

I’m curious to hear what other traders think. Is this the right approach? To me, it appears to create a loophole that could potentially be used to inflate profit figures in the Verified P&L report.

1 Like

I think a table would be a better AI summary:

Date Order Description Qty Buy Price (₹) Sell Price (₹) Realized P/L (₹)
Mar 27 Morning Scalp 520 508.38 513.70 +2,766.40
Mar 27 Swing Entry (Initial) 260 462.25 289.48 -44,920.20
Mar 30 Scaling Order #1 260 287.17 289.48 +600.60
Mar 30 Scaling Order #2 260 248.65 289.48 +10,615.80
Mar 30 Scaling Order #3 260 220.82 289.48 +17,851.60
Mar 30 Scaling Order #4 260 171.75 289.48 +30,609.80
TOTAL 1,820 +17,524.00
1 Like

So What do you think? Who is in the right and who is in the wrong ? Or should we ask the AI to decide?

Broker’s Calculation (As Alleged)

Step 1: Aggregate All Buy Trades (Including Closed Intraday)

Date Type Quantity Price (₹) Value (₹)
Mar 27 Intraday Buy 520 508.38 264,357.60
Mar 27 Carry Buy 260 462.25 120,185.00
Mar 30 Buy 260 287.17 74,664.20
Mar 30 Buy 260 248.65 64,649.00
Mar 30 Buy 260 220.82 57,413.20
Mar 30 Buy 260 171.75 44,655.00
Total 1,820 625,924.00

Step 2: Weighted Average Buy Price

Weighted Average Price = 625,924.00 ÷ 1,820 = ₹343.92


Step 3: Apply Average to Exit Trade

Component Quantity Price (₹) Value (₹)
Sell (Apr 1) 1,300 289.48 376,324.00
Implied Cost 1,300 343.92 447,096.00

Step 4: Final Reported P&L

Metric Value (₹)
Total Sell 376,324.00
Implied Cost 447,096.00
Net P&L -70,772.00

Structural Observation

Metric Quantity
Total Buy Quantity Used 1,820
Total Sell Quantity Used 1,300
Unmatched Quantity 520

This tabulation reflects the broker’s apparent methodology of including all buy trades in the cost basis while excluding the corresponding intraday sell leg during averaging.

There’s no concept of intraday in F&O. FIFO is the most tax compliant way. But even if you want to use weighted average you still need to account for that initial intraday sell. If you add -70k in next FY, you need to add the remaining in this FY i.e., 70k + 14k for the accounts to match.

1 Like

It should probably be present in previous FY Global P/L. Did you check that?

520 quantity will never be part of the carry forward averaging, it was done and dusted in intraday, it will never be part of the carry forward, followed by averaging orders are supposed to be calculated together, 520 will never be part of the averaging because it was never held overnight. I believe I am making sense, wild card entry of the major error is showing 6k profit as 70k loss, which was never booked