Industries where software has to stand up to inspection.

We work for five kinds of organisation. This page sets out what each is up against and what we build for it.

Who we work for

Stack9 works for organisations that pay heavily for a wrong record. Most answer to a regulator, an auditor or a licensing authority. Someone can ask what happened, who did it and when. The answer has to come from the system, not from memory. We build the software that holds that answer.

The rules differ by sector, but the work is similar. Records must be complete. Reports must match the records. Old and new systems must exchange data without re-keying. We work from Sri Lanka, for clients here and abroad.

Banks and finance companies

Banks and finance companies answer to the Central Bank of Sri Lanka and file reports with the Financial Intelligence Unit. Every record, approval and report has to trace to its source. Much of that data sits in a core system never built to share it.

  • Customer onboarding and KYC records

    A workflow that captures identity documents, runs the checks your policy requires and records who verified what and when. Service line: compliance technology.

  • Regulatory report generation

    Reports produced from the system of record in the regulator's format, with a reproducible query behind every figure. Service line: compliance technology.

  • Core system and payment gateway connections

    Adapters between the core system, payment gateways and internal tools, with a daily reconciliation report. Service line: integration.

Insurers

Insurers answer to the Insurance Regulatory Commission of Sri Lanka, and to policyholders who expect claims paid on time. Policy, claims and finance data often live in separate systems. A figure can change at every hand-off, with no record.

  • Claims workflow with a decision history

    A claims system that records each step from notification to settlement: who assessed, who approved and why. Service line: engineering and compliance technology.

  • Policy system to ledger integration

    Connections that carry premiums, commissions and claim payments from the policy system to the general ledger without re-keying. Service line: integration.

  • Regulatory and management reporting

    Returns and internal reports generated from the same source data, so the regulator and the board see the same figures. Service line: compliance technology.

Healthcare providers

Hospitals, clinics and laboratories hold the most sensitive data a person has. Patient records are personal data under the Personal Data Protection Act, No. 9 of 2022. Staff still need the right record in seconds.

  • Patient record access controls and logs

    Role-based access to patient records, with a log of every view and every change. Service line: compliance technology.

  • Laboratory, pharmacy and billing integration

    Connections between the systems you already run, so a test result, a prescription and an invoice attach to the same patient. Service line: integration.

  • Appointment, admission and discharge systems

    Custom software for the way your wards and clinics run, built to a written specification and tested against it. Service line: engineering.

Licensed businesses

Importers, pharmaceutical distributors and money changers trade on a licence that can be withdrawn. The authority that issued it can ask for records at any time. Records kept in spreadsheets and inboxes take days to produce and prove little.

  • Licence and permit record-keeping

    A system of record for your licences and permits, their conditions and renewal dates. It alerts a named person before anything lapses. Service line: compliance technology.

  • Batch and transaction traceability

    Software that follows each batch or transaction from receipt to sale, with documents attached at every step. An inspector's question becomes a search. Service line: engineering and compliance technology.

  • Automated filing to government portals

    Filing to portals built for a person with a browser. The system keeps each submission and the acknowledgement that came back. Service line: integration.

Companies with legacy systems

Some companies run on an old ERP, a database nobody dares touch or a system whose supplier has gone. The business depends on it, so nobody can switch it off. Every year it gets harder to change.

  • Adapters around a system with no API

    Where the old system exposes nothing, we build the adapter. New tools can then use its data without touching its internals. Service line: integration.

  • Data migration with reconciliation

    Migration scripts run against a copy first. A reconciliation report shows record counts and totals on both sides before we switch over. Service line: integration.

  • Staged replacement of the old system

    A replacement built to a written specification, one module at a time, while the old system keeps running. Service line: engineering.

Outside these sectors

We also take engineering and integration work outside these sectors. The test is whether the system matters enough to be built properly: a written specification, automated tests, documentation and a full handover.

Some work is not a fit. We do not build marketing websites or quick prototypes with no specification. If that is what you need, another team will serve you better, and we will say so in our first reply.

  • Compliance technology

    Audit trails, regulatory reporting, KYC, access controls and data retention.

  • Integration

    ERPs, banks, payment gateways, government portals, legacy databases and data migration.

  • Engineering

    Custom software built to a written specification.

  • Process

    From the 1-week discovery to go-live and the first 30 days.

Tell us your sector and the system you need, and we reply within 2 working days.

Start a project