General ledger control
- Chart of accounts
- Journal posting
- Reversal workflow
- Period controls
ບໍ່ພົບການເຊື່ອມຕໍ່ອິນເຕີເນັດ
ກຳລັງພະຍາຍາມເຊື່ອມຕໍ່ໃໝ່
ມີບາງຢ່າງຜິດພາດ!
ກຳລັງພະຍາຍາມເຊື່ອມຕໍ່ໃໝ່
ການເງິນ ແລະ ລາຍຮັບ
Financial control for accounts, journals, budgets, reports, tax evidence, and close readiness.
| ພື້ນທີ່ | ສະຖານະ | ຫຼັກຖານ |
|---|---|---|
| Journals | Workflow controlled | Audit + idempotency |
| ລາຍງານ | Snapshot ready | Export checksum |
| Tax | Provider aware | Submission evidence |
ຂັ້ນຕອນຫຼັກ
Each workflow is written as an operational path, not a marketing claim, so buyers can understand the day-to-day module fit.
Feature checklist
How this module exchanges business context with the rest of ERPStack.
| Module | ຄວາມສຳພັນ |
|---|---|
| ການເກັບເງິນ | Invoices, payments, refunds, and revenue evidence |
| ຄ່າໃຊ້ຈ່າຍ | Approved claims and reimbursement accounting handoff |
| ເງິນເດືອນ | Payment approval, payslip, and reconciliation evidence |
| ສິນຄ້າຄົງຄັງ | Valuation readiness and stock movement financial impact |
Controls and management visibility expected from a serious ERP module.
AI coverage policy
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
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.
Buyers can see concrete function groups instead of vague capability claims.
Workflows, users, and connected modules show where the module belongs.
RBAC, audit, SIEM, approvals, and reporting are surfaced as first-class concerns.
Public pages link back to app routes so reviewers can compare page claims to product surfaces.