ERPClaw Full-Stack ERP Controller

Problem

Small-business operations often split customers, invoices, payments, inventory, payroll, and accounting across spreadsheets, chat threads, and scratch files. The hard part is not recording a single item, but having a trustworthy system of record: who was billed, what remains open, whether account balances agree, and how period close should proceed. erpclaw treats the ERPClaw database as the authoritative source, requiring lookups of companies, customers, and items before answering or acting, rather than relying on memory or loose files.

How it works

• Local-first: SQLite-based, with column-level encryption for sensitive fields, parameterized queries, and RBAC using PBKDF2.
• Double-entry GL: covers chart of accounts, journal entries, payments, tax, and financial statements, with an immutable ledger and audit trail for reports such as trial-balance, profit-and-loss, and balance-sheet.
• Business workflows: supports customers, quotations, sales orders, invoices, receipts, suppliers, purchasing, inventory, billing, HR, US payroll, and 1099-related flows, with optional industry modules.
• Runtime constraints: high-impact actions require --user-confirmed; read-only queries do not. Industry setup is detected and then confirmed by the user before proceeding.

Boundaries

It is not a cloud SaaS product or a general BI platform. Network access is limited to a public exchange-rate API and user-approved module installs. If another ERP is already the system of record, the data source must be explicit to avoid mixing ledgers. It fits auditable, local, double-entry business operations, not just lightweight invoicing.