Skip to main content
GullySystem
Financial services

Bank Reconciliation for Stock brokers

Match bank statement entries with the ledger.

Finance & Accounting

Does this function belong in your operation?

Use when bank activity needs checking against the books.

A statement becomes available for a period.

Choose a transaction associated with “New demat and trading account opening” that requires this accounting function. Trace its supporting documents through review and posting with your finance team.

Bring the records the workflow depends on.

  • Bank transactions
  • Ledger entries
  • Matching rules

Outputs to check

  • Matched transaction register
  • Unmatched and disputed entry list
  • Reconciled account statement

Follow the bank reconciliation workflow.

Use this sequence to compare your current process with the proposed module. Agree the owner, permission and exception at each step.

  1. 1. Load the statement

    Check the account, period and opening balance.

  2. 2. Load ledger entries

    Use the corresponding books and retain source references.

  3. 3. Propose matches

    Compare amounts, dates and references, including grouped payments.

  4. 4. Resolve exceptions

    Review charges, reversals and unidentified entries before approved adjustment.

  5. 5. Close the reconciliation

    Verify ending balances and retain any unresolved differences explicitly.

Who uses the module, and who approves?

Keep responsibilities distinct even when one person holds more than one role.

Accounts assistant

Runs the match, clears the easy lines, and leaves the questions for somebody who knows the customers.

Your accountant or auditor

Opens the unmatched list at closing and sees the reason written against each entry.

Owner

Sees the real cash position, without counting a cheque from a customer who has stopped answering.

Decide how exceptions are handled.

These business rules belong in configuration and testing. A normal transaction alone does not demonstrate that the workflow is ready.

Bank charge missing in books

Prepare an adjustment for accounting approval before completing the match.

One payment covers several entries

Record the allocation and verify that the combined amount agrees.

Reversed bank transaction

Unwind the earlier match with history intact and review the affected ledger entry.

Can this work independently?

Reconciliation can use exported statements and ledger files. Receipt, expense and accounting links reduce re-entry but are not required for a controlled import. Approved adjustments must be posted in the accounting process; matching alone does not change the bank account.

Systems and records it connects with

  • Receipts management: Recorded customer payments and invoice allocations.
  • Expense tracking: Approved cost entries, evidence and payment references.
  • Payment gateway settlements: Provider transaction references, fees and settled amounts.
  • Finance and accounting reporting: Ledger-based period totals and reconciliation outputs.

Configure, test and introduce the workflow.

  • List each account and the format its statement arrives in. A note comes back. It names the accounts to set up and the import route for each.
  • Provide a closed-period bank statement and its ledger. Test ordinary matches, bank charges, combined payments and reversals. The accountant checks matched entries, unresolved differences and the ending reconciliation before approving the rules.
  • The accounts assistant and the accountant sit down with their own data. Questions are logged and answered in writing. The next statement is imported on arrival. The close is reviewed together, and rules are adjusted from what the team found.

Check the result before rollout.

Apply these checks to a sample from the agreed workflow, then repeat with an exception. Keep the expected result beside the test record.

  • Opening and closing balances reconcile.
  • Transactions are not matched twice.
  • Unresolved differences remain visible.
Stock brokers

How the business operates.

Order routing, margin blocks and risk checks run on the licensed terminal from your main broker or the exchange, and they should stay there. Your branch still needs its own books.

Account opening tracker

Follow each application from form received to client code issued, stage by stage. If a signature, cancelled cheque or nominee page is absent, the tracker names the gap and prompts the client for it. Stuck files stand out.

Re-KYC and modification requests

Track re-KYC, bank mandate and nominee changes and segment activations per client code, with the form and its stage kept against each one. A lapsed record is listed before the main broker freezes the code.

See the full industry workflow, reports and implementation plan →

The records that hold the operation together.

  • Enquiries and prospects. Log every prospect with its source, the dealer who owns it and the next call date. Introducer referrals and walk-ins sit in a single list, and conversions to opened accounts are counted by source.
  • Account opening tracker. Follow each application from form received to client code issued. The document list changes with the client type. A missing signature page or proof of address is named on the file, so the back office chases the right paper.
  • Client master and linked accounts. Hold one record per client with the client code, bank details, nominees, linked family accounts, dealer and introducer. A query never starts with a search through three workbooks. The dealer opens the record and answers.
  • KYC papers and expiry dates. File identity proofs, address proofs and signed forms against the client. Expiry and review dates sit beside each paper, with the oldest dates first. The back office works down the list each morning.

Operational bottlenecks to check

Account opening files get stuck

A missing signature beside the nominee declaration stalls activation for a week, and by the time the courier returns the corrected form the prospect has already installed a discount broker’s app. Lost for good.

Dormant clients drift away

A client who bought index options every Thursday goes silent in October, and nobody notices until a closure request or a transfer-out instruction lands in January. One phone call earlier would have cost nothing. The holdings walk.

How work flows across this business

This module sits within a wider operating process. Use the sequence to identify the other teams and records affected by a change.

  1. 1. Prospect

    Walk-ins, introducers and seminars each open an enquiry that carries its source and the dealer who owns it. A follow-up date is fixed, and the outcome is kept whether or not the person opens an account. Nothing is forgotten.

  2. 2. Application

    The documents your clearing broker asks for are listed for that client type, such as individual, joint or corporate. Papers are ticked off as they arrive. A missing page is named on the file, and the stage moves from received to checked to sent.

  3. 3. Activation

    The clearing broker returns the client code, and the system holds it against the client, the dealer and the introducer. The welcome message goes out. The first review date is set that same day.

  4. 4. Servicing

    Ledger, payout, contract note and login queries become numbered requests with a named owner. Dealers answer from the same record. The days taken to close each request are kept for the compliance officer.

  5. 5. Monitoring

    Morning trade and turnover files are loaded, and clients trading below their own usual pattern appear on a call list. Review dates coming due are shown alongside. The dealer calls the biggest balances first.

  6. 6. Month end

    The sharing statement is loaded and compared with the share expected by client code, slab and segment. Gaps are listed with a reason. The payout to every introducer is then drawn from the agreed terms.

Industry reports to connect with

  • Applications by stage, with the oldest waiting file and the document it lacks
  • Review and update dates falling due, by dealer and client type
  • Dormant client codes ranked by securities and ledger balance held
  • Brokerage by dealer, introducer, segment and month

Questions before implementation.

When should stock brokers consider bank reconciliation?

Use when bank activity needs checking against the books. A statement becomes available for a period.

What should we bring to the requirements discussion?

Bring anonymised examples of Bank transactions; Ledger entries; Matching rules. Show who creates, checks and changes each record. Use only records from an activity that meets the suitability conditions above.

Does this replace our existing business software?

The starting point is your current system and the gap you need to close. Match bank statement entries with the ledger. Configuration, a connected module or a custom build are evaluated against that gap before a replacement is proposed.

What is outside this module?

The module does not authorise payments or decide accounting adjustments.

How are scope, price and rollout decided?

The proposal follows a review of your records, user roles, branches and existing software. Data migration, connections, training and support are scoped separately where needed. Opening and closing balances reconcile. Use this check when reviewing the first working version.

Talk to us

Discuss bank reconciliation for your business.

Tell us which workflow needs attention and which systems your team uses. The next step is a requirements discussion and a written scope.

What happens after you share your requirements

  1. We review your brief and the systems you already use.
  2. We clarify the workflow, missing information and the work to consider first.
  3. The proposed scope sets out the deliverables, responsibilities and dependencies.
  4. Review the scope and commercial terms before deciding whether to proceed.

Start with your requirements

Describe your current process, the people involved and the change you need. Start with the details you know; we can clarify the rest together.

Share your requirements