General ledger control
- Chart of accounts
- Journal posting
- Reversal workflow
- Period controls
Tai chinh va doanh thu
Kế toán
Financial control for accounts, journals, budgets, reports, tax evidence, and close readiness.
Đã triển khai
Evidence-first module page
Primary users
Accountant
Finance manager
Controller
Auditor
App-derived visual
Accounting workbench
Posting control
RBAC gated
Period close
Evidence tracked
Provider refs
Replay guarded
| Khu vực | Trang thai | Bằng chứng |
|---|---|---|
| Journals | Workflow controlled | Audit + idempotency |
| Bao cao | Snapshot ready | Export checksum |
| Tax | Provider aware | Submission evidence |
Quy trình chính
What the module helps operators complete.
Each workflow is written as an operational path, not a marketing claim, so buyers can understand the day-to-day module fit.
Step 1
Manage chart of accounts and dimensions
Step 2
Post and reverse governed journals
Step 3
Review period-close and statutory report evidence
Step 4
Analyze budget and financial report readiness
Feature checklist
Capabilities grouped the way operators look for them.
Financial reporting
- Trial balance
- Report snapshots
- Statutory packs
- Xuất bằng chứng
Tax and bank evidence
- Tax code support
- Provider submissions
- Bank feeds
- Reconciliation paths
Connected module map
How this module exchanges business context with the rest of ERPStack.
| Module | Quan hệ |
|---|---|
| Thanh toán | Invoices, payments, refunds, and revenue evidence |
| Chi phí | Approved claims and reimbursement accounting handoff |
| Lương | Payment approval, payslip, and reconciliation evidence |
| Tồn kho | Valuation readiness and stock movement financial impact |
Governance and reporting
Controls and management visibility expected from a serious ERP module.
Quản trị
- RBAC posting controls
- Audit trail
- Idempotency
- SIEM anomaly events
Bao cao
- Ledger
- Trial balance
- Financial statements
- Budget variance
AI coverage policy
What ERPStack can honestly claim for this module today.
AI claims are tied to the official Agent Tool Registry, evaluation evidence, safe-mode controls, and scheduled-agent monitor readiness. Roadmap modules only show planned coverage until module-native tools are implemented.
AI L3 ready| Coverage claim | Current AI coverage: Accounting L3/L3 ready through the official Agent Tool Registry. |
|---|---|
| Governance evidence | Governance evidence: 9 registered tools, 9 evaluation cases, tenant/RBAC/safe-mode registry controls, and AI log evidence. |
| Scheduled monitor | Scheduled monitor readiness: 1/1 ready (Finance Close Variance Monitor). |
| L4/L5 boundary | Remaining L4/L5 gap: no autonomous execution or self-optimizing agent behavior is claimed; write paths remain permissioned, previewed, and confirmable. |
Evidence-first standard
Module pages explain value, workflow, control, and proof in one place.
This page structure supports the current public module catalog with app-derived visuals, connected-module evidence, governance proof, and report context that can be compared against real product routes.
Feature clarity
Buyers can see concrete function groups instead of vague capability claims.
Operational fit
Workflows, users, and connected modules show where the module belongs.
Governance proof
RBAC, audit, SIEM, approvals, and reporting are surfaced as first-class concerns.
Review path
Public pages link back to app routes so reviewers can compare page claims to product surfaces.