Case study
Fundline
Cash-movement approvals for a brokerage back office, with reports and email
A back-office tool that decides which money may leave or enter a brokerage customer’s account: requests arrive, are checked against the account on file and the sanctions list, are approved by the right desk under rules an admin sets, go to the bank, and leave a trail anyone can read.
Web app for desktop browsers, designed at 1440 wide, with PDF reports and HTML emails
The challenge
Every deposit and withdrawal at a clearing firm needs a check, a decision and proof. Treasury platforms are built for corporate treasury, and clearing services offer the rails without an operator’s approval screen. The back office needed one place where the right person approves the right request, quickly and on the record.
What we did
- Product design
- Approval workflow and rules
- Brand sheet and components
- PDF report and email templates
What changed
- An approval queue where the account-match check is the first thing a reviewer reads, and approve or reject sits on the row.
- Approval rules written as sentences (amount, then the desk that must approve), set by an admin without a developer.
- A four-eyes setting by desk, kept apart from the amount rules.
- An audit trail that reads one request as a story, from created to screened to approved.
- A dashboard per desk, plus emailed digests and PDF reports for the paperwork that follows.
Overview
Fundline is a web app for the cash desk of a brokerage clearing firm. It holds the bank accounts customers may move money to and from, takes deposit and withdrawal requests (ACH, wire and linked-account deposits), routes each one to the right approver, and hands approved money to the bank as a file.
Four desks use it: Admin, Treasury, Margin and Compliance. They see the same screens; what changes is which requests wait for them.
The design file runs from a brand sheet (colours, type, buttons, inputs, icons) to high-fidelity screens for each desk, dialogs for every decision, PDF report templates and notification emails. This case study shows the design; the sample data is invented.
The challenge
Moving a customer’s money is easy to do and expensive to get wrong. A withdrawal to the wrong account, a payment to a sanctioned party, or one person approving their own large transfer: each is a loss or a finding.
Before a request leaves, three questions need answers: is this the account we have on file, is the payee clear of the sanctions list, and has the right desk said yes. Afterwards comes a fourth: can we prove it?
The tool had to answer all four on the screen where the work happens, for desks that clear many requests a day before the bank cut-off.
The landscape
We reviewed seven payment-operations, treasury and clearing products that approve or move money. Every claim links to its source; where a vendor page blocked us, the claim comes from a search summary and says so.
In the matrix, "no" means not shown publicly and "unknown" means we could not verify it. The Fundline column reflects the design file, not a shipped build.
| Feature | Ours | |||||||
|---|---|---|---|---|---|---|---|---|
| Amount-threshold approval rules | Yes | Yes | Yes | Yes | Yes | Yes | Partly | Not known |
| Role-based approvers | Yes | Yes | Yes | Yes | Yes | Yes | Not known | Partly |
| Four eyes, no self-approval | Yes | Yes | Yes | Partly | Not known | Yes | Not known | Not known |
| Account-match check on each request | Yes | Not known | Not known | Partly | Not known | Not known | Not known | Not known |
| Sanctions screening in the flow | Yes | Not known | Not known | Yes | Yes | Not known | Not known | Not known |
| Audit trail | Yes | Yes | Not known | Yes | Partly | Not known | Not known | Yes |
| Bank file or wire status | Yes | Not known | Not known | Yes | Yes | Not known | Partly | Partly |
| Emailed digests and PDF reports | Yes | Not known | Not known | Not known | Partly | Partly | Not known | Partly |
| Built for a brokerage cash desk | Yes | No | No | No | No | No | Yes | Yes |
| No features match this filter. | ||||||||
- Yes
- Partly
- No
- Not known
- Not public
Where they do better
An honest read: these are the places the others are ahead today.
- Rule depth: Modern Treasury combines conditions in AND / OR blocks and makes every reviewer approve again after an edit; Atlar adds tiers, fallback chains and a creator-approval switch.
- Bank reach: Kyriba connects to over 10,000 banks in ISO 20022 and SWIFT formats. Fundline sends to one bank.
- Screening breadth: Kyriba lists several sanctions lists and anomaly detection; the design file shows one sanctions check.
- Self-serve simplicity: Mercury’s owners set an approval rule in settings. Fundline needs an admin role and its own setup screen.
Sources
- Modern Treasury docs, approval rules overview (opens in a new tab)
- Modern Treasury journal, payment approvals (search snippet) (opens in a new tab)
- Atlar docs, approval chains (opens in a new tab)
- Kyriba, payments (opens in a new tab)
- Kyriba payments fact sheet (search snippet) (opens in a new tab)
- Finextra on Kyriba sanctions screening (search snippet) (opens in a new tab)
- HighRadius, payment workflow and approval (opens in a new tab)
- Mercury help, navigating approvals (search snippet) (opens in a new tab)
- Mercury help, separation of duties (search snippet) (opens in a new tab)
- Apex Cash overview (search snippet; now redirects) (opens in a new tab)
- Apex ascend-sdk, ACH transfers (search snippet) (opens in a new tab)
- BNY Pershing, client and account management (opens in a new tab)
What they say, think and feel: The release desk
Out loud, in meetings and messages
- “Does the account match?”
- “Is this one mine or Margin’s?”
What goes unsaid
- One wrong release costs more than a slow afternoon.
- Most requests are routine; a few are not.
Observable behaviour
- Scans the queue for anything not matched.
- Approves from the row and opens only the odd ones.
The emotional undertow
- Pressed before the cut-off.
- Calm when the risky ones stand out.
Pains
- Checks hidden behind a click.
- Decided requests that still show buttons.
Gains
- Match status as the first column.
- Approve and reject on the row, outcomes as chips.
What they say, think and feel: The screener
Out loud, in meetings and messages
- “Who approved this, and on what basis?”
- “Was it screened before it went out?”
What goes unsaid
- The trail is the product an auditor sees.
- Four eyes only works if the tool enforces it.
Observable behaviour
- Reads a request’s events in order.
- Sets which desks need a second approver.
The emotional undertow
- Exposed when evidence is scattered.
- Confident when one row per event tells the story.
Pains
- Reconstructing decisions from email.
- Screening results in another system.
Gains
- An audit trail with created, screened and approved as separate rows.
- A reason recorded with every approval.
Release a withdrawal before the cut-off
Know there is new work and how much.
Feeling today: Frustrated (−1)After the redesign: Neutral (0)
Actions
- Read the digest email of requests waiting.
- See the count on the bell.
Touchpoints
- Digest email
- Notification bell
Pain
New requests are noticed late.
Opportunity
Tell the desk as soon as work lands.
Design answer
A digest email lists the new requests, and the header bell shows how many are unread.
See what is waiting for this desk.
Feeling today: Frustrated (−1)After the redesign: Pleased (+1)
Actions
- Filter the pipeline to the desk.
- Scan the queue cards for anything not matched.
Touchpoints
- Dashboard
- Requests pipeline
- Queue cards
Pain
Every desk’s requests in one undivided list.
Opportunity
Split the pipeline by desk and surface the match first.
Design answer
The dashboard splits today’s requests by desk and outcome, and each queue card leads with its match status and carries approve and reject.
Be sure the money goes where it should.
Feeling today: Very frustrated (−2)After the redesign: Pleased (+1)
Actions
- Open the request.
- Read the account match and the screening result.
Touchpoints
- Approval queue
- Approve dialog
Pain
The checks sit in other systems.
Opportunity
Put both results beside the decision.
Design answer
The queue’s first column is the account match; the approve dialog restates the whole request with the match and the screening result beside it.
Approve or reject, on the record.
Feeling today: Neutral (0)After the redesign: Pleased (+1)
Actions
- Write a reason.
- Approve, or reject from its own dialog.
Touchpoints
- Approve dialog
- Reject dialog
Pain
Decisions without a recorded reason.
Opportunity
Make the reason part of the decision.
Design answer
The approve dialog asks for a reason before Yes, approve, and reject has its own dialog; rules and four eyes send large amounts on to the next desk.
Know the money left.
Feeling today: Frustrated (−1)After the redesign: Pleased (+1)
Actions
- Watch the request move from scheduled to transmitted.
Touchpoints
- Wires transmitted
- Outgoing file email
Pain
No sign of whether the bank got the file.
Opportunity
Show the transmission as a status in words.
Design answer
Wires show Scheduled for transmission, then Transmitted to the bank; a daily email attaches the outgoing file as a PDF.
Answer any question about this request later.
Feeling today: Neutral (0)After the redesign: Delighted (+2)
Actions
- Open the audit trail for the request.
- Export the audit report.
Touchpoints
- Audit trail
- Audit report PDF
Pain
Evidence scattered across tools and inboxes.
Opportunity
One row per event, exportable.
Design answer
The audit trail lists created, screened, approved and auto-approved as separate rows with who acted and why, and exports as a report.
From request to decision
The dashboard splits today’s requests by desk and outcome, shows last week’s deposits against withdrawals, and lists the queue as cards a reviewer can clear in place.
The approval queue leads with the account match; approving opens a dialog that restates the request beside its checks. All screens are rebuilt as live HTML and SVG with sample data.
Dashboard
Requests pipeline
Today- Accepted1,016(70%)
- Pending261(18%)
- Rejected175(12%)
Cash flow
Last week- 2000K
- 1500K
- 1000K
- 500K
- 0K
- Mon20/11
- Tue21/11
- Wed22/11
- Thu23/11
- Fri24/11
Approval queue
20All- Amount
- $48,200
- Name
- Alex Moreno
- Bank
- Harbor Sample Bank
- Account no.
- •••• 4821
- Back-office account
- 2FL-118-204-C
- Amount
- $12,750
- Name
- Priya Raman
- Bank
- First Example Bank
- Account no.
- •••• 0937
- Back-office account
- 2FL-118-377-K
- Amount
- $3,400
- Name
- Jonah Fields
- Bank
- Harbor Sample Bank
- Account no.
- •••• 5520
- Back-office account
- 2FL-118-412-C
- Amount
- $96,010
- Name
- Lena Ortiz
- Bank
- Northgate Demo Bank
- Account no.
- •••• 7316
- Back-office account
- 2FL-118-509-K
- Amount
- $1,250
- Name
- Sam Okafor
- Bank
- First Example Bank
- Account no.
- •••• 2284
- Back-office account
- 2FL-118-633-C
- Amount
- $22,900
- Name
- Mia Chen
- Bank
- Harbor Sample Bank
- Account no.
- •••• 6041
- Back-office account
- 2FL-118-781-C
Fundline · sample data for illustration only
Fundline · sample data for illustration only
Fundline · sample data for illustration only
Approve funds request
Do you want to approve this funds request?
- Amount
- $48,200.00
- Date
- 11/14/2023 09:12:40
- Transaction type
- Deposit to customer account
- Name
- Alex Moreno
- Account no.
- •••• 4821
- Bank
- Harbor Sample Bank
- Routing no.
- •••• 0190
- Address
- 12 Sample Street, Springfield
- Account type
- Checking
- Account matchMatched
- OFAC screeningNo match on the sanctions list
Rules and proof
An admin sets who approves what as a list of sentences, and which desk needs a second approver.
The audit trail keeps one row per event, so a single request reads from created, to screened, to approved.
Needs four-eyes approval from
Fundline · sample data for illustration only
Fundline · sample data for illustration only
A deep navy carries the product: the rail, titles and primary buttons. Sky blue is its partner for quiet states and secondary data; mint marks where you are.
Green and red mean approve and reject, nothing else. Every status pairs its colour with a word, on a soft chip.
The paperwork has its own voice. PDF reports switch to a warm peach so a printed page is never mistaken for the screen.
Brand: colour
Primary. Rail, titles, primary buttons, deposit bars
Rail icons, withdrawal bars, selected filters
Date badges and soft highlights
The current page in the rail
Secondary brand colour
Approve buttons and approved text (read from the frames)
Reject buttons and rejected text (read from the frames)
Tertiary. Export actions
Body text
Table headers and quiet pills
Page background and alternate rows
Messaging
Messaging
Messaging
PDF report headers and totals (read from the frames)
Brand: type
Inter
Everything in the app. Headings bold at 40, 36, 32, 24 and 20; body semibold at 18, 16, 14 and 12; paragraphs regular at 14/22
$48,200.00 · Matched
- 400
- 500
- 600
- 700
Brand: logo notes
- The client’s logo is not shown, because the client is anonymised. The mark on the rebuilt screens is a neutral codename wordmark drawn for this case study, in the product’s navy, sky and mint.
- The original pairs a small mark with a two-tone wordmark; the emails set it in a white header card between two dot-grid patterns.
- Colour and type values come from the design file’s variables; the approve, reject and report colours were read from the rendered frames.
What the file covers
The design file holds a brand sheet and components, high-fidelity screens drawn once per desk, the dialogs for every decision, PDF report templates and notification emails.
The groups below are its sections and the screens and states inside them.
- Colours and messaging states
- Type scale
- Buttons and their states
- Input fields
- Icon sets
- Card shadows
- Banking instructions
- Funds requests
- Post a funding request
- Approval queue
- Wires transmitted
- Automatic transmission
- ACH file transfer
- Approve dialog
- Reject dialog
- Cancel dialog
- View details
- Delete confirmation
- Approval flow setup
- Four eyes by desk
- Audit trail
- Configuration
- Users and roles
- Outgoing file report
- Audit report
- Wide report grids for 10, 13 and 17 columns
- Digest of requests waiting
- Outgoing file email
- Login
- Forgot password
- New password
- Notifications
- Announcements
Reflection
Speed and control usually pull against each other on a cash desk. Here they meet on the row: the check sits beside the button, so the fast path is also the safe one.
Next, these design assumptions need sessions with a real cash desk, and the four-eyes setting needs a sharper definition: whether it asks for a second person on the same desk or a second desk.
The rule table is deliberately simple. If the desk outgrows it, the competitors show where to go next, with combined conditions and approval tiers.