Software where the numbers have to reconcile
Financial software is judged on two things a demo never shows: whether every number is exactly right, and whether you can prove afterwards what happened. The problems we see most often:
- Money stored as floating-point numbers. Tax splits and currency conversions done in binary floats drift by fractions of a cent, and month-end reconciliation fails for reasons nobody can find.
- Audit trails that can be edited. If an administrator can update or delete rows in the audit table, it is a log, not evidence.
- Legacy databases nobody dares move. Ledgers and customer records sit on SQL Server, Oracle or Db2. Migrating usually means a weekend freeze and a row-count spreadsheet that proves very little.
- Card data spreading through systems. Every service that touches a card number falls into PCI DSS scope, and scope grows quietly as features are added.
- Confidential files on desktops. Accounting firms and back offices copy client files locally to work on them, then forget them there, often on machines staffed by seasonal hires.
- Sensitive data in call recordings. Customers read card numbers and bank details aloud, and those recordings increasingly go to AI tools.
Work of ours that applies
Exact invoicing and an audit log that can't be edited. Esparks Biz, our live inventory, sales and invoicing app, calculates tax with exact decimal arithmetic rather than floating point. It splits Indian GST into CGST, SGST and IGST and validates GSTINs. A database trigger stops audit-log rows from being edited, and one shared data layer adds the business to every query. It also imports customers, suppliers and products from Excel or CSV, recognising Tally-style column headings. The tax rules are Indian, not US sales tax, Canadian GST/HST or UAE VAT, but the method carries over directly.
Database migrations you can prove. Our database migration platform, currently in early access, uses change data capture so the source system keeps taking writes during the move. In September 2026 it loaded a live SQL Server estate of about 780 million rows across 405 tables into PostgreSQL, and it keeps the two in sync ahead of cutover. A sampled key check across 401 tables (up to 1,000 keys each) found none missing. It supports SQL Server, PostgreSQL, MySQL, Oracle and Db2. The Oracle and Db2 connectors are implemented but not yet verified against live databases.
Desktops that hold no client data. The ThinClient OS financial services solution gives accounting and back-office staff a cloud desktop with no local storage. Every administrative action goes into an audit log, and server-managed credentials mean each session belongs to one named person.
Redaction before AI. CallIntell, in pilot, strips identifiers from call transcripts before any text reaches a language model. That includes card and account numbers read aloud in groups, which speech recognition writes as separated digits.
Payments. We have integrated PayPal and Razorpay. Esparks Edu collects fees through webhook-verified Razorpay payments that post straight to its ledger, and bills its own subscription tiers the same way.
What we have and haven't built in finance
Our portfolio contains no core-banking system, card-issuing platform, lending or loan-origination system, trading platform, or Sharia-compliant product. We have not integrated Stripe, Adyen, Plaid or a card processor; PayPal and Razorpay are the only payment gateways we have shipped. What we have shipped is the layer finance teams spend the most time on: invoicing, ledgers, migrations, reconciliation and audit trails.
Compliance: what we design for
We design for PCI DSS v4.0 controls, starting with keeping card numbers out of your systems through the gateway's hosted checkout wherever possible. We design for the SOC 2 trust criteria your auditor will test, for the GLBA Safeguards Rule on US projects, for PIPEDA in Canada, and for the UAE PDPL or the DIFC and ADGM regimes in the UAE. Esparks IT Solutions is not certified against any of these. We are not a PCI-assessed service provider, we hold no SOC 2 report, and our ISO/IEC 27001:2022 certification is in progress.
How we would approach a finance build
We start with the ledger model and the audit trail, because they are the hardest things to change later. Money is stored as exact decimals in one currency per amount, every state change is written to an append-only log, and reconciliation reports are built alongside the features they check, not added before the first audit.
How to start
Finance work usually starts with backend and API development, data and reporting, or a security review ahead of an audit. We work remotely with clients in the United States, Canada and the UAE, and we sign an NDA before you share details.