Skip to content
← All case studies

AI Fintech · Private build · 3 min read

Ledgerline

A bilingual finance workspace designed to distinguish actual cash, expected cash, and source-system records.

603 tests passed in a dated financial-control verification

01

Project overview

Financial reports that distinguish actual cash from expected cash

Services: AI Fintech ; AI Workflow Automation ; AI ERP & CRM
Delivery: Bilingual finance workspace with accounting integrations and AI-assisted review. Portfolio alias.

02

Project Snapshot

FigureWhat it represents
14 findingsFinancial-control issues addressed in the July 25 verification
603 tests in 122 filesPassing suite recorded by that verification
2 languagesArabic and English
3 user rolesOwner, administrator, and viewer in the documented product scope

These are engineering and product figures. The verification used demonstration data, not a client's audited financial statements.

03

The Problem

Ledgerline brings accounting, bank, and imported spreadsheet records into one finance workspace. The difficult part is deciding what each number represents before adding it to a report.

An invoice amount can include VAT. A bank movement can duplicate the payment already recorded by an accounting system. An expected customer payment belongs in a forecast, not in actual revenue. Different currencies cannot be added as if they were the same unit.

These distinctions became the focus of a financial-control review covering dashboards, cash visibility, reconciliation, duplicate handling, VAT, Zakat, and consolidated reporting.

04

What We Delivered

The product connects Qoyod, Zoho, Lean banking data, and file imports to a canonical ledger. Users review transactions, mappings, duplicate candidates, and bank-to-books matches.

AI assists with account mapping, bank classification, and review tasks. It works from transaction descriptions, merchant context, categories, and approved tenant history. Dedicated calculation modules produce cash, cost, tax-estimate, and group views.

The remediation introduced explicit actual-versus-forecast treatment, VAT-exclusive P&L values, reporting-currency rules, and one-to-one reconciliation. Pending duplicate candidates no longer suppress records before acceptance. A matched bank copy is excluded when its accounting event is already counted.

05

A Concrete Verification Example

In the demonstration dataset, SAR 73,600 of expected incoming cash and SAR 73,775 of expected outgoing cash had to stay out of actual KPIs.

The corrected cash view retained them as forecasts:

  • Cash available: SAR 760,000.
  • Expected incoming: SAR 73,600.
  • Expected outgoing: SAR 73,775.
  • Projected closing cash: SAR 759,825.

That example shows the reporting behavior. It is not money saved or revenue earned by the client.

06

Results

The July 25 remediation record closes fourteen findings and records 603 passing tests, a successful production build, a database migration, and browser checks across the finance views.

Unsupported currencies are sent to review until a conversion policy is available. VAT and Zakat remain estimates requiring professional review before filing.

07

Technology stack

Next.js 15, React 19, TypeScript, PostgreSQL, ExcelJS; Qoyod, Zoho, Lean; Anthropic-based financial suggestions; canonical ledger and deterministic reporting modules; role-based access, bilingual dictionaries, AI-usage and finance-audit records.

08

Project at a glance

Accounting data and AI review, with explicit financial controls.
Ledgerline connects accounting, banking, and file imports. A dated verification records fourteen financial-control findings addressed and 603 tests passing against demonstration data.

09

Project summary

We built a finance workspace where AI helps with classification and mapping, while the reporting rules remain explicit. The work included separating forecasts from actuals and preventing bank and accounting records from counting the same cash twice.

Build a system around your workflow.

Tell us where the work gets stuck. We will map the first release, integrations, cost, and timeline.

Discuss a similar project