Skip to main content
GullySystem
Financial services

Document Management for Stock brokers

Store business papers with their owners, versions and renewal dates.

Human Resources

Does this function belong in your operation?

Use when business documents are scattered across folders or inboxes.

A document arrives, changes or approaches expiry.

Signed account opening forms, KYC proofs, cancelled cheques and nominee papers are filed against the client code. Expired address proofs surface before a modification request stalls. Scanned originals stay one click from the dealer.

Bring the records the workflow depends on.

  • Document types
  • Access groups
  • Files and renewal dates

Outputs to check

  • Searchable document register
  • Version and access history
  • Renewal action list

Follow the document management workflow.

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

  1. 1. Register the document

    Assign its owner, type, business reference and relevant dates.

  2. 2. Check the file

    Confirm readability and whether it is a draft, signed copy or replacement.

  3. 3. Set access

    Apply the approved audience before wider sharing.

  4. 4. Issue a version

    Retain earlier copies and identify the version currently in use.

  5. 5. Review or retire

    Record renewal, replacement or authorised archival without losing required history.

Who uses the module, and who approves?

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

Owner

Reviews important agreements and authorises access, renewal or retention decisions assigned to management.

Accounts assistant

Pulls the registration certificate or the insurance policy the moment a bank or an auditor asks.

Administration in-charge

Watches the renewal list and starts the paperwork with weeks to spare.

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.

Duplicate upload

Compare the reference and version before retaining a second copy.

Expired document

Keep the old file as history while showing that it is no longer current.

Access request

Require the document owner to approve wider visibility rather than forwarding a restricted file.

Can this work independently?

This can operate as a controlled document library without accounting or HR modules. Links to contracts, suppliers or employees attach files to business records; reminders require the agreed notification channel and recipient rules.

Systems and records it connects with

  • Contract management: Operative agreement terms, amendments and obligation dates.
  • Vendor management: Approved supplier identities, terms and sensitive-change controls.
  • HR document management: Restricted employee documents and completeness status.
  • Notifications: Approved event messages and delivery or failure status.

Configure, test and introduce the workflow.

  • Start with an inventory. You tell us the kinds of papers and where they sit now, and we return folders by type and the dates that matter.
  • The owner says who may open which type. You get a role screen to check. Hand over a sample. A trial import of your scans and files comes back with fields filled and gaps marked.
  • Whoever scans and uploads practises naming, dates and linking. That group is trained before the rest.

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.

  • Documents are searchable by reference.
  • Restricted files remain protected.
  • Earlier versions remain identifiable.
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 document management?

Use when business documents are scattered across folders or inboxes. A document arrives, changes or approaches expiry.

What should we bring to the requirements discussion?

Bring anonymised examples of Document types; Access groups; Files and renewal dates. 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. Store business papers with their owners, versions and renewal dates. Configuration, a connected module or a custom build are evaluated against that gap before a replacement is proposed.

What is outside this module?

Storage does not establish legal validity or provide legal review.

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. Documents are searchable by reference. Use this check when reviewing the first working version.

Talk to us

Discuss document management 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