See what changed in ZoikoTax Coverage — and verify what is current.
Track governed public changes to capability readiness and pack/release context by market and scope. Status & Releases explains the chronology; Coverage Overview remains the source for current public availability.
Events publish only from authoritative coverage/release data. A release event applies only to the stated market, capability and scope.
Chronology provides context. The current Coverage route resolves the state that applies now.
What is ZoikoTax Status & Releases?
It is the public chronology for governed Coverage changes. It records what changed, where, for which capability and scope, then hands readers to Coverage Overview to verify what is current.
How to read Status & Releases
Read all five dimensions together. A state without its scope, time basis and proof route is incomplete.
Event
The governed public record of a change, with a stable event label and neutral summary.
State
The stated transition or event outcome. Color supports the label; it never replaces it.
Scope
The exact market, capability, obligation or workflow boundary to which the event applies.
Time
Effective, published and verified are separate labels. They answer different questions.
Proof
Public-safe provenance and handoffs show how the record was governed and where to verify current truth.
When the stated change applies to its exact scope.
When the public chronology record became available.
When the public current-state handoff was last checked.
State vocabulary
These labels describe bounded operating states, not a celebratory maturity ladder. Always read the explicit text definition and scope.
Coverage content is being researched. It is not available for governed operation.
Coverage content is under governed validation. Production use is not represented.
A bounded pilot may apply only to the stated participants, capability and scope.
The stated capability and scope are available in a governed production context.
ZoikoTax-managed operation applies to the expressly stated capability and scope.
The stated capability and scope are temporarily not represented as currently available.
The stated Coverage has been removed from current public availability.
Current state could not be verified. No availability inference should be made.
A change can move in either direction. Historical state does not determine current state; use the current Coverage handoff.
View Current CoverageLatest governed changes
Filter by the dimensions that define an event. The examples below demonstrate the pattern only and do not represent live Coverage.
All four populated records use fictional markets, IDs, scopes and non-real date labels. They are interface specimens, not live ZoikoTax Coverage data.
Illustrative indirect tax determination scope for a fictional service class.
The stated illustrative scope moved from validation into a bounded pilot context. No broader market inference is made.
Illustrative filing scope
The stated historical filing scope changed to SUSPENDED. This record does not assert a cause or describe current market-wide Coverage.
Illustrative outbound document exchange scope for a fictional clearance route.
The public scope description changed. No capability-wide state transition is represented by this specimen.
Illustrative managed return preparation and submission scope.
The stated illustrative scope moved to a managed operating context. The event does not claim universal customer activation.
EVT-1002 · historical public status
A complete synthetic specimen showing how a governed event can explain chronology without pretending to be current truth.
EVT-1002, Illustrative Market B, all scopes and all date labels below are illustrative synthetic data. This specimen is not a production record.
EVT-1002 · Compliance & Filing
Neutral summary
For the stated illustrative filing scope, the public chronology records a historical transition from PRODUCTION to SUSPENDED. No cause is asserted by this synthetic specimen.
What this does not mean
It does not establish current country-wide status, incident cause, customer impact, legal correctness, uptime or the state of another capability or scope.
Pack / release context
A fictional pack context may accompany this event. Pack lifecycle and activation remain separate; a pack release does not imply every capability changed.
Current-state handoff
Chronology does not determine what applies now. Resolve current market × capability × state × scope in Coverage Overview.
Public-safe evidence & provenance
Bounded metadata demonstrates governance without exposing restricted sources.
This public event record is not transaction-level replay proof and does not disclose restricted authority material.
Edge and degraded states
The chronology must state uncertainty directly. No results does not mean no Coverage, and stale chronology must not be silently presented as current.
No records
No public chronology records are available for this route. Do not infer current Coverage.
No results
No events match the selected filters. This does not mean no Coverage exists.
Status unavailable
Current state could not be verified. Availability must not be inferred.
Dependency / source error
An authoritative dependency could not be read. Stale chronology is not shown as current.
Historical
This event describes a prior state. Verify the current state before acting.
SUSPENDED
The stated scope is temporarily not represented as currently available.
WITHDRAWN
The stated Coverage has been removed from current public availability.
Stale chronology blocked
A chronology view that cannot establish freshness is withheld rather than presented silently.
Current Coverage is the source of truth
Chronology explains how Coverage changed. It never overrides the current market × capability × state × scope truth published in Coverage Overview.
Pack releases provide context—not blanket capability change.
Packs own lifecycle, versions and governed activation context. A pack release does not imply that every capability, scope or current state changed.
Verify Coverage by capability
Each route opens current scope for the named capability. A route is not itself an availability claim.
Tax Determination
Inspect current market, service and determination scope.
Regulatory Obligations
Inspect current obligation and responsibility scope.
Compliance & Filing
Inspect current return, filing and workflow scope.
Remittance
Inspect current payment and remittance scope.
E-Invoicing & CTC
Inspect current document and exchange scope.
Managed Compliance
Inspect current managed operating scope.
A governed change record—with explicit limits.
A public status event establishes a governed Coverage change. It is not transaction-level replay proof, certification, residency proof, uptime or SLA evidence, or an incident declaration.
Evidence & Replay
Follow reconstructable outcome evidence for transaction-level proof.
Trust
Review governance, controls and assurance boundaries.
Security
Review security architecture and control posture.
Privacy
Review privacy commitments and processing boundaries.
Residency
Review separate data-residency information; status is not proof.
Developers
Use APIs and implementation guidance for governed integrations.
Support
Ask for assistance without turning chronology into an incident feed.
AI assists. Approved rules decide. Evidence proves.
Four public surfaces, kept distinct
Each public route has one canonical job. Keeping them separate prevents chronology, pack lifecycle and product delivery from being mistaken for current Coverage.
Coverage Overview
Canonical current market × capability × state × scope truth.
Country & Regulatory Packs
Pack lifecycle, versions and governed activation context.
Status & Releases
THIS SURFACEPublic chronology of governed Coverage changes.
Product Release Notes
Product delivery changes; not a Coverage availability route.
Questions buyers ask about Coverage chronology
Bounded answers keep status history, current Coverage and product delivery from being conflated.
What is Status & Releases?
Does an event mean the whole country is supported?
Is this the same as product Release Notes?
What happens if current status cannot be verified?
Does PRODUCTION mean every customer transaction is legally correct?
Can AI change a Coverage state?
Inspect the truth before the meeting.
Review current Coverage, governed chronology and public evidence routes first. Evidence is not gated behind lead capture.