The co-operative society, audit-ready every day.
Sahakār brings statutory admissions, deposits such as FD, RD and savings accounts, loans with approval, shares, funds, dividends and daily cash controls into one operational system. Every financial event posts to a hash-chained double-entry ledger that an auditor can verify, while the pre-audit workspace identifies discrepancies early.
Everything the Act expects, built in
Members & statutory admission
Form XXVIII applications with the 45-day board clock and automatic deemed acceptance at 60 days (s.64), a Form XII member register, KYC documents and maker-checker edits.
Deposits: FD, RD, savings, current
Board-resolved rate slabs are frozen at opening. The system records quarterly savings interest, maturity and premature closure calculations, nominees and passbook statements.
Loans with board approval
Purpose-stated applications (s.49), flat or reducing schedules, Secretary approval before disbursal, principal/interest split on every repayment (Rule 67(1)(x)).
Double-entry books & daily cash book
Every rupee posts through a balanced double-entry ledger; the cash book closes daily (Rule 67(1)(vii)) and nothing can be backdated into a closed day.
Shares, funds & dividends
Share ledger with the s.75 one-fifth cap, year-end statutory allocations (Bad Debt ≥15%, Reserve ≥10%) and a permanent Register of Dividend (ss. 80–86).
Statutory roles
Secretary, operator, accountant, cashier and internal auditor have separate responsibilities. Rule 73 keeps cash handling separate from account keeping.
Audit-ready statements
Trial balance, receipts and payments, balance sheet, deposit position and year-wise overdue classification under Rule 155A are available on screen and as CSV.
Statutory return preparation
A dated amended-s.97 preparation pack combines activity and ledger evidence with the attachments checklist for auditor certification and manual filing.
Documents with citations
ID cards with verification QR, receipts, sanction letters and deposit statements include the relevant Act or Rule citation.
Member portal
Members can see their own shares, payments, deposit passbooks with PDF statements and loans. This supports the Rule 67A inspection right.
Evidence, not trust
Every action lands in an append-only audit log chained with SHA-256. Each event seals the hash of the one before it. Every rupee flows through one posting function into a double-entry ledger that is itself hash-chained, sealing a digest of its debit/credit lines.
Edit a row, delete a row or add a row out of sequence and the chain breaks visibly, down to the exact transaction. The register of members is prima facie court evidence (s.151); these books are built to carry that weight.
AI pre-audit review
One button runs a pre-audit check in the background: chain verification, liquid-cover ratios (Rule 81), overdue classification (Rule 155A), admission deadlines (s.64), unclosed cash-book days. When configured, an AI review reads the same snapshot like an auditor would.
Discrepancies come back in plain language with the rule they break, so the Secretary fixes them before the statutory audit, not during it.
The Rules Assistant is available in the staff and member portals. It explains each option, how to use it and its supporting law from the approved Act, amendment and Rules sources. Daily role-specific alerts remain planned.
Roles the way the Rules wrote them
The Secretary assigns roles and approves; the operator admits members; the accountant keeps the books and validates the cash day; the cashier handles cash (Rule 73 keeps those two apart); the internal auditor reads everything; and the government-appointed Regulator gets independent, read-only access the society itself cannot grant, change or revoke. Sensitive powers such as creating members, issuing loans and opening deposits are each exclusive to exactly one role. A built-in guide explains who to assign where.
The team behind Sahakār
Dr. Arindam Banik B.Tech. (IT), M.B.A., Ph.D.
Co-founder and CEO.
Tanmoy Sadhukhan B.Sc (Comp Science), P.G in AI/ML (IIT Guwahati)
CTO and Co-founder.
Frequently asked questions
A practical guide to Sahakār's legal grounding, evidence controls, user access and the boundaries of its live capabilities.
The West Bengal Co-operative Societies Act, 2006, the 2011 Amendment Act, the 2013 Second Amendment Act, and the consolidated WBCS Rules, 2011. These approved sources are retained in the system and index the Rules Assistant. Implemented workflows enforce admission deadlines, share caps, deposit limits, fund allocations, dividend ceilings and record-keeping controls; governance workflows remain separately scoped.
Two SHA-256 hash chains protect the records. Each action seals the previous audit event, and each money movement goes through a single posting function into a double-entry ledger that seals its debit and credit lines. Both chains can be checked at a click. Financial rows cannot be edited or deleted. Corrections use reversal entries.
One button runs a background review of books, members, deposits and loans. Chain verification, liquid cover, overdue classification, admission deadlines and unclosed cash-book days are always checked. When the platform AI provider is configured, the review also flags additional discrepancies in plain language so the Secretary can act before the statutory audit.
Yes. Reports includes a statutory-return preparation pack for the selected co-operative-year period. It compiles the activity and ledger evidence Sahakār holds and lists the auditor-certified and signed attachments required before manual filing. It is audit-logged; it does not claim to certify or electronically submit the return.
The platform Super Admin appoints a read-only Regulator account to a cooperative, mirroring the section 97 statutory audit officer. Cooperative staff cannot invite, re-role or deactivate that account, which preserves audit independence.
Member details go through maker-checker approval with proof attachments. Financial records are append-only. A wrong entry is corrected by a reversal transaction dated today, while the original entry and the audit trail remain intact.
A self-service portal with their profile, share capital, payment receipts, deposit passbooks with downloadable statements, loan schedules and sanction letters, plus a PVC-style ID card with a public verification QR.
No. The Rules Assistant is read-only and grounded only in the approved Act, amendment Acts, consolidated Rules and product guide. It cannot access a cooperative’s books, member records or other tenant data, and it cannot change records.
Auditors can review the audit trail, verify both hash chains, inspect the source entries behind reports and use cited documents such as receipts, statements and sanction letters. The statutory-return preparation pack brings the available activity and ledger evidence together for the selected co-operative year.
Sahakār separates the Secretary, operator, accountant, cashier and internal-auditor responsibilities. In particular, Rule 73 separation between cash handling and account keeping is reflected in the assigned responsibilities, while sensitive actions are restricted to their intended role.
The platform keeps supporting documents with the relevant workflow, including KYC evidence for admissions and documents for member, loan and deposit records. Generated identity cards, receipts, sanction letters and statements include the applicable legal citation where relevant.
The live capabilities focus on operational records, pre-audit review and the read-only Rules Assistant. Daily role-alert delivery and governance workflows for board meetings, AGM, elections and statutory-return filing are not live; statutory-return output is a preparation pack for auditor certification and manual filing.
© Sahakār · Developed by DIGIIDEA PRIVATE LIMITED