Books
Indian default ledgers, eight voucher types numbered per year, draft to posted with reversal and amendment history, parties with CGST, SGST or IGST and TDS, and month locks.
Books, GST and daily entry in one place
Keep the books for a business: vouchers with GST, bank reconciliation, statements, and a simple daily entry and khata for small dues.
Company with GSTIN check, April-March years, opening balances that must balance, month locks and year-end close; Indian default groups and ledgers; eight voucher types numbered per type per year, draft to posted, reversal and amendment with history, with the database refusing an unbalanced post and any edit or delete of a posted voucher; parties with CGST and SGST or IGST, round off and TDS. Reports: day book, ledger, trial balance, profit and loss (by cost centre), balance sheet with last year, receivables and payables ageing, cash and bank book, with CSV and print. Bank reconciliation from a CSV statement with saved mapping, suggested matches and posting from a statement line. The simple side: money in and out, transfers, repeating entries, a khata of what customers owe or are owed with part and full settlement and due dates, reminders by email or a ready WhatsApp link, a public /s/<token> statement with a UPI QR, and a day close that locks the day. An inbox proposes entries from Billing invoices, Purchase bills, Expense claims, Payroll runs and Shop days, once each, through service bindings and keys pasted per domain; it is refreshed with a button, not on a schedule. GST and TDS pages are working papers (outward and inward, HSN, B2B list, monthly liability, TDS by section): the rates, HSN rows and TDS table are unverified defaults the owner edits in Settings and confirms with their CA; they are not GSTR-1 or 3B, no portal filing or e-invoicing, no input credit rules, reverse charge, cess or composition. Optional Claude features suggest a ledger and explain a movement and never post. API: GET vouchers, ledgers and trial balance, and POST that creates drafts only, with an API key or the workspace key; webhooks voucher.posted, voucher.reversed and period.locked. Not built: attachments and bill photos, reopening a closed year, TDS threshold enforcement, stock valuation, multi-currency, depreciation, a Payments receipts source.
What Accounting does for you.
Indian default ledgers, eight voucher types numbered per year, draft to posted with reversal and amendment history, parties with CGST, SGST or IGST and TDS, and month locks.
Day book, ledger, trial balance, profit and loss, balance sheet, ageing, cash and bank book, with CSV and print; bank reconciliation from a CSV statement.
Money in and out, repeating entries, a khata of what customers owe with reminders and a statement link with a UPI QR, and a day close.
A suggested path for Accounting. What you can do depends on your access in the app.
Company, financial year and opening balances.
Post vouchers or use simple entry; post from Billing, Purchases, Expenses and Payroll.
Reconcile, lock the month and export.
Live host, inventory, governance, health checks, verification, dependencies and history.
Company with GSTIN check, April-March years, opening balances that must balance, month locks and year-end close; Indian default groups and ledgers; eight voucher types numbered per type per year, draft to posted, reversal and amendment with history, with the database refusing an unbalanced post and any edit or delete of a posted voucher; parties with CGST and SGST or IGST, round off and TDS. Reports: day book, ledger, trial balance, profit and loss (by cost centre), balance sheet with last year, receivables and payables ageing, cash and bank book, with CSV and print. Bank reconciliation from a CSV statement with saved mapping, suggested matches and posting from a statement line. The simple side: money in and out, transfers, repeating entries, a khata of what customers owe or are owed with part and full settlement and due dates, reminders by email or a ready WhatsApp link, a public /s/<token> statement with a UPI QR, and a day close that locks the day. An inbox proposes entries from Billing invoices, Purchase bills, Expense claims, Payroll runs and Shop days, once each, through service bindings and keys pasted per domain; it is refreshed with a button, not on a schedule. GST and TDS pages are working papers (outward and inward, HSN, B2B list, monthly liability, TDS by section): the rates, HSN rows and TDS table are unverified defaults the owner edits in Settings and confirms with their CA; they are not GSTR-1 or 3B, no portal filing or e-invoicing, no input credit rules, reverse charge, cess or composition. Optional Claude features suggest a ledger and explain a movement and never post. API: GET vouchers, ledgers and trial balance, and POST that creates drafts only, with an API key or the workspace key; webhooks voucher.posted, voucher.reversed and period.locked. Not built: attachments and bill photos, reopening a closed year, TDS threshold enforcement, stock valuation, multi-currency, depreciation, a Payments receipts source.
Invoices to customers belong to Billing; purchase bills to Purchases; salaries to Payroll; counter sales to Shop. Statutory filing is not done here.
5 of 18 required controls are configured. Catalog deployment and inventory maturity remain independent until every required control is present.
accountings.appneural.com
No remediation required.
No remediation required.
No remediation required.
No remediation required.
Configure or repair: Repository exists.
Configure or repair: Business owner exists.
Configure or repair: Product owner exists.
Configure or repair: Technical owner exists.
Configure or repair: Maintaining team exists.
Configure or repair: Documentation exists.
Configure or repair: Architecture documentation exists.
Configure or repair: Security review is current.
No remediation required.
Configure or repair: Dependencies exist.
Configure or repair: Consumers exist.
No remediation required.
Configure or repair: SLA or SLO exists.
Configure or repair: On-call exists.
Configure or repair: Release exists.
No remediation required.
Configure or repair: Infrastructure drift is clear.
No remediation required.
No remediation required.
No remediation required.
No remediation required.
Configure or repair: Repository exists.
Configure or repair: Business owner exists.
Configure or repair: Product owner exists.
Configure or repair: Technical owner exists.
Configure or repair: Maintaining team exists.
AI outputs are saved as drafts with evidence references. They never replace verified catalog fields automatically.