Define measures
Separate objects, retained bytes, jobs, verifications, timestamps and exports; billable units belong to the contract.
MOBILE-ID · TRUSTED LTANS
Management Reporting
Aggregate operational data and contracted usage units with source-transaction traceability.
Outcome and scope
Explain operational and usage figures from source transactions without conflating intake, completion and billing units.
Documentation scope Workflow design and integration contract; operational configuration is confirmed per environment.
| Prepare | Receive |
|---|---|
| Reports on records, jobs, storage, verification, renewal and exports. | Tenant/period reports and discrepancies to resolve before closing. |
Participants: Service owners, operations, commercial reconciliation and audit.
Workflow and decision points
Collect with provenance
Retain tenant, period, eventId and relevant archiveId/jobId, distinguishing transaction and ingestion times.
Deduplicate and reconcile
Replay must not increase usage; failed jobs and late completions require explicit adjustment rules.
Close and export
Expose unreconciled amounts, period scope and report revision. Corrections link to the closed report.
States, guards and authority
| Current | Guard | Actor | Next | Artifact / recovery |
|---|---|---|---|---|
| Open period [model] | Deduplicated event with provenance | Audit & Reporting | Projection updated [model] | Separate transaction/ingestion time and tenant; replay does not recount. |
| Unreconciled [model] | Compare source transaction, revision and unit | Usage reconciliation | Reconciled / discrepancy [model] | Usage is not an approved charge; pricing belongs to the contract. |
| Closed period [model] | Approved late adjustment | Report owner | Adjusted revision [model] | Keep adjustment provenance and earlier reports; no silent edits. |
Exceptions and controls
| Situation | Action | Boundary |
|---|---|---|
| Duplicate event | Deduplicate by eventId within tenant context. | No second charge. |
| Late transaction | Apply an auditable adjustment. | Do not silently edit approved reports. |
| Missing source data | Report unreconciled amounts. | Do not present unconfirmed totals as settled. |
Authorization, approval and recovery
Distinguish accepted requests, completed jobs, retained storage and billable events. billing:read is scoped to the matching tenant.
Replayed events must not be double-counted; deduplicate by eventId and reconcile archiveId/jobId before closing.
Reconciliation artifacts and acceptance
Deduplicate replayed events by eventId, reconcile archiveId/jobId and distinguish intake requests from completed billable results.
- Replaying an
eventIdleaves totals unchanged; a valid adjustment records its revision and source. - audit:read alone does not grant billing:read or cross-tenant visibility.
Integration and data contract
| API | Application scope | Documentation |
|---|---|---|
| GET /v1/audit-records | audit:read | Audit and Reporting API |
| GET /v1/usage-reports | billing:read | Audit and Reporting API |
Technical input and references
| Element | Definition |
|---|---|
| Input | Transaction logs, plan-specific usage units, quota, reporting period and tenant identifier. |
| Output | Usage report, reconciliation differences and billing input; no unapproved pricing or quotas are published. |
Execute and reconcile a scenario
| Element | Action |
|---|---|
| Synthetic ID | usage-test-001 |
| Task | Fix measurement period, units, source transactions and duplicate exclusions. |
| Acceptance case | Reconciliation does not recount retries; separate storage, operations and bandwidth. |
These are business test criteria; synthetic packages alone do not establish backend execution or valid ERS.