Skip to main content
GullySystem
Financial services

Workflow and Approvals for Stock brokers

Route business requests through defined approval steps.

Platform

Does this function belong in your operation?

Use when requests need explicit approval before money, stock or records change.

A transaction or request requires authorisation.

A pay-out above a set amount waits for the branch head’s yes before accounts release it. Segment activation and bank detail changes follow the same route. Nothing moves until an approver signs off.

Bring the records the workflow depends on.

  • Request types
  • Approval limits
  • Delegation and escalation rules

Outputs to check

  • Request and decision history
  • Pending-approval queue
  • Authorised downstream action record

Follow the workflow and approvals workflow.

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

  1. 1. Define authority

    Set request types, value limits and delegation rules.

  2. 2. Submit the request

    Collect the evidence and proposed transaction details.

  3. 3. Route the decision

    Identify the approver with authority for the current request.

  4. 4. Record the outcome

    Retain approval, rejection or return comments and timestamps.

  5. 5. Release the handoff

    Allow only the authorised downstream action and reapprove material changes.

Who uses the module, and who approves?

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

Owner or partner

Clears the day’s approvals between meetings, and sees what they cleared last week.

Department head

Approves what belongs to their team and nothing beyond it.

Whoever raises it

Knows where the request is standing without ringing anyone.

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.

Approver unavailable

Use the documented delegation rule and retain the acting approver.

Value changes after approval

Return the revised request for the required approval rather than inheriting the old decision.

Request withdrawn

Stop pending actions and preserve the previous decision history.

Can this work independently?

Approval routing can operate as a standalone register, but blocking a transaction requires the transaction system to honour the decision. Role and delegation data identify authority; audit records retain evidence. An approval message alone should not be mistaken for execution of payment or fulfilment.

Systems and records it connects with

  • Purchase orders: Authorised supplier commitments and open line balances.
  • Price lists and schemes: Effective-dated rates and customer eligibility rules.
  • Credit control: Customer limits, current exposure and authorised order releases.
  • Leave and holiday management: Approved absence and branch calendar information.

Configure, test and introduce the workflow.

  • We sit with the owner and department heads. You describe what needs whose approval. A table of rules returns for your correction.
  • Named approvers and their stand-ins are entered. Each person sees what they will receive. Purchase orders, discounts or leave requests are linked to the rules. Test requests are raised for each type.
  • A single department uses the screens for real approvals. Its group chat is closed. Remaining departments follow. Waiting times and reasons for refusal are reviewed with the owner.

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.

  • Unapproved requests cannot take restricted actions.
  • Decisions retain an approver and time.
  • Absent-approver cases follow the agreed rule.
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 workflow and approvals?

Use when requests need explicit approval before money, stock or records change. A transaction or request requires authorisation.

What should we bring to the requirements discussion?

Bring anonymised examples of Request types; Approval limits; Delegation and escalation 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. Route business requests through defined approval steps. Configuration, a connected module or a custom build are evaluated against that gap before a replacement is proposed.

What is outside this module?

An approval workflow records authority; it does not determine whether a transaction is legally or commercially appropriate.

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. Unapproved requests cannot take restricted actions. Use this check when reviewing the first working version.

Talk to us

Discuss workflow and approvals 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