Case study

Olbrich Financial

A Persian double-entry accounting and treasury platform for project cost, approvals, auditability, and reconciled historical migration.

Status: Completed
Field: Financial infrastructure
Year: 2026
Client: Olbrich Construction Company

Olbrich Financial is the accounting engine behind Olbrich operations. Its dedicated API and database support multi-company books, fiscal years, four-level accounts, vouchers, treasury, cheques, project cost, fixed assets, approvals, reporting, attachments, and reconciliation. The financial workspace is integrated into Olbrich Portal while the accounting backend remains independently governed. Accounting rules are treated as system invariants, not interface suggestions. Posting, reversals, fiscal periods, project links, treasury events, and cross-ledger mappings are validated at the service and database boundaries so that operational convenience cannot silently weaken the books.

Capabilities

General ledger and vouchers

Four-level accounts, balanced voucher lines, controlled draft and posting states, attachments, search, and audit history form the accounting core.

Treasury and cheque lifecycle

Bank accounts, receipts, payment slips, issued and received cheques, status transitions, and bank evidence remain tied to their accounting event.

Project cost accounting

Canonical project and detail identities connect financial postings to construction activity without duplicating project codes across systems.

Procure-to-pay traceability

Material requests, warehouse receipts, supplier invoices, payment orders, bank evidence, and vouchers can be followed as one chain.

Reconciliation and close

Statement import, matching, unresolved-item review, period controls, and close-readiness views expose exceptions before reporting.

Migration and auditability

Historical records are normalized, reconciled, and retained with source references so the modern system does not erase the legacy trail.

Product views

Olbrich Financial procure-to-pay workspace showing connected accounting stages — The procure-to-pay view follows a transaction from construction demand through invoice, payment, banking evidence, and the final voucher.

Olbrich Financial account connection graph workspace in Persian — Account connections expose how a selected account, detail account, and project are linked across posted records.

Olbrich Financial ledger mapping workspace for moving documents between books — Ledger mapping formalizes equivalent accounts and project details before documents move between company books.

The operating challenge

Modernize the books without weakening control

The new platform had to preserve historical accounting integrity while adding project-aware workflows, stronger validation, and modern access.

Legacy data migration risk
Complex voucher and treasury rules
Separate operational and financial identifiers

Solution

Accounting invariants at the database boundary

A dedicated financial backend combines reconciled migration, explicit lifecycle rules, and a focused portal workspace.

Reconcile historical data to the rial
Enforce balanced posting in PostgreSQL
Connect project costs through canonical project identities

Technology and delivery

TypeScript
Fastify
PostgreSQL
React
Zod
Vitest

Where it works

General ledger
Construction project costing
Treasury operations
Financial control