Initialising xBodhi
Bodhi brings practice operations, cloud books, bank and document automation, tax work, audit evidence, client collaboration, and governed AI into one role-aware workspace.
Start with the firm, select the client and period once, then move from source evidence to books, compliance, review, and delivery without losing context.
Firm command centre for clients, entities, teams, obligations, deadlines, maker-checker review, work queues, exceptions, billing, and profitability.
Cloud double-entry accounting designed for Indian businesses and the accountants who close their books.
Multi-client banking, OCR, GST, TDS, income tax, audit, notices, MCA, and workpapers under professional review.
Safe exchange with TallyPrime, Tally.ERP 9, Zoho Books, Vyapar, bank feeds, and structured ERP files.
Provider-neutral AI for extraction, classification, explanation, and draft actions—never the owner of arithmetic or professional authority.
Every capability enters through the same controls: client context, source evidence, exact calculations, review authority, and an immutable result trail.
Bulk statement and invoice intake, approved-password handling, layout/OCR lanes, source coordinates, continuity math, BRS, counterparty analysis, proposed vouchers, and audit-ready exports.
Accounting, bills, inventory, invoicing, payroll, assets, controls, and financial statements in one web workspace.
Returns preparation, 2B matching, IMS actions, Table 4, e-invoice/e-way adapters, and turnover reconciliation.
AIS, TIS, 26AS, Form 16, broker files, TDS returns, ITR schedules, official JSON gates, and ERI boundaries.
PBC, materiality, sampling, scrutiny, 3CD, CARO, Schedule III, 43B(h), findings, review notes, and file lock.
Structured document requests, secure uploads, queries, approvals, consent, acknowledgement, reminders, multiple business channels, and permission-isolated conversations.
Role-specific partner, manager, staff, client/CFO and auditor views; KPI contracts, evidence drill-through, forecast ranges and frozen PDF/XLSX/CSV packs with exact control totals.
POS, thermal invoices, UPI intents, settlements, marketplace accounting, receivables, and CFO analytics.
Bodhi automates the complete route, not just one AI response.
Portal, upload, email, official WhatsApp, API, or local connector.
Identity, source coverage, schema, exact paise math, and duplicates.
Rules and memory propose mappings, vouchers, returns, and workpapers.
Maker, reviewer, partner, and client consent gates remain explicit.
Post, export, submit, communicate, and store the real receipt.
Numbers come from parsers and deterministic engines. AI extracts, classifies, explains, and prepares. Material actions still require evidence, policy, permission, and confirmation.
Each connection is truthful about configuration, heartbeat, consent, checkpoints, conflicts, and reconciliation.
Connection names describe supported architecture and roadmap. A provider is shown as connected inside Bodhi only after a real verified probe.
Tenant isolation, least privilege, encrypted evidence, no secret-bearing logs, append-only history, provider receipts, and truthful failure states are part of the operating model.
Firm-wide operational status across all clients, obligations, and exceptions.
| Client / Entity | Obligation | Statutory Due | Stage | Assigned Staff |
|---|
| Team Member | Role | Assigned | Overdue | Review |
|---|
Scalable multi-entity client directory with server-side pagination and filters.
| Client Group | Primary Legal Entity | Entity Type | PAN | Primary GSTIN | Partner / Manager | Deadlines | Next Due Date | Risk | Actions |
|---|
Primary Entity: — · PAN: —
Monitors GST, TDS, ITR, Advance Tax, and Audit obligations firm-wide.
| Compliance Form | Client Entity | Period | Statutory Due Date | Internal SLA | Stage | Assigned Staff |
|---|
Real-time review backlogs, overdue items, and task distributions.
| Staff Name | Firm Role | Active Work | Overdue | Review Backlog | Blocked |
|---|
Invite team members with a defined role. Access remains server-enforced and workspace scoped.
| Name | Role | Joined |
|---|
The invitation is bound to the verified email address and expires automatically.
Bank math failures, unclassified transactions, and missing compliance proofs.
| Severity | Source Module | Exception Details | Client Entity | Status | Timestamp |
|---|
Indian chart, exact-paise double entry, bill-wise AR/AP, cost centres, inventory, orders, payroll drafts, fixed assets, maker-checker review, immutable corrections and drill-through financial statements.
Posted, reversed and revised records remain visible.
| Date | Number | Type | Narration | Debit | Credit | Control state |
|---|
Explicit setup creates masters only—never demo balances.
| Ledger | Group | Bill-wise | Currency | Opening balance | Status |
|---|
New Ref, Agst Ref, Advance and On Account settlements with concurrent over-allocation protection.
| Side | Party | Reference | Due date | Age bucket | Open amount |
|---|
FIFO, LIFO, weighted average, standard cost and last purchase are calculated from retained movements.
| Item | Unit | Valuation | Quantity | Value | Control |
|---|
Every number drills back to a voucher and source evidence reference.
Run reports to inspect reconciled control totals.
Account identity, source anchors, statement continuity, exact paise math, BRS, reviewed voucher proposals, and reversible posting.
Link the statement identity to the exact books ledger before analysis.
Use the original bank-generated CSV, XLSX, or text PDF. Safety scanning must pass before parsing.
| Date | Narration | Channel | Counterparty | Direction | Amount | Balance | Category | Match | Source |
|---|
| Bank Row | Voucher | Match | Date Gap | Status |
|---|
| Date | Type | Narration | Amount | Target Ledger | Status |
|---|
Process up to 100 retained statements across clients and accounts with exact identity, period, continuity, duplicate, coverage and math gates—then inspect BRS, transfers, recurring payments, EMI candidates, anomalies and independently reviewed semantic exceptions.
Choose a registered account and Smart Inbox evidence. Passwords stay only in browser memory for the current run.
Processing continues around a failed item. Nothing posts, files or exports tax JSON automatically.
GST/Income Tax output remains unavailable unless exact official schema and applicable facts are proven. Proprietary Tally backups are never reverse engineered.
Bulk files enter one safety, duplicate, password, classification, encryption, and review pipeline.
Up to 20 files per batch. Originals are encrypted before object storage. Files do not enter OCR or books until safety gates allow processing.
| File | Class | Safety | Password | Processing | Evidence ID |
|---|
| Request | Type | Period | Due | Status |
|---|
Specify exactly what is required, for which period, and when. A validated upload can complete the request automatically.
Multi-GSTIN periods, evidence-locked 2B, explainable matching, October 2025 IMS and BoE rules, Table 4, return snapshots, IRN/EWB preflight and professional DRC workpapers—without pretending a provider filed anything.
One client can hold multiple registrations without losing state and period scope.
Direct upload remains preview-only. IMS approval needs the matching encrypted Smart Inbox vault object.
| Status | Match type | Taxable variance | Tax variance | Reason |
|---|
| Action | Rule reason | ITC impact | Allowed |
|---|
Versioned internal normalized snapshots. They are not represented as official portal JSON or filed returns.
Maker-checker approval, single-use scoped taxpayer consent, accredited provider configuration and a real acknowledgement are separate requirements. OTP/DSC values are never retained.
TDS/TCS aggregation, challans and corrections; payroll proofs and effective rules; AIS/26AS/Form 16 evidence graph; explainable ITR-1 through ITR-7; official CBDT schema validation and a fail-closed ERI boundary.
| Status | Match | Variance | Evidence basis |
|---|
Internal workpaper export remains available. Official JSON is labelled valid only after the exact AY/form schema passes.
Employee regime, other-employer income, perquisites and deduction claims remain unverified until retained evidence is reviewed.
Every payroll run retains state, effective version and exact statutory calculation inputs.
Preparation, computation and manual JSON/workpaper export continue without accreditation. Add-client, prefill, validate/submit, e-verify and acknowledgement remain provider- and consent-gated.
Session tokens are AES-256-GCM encrypted. OTPs and DSC private keys are never accepted or retained.
Each add-client, prefill, submit, e-verify or acknowledgement action uses a separate expiring single-use consent.
Seven CBDT AY 2026-27 schema copies are retained with SHA-256. A Bodhi workpaper is not renamed as official ITR JSON unless the selected form schema validates it.
Versioned AIS, TIS, 26AS, Form 16/16A, TDS, challan, acknowledgement and GST offline-file profiles with exact taxpayer/period identity, source hashes and integer-paise controls—plus evidence-linked agents that prepare drafts without filing, paying, signing or scraping portals.
No authenticated portal login, CAPTCHA bypass, OTP or DSC.
Compare independent file sources; export workpapers, not fabricated portal files.
ITR JSON requires the exact locally retained official schema. GST/TDS snapshots remain internal workpapers unless their own official/provider gate passes.
Agents inspect only assigned tenant evidence and produce reviewable tasks.
Review changes task state only; it never executes the underlying action.
Acceptance to archival, evidence-linked workpapers, reproducible sampling, JE risk indicators, 43B(h), notice mutation gates and MCA preparation—without automated opinions, fabricated UDINs or invented SRNs.
Partial payments, debit notes, non-trade balances, disputes, year-end outstanding and post-year payment remain separate facts.
Changed PAN/GSTIN, AY/FY, date, amount or reference creates a different mutation hash and cannot replace accepted evidence.
Issue trees retain missing evidence and official-source research placeholders. Partner review and client authority remain mandatory.
Forms, calendars, registers, checklists and manual/provider exports are prepared without scraping MCA or fabricating SRNs.
Edit-log analytics provide exceptions only. The auditor’s reporting conclusion remains explicit professional judgment.
CARO, 3CD, Schedule III, going concern, fraud, notices, UDIN and filing outcomes are never inferred from a green checklist.
Inventory-aware counter billing, exact GST/discount/rounding, split tender, offline idempotency, returns, 58/80mm print and payment evidence—where a QR is never proof of payment.
Complete a controlled sale to generate the receipt.
LINK_CREATED → INITIATED → PAID_EVIDENCE / FAILED / REFUNDED_EVIDENCE → SETTLEMENT_RECONCILED. Only verified webhooks and settlement evidence move financial state.
Mobile tasks, structured requests, secure uploads, query threads, approvals, consent, acknowledgements, invoices and payment truth—with official WhatsApp/email delivery states and quiet-hour automation.
Official Meta Cloud API and signed webhooks only. Personal WhatsApp Web QR sessions and fake “delivered” states remain prohibited.
Partner, manager, staff, client/CFO and auditor dashboards share exact KPI contracts, evidence drill-through and one frozen source across PDF, XLSX and CSV. Empty data stays empty; a forecast is always a range with assumptions.
Bodhi will not fill an empty tenant with sample revenue, automation percentages or forecasts. Post or import reviewed source records, then recompute.
Numerator, denominator, exclusions, timezone, query hash and evidence remain inspectable.
| Metric | State | Numerator | Denominator | Value | Source / exclusions |
|---|
20-sheet workbook, Indian-formatted PDF and control-total CSV use the same immutable snapshot ID.
Actual book history stays visually separate from scenario bounds. Basis points are explicit.
Integer-minute time, recurring idempotency and evidence-defined collections feed the analytics above.
Staff/client roles never receive compensation or staff-cost metrics. Recommendations require assignment authorization.
Versioned file profiles, reviewed SKU maps, partial settlements, section 9(5), duplicate deductions and draft-only accounting proposals.
Manage personal and firm profiles, notifications, sessions, roles, data governance, integration truth, report schedules, API/webhook access, account export/deletion requests and local-AI readiness—without returning credential values or weakening authority gates.
Never paste a key here. Use OS keychain or encrypted local vault.
Layered request limits, bot challenge boundaries, tenant isolation, encrypted diagnostics, owner alerts, secret posture and model-route confidentiality—with no claim that any system is unhackable.
Run operational readiness to see exact deployment blockers.
High-severity records are pending owner review until acknowledged. Delivery is never claimed without provider evidence.
No secrets, prompts, document contents, PAN/GSTIN or raw financial rows.
Values, fingerprints and model routes are never returned to the browser.
Descriptions are redacted and encrypted when the observability key is configured.
Reports whether a persisted tamper-evident hash chain is configured. Stored events alone are never presented as cryptographically verified.
Checks whether the server-side master key is configured. A named algorithm without a key is not reported as active encryption.
Rules and approved client memory first; one capability-routed provider when needed; evidence citations, multidimensional gates, shadow evaluation, editable voice transcripts and draft-only actions with confirmation and undo.
Raw audio never executes an action. Browser speech creates editable text only.
Answers cite exact tenant sources or say that data is absent, stale, ambiguous or unavailable.
Review affected records and payload. This cannot file, pay or grant client consent.
Mappings are entity-scoped, versioned and reversible. A single correction never becomes automatic memory.
English, Hindi, Marathi, Gujarati and code-mixed evaluation sets include injection and abstention cases. No fixed vote confidence is reported.
Filing, payments, e-verification, OTP/DSC use and client consent cannot be completed from voice. Transcript preview does not weaken RBAC or maker-checker gates.
Circuit breakers, budgets and kill switches fail closed. Provider/model identities and secrets stay server-side.
Preview-first Tally XML, a signed-request outbound local agent, stable checkpoints, explicit conflicts and post-sync count/hash/Trial Balance controls—never a green badge from configuration alone.
Documented XML only. Unknown groups, ledgers, voucher types and godowns stop for explicit mapping.
| Object | External identity | Action | State | Exception |
|---|
The cloud never calls localhost. The agent opens no inbound port and signs every outbound request.
| Device | Agent | Heartbeat | Tally |
|---|
OAuth v3 organization scope, incremental checkpoints and signed webhook boundary. No credentials in the browser.
Versioned CSV/XLSX profiles, exact decimal controls and dry-run quarantine. No undocumented direct API claim.
Consented provider boundary with purpose, scope, duration, revocation and fetch audit. Banking passwords and PINs are prohibited.
Fixture and local mock contracts are verified. A release is marked live only after a licensed Tally machine produces a timestamped heartbeat, company identity, acknowledgement, count/hash and Trial Balance reconciliation.