Glob Payment

Menu Structure

Companion to the scope proposal

Menu structure —
both portals

Every item, fully expanded, nothing collapsed. The nav tree is where scope becomes visible: if a capability isn't in one of these two trees, we're not building it.

Legend

P1Phase 1 — first client live
P2Phase 2 — collections
P3Phase 3 — scale
4work count
2needs attention

§01 — Side by side

Customer portal vs backoffice

Customer portal

app.weglob.net

Glob
Overview P1
Dashboard
Action centre3
Banking calendar
Accounts P1
Balances
Account detail
Transactions
Send money P1
New payment
Bulk upload
Approvals2
Payment tracking
Scheduled & recurringP3
Receive money P2
Virtual accounts
Payment links
Incoming payments
Settlement
Convert P1
Quote & convert
Conversion history
Beneficiaries P1
Directory
Pending approval1
Statements P1
Period statements
Export centre
Compliance P1
Documents
Requests for information1
Settings P1
Team & roles
Approval policy
Security
Company profile
API keys & webhooksP3

Acme Trading Ltd

GLB-2847-001 · Maker

9 modules · 28 screens. Role shown in the footer card because Maker and Checker see different things — a user who forgets which hat they're wearing files a support ticket.

Backoffice

ops.weglob.net

Glob
OPS

Work

My queue 12
Assigned to me12
Watching
Team workload

Clients

Client management P1
Client directory
KYB onboarding5
Client profile
Periodic review8
View as client

Risk

Compliance P1
Screening queue7
Transaction review4
Cases3
Rules configuration
Regulatory reporting

Money

Payment operations P1
Payment explorer
Exception queue6
Unmatched payins2P2
Repair & resubmit
Manual adjustment
Treasury & recon P1
Pooled position
Safeguarding check!
Partner reconciliation
Break resolution3
Liquidity monitor
FX position
Pricing & billing P2
Fee schedules
FX margin config
Revenue reporting

Platform

Administration P1
Staff & roles
Audit log
Corridor & partner config
Partner health1

J. Tan

Compliance · Ops

7 modules · 31 screens, in 5 groups. Grouped by function (Work / Clients / Risk / Money / Platform) because staff are specialists — a compliance officer never opens Treasury. Counts are live work, not decoration.

§02 — Naming decisions

Choices worth arguing about

Customer · structure

Send / Receive, not product names

Epay groups by product line (汇款 / Epay账户 / 多币种账户), which mirrors their internal org. Clients think in directions of money. The counter-argument: if Glob's clients already use Epay, familiarity may beat logic.

Customer · structure

Convert is top-level, not under Accounts

FX is a revenue line and a frequent standalone task, not an account setting. Burying it costs conversions — literally.

Customer · structure

Approvals live under Send money

Considered a top-level "Approvals" item. Rejected: a Checker's job is a mode of sending, not a separate destination. The Action centre on the dashboard carries the urgency instead.

Backoffice · structure

"My queue" sits above everything

Staff don't browse — they work a list. If an ops person has to remember which of six modules holds their next task, the tool is fighting them. Everything else is reference; this is the job.

Backoffice · structure

Grouped by function, not by client

Work / Clients / Risk / Money / Platform. A compliance officer never opens Treasury; a treasury analyst never clears a sanctions hit. Grouping by client would force everyone through everything.

Backoffice · risk

Counts are load-bearing, not decoration

Every red badge is money or a regulatory clock. The ! on Safeguarding check is deliberate — a break between client balances and the pooled account is a reportable event, and it should never be a number you can scroll past.

§03 — vs Epay

What we kept, moved, and cut

Epay item Glob equivalent Decision
首页 Home Overview → Dashboard KEPT
汇款 Remittance Send money RENAMED
Epay账户 / 多币种账户 Accounts Accounts — merged into one MERGED
兑换 Exchange Convert — promoted to top level PROMOTED
收款人管理 Beneficiaries Beneficiaries — + approval step KEPT+
账户明细 Statements Statements KEPT
虚拟资产 Virtual assets — CUT doubles compliance surface
开发者 Developer Settings → API keys & webhooks DEFERRED P3
— not in Epay Receive money NEW Glob pillar 03 — collections
— not in Epay Compliance NEW RFI + document vault
— not in Epay Settings → Approval policy NEW maker–checker thresholds

The one Epay item I'd argue hardest to keep: the 节假日 holidays panel. It looks like filler on a dashboard, but it exists because cross-border value dates die on banking calendars — and a client who doesn't know Thursday is a holiday in the destination country blames you for the delay. It's in our Overview group as Banking calendar.