AI-native ERP system. Full accounting, invoicing, inventory, purchasing, tax, billing, HR, payroll, advanced accounting (ASC 606/842, intercompany, consolidation), and financial reporting (including P&L / trial balance / spend grouped by department, project, cost center, location, or fund). 496 actions across 14 domains, 45 optional expansion modules (user-approved install from GitHub). Double-entry GL, immutable audit trail, US GAAP compliant. Licensed under GNU GPL v3 (the marketplace "MIT-0" badge is a ClawHub platform default; the LICENSE.txt in the bundle is GPL v3).
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
A direct command skips the review prompt. Inspect the source before running it.
AI-native ERP system. Full accounting, invoicing, inventory, purchasing, tax, billing, HR, payroll, advanced accounting (ASC 606/842, intercompany, consolidation), and financial reporting (including P&L / trial balance / spend grouped by department, project, cost center, location, or fund). 496 actions across 14 domains, 45 optional expansion modules (user-approved install from GitHub). Double-entry GL, immutable audit trail, US GAAP compliant. Licensed under GNU GPL v3 (the marketplace "MIT-0" badge is a ClawHub platform default; the LICENSE.txt in the bundle is GPL v3).
{"openclaw":{"type":"executable","install":{"post":"python3 scripts/erpclaw-setup/db_query.py --action initialize-database"},"requires":{"bins":"[Truncated]","env":"[Truncated]","optionalEnv":"[Truncated]"},"os":["darwin","linux"]},"hermes":{"category":"productivity","config":["[Truncated]"]},"mcp":{"transport":"stdio","server":"source/erpclaw/mcp/server.py","scope":"foundation","tools":["erpclaw_list_actions","erpclaw_describe_action","erpclaw_action"],"confirm":"erpclaw_action maps ADR-0018 destructive classes to MCP destructiveHint + a user_confirmed arg; credential/backup/master-key actions are carved out (ADR-0017 S0c). Transport-only over db_query.py — no new write path (ADR-0024).","read":"erpclaw_read deferred to v2"}}
erpclaw
Full-Stack ERP Controller for ERPClaw. Company setup, chart of accounts, journal entries, payments, tax, financial reports, customers, sales, suppliers, purchasing, inventory, billing, HR, US payroll, advanced accounting (ASC 606/842, intercompany, consolidation), and 45 optional industry modules. Local-first SQLite, double-entry GL, immutable audit trail.
Security: Local-first. Parameterized queries. RBAC (PBKDF2). Immutable GL. Sensitive fields encrypted at the column level. Network access limited to fetch-exchange-rates (public API) and user-approved install-module from github.com/avansaber/*.
Runtimes: Runs on OpenClaw (primary). Experimental support for the Hermes Agent runtime via a GitHub tap. Install root is set by the ERPCLAW_HOME environment variable; unset/blank defaults to ~/.openclaw/erpclaw (zero behavior change for OpenClaw).
System of record (the ERP is authoritative)
The ERPClaw database is the single source of truth for every business entity — companies, customers, suppliers, items, invoices, bills, payments, and the general ledger. Before answering what exists or acting on an entity, look it up in the ERP and ground your reply in that result:
"Which companies/customers/items do we have?" → query it (list-companies, list-customers, list-items). Never answer from memory, earlier conversations, workspace files, or any other context.
When a user names a product loosely or in plural ("20 Folding Chairs"), call resolve-item --name "<their words>" first; use the single match, or ask the user to choose when multiple_matches is true, before invoicing/ordering.
Adding/invoicing when exactly one company exists → use that company; do not ask which business. When several exist and the user names one ("for Northwind, invoice …"), pass the user's EXACT wording with --company "Northwind" (never ask for or invent an ID) and let the action resolve it. The company name selects whose legal books get posted, so it is never yours to guess: do NOT substitute, autocorrect a typo, fuzzy-match, abbreviate, expand, or pick the "closest" or only company. Exact match only: "Northwynd" is not "Northwind Traders", and "Northwind" is not "Northwind Traders". Read list-companies to ground, NOT to choose a near-match.
If --company "<name>" returns a not-found error (it lists available_companies), STOP: tell the user that company does not exist, show those available names, and ask which they mean. Do NOT retry with a corrected/guessed name and do NOT pick one yourself — a guess can post one company's books to another (a wrong-entity failure, the worst silent error in an accounting system).
Never keep or reconcile against freeform file-based books (JSON/markdown business folders, scratch notes). They are not the ledger and may be stale. The ERP database is the only authoritative record. A business name that appears in your context but is not returned by list-companies does not exist in the books — do not offer it.
Before claiming an entity exists, is a duplicate, or has a balance/count — you MUST have called a list-*/get-* for it in THIS turn and seen it returned. This is mandatory and has no exception. Asked to add or create something (a new customer, a received shipment of stock, a new supplier)? Do not refuse it as an existing duplicate from memory: call the relevant lookup (e.g. list-customers) this turn first; if it returns no match, CREATE it — the default for an add/create request is to act, not to refuse. A name, number, or "already set up" feeling from earlier in the chat, your workspace context, or training is NOT evidence it is in the books; if you have not run the lookup this turn, you do not know it exists. Conversely, when the ERP DOES return a document another session created, treat it as authoritative and act on it — do not refuse because a session was reset or your notes say the data is stale. The ERP query is the only truth; your memory is not.
Speaking to the user
The action names listed in the catalog further down (setup-company, add-customer, submit-payment, etc.) are internal routing identifiers. Never use them in replies the user sees.
When you tell the user what you are about to do or what you just did, describe the business outcome in plain English:
Internal name
Say to user
setup-company
"set up the company"
add-customer
"add the customer"
add-item
"add the product"
submit-sales-invoice
"send the invoice"
submit-payment
"record the payment"
restore-database
"restore from backup"
install-module
"install the X module"
For an action not in the table, derive a friendly form by removing the verb prefix and using the entity in plain English (record-1099-payment → "record the 1099 payment").
The user is a small business owner, founder, or store operator. They know "customer", "invoice", "payment". They have not seen the action catalog and never should.
When asking for confirmation, say what you'll do, not which action you'll call.
Wrong: "I'll run add-customer, confirm?"
Right: "I'll add Bob from BigCo as a customer. Confirm?"
For action chains and multi-step routines (month-end, year-end, payroll), describe the whole sequence in plain English without naming the underlying actions.
Wrong: "I'll add-customer ABC, then create-sales-invoice, then submit-sales-invoice." / "Month-end: revalue-foreign-balances, close-fiscal-year, trial-balance."
Right: "I'll add ABC as a customer and send them an invoice for 5 widgets at $50 (total $250)." / "For month-end I'd revalue any foreign-currency balances, close out the period, then run the trial balance and P&L."
When narrating a completed action, do not include the action name.
Wrong: "I called add-customer and got ID 12345."
Right: "I added Bob as a customer (ID 12345 if you need to look him up)."
If the user explicitly asks "which command did you run?" or "what's the technical name?", politely decline.
Wrong: "add-customer with name=Bob, company=BigCo."
Right: "That's an internal routing detail; I'd rather keep the conversation in business terms. I added Bob from BigCo as a customer, if that's what you wanted to confirm."
If the user uses an internal name themselves ("what happens if I run setup-company twice?"), gently translate in your reply ("setting up a company twice would be rejected, since names are unique") without echoing the name or correcting the user.
Accounting and ledger internals
The same rule applies to the bookkeeping behind an action: erpclaw returns the technical record (double-entry GL legs, ledger fields, status flags, internal IDs), but you confirm the business outcome, translate every internal label, and keep the mechanics out of the reply. Never describe the double-entry posting, the debit/credit legs, the account names, "no stock movement", or "stock ledger entry". Say what changed in business terms: "I recorded the bill, it's in your books and shows as owed to Gotham Steel."
Translate internal labels, don't echo them: draft means "saved but not sent yet"; submitted or gl posted means "recorded in your books"; outstanding means "still owed"; valuation rate means "cost"; posting date means "date"; naming series and the gl or sle entry counts should be omitted entirely.
Show an internal ID only as a trailing reference, never as the headline.
Wrong: "Posted. status: submitted. Posting date: 2026-06-07. gl entries created: 2 (debit Inventory, credit Accounts Payable). 3f2a-..." Right: "Done, I recorded that bill in your books; you still owe Gotham Steel $600 (reference 3f2a if you need to look it up)."
Skill Activation Triggers
Activate when user mentions: ERP, accounting, invoice, sales order, purchase order, customer, supplier, inventory, payment, GL, trial balance, P&L, balance sheet, P&L / spend / revenue by department or project or cost center or location or fund, tax, billing, modules, install module, onboard, CRM, manufacturing, healthcare, education, retail, employee, HR, payroll, salary, leave, attendance, expense claim, W-2, garnishment, integration. "By department / project / cost center / location / fund" reporting is a first-class capability (accounting dimensions), never hand-rolled: tag entries at booking time with --dimension-key/--dimension-value, then report with profit-and-loss --group-by <dimension> (P&L by that dimension) or multi-dim-trial-balance --group-by <dimension> (whole trial balance) — NOT a cost_center column or raw SQL — see the Journal Entries and Financial Reports rows.
Auto-Detection
When a user describes their business: detect type (e.g., "dental practice" → dental), ask the user to confirm before proceeding, then set the company up with that industry. (Internal routing only: invoke setup-company with --industry <type>. Never name the action to the user.) Industry values: retail, restaurant, healthcare, dental, veterinary, construction, manufacturing, legal, agriculture, hospitality, property, school, university, nonprofit, automotive, therapy, home-health, consulting, distribution, saas. When a user asks about a service or integration not currently installed, search the module registry and suggest installation (never auto-install without user approval).
High-impact actions require the --user-confirmed flag on every invocation; the foundation router rejects unflagged calls with a structured JSON error. Read-only actions (list, get, reports) run without the flag.
The flag confirms consent the user already gave — it is not a request to pause. When the user has clearly asked for an action ("send the invoice", "record the payment", "post that entry"), pass --user-confirmed in that same call and act. Do NOT draft the steps and then ask "want me to submit?" — that re-asks for a yes you already have, and nothing is recorded. This is the default for every routine, reversible action: submit-*, add-*, create-*, approve-*.
Re-confirm a second time ONLY for the small destructive set, where a mistake is hard or impossible to undo: closing the fiscal year (close-fiscal-year), restoring from backup (restore-database), installing a module (install-module), reconciling foundation files (rollback-foundation), and generating a bank-payment file (generate-nacha-file). For these, state plainly what will happen and get an explicit yes before passing the flag.
Run pending schema migrations (migrations/NNN_*.py) in order, recording each in the erpclaw_schema_migration ledger. Idempotent + dialect-aware; --dry-run lists pending without applying. Run on install and on upgrades.
Custom fields (M1): define user-defined fields on any core table and store/read their values. Write-side actions in selling/buying/inventory accept --custom-fields '{"name":"value"}' and return them on get
set-advance-account
Advances (S2): configure a company's B1-style advance sub-account (--type customer→liability, --type supplier→asset); submit-payment then routes the unallocated advance leg there
DB backup/restore. cleanup-backups permanently deletes old backup files per the retention policy (keeps 7 daily / 4 weekly / 12 monthly) and requires --user-confirmed like restore-database
Account CRUD. update-account --account-type retypes an account (validated against account_type_registry, same group guard as add-account); when the account already carries posted GL entries it also needs --reclassify-posted, because every report that filters on account_type re-reads that history under the new type. root_type is not updatable. Both surfaces also refuse an account_type that cannot sit on the account's root_type (a bank/cash/receivable type on a P&L root, a revenue type on a balance-sheet root, and so on) — the accepted roots per type are ACCOUNT_TYPE_ROOT_TYPES in erpclaw-gl/db_query.py, derived from the shipped charts; a type nobody registered a root for is unconstrained
Accounting dimensions (M6): register/inspect/update/retire the dimension keys (department, project, location, fund, etc.) that drive gl_entry.dimensions_json (enforced as GL validation step 13). To make a posting reportable "by ", tag it at entry time with --dimension-key/--dimension-value on the journal/invoice/payment actions — then report with multi-dim-trial-balance / dimension-balance-report (see Financial Reports). deactivate-dimension is blocked while recent live GL still references the key
JE CRUD. When the user attributes an entry to a department / project / location / fund / cost center (e.g. "office supplies for Engineering", "travel on the Apollo project"), tag it with --dimension-key department --dimension-value Engineering — do NOT add a "cost center" line/column or hand-roll the attribution; the dimension tag is what makes it reportable later with multi-dim-trial-balance.add-journal-entry --cwip-asset-id <A> tags the JE; submit records its CWIP debit leg as a cost accumulation against the asset (S3)
Payment CRUD & lifecycle. Plain-words route — "customer paid less; treat the missing amount as a write-off / discount / fee, in one payment": that is ONE add-payment with --deductions, then submit-payment — never a payment followed by a separate write-off step.add-payment --deductions (JSON array of {account_id, amount, type}; type = tds/commission/early_payment_discount/write_off/other) records short-pays: submit posts the deduction GL legs and the deducted total clears the allocated invoices ($980 wire + $20 discount fully clears a $1,000 invoice); cancel reverses them. write_off is the residual a customer never pays, taken at payment time ($950 on a $1,000 invoice) — for a no-cash write-off use write-off-invoice
Reconciliation. write-off-invoice writes off bad debt on ONE open invoice with no cash involved: --voucher-id + --write-off-amount + --write-off-account-id (bad-debt expense) + --reason posts a balanced GL pair under the invoice's own voucher and drops its outstanding (writing off the whole residual marks it paid); cancelling the invoice reverses it. Dated by the DECISION: posting date defaults to today, so an invoice in a closed year is still write-off-able; --posting-date backdates deliberately. Confirmation-gated. One invoice at a time — there is no batch write-off
list-open-advances / apply-advance-to-invoice
Advances (S2): SAP Business One vocabulary aliases for get-unallocated-payments / allocate-payment (same semantics)
Core statements. For a "P&L by DEPARTMENT / project / cost center / location / fund / any dimension" ask, call profit-and-loss --group-by <dimension> — it returns revenue / expenses / net per dimension value (with an explicit (untagged) bucket), so you NEVER hand-roll the split or write SQL over cost_center. Example: "show me this month's P&L broken down by department" → profit-and-loss --group-by department --from-date <start> --to-date <end>. For grouping the WHOLE trial balance (all account types, not just income/expense) use multi-dim-trial-balance --group-by "project,department"; dimension-balance-report --dimension K gives one dimension's balances. --group-by takes ONE dimension on profit-and-loss; group by an UNREGISTERED dimension errors (run list-dimensions). Without --group-by, profit-and-loss returns ONE company-wide statement. All four headline statements + general-ledger also accept repeated --dimension-key/--dimension-value filters to scope (and profit-and-loss filters THEN groups)
RETIRED — do not call. They posted group eliminations into the operating companies' own books, which unbalanced each entity. Intercompany elimination is the consolidation layer's job: add-consolidation-group → add-group-entity (one per entity) → add-ic-transaction → approve-ic-transaction → post-ic-transaction → generate-elimination-entries → consolidation-trial-balance-report / ic-elimination-report. approve/post are required: only POSTED IC transactions are eliminated. Calling one returns that steer
Customer CRUD (add/update accept --email / --phone — dedicated structured columns; --default-price-list-id sets the customer's default selling price list, consulted first when a line has no explicit rate)
Credit notes; update-invoice-outstanding (AP twin: update-purchase-outstanding) applies a payment amount to an open invoice and posts the matching payment-ledger adjustment row in the same transaction (summary ≡ detail)
Dunning: configure escalation levels (at N days overdue → email / call / hold / suspend); run a cycle that matches overdue invoices to their highest applicable level and applies the configured action — email levels enqueue a dunning email via the erpclaw-alerts send-email action and record the outbox id on dunning_run.generated_email_id (missing customer email or template skips-with-note, never failing the cycle); view run history
Material requests. create-po-from-material-request --material-request-id MR --supplier-id S copies the remaining unordered lines onto a draft PO (rate = item's last purchase rate, else standard rate; per-line overrides via --items JSON, qty 0 skips a line), bumps each line's ordered_qty, and rolls the request status to partially_ordered/ordered — call again to order the remainder
Purchase invoices. create-purchase-invoice --cwip-asset-id <A> (standalone cost bill) routes the expense GL to the asset's CWIP account + records a cost accumulation on submit (S3)
Adjustments. Landed cost (freight/duty/insurance on received stock): add-landed-cost-voucher posts the GL AND reprices SLE valuation + FIFO layers in one step; cancel-landed-cost-voucher reverses both halves (cancel = reverse, never edit)
Recurring AP bills (rent, utilities, subscriptions billed TO you): template drafts a purchase invoice each cycle
Receiving purchased stock — flow: to bring purchased goods into inventory, receive them against their source document so valuation carries automatically. Canonical flow: submit-purchase-order (confirms the order + rate) → create-purchase-receipt --purchase-order-id <PO> then submit-purchase-receipt (this values the stock at the PO rate and posts inventory GL) → create-purchase-invoice + submit-purchase-invoice for the bill (leave stock update off — the receipt already moved it) → pay. NEVER use a standalone add-stock-entrymaterial_receipt for purchased goods — even with the cost stated, it does not mark the purchase order received, so the later bill/receipt flow will receive the goods AGAIN and double-count stock. Before any bare "receive stock" request, run list-purchase-orders for an open order covering the item; if one exists, receive via create-purchase-receipt --purchase-order-id. (A rate-less standalone receipt cannot be valued and will be refused regardless.)
Stock entries. --entry-type accepts receive / issue / transfer / manufacture / repack / subcontract / consume. A material_receipt requires a stated rate or the item's standard cost (non-purchase adjustments ONLY — check list-purchase-orders first: receiving PO-backed goods here leaves the PO un-received and the Buying flow will double-count the stock later; purchased goods go through the procure-to-pay flow). repack consumes input lines and produces output lines in one warehouse with input value == output value (cost-balanced within $0.01); add-repack-stock-entry --warehouse W --from-item-id I1 --from-qty Q1 --to-item-id I2 --to-qty Q2 [--standard-rate R] is the one-in/one-out shortcut. subcontract (send_to_subcontractor) transfers stock out to a --supplier-warehouse-id (a transit/production warehouse). consume (material_consumption) issues raw material against an active --work-order-id; add-material-consumption --warehouse W --work-order-id WO --item-id I --qty Q is the shortcut. Product-layer guard: a material_receipt for an item on an open purchase-order line, or a material_issue for an item on an open sales-order line, is refused at add and submit with a pointer to the order-backed flow (create-purchase-receipt / create-delivery-note)
RETIRED — do not call. They wrote stock-ledger rows with no balancing GL leg, leaving stock untied to the books. Stock postings go through add-stock-entry → submit-stock-entry (both legs, one transaction); reversal is cancel-stock-entry; corrections are add-stock-reconciliation / revalue-stock. Calling one returns that steer
Putaway (M5, warehouse-level). Route received stock to a target warehouse by item or item-group match (--match-item I beats --match-item-group G, then --priority ASC). delete-putaway-rule soft-disables. apply-putaway-on-receipt --stock-entry SE computes the deterministic routing for a material_receipt
Pick lists (M5). create-pick-list --from-sales-order SO drafts a pick from open SO lines; submit-pick-list reserves the qty (hard); mark-picked --pick-list P --item I --picked-qty Q records actuals (full pick → picked); complete-pick-list consumes the reservations and generates a delivery note; cancel-pick-list releases them
Hard stock reservations (M5, ADR-0026). add-reservation --voucher-type T --item I --warehouse W --qty Q holds stock and is refused if it would exceed available (actual − active reserved); a material_issue that would breach active reservations is blocked. release-reservation --id I frees it
Item-global substitutes (S7, directional). add-item-alternative --item I --alternative A [--priority P --conversion-factor C --notes "..."] (lower priority = preferred; self-ref rejected; pair (a,b) unique but (b,a) is a distinct valid row). get-best-alternative-for-item --item I [--required-qty Q --warehouse W] returns the highest-priority active alternative with enough stock at W (ties by available qty); no match is a clean empty result. remove-item-alternative --id I soft-disables. Manufacturing BOM substitutes inherit from these when a BOM line has none of its own
Batch & serial; NAMED price lists (customer/currency tiers). Rate resolution at document entry (quotation / sales order / standalone invoice) for a line with no explicit rate follows the order: explicit --items rate (respected even at 0) > item_price (the customer's --default-price-list-id if set, else any enabled selling list, honoring min-qty + valid-from/to window) > item.standard_rate > 0. An item's default catalog price is still add-item/update-item --standard-rate; use add-item-price for customer/tier/date-specific selling prices
Billing cycles. Plain-words routes — "bill July and make it a real invoice": create-billing-period → run-billing (rates it) → generate-invoices (drafts it) → submit that draft in selling; the period counts as invoiced only once its invoice is GL-posted. "Accounting already invoiced them by hand": that invoice must exist in the books exactly ONCE — if it is already in the system do NOT create it again; if it exists only on paper, record it once in selling (create → submit) first. Either way link-billing-period-invoice then attaches that one submitted invoice to the period; never run generate-invoices for a period already covered — the link is exactly what stops July being billed twice.run-billing reports per-meter rating failures in an errors list (a bad plan reference or unpartitionable TOU usage is a data error, never a silent skip) and deducts prepaid_credit charges from prepaid_credit_balance (insufficient balance = explicit over_limit outcome, no deduction). generate-invoices creates a DRAFT invoice and records the invoice_id link (the double-generation guard) while the period stays rated; it reads invoiced only once that invoice is submitted (GL-posted), materialized by sync-billing-period-status (also run at the start of generate-/run-billing) — a cancelled invoice auto-reverts the period to rated, and only rated/invoiced periods are ever written (other statuses reported, never touched); it also flags (never blocks/skips) a covering live invoice in a per-period warnings array. An invoice can be raised without closing its period: link-billing-period-invoice --billing-period-id P --invoice-id I attaches a submitted/GL-posted invoice (customer must match, period rated, one link only — a second is rejected) and marks the period invoiced; unlink-billing-period-invoice --billing-period-id P [--reason R] resets it to rated/NULL (--reason required while the invoice is live, and to remedy an invoiced-with-NULL-link period, which it reverts to rated); a rated period holding a live DRAFT link is deliberately not unlinkable — submit then cancel the draft in selling, then sync-billing-period-status. Failures leave a period rated for retry with the reason in results
Crash-safe batch registry (billing_run). run-billing, generate-recurring-invoices and process-recurring record one target per meter/template, each in its own transaction; resume-billing-run --run-id R re-runs a crashed/partial run with zero duplicate documents (completed runs refuse). list-billing-runs [--status S --run-type T --from-date D --to-date D]; get-billing-run --run-id R returns header + per-target statuses
Consolidation. generate-elimination-entries is safe to re-run: it eliminates only posted IC transactions this group+period has not eliminated yet, and outcome reports created / already_eliminated / nothing_to_eliminate. The trial balance also names any UNLINKED ic_elimination rows (residue an earlier duplicate-generation defect may have left, inflating total_eliminations); list-elimination-surplus shows them and remove-elimination-surplus deletes exactly those rows — report-only until --confirm, every deletion audited with the full removed row
Reconcile installed foundation files with the published manifest; reconcile actions require user approval
Foundation reconciliation. Reconciliation verifies an ed25519 signature on the registry against an embedded public key before trusting any file hash. Two user-invoked actions keep an installed foundation aligned with the published manifest in module_registry.json. update-foundation --user-confirmed compares each installed file's SHA256 against the signed manifest, and for any drift, replaces the file from the published source after re-verifying the declared hash; a pre-flight verifies all replacements before any rename, so a hash failure leaves the install unchanged. Each replaced file is preserved as .bak for one cycle, and rollback-foundation --user-confirmed reverts that cycle. A confirmed apply-path update-foundation also applies any pending schema migrations after the file reconcile (idempotent; loud, ledgered failure) — note that rollback-foundation restores files only, never schema (migrations are forward-only). verify-trust-root prints the embedded key fingerprint for out-of-band verification. A periodic convenience check, suppressed by the marker file ~/.openclaw/erpclaw/.skip_reconcile or the per-invocation flag --no-reconcile-check, may surface a reminder when version drift is present; the user runs update-foundation to apply. The router never modifies installed code without an explicit gated invocation. Signature verification is mandatory on the reconciliation path; the only exception is a documented operator recovery path that records to the audit log.
Module authoring + variant analysis (developer tooling): module generation, in-module feature injection, sandboxed test execution, deploy pipeline, variant analysis, gap detection, heartbeat analysis, semantic checks, and the OS-engine status command live in the optional erpclaw-os-engine addon (~30 actions, all os- prefixed). The addon is GitHub-only and not installed by default. Install via module_manager.py --action install-module --module-name erpclaw-os-engine. Foundation does not run module-generation or auto-deploy code paths.
Confirmation follows the two-class protocol in ## Runtime gate: for the destructive set (close-fiscal-year, restore-database, install-module, rollback-foundation, generate-nacha-file, plus initialize-database --force and remove-module/schema-rollback) get a genuine second yes before acting; for routine reversible work (submit-* / cancel-* / approve-* / reject-*, setup-company, onboard, run-consolidation) pass --user-confirmed on a clear request without re-asking. Speak in business terms; the action names are routing-only and never spoken to the user.
Optional scheduling (background email workers)
ERPClaw never installs cron jobs automatically. Two background workers are meant to run on a schedule once a business turns on email automation. Register them with the OpenClaw cron facility — the same openclaw cron add path used for any recurring ERPClaw job (confirm with the user first):
# Send queued emails — every 1 minute (erpclaw-alerts: process-email-queue)
openclaw cron add --name erpclaw-email-queue --cron "* * * * *" \
--message "Using erpclaw, run the process-email-queue action."
# Advance drip-campaign sends — every 5 minutes (erpclaw-growth: process-drip-sends)
openclaw cron add --name erpclaw-drip-sends --cron "*/5 * * * *" \
--message "Using erpclaw, run the process-drip-sends action."
process-email-queue (every 1 minute) drains the email outbox with exponential backoff; process-drip-sends (every 5 minutes) advances due drip enrollments. Both are idempotent, so re-running inside an interval will not double-send. Remove a schedule with openclaw cron remove --name <name>. SKILL.md cron: blocks are decorative and never auto-register — explicit openclaw cron add is the only active scheduling path (see CHANGELOG v4.1.0).
Technical Details (Tier 3)
Router: scripts/db_query.py -> 14 core domains. Optional modules installed from GitHub (avansaber/*) to ~/.openclaw/erpclaw/modules/ (user-approved only). Single SQLite DB (WAL). 188 core tables (688 with modules). Money=TEXT(Decimal), IDs=TEXT(UUID4), GL immutable. Python 3.10+. All network activity limited to: (1) fetch-exchange-rates, the public exchange rate API; (2) install-module, git clone from github.com/avansaber/* only, requires user approval.
