Skip to content
Menu
Services · Integrations and APIs

Systems that talk to each other without a person in the middle

Most companies run several systems, and someone in the middle retypes data between them. We connect them instead: Tally two-way sync, bank payment files and reconciliation, payment gateways, Amazon and Flipkart orders, Unicommerce, Microsoft Entra ID single sign-on with group-to-role mapping, Samsung Knox EMM device data, biometric attendance, lab machines and WhatsApp. We also publish APIs for partners who need your data.

Problems we are usually called for

01Orders from marketplaces are typed into the ERP by hand.
02Payments arrive in the bank and someone matches them to invoices in a spreadsheet.
03Accounts stay in Tally while operations move to a new system.
04Several systems need to talk to each other behind one sign-on.
05A partner needs your data, and you need control over what it can ask for.

How the work runs

The same six waypoints and three gates as every implementation.

  1. Survey · 2 weeks
  2. Chart · 2 to 4 weeks
  3. Build · 4 to 12 weeks by tier
  4. Rehearse · 3 to 5 weeks
  5. Cross over · 1 to 2 weeks, plus the parallel run
  6. Settle · 30 days
  7. Next leg · Optional add-on, as scoped
YOU SIGN ATBlueprint sign-offGo-live readiness reviewHandover sign-off
How we implement, waypoint by waypoint →

What is included

System
What we build
Tally
Two-way sync where Tally stays for statutory accounts.
Banks and payment gateways
Payment files, statement import and automatic reconciliation against open invoices.
Marketplaces and order systems
Amazon and Flipkart orders, Unicommerce and Shopify. Marketplace payout reconciliation is built for EasyEcom, not yet live at a client.
Identity
Microsoft Entra ID or institutional single sign-on, with group-to-role mapping and SSO-only login where required.
Devices
Samsung Knox EMM device data, biometric attendance machines and lab machines.
Your own APIs
Documented REST APIs and webhooks for partners, rate-limited, with a mandatory date range where the data is large.

Proof

Client
What we connected
Sonotech Medical Center
A payment gateway reconciled against about 1,000 invoices a day, automatically.
NewJaisa
Two marketplaces and the ERP, across 35,000+ SKUs of refurbished items.
IIT Bombay
ESTEM with SAP FI and single sign-on, on-premise.
Living Liquidz
A rate-limited vendor portal API with a 90-day query window.
AdComp Systems
Web, mobile, IVR, kiosk and POS payment channels synchronised with SmartCourt, so every payment lands against the right case.
A security services company
An EMM feed into a device pass system.

Each has a full case study below.

Technology

  • Tally
  • Bank payment files and statements
  • Payment gateways (generic)
  • Amazon (SP-API)
  • Flipkart (Seller API)
  • Unicommerce
  • Microsoft Entra ID (SSO)
  • Single sign-on (institutional / OAuth2)
  • Samsung Knox Manage (EMM)
  • Biometric attendance devices (ZKTeco)
  • Lab machines and LIS
  • SAP (SAP FI)

Where we have done it

All 12 case studies for this service →

Industries

FAQ

Yes. Where Tally stays for statutory accounts, we sync invoices and receipts to it so both agree.

No. Most of our integrations have ERPNext on one side, but we also connect custom platforms, portals and mobile apps to banks, identity providers and device managers.

Yes, through REST, files or database views depending on the system. ESTEM at IIT Bombay works alongside SAP FI.

Start a conversation

Tell us what you need.

An engineer reads it and replies within one working day with questions, not a brochure.