Enterprise Platform Engineering
Connect your systems to banks, Tally, GST and the plant
Brihat Infotech links the software you run: ERP to CRM, your app to a bank, the plant floor to the office. We plan the connections as a design, with a log and a replay for each.
What an integration project includes
- Integration architecture
event streams and gateways that decide how systems talk.
- Connectors for ERP, CRM and commerce systems.
- An API platform
versioned interfaces with published documentation.
- Banking and government interfaces
payment gateways, GST filing, the e-invoice and e-way bill portals, and the account aggregator network.
- Logging and replay
every message is recorded, and a failed one can be sent again.
Tools include Kafka, API gateways, webhooks and OpenAPI. An iPaaS (a hosted integration service) is used where it fits. An integration architect leads, with a few engineers building the connectors.
Core banking: Finacle, Flexcube and BaNCS
Banks run Infosys Finacle, Oracle Flexcube or TCS BaNCS. We connect through the service layers these products publish, with ISO 20022 and SWIFT messages where payments are involved. We do not query core tables directly: a bank's core database is not an interface, and a stray query can slow the bank's day.
NPCI payments: UPI, NACH and IMPS
Access to NPCI rails goes via your sponsor bank, or via a payment service provider (PSP). Building the call is the short part. Most of the effort goes to reconciliation, matching every payment to its bank record, and to dispute handling for the ones that fail or are reversed. We build both in from the start.
Tally
Tally speaks XML over HTTP, and we extend it with TDL (Tally's own customisation language) where a field or report is missing. Tally holds no queue of its own, so the connector keeps one, retries failed entries and logs each. Tally keeps the statutory books and GST; your ERP or app sends it the entries.
SCADA and PLC plant systems
Plant data leaves through OPC UA, or through OPC DA via a gateway for older equipment. It travels in one direction only, out of the plant, with no write-back to the controllers. Stock, production and downtime figures then appear in the ERP.
Designing for failure
Every integration fails sometimes: a bank times out, a portal is down for maintenance, a Tally company file is locked. Each message therefore carries an identifier, goes through a queue, and is retried with a delay. A message that still fails lands in a review list with its full payload, so someone can fix the cause and replay it. Replaying the same message twice does not create a duplicate entry.
Dashboards show how many messages are waiting, how many failed and how long the oldest has been waiting. The same view serves your support team and ours.
Related work
Multi-city hospital network. One scheduling layer connected to three hospital information systems, behind a patient app. See the hospital patient platform case study
Pan-India logistics operator. A control tower that collects vehicle GPS, scans at each hub and events from the driver app, and gives customers tracking through an API. See the logistics control tower case study
More in Enterprise Platform Engineering
List the systems that must talk to each other, and which one holds the master record.
Tell us what you want to build.
The first call is 45 minutes with an architect, usually the founder. It is free, and we will sign an NDA first if you ask.