Synapses · Broker ERP and back office

The books, the branches and the payouts.

The ERP behind the desk: trade files in from every exchange and segment, contract notes, ledgers and registers out, and the branch hierarchy the whole firm is organised into.

It runs today as the internal system of a working brokerage, which is a different claim from a demo — it closes a real settlement day, every day.

  • Every exchange and segment
  • Live internal system
Back officeTrade fileContract notesLedgerPayoutDay closed
Synapses — broker erp and back office

In plain words

What Synapses actually is.

A broking back office is judged on the two hours after the exchange files land, and on the day somebody asks what happened eighteen months ago. Everything else about it is preference. Synapses is built for those two moments: the settlement run that has to finish, and the register that has to survive an inspection.

It is the platform the rest of the catalogue stands on. The client master it holds is the one the app signs clients into, the ledger it writes is the one the IPO desk posts to, and the branch tree it keeps is the one the sub-broker payout is worked out from — so there is nothing between the modules to reconcile.

The demo

Synapses, right here.

/dashboard/synapses-hub · demo data
Synapses
PN
DEMO00101-04-202606-10-2026SearchForce Refresh2026–2027Export

Client: DEMO001 — ARAV TEXTILESBranch: HQ001 (HQ001)POA: No KRA: No

Net debit

₹1,189.32

Net credit

₹2,70,096.20

Ledger balance

₹2,68,906.88

Holdings value

₹0.00

Reconcile
Type:
Trd dateVal dateTypeVoucher no.Ledger codeNarrationDebit (₹)Credit (₹)Balance (₹)
29/09/26NoneBILLCBV2040312NSE_FNOBILL ENTRY FOR FO-F2909202641.502,70,041.50 CR
30/09/2630/09/26JOURNALJVL51207NSE_CASHBEING MTF CHARGES DEBITED FOR DEMO00161.002,69,980.50 CR
01/10/2601/10/26BILLCBV2041106NSE_CASHBILL ENTRY FOR M-20261861.212,69,979.29 CR
01/10/2601/10/26JOURNALJVJ208441NSE_CASHFUND TRANSFER FROM NSECASH TO MTF15.902,69,963.39 CR
01/10/2601/10/26JOURNALJVJ208442MTFFUND TRANSFER FROM NSECASH TO MTF15.902,69,979.29 CR
01/10/26NoneBILLCBV2041275NSE_FNOBILL ENTRY FOR FO-F0110202636.192,69,943.10 CR
01/10/2601/10/26JOURNALJVL51330NSE_CASHBEING MTF CHARGES DEBITED FOR DEMO00111.002,69,932.10 CR
02/10/2602/10/26JOURNALJVL51424NSE_CASHBEING MTF CHARGES DEBITED FOR DEMO00111.002,69,921.10 CR
03/10/2603/10/26JOURNALJVL51518NSE_CASHBEING MTF CHARGES DEBITED FOR DEMO00111.002,69,910.10 CR
04/10/2604/10/26JOURNALJVL51612NSE_CASHBEING MTF CHARGES DEBITED FOR DEMO00111.002,69,899.10 CR
05/10/2605/10/26BILLCBV2041526NSE_CASHBILL ENTRY FOR M-2026187982.222,68,916.88 CR
05/10/2605/10/26JOURNALJVJ208895MTFFUND TRANSFER FROM MTF TO NSECASH38.802,68,878.08 CR
05/10/2605/10/26JOURNALJVJ208896NSE_CASHFUND TRANSFER FROM MTF TO NSECASH38.802,68,916.88 CR
05/10/2605/10/26JOURNALJVL52173NSE_CASHBEING MTF CHARGES DEBITED FOR DEMO00110.002,68,906.88 CR
Grand Total1,189.322,70,096.202,68,906.88 CR

Sample data for a made-up client. Filter by segment or type, or open a menu above.

What you get

Four things it does, and what is behind each.

Every line below names something that can be shown in a walkthrough. If one of them cannot be, we would rather you found out in the hour than after the signature.

  • Files in, notes out

    Trade files from every exchange and segment, with brokerage, STT, stamp duty and GST computed to the rule and the working shown for an inspection.

    • Every exchange and segment
    • Statutory charges to the rule
    • The working kept
  • Ledgers and registers

    The client ledger, the registers an inspection asks for, and the ones the desk reaches for at four o’clock — the same data, two audiences.

    • Client and branch ledgers
    • Statutory registers
    • In-built report writer
  • Payouts that close

    The payout run, the bank file behind it and the obligation it settles against — worked as one pass rather than three spreadsheets and a phone call.

    • Payout run
    • Bank file generation
    • Settled against obligation
  • Branches and roles

    Head office, branch and sub-broker as a hierarchy with what each can see and do scoped to it — because most back-office accidents are a permissions problem.

    • Branch hierarchy
    • Role-scoped access
    • Per-branch books

Common questions

The ones that come up on the first call.

If yours is not here, it is a better use of an hour than a slide deck — bring it to a walkthrough.

Can we run it alongside our current back office?

For a period, yes — and we would insist on it. A settlement system that has not been run in parallel against the one it replaces has not been tested, it has only been installed.

Is it really running somewhere?

Yes. It is the internal system of ATS Share Brokers and closes that firm’s settlement day. Ask at the walkthrough and you will be shown the working system rather than a sandbox with sample data in it.

The next step

See Synapses on your own books.

Tell us how this part of your firm runs today and what you would want it to stop doing. We will walk you through the same screens your team would work in.

Or call +91 76765 83344