For Indian F&O proprietary desks

Your desk’s P&L, to the rupee. Every evening.

MTM Desk turns an F&O desk's daily terminal exports into a book it can read, reconcile and bill from: dealer-wise P&L, open positions valued at exchange settlement prices, day-wise interest on deposit, and a monthly invoice as a PDF.

Built to agree with the terminal’s own Clientwise Net Position report. On the reference window it reconciled exactly — difference ₹ 0.00.

Book a demo See how it works
₹ 0.00
Difference against the reference terminal report
2
Files uploaded a day — that is the whole daily routine
12
Screens, from the P&L console to the month’s invoice
4×
Closing prices re-fetched each evening, so mornings are priced
The evening as it stands

The terminal exports the day. Then the actual work starts.

A desk runs several dealers under one or more client entities. Five things go wrong between the close and the invoice, and every one of them is quiet.

  1. The numbers live in spreadsheetsEvery month a workbook is rebuilt by hand, and every month it has to be trusted without being checked.
  2. Closing prices are guessed atA position export carries a market price column with no timestamp — a mid-session snapshot used as if it were a settlement price — and the P&L drifts.
  3. Charges are approximatedA desk-wide rate on a desk-wide turnover is close, but it is not what any individual dealer actually owes.
  4. Interest is a single figureThe deposit funding a dealer’s margin changes during the month, and one flat number quietly absorbs the difference.
  5. And the invoice has to tie outThe client sees the terminal’s own report. If your bill disagrees with it, the conversation is about the spreadsheet rather than the trading.

Because the client sees the terminal’s own report — and if your bill disagrees with it, the conversation is about the spreadsheet rather than the trading. MTM Desk exists to end that conversation.

How it works

Two files a day. One book that agrees with the exchange.

Nothing changes on the desk

Your dealers trade exactly as they do today. The terminal produces the same export it already produces, and someone drops it in. There is no integration in your trading path and no API key to ask the broker for.

Every mark comes from the exchange

The official settlement data is pulled from the NSE and BSE archives and applied per contract, per day. Never from a pasted sheet, because a position export carries no timestamp and its price is a mid-session snapshot rather than a settlement figure.

And the invoice ties out

Charges off each dealer’s own slab, interest off a dated deposit ledger, and a monthly bill whose printed lines add up to its printed total. On the reference window it matched the terminal’s own report exactly.

What you get

A console that answers back

Upload the day’s file and every screen is live: per dealer, per scrip, per day, per underlying, per expiry. One filter bar drives all of them.

All 12 screens

P&L Console

A KPI strip across the top — gross mark-to-market, realised, open, turnover, charges — then a day-wise summary, an underlying-wise summary, and an intraday profile showing when in the session the money was actually made.

Dealer-wise Performance

One row per dealer: realised, open, mark-to-market, turnover and charges, alongside that dealer’s own funding terms, charge slab and rate card.

Open Positions

Per dealer and per scrip: lot size, net lots, side, entry price, the current mark, value, open P&L, last traded, and whether the contract has expired. One toggle switches between live positions and settled ones.

Invoice

The monthly bill on screen, with charge, software and interest each switchable on or off, so you can see what the client is being billed and what they are not. One click renders it to a PDF, with the rupee glyph, ready to send.

Interest & Margin

Not a single number. Each entry says how much was on deposit from which day, interest accrues day-wise, and the window is broken into segments at every deposit change and every month boundary.

Data Ingest

Drop the day’s trade export in, name the session date, done. The screen lists every past run, lets you download the original file back, and delete one.

Why it ties out

Most systems get to approximately right and stop.

Getting to the rupee took three rules that are not obvious. They are the reason this console agrees with the terminal instead of nearly agreeing with it.

  1. Priced from the exchange, not the terminalNever from an uploaded sheet. The terminal’s position export carries a market price column but no timestamp, so a mid-session export cannot be told apart from an end-of-day one, and its price is an unpublished intraday snapshot rather than a settlement figure. Using it is how a book drifts.
  2. Expiry day is settled, not guessedOn its own expiry day an option is valued at what it settled for — zero if it is out of the money — not at the last price it happened to print at. Valuing one expiring out-of-the-money contract at its last trade put a four-figure error into the month.
  3. A window carries its positions inA dealer long 500 lots on the 28th does not have those fills counted into a window that starts on the 29th. But the position is still there, and its P&L inside the window has to be measured from the price it was carried in at — the previous close — not from what was originally paid for it.
The whole reconciliation story
Where the data comes from

Two sources, and one of them is optional

NSE and BSE Required

The authoritative source for every closing price in the system. Contract-level settlement data taken directly from the exchange archives, parsed, and cached once the day is final. Settlement price, closing price and underlying price, per contract, per day.

Angel One SmartAPI Optional

Adds a live traded price during market hours. Honestly scoped: it is a live feed, not a source of truth. Its instrument list carries only contracts listed today, so expired series cannot be resolved at all, and what it returns is a traded close rather than a settlement price. What it supplies is stored as a placeholder a real settlement price may overwrite without asking. Leave it unconfigured and everything else is unaffected.

Your terminal, by its own exports No install

Not a network integration, and deliberately so. The desk exports the two files it already exports and uploads them. Both modern and pre-2007 Excel are accepted and converted in memory, because they tend to arrive on alternating days.

Built for a desk, not a demo

The parts you only notice when they are missing

Access that holds, uploads that are treated as hostile, tables that open a year of history as fast as a day, and a server that is yours.

  • Built to be locked down

    Signed sessions with a configurable lifetime, one tenancy check every book request passes through, and an audit log recording who uploaded, replaced, granted and revoked what.

  • Uploads are treated as hostile

    Size caps, file-signature checks, macro-enabled workbooks refused, and duplicate detection by hash. A workbook holding two genuinely different books is refused with the dealer codes in each named, because picking one would be a guess — and a wrong guess is a whole session of P&L on another client’s book.

  • Sized for real history

    Every long table is paged on the server, and every total is computed over the whole filter regardless of what any page shows. It has been driven against real multi-month books, not a demo week.

  • Your data, your server

    One server, yours. Your database, your uploads. Nothing is sent anywhere except the public exchange archives.

Questions

The ones desks ask first

All 13 answers
Is this back-office software for an F&O desk?

Yes, in the sense a desk usually means: it is the system that takes the day’s futures and options trades and turns them into a position book, a dealer-wise P&L and a bill. It covers trade ingestion, mark-to-market against exchange settlement prices, net and open positions, interest on a dated deposit ledger, and monthly invoicing. It is not an order management system or a trading terminal, it does not place orders, and it is not an accounting package — it produces the numbers your accountant bills from, not the books of account.

Do we have to change how our dealers trade?

No. Nothing changes on the terminal or in the trading path. The desk exports the same files it exports today and someone uploads them.

How long does the daily routine take?

Upload one file and name the session date. Under a minute. The closing prices arrive on their own, including overnight.

What if someone uploads the wrong file, or the same file twice?

A re-upload supersedes the previous run for that session rather than adding to it, so the day’s P&L is never counted twice. The audit log names who replaced what, and the original file can be downloaded back at any time.

What if the exchange has not published the day’s data yet?

That day is recorded as a gap rather than filled with a guess. The overnight job retries four times each evening, and the day resolves once the file appears.

Can one login handle two branches?

Yes — that is exactly what an edit-level book grant is for. One login, both books, chosen in the book selector, instead of two sets of credentials or an admin account handed to someone who should not have the desk.

Where does the data live?

On your server, in your database. Nothing leaves it except requests to the public exchange archives.

What does it cost?

Licensing is quoted per desk rather than listed, because it depends on how many books and dealers you run and how it is deployed. Tell us the shape of the desk and we will send a figure.

Stop rebuilding the workbook every month.

See MTM Desk against your own files. Send us one session’s export and we will show you the book it produces.

Book a demo Or email us directly
Chat on WhatsApp