Case study · Banking & Fintech

Bank statement analyser for lenders

Affordability assessment became a review of a structured summary rather than a manual read of a PDF, and each decision carries the transaction-level trail an auditor asks for.

All case studies

Challenge

Credit teams were reading PDF bank statements by hand to assess affordability. Every lender's statement format differs, the work is slow and inconsistent between assessors, and the decision has to be explainable to a regulator afterwards.

Approach

We built an analyser that parses statements from any layout, classifies each transaction into income, committed spend and discretionary categories, and surfaces the patterns lenders actually underwrite against: salary regularity, existing obligations, returned payments and month-end position. Every derived figure links back to the transactions it came from, so an assessor can audit the number rather than accept it.

Outcome
Affordability assessment became a review of a structured summary rather than a manual read of a PDF, and each decision carries the transaction-level trail an auditor asks for.

More work

Related case studies

Leads management software

Leads management software with predictive scoring

Challenge: A lending team was working its pipeline in submission order. High-intent applicants waited behind enquiries that were never going to convert, and the sales team's own sense of which was which had never been tested against the outcomes.
Approach: We built the leads platform covering capture, routing, activity tracking and reporting, then layered a scoring model trained on historic conversion data on top. The queue is now ordered by likelihood to convert, with the reasons for each score visible so the team can disagree with it and have that disagreement feed back into training.

27%

improvement

lift in qualified-lead conversion

Next.js
Python
scikit-learn
MLflow
AWS
Docker

Outcome

The pipeline reordered itself around intent rather than arrival time, and reps stopped spending their first hour deciding who to call.

Sector: Banking & Fintech

Read the case study

E-commerce application

E-commerce application with demand-aware merchandising

Challenge: A fast-moving consumer goods business was running promotions on instinct. Best sellers went out of stock mid-campaign while slower lines were discounted into a loss, and nobody could say which decision had caused which result.
Approach: We built the storefront and order platform, then wired a demand model into the merchandising layer. Sales, stock position and campaign calendar feed a forecast that ranks what to surface and flags lines heading for a stockout before the promotion goes live.

32%

reduction

fewer mid-campaign stockouts

Next.js
Python
Databricks
PostgreSQL
AWS
Kubernetes

Outcome

Merchandising decisions moved from a weekly meeting to a daily ranked list, and the stockouts that used to end campaigns early became a pre-campaign warning instead of a post-mortem.

Sector: FMCG

Read the case study

Your problem next

Does this look like your situation?

Tell us which part of this case study sounds familiar. Starting from a problem we have already solved is the fastest call we have.

Book a consultation hello@post-ql.com

We reply to every enquiry within one business day.

Approach