Case study

A finance operations portal

North Ledger · Leeds, UK

We built an operations portal on top of the ledgers and bank feeds already in place: balances, invoice status, cash movement for a chosen period, and role-based access for named people.

Angular.NETSQL ServerAzureBank feeds

Discuss a similar brief

Location: Leeds, UK
Duration: 6–9 months
Industry: Banking & finance
Project type: Web development

About the client

A mid-market finance team in Leeds (controller plus three accountants) ran cash, invoices and bank balances across spreadsheets and a desktop accounts package. Month-end meant exporting CSVs, pasting into workbooks, and chasing overdue invoices from a separate list.

Replacing the accounts package was out of scope. The brief was a morning portal: cash, receivables, payables and a short queue of items that still need a person — reading bank feeds and the ledger they already keep.

Project overview

We built an operations portal on top of the ledgers and bank feeds already in place: balances, invoice status, cash movement for a chosen period, and role-based access for named people.

Angular on the desk, .NET and SQL Server on Azure for aggregation and roles. The portal never posts to the books; the accounts package remains the book of record.

Technologies

Angular.NETSQL ServerAzureBank feeds

Duration

6–9 months

What we shipped

Web development

Page screenshots

1 / 3

Functionality

Cash, receivables, payables and net movement for a chosen period
Outstanding invoices with due dates and overdue filters
Recent transactions tied to named bank accounts
Roles so named people see only what they should
Read-only over the existing ledger; not a second set of books

Solution

The morning overview pulls cash and open invoices from the same sources month-end used to export by hand, with drill-down into line items.
Overdue is a filter on the invoice list the team already recognises — not a surprise report on day 30.
Bank account names and recent transactions sit beside the balance so a figure can be traced without another CSV.
Access is named Azure AD users and roles, not a workbook on a shared drive.

Project results

The controller opens one portal each morning instead of rebuilding a CSV pack.

Overdue invoices sit in the same product as cash and payables.

Bank balances and the ledger tell the same story on screen.

Access is named people; the shared-drive workbook path is gone for this job.

Customer review

“Month-end is no longer a pile of CSVs. Cash, invoices and the bank accounts are in one portal, and access is named people rather than a spreadsheet on a drive.”
Mr. Rupert S., Finance manager, Leeds, UK

Next step