Integrations: KeyMatrix plays well with your stack
A society already has a payment gateway, a Tally file, a set of gate hardware and a WhatsApp habit. KeyMatrix is built to sit with those rather than to replace all of them at once.
KeyMatrix integrates with Indian payment gateways for UPI, cards, netbanking and e-mandate autopay; exports and syncs to Tally; connects to ANPR cameras, boom barriers and biometric or face-recognition devices at the gate; and delivers notifications over WhatsApp Business, SMS, email and push. Open REST APIs and webhooks cover everything else.
Payments
Collection is where an integration either saves the treasurer a week a month or creates a second reconciliation problem. The difference is whether the payment lands back against the bill it was raised for. In KeyMatrix the invoice, the payment and the receipt are the same record, so a successful transaction closes the bill and updates the arrears ageing without anyone marking it off.
UPI, cards and netbanking gateways
KeyMatrix works with leading Indian payment gateways covering UPI, cards and netbanking. The society chooses its gateway and settles directly into the society’s own bank account — money does not route through KeyMatrix, and we take nothing per transaction.
Payment status flows back automatically, including failures. A failed UPI mandate that nobody notices is one of the more common causes of a resident being chased for a bill they believe they paid, so failures raise a flag rather than silently leaving the invoice open.
Autopay and e-mandates
Recurring maintenance is the ideal autopay case: the amount is predictable, the cycle is fixed and the alternative is a monthly reminder to several hundred people. E-mandates let a resident authorise once, after which each cycle’s bill is collected on its due date.
Mandates need managing, not just creating. Amounts change at a budget revision, cards expire, and banks drop mandates. Those states are surfaced as exceptions to work through, which is what stops autopay quietly decaying into a manual collection process over a couple of years.
Accounting
Most societies have an auditor and a CA who work in Tally, and no interest in changing that. The integration goal is not to move them off it — it is to stop the treasurer from typing the same transactions twice.
Tally export and sync
Books maintained in KeyMatrix export in Tally-compatible formats, so statutory filing continues in the tools the CA already uses. Ledgers, vouchers and the chart of accounts map across rather than arriving as an undifferentiated transaction list that someone has to re-code.
The practical test is whether the auditor asks for anything beyond the export. Getting the mapping right at setup — before a year of transactions exists — is the difference between an export that is used and one that gets rebuilt by hand each March.
Bank statement import
Bank statements import and match against outstanding bills, which is what turns reconciliation from a data-entry task into a review of exceptions. Payments made outside the gateway — a cheque, an NEFT straight to the society account, cash at the office — are the ones this catches.
Unmatched credits queue for a human rather than being force-matched. A payment attributed to the wrong flat is worse than an unattributed one, because the second gets found and the first turns into a dispute at the AGM.
Hardware at the gate
Gate hardware is where integrations get specific, because the equipment already installed varies enormously and a committee that has just spent on cameras will not replace them to adopt software.
ANPR cameras and boom barriers
Number-plate recognition reads the plate at approach, checks it against the resident vehicle register, and drives the barrier for a known vehicle. Unknown plates fall back to the guard, which is the behaviour you want: an ANPR system that opens for everything it cannot read is a barrier that is always open.
The entry is written to the same gate log as a walk-in visitor, so the record of who came in is one list rather than a camera system’s history plus a register.
Biometric and face recognition devices
Biometric and face-recognition devices are used mainly for staff attendance and for domestic help and vendor entry, where the same people arrive daily and OTP-per-visit is friction with no benefit. Attendance captured at the device flows into staff rosters and payroll-ready reports rather than a separate spreadsheet.
Device compatibility is genuinely device-specific. Share your models during the demo and the team will confirm before you commit — that is a more honest answer than a compatibility list that turns out to be aspirational at installation.
Messaging
A notice nobody reads has not been served. Delivery channel is not a cosmetic choice in Indian societies — it is the difference between a 30 percent and a 90 percent read rate on a bill.
WhatsApp Business notifications
Invoices, payment reminders, visitor approvals, circulars and OTPs can be delivered through the WhatsApp Business API. This materially improves read and payment rates for the straightforward reason that it reaches people where they already are, without requiring them to open another app.
Because it goes through the Business API rather than a group, messages are addressed to the individual and carry delivery and read status. A reminder that reached the resident and one that bounced are distinguishable, which matters when the next step is a late fee.
SMS and email providers
SMS remains the reliable floor for OTPs and urgent notices, and email is where the auditor and the CA expect statements to arrive. Both run alongside WhatsApp and push rather than instead of them, with per-notification-type routing so a water-supply notice and a legal notice do not have to travel the same way.
API and webhooks for custom workflows
Larger operators — builders handing over multiple projects, FM companies with their own CRM, portfolios with a data warehouse — need KeyMatrix to be a component rather than a destination. Open REST APIs let units, members, leads and payments be pushed in and pulled out, and webhooks fire on the events worth reacting to.
The API covers the core objects rather than a curated subset, which is the practical difference between an integration you can build and one you have to request. Where a workflow needs data KeyMatrix holds, it is available; where it needs to react to something happening, there is an event for it.
This is also the honest answer to feature requests we do not plan to build. A workflow specific to one operator is usually better built by that operator against the API than approximated for everyone in the product.
Request an integration
If something you depend on is not listed here, tell us what it is and what the integration would have to do. The useful detail is the workflow, not the product name: “our CA needs the quarterly GST working in this format” is actionable in a way that “integrate with our accounting tool” is not.
Requests that would be useful to more than one property get built. Requests specific to one operator usually get answered with the API and, where it helps, a worked example. Either way you will get a straight answer about which one it is rather than a place on a roadmap.
- Integration requests. sales@keymatrix.co, or raise it during the demo
- Device compatibility. Send model numbers for gate hardware and we will confirm before you buy
- API access. Available on request; documentation is shared during onboarding