Fiscal API
Fiscal issuance, reconciliation, and governance endpoints for PT operations.
reference • updated 2026-03-15
Goal
Control fiscal document issuance, reconciliation, and setup readiness to keep compliance stable without interrupting commercial operations.
Primary endpoints
| Endpoint | Function | Typical usage |
|---|---|---|
GET /v1/fiscal/overview | aggregate fiscal status | daily monitoring and operational handover |
POST /v1/fiscal/documents | issue fiscal documents | after eligible commercial events |
POST /v1/fiscal/reconciliation | reconcile discrepancies | daily/month-end close or incident response |
GET /v1/fiscal/setup-state | validate fiscal readiness | before go-live and after config changes |
Issuance prerequisites
- Organization fiscal profile validated.
- Series/sequences active in the target mode (
testorlive). - Fiscal provider integration healthy and monitored.
Recommended issuance flow
11) Check setup
Callsetup-stateand block issuance on critical pending items.22) Issue document
Calldocumentswith consistent payload and idempotency.33) Persist outcome
Store fiscal identifiers and final status.44) Reconcile
Runreconciliationto close pending mismatches.
Typical errors
| Code | Common cause | Mitigation |
|---|---|---|
400 | incomplete fiscal payload | validate required fields before submit |
409 | sequence/series conflict | resync sequence state and retry safely |
422 | fiscal rule not satisfied | review document type/regime/customer data |
503 | transient provider outage | retry with backoff and alert operations |
Recommended controls
- Alerts for fiscal backlog and per-organization error ratio.
- Daily reconciliation with defined correction SLA.
- Audit trail for changes to series, profile, and permissions.