Menu
The portal now compiles and sends those reports on schedule, returning 20 hours each week to the team.
A regulated payments company was running its whole operation — onboarding business customers, tracking every transaction, and reporting on all of it — across disconnected tools and manual spreadsheets. It needed one portal to run the business from.
I built roughly 90% of that portal's frontend. Customers get onboarded in bulk instead of one form at a time, and every account sits in one place.
The money — cash in, cash out, collections, transfers — is watched live instead of pieced together after the fact.
The biggest win was reporting. Two people used to lose around 20 hours every week to reporting alone — 15 to 20 recurring weekly and monthly reports, every one built by hand.
Pulling numbers from thousands of daily transactions, writing Excel formulas, and formatting each file was the manual grind. Now the portal compiles and sends those same reports on schedule, with nobody touching a spreadsheet.
Confidentiality note: Client and company names have been changed or omitted for confidentiality. The work, my role, and project scope are real.
Two people once spent about 20 hours a week hand-building 15–20 weekly and monthly reports — now the portal compiles and sends them on its own
Cash-in, cash-out, collections, and P2P watched live — not reconciled after the fact
Nearly the entire web portal frontend, designed and delivered end to end
Every one of the 15–20 recurring weekly and monthly reports now compiles and sends itself
Ledgers, subledgers, and multi-party transactions had to become screens non-specialist staff could operate confidently.
TypeScript with Redux Toolkit state management and an Ant Design system, structured in feature modules so the portal could keep growing.
Live transaction streams across four payment flows — anywhere from 1,000 to 10,000 a day — needed one always-current view without overwhelming the interface.
One real-time view across cash-in, cash-out, collections, and P2P — paired with streamlined single and bulk user onboarding.
Large financial tables had to export to polished PDF and Excel files client-side without freezing the portal.
On-demand and scheduled PDF (jsPDF + AutoTable) and Excel (XLSX) reports that generate and deliver themselves — turning hours of manual compilation into a background job.
Business customers needed to bring large user bases onto the platform — one manual form at a time would never keep up.
Role-based access, company account management, and searchable transaction histories with statuses — plus settlement and reconciliation views in a responsive interface tuned for large datasets.
The portal is where our teams run the business now — onboarding, ledgers, and live transaction views in one place. Muhammad understood the business side, not just the specs.
Client identity is confidential. This summary reflects verbal feedback shared with Muhammad and the project team.
Share what you are building or improving, and I'll help you identify a practical next step.
No comments yet. Be the first to share your thoughts.
Get insights on web development and building products that ship.