How to check F&O Turnover?

Modified on Wed, 12 Jun at 4:19 PM

In this tutorial, we will explain how to calculate turnover in futures and options (F&O) in MProfit.

Here, we will explain a series of transactions within a portfolio and illustrate how to generate a turnover report.

Start by examining the transactions in the portfolio.

On June 3rd, 100 TCS options were purchased at a rate of 150 per option, amounting to 15,000 rupees.

These options were sold on June 6th for 20,000 rupees, resulting in a profit of 5,000 rupees.

Subsequently, another option for Tata Steel was purchased - 100 quantities at a rate of 500 rupees per option, totalling 50,000 rupees. 

On June 11th, this option was sold for 30,000 rupees, resulting in a loss of 20,000 rupees.


To generate the turnover report, follow the steps below:

Step 1: Navigate to the Reports section at the top of the screen.


Step 2: Choose the F&O Turnover option.


Step 3: Select the desired report:

All Instruments, Stock F&O or Other F&O.

For this tutorial, select Stock F&O.


Step 4: Customize the Period from the drop-down menu.


Step 5: Click on Generate Report.


Step 6: Once the report is generated, click on the link to download it in Excel format.

The report will show the sale amount, purchase amount, and realized profit or loss for each transaction.

For instance, for TCS, the sale amount is 20,000, the purchase amount is 15,000, and the realized profit is 5,000.

For Tata Steel, the sale amount is 30,000, the purchase amount is 50,000, and there is a loss of 20,000.

However, it's still counted as a turnover of 20,000.

The total turnover is 25,000 according to income tax rules.

The same calculation applies to future instruments as well.


This is how you can seamlessly calculate turnover in futures and options (F&O) in MProfit!

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article