White labelFinancial services

Inventory system

One inventory system across six departments, without breaking the reports

A nationwide non-banking financial institution needed six departments to work from one inventory system of record. The hard part was not the build. It was making every report produce the number each department already trusted.

We keep this client’s name private. The client is real, and so is the system.

At a glance

Database architecture, authentication, and a multi-departmental inventory workflow and reporting system spanning six departments

Client: A nationwide non-banking financial institution with a large branch network and physical inventory operations
Industry: Financial services
Status: Delivered and maintained in release packages, each validated in production
Engagement: Long-term software design, development, and release engineering

The challenge

Six departments, one item, and six sets of reports that all had to agree.

The chain of custody crossed six departments
The same item is appraised, priced, distributed, and released by different teams, and any gap becomes an unexplained stock difference.
The existing reports were the real specification
Departments operate from reports they trust. A system that answers the same question differently creates reconciliation work, not progress.
The same figure was computed in three places
Application code, a shared services layer, and database stored procedures each produced parts of the same report.
Product categories are not uniform
Specific categories are handled differently by different departments, so a single generic rule produced wrong subtotals.
A wrong number is worse than a missing feature
In inventory reporting, a figure that looks plausible but disagrees with the department’s own record destroys trust in the whole system.

How we built it

Symph worked in three steps, each one building on the last.

Build the foundation
Enterprise-grade database architecture and authentication came first, so a single inventory record could be shared safely across departments with the right access for each role.
Connect the six departments
The workflow system carries an item through appraisal, pricing, distribution, and release inside one system of record, instead of across handoffs between separate tools.
Drive the reports to parity
Each report was matched to the figures the department already relied on, with behaviour aligned across the application, the shared services layer, and the stored procedures rather than corrected in one surface only.

Modules

01
Database architecture
The shared inventory data foundation the six departments work from.
02
Authentication and access
Role-based access so each department sees and acts on what belongs to it.
03
Departmental inventory workflow
Carries an item through appraisal, pricing, distribution, and release across six departments.
04
Stock and consignment reporting
Good stock and consignment reporting matched to the figures departments already use.
05
Unreceived items reporting
Shows what has left one department but has not been received by the next.
06
Inventory against returns
Reconciles inventory positions against returned items.
07
Departmental subtotals
Per-department totals computed consistently across every reporting surface.

Delivery model

01
Long-term development engagement
Symph holds continuing design, development, and release responsibility rather than a single closed build.
02
Frozen release packages
Accepted work is grouped into a package with exactly one reviewed implementation per owning repository, then promoted through pre-production before production.
03
A hard acceptance gate
Every change passes quality assurance, regression testing, live user acceptance testing with the departments, and production validation.

How it’s built

Proven architecture

The platform separates the application, a shared services layer, and database logic, so the same figure can be made consistent across all three.

Secure by default

Role-based authentication, strict access controls, and encryption protect inventory and customer records. Symph follows OWASP-aligned practices and the Philippine Data Privacy Act.

AI-native delivery

Symph’s engineers build and review with AI coding tools like Claude Code and OpenAI Codex, which is a big part of how parity work across three surfaces stays tractable.

Google Cloud: Google Cloud
AI-native development: Claude CodeOpenAI Codex

The result

One item, one record, six departments, and reports that agree with the numbers the departments already trusted.

66departments on one inventory system of record
33reporting surfaces aligned to the same figures

One system of record
An item moves from appraisal through pricing, distribution, and release without leaving the system.
Report parity, not report replacement
Reporting was matched to the figures departments operate from, so adoption did not start with a reconciliation exercise.
Consistent across three surfaces
Application, shared services, and database logic were aligned together rather than patched individually.
A repeatable release gate
Quality assurance, regression, live user acceptance testing with the departments, and production validation run on every package.
A long-term partnership
The engagement continues as ongoing design, development, and release engineering across the platform.