Tenant billing
- Subscriptions
- Invoice history
- Payment methods
- Usage evidence
재무 및 매출
Billing & Marketplace
Tenant billing, invoices, payment methods, refunds, module marketplace subscriptions, and provider-readiness evidence.
통합 준비됨
Evidence-first module page
Primary users
Platform operator
Billing admin
Tenant owner
Marketplace reviewer
App-derived visual
Billing and marketplace workspace
Invoices
Snapshot ready
제공자
Readiness tracked
Marketplace
Install audited
| 영역 | 상태 | 증거 |
|---|---|---|
| Invoices | Issued snapshot | Line evidence |
| Payments | Provider aware | Webhook proof |
| Marketplace | Subscription tracked | Install audit |
핵심 워크플로
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
Review tenant subscription and invoice history
Step 2
Manage payment methods, payments, and refunds
Step 3
Monitor marketplace modules and revenue-share evidence
Step 4
Prepare provider certification and production-readiness checks
Feature checklist
Capabilities grouped the way operators look for them.
Payment operations
- Payment recording
- Refund controls
- Webhook evidence
- Settlement readiness
Marketplace control
- 모듈 카탈로그
- Install lifecycle
- Review state
- Revenue share
Connected module map
How this module exchanges business context with the rest of ERPStack.
| Module | 관계 |
|---|---|
| 회계 | Revenue, payment, refund, and settlement evidence |
| Tenant Management | Tenant limits, subscription state, and usage |
| 보안 운영 | Payment webhook and refund security events |
| BI | Revenue, marketplace, and subscription analytics |
Governance and reporting
Controls and management visibility expected from a serious ERP module.
거버넌스
- Payment-provider readiness
- Refund override monitoring
- Marketplace install audit
- Revenue-share evidence
보고서
- Tenant billing
- Invoice history
- Marketplace revenue
- Provider settlement
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 L2 ready| Coverage claim | Current AI coverage: Billing and Marketplace L2/L2 ready through the official Agent Tool Registry. |
|---|---|
| Governance evidence | Governance evidence: 2 registered tools, 2 evaluation cases, tenant/RBAC/safe-mode registry controls, and AI log evidence. |
| Scheduled monitor | Scheduled monitor readiness: not in the current proactive-agent monitor wave. |
| 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.