Skip to main content
Download OpenAPI

Re-Verification & Disconnection Lifecycles

Account management is not a one-time event. Beyond initial provisioning (LINK), our unified compliance engine dynamically manages secondary lifecycle scenarios based on changes initiated inside your EmaraTax portal.

Data Updates & Profile Alignment​

If your company changes its official corporate registration email, modifies its trade name, or updates its constitutional tax group mapping, you must trigger a re-verification flow from EmaraTax.

Zero Downtime Guarantees

When performing a REVERIFY action, your organizational status remains strictly ACTIVE across our production routers throughout the entire 4-step sync sequence.

Your inbound and outbound B2B e-invoicing pipelines will experience zero network downtime while our background systems map out your updated government records.

Graceful Network Offboarding​

If your organization explicitly requests a disconnection or transitions to a separate infrastructure framework, a DELINK lifecycle sequence is initiated.

The Offboarding Protocol Sequence:​

  1. Identity Guard: The offboarding user must pass the initial Step 1 EmaraTax credential check to prove corporate ownership before teardown commands are authorized.
  2. Active Buffer: During the provisioning and metadata unmapping phases (Steps 2 and 3), your routing node is kept provisionally ACTIVE to handle in-flight documents and prevent immediate network drops.
  3. Permanent Teardown: Upon successfully concluding Step 4, our systems execute an official disconnect from the UAE Central Registry and Peppol SMP systems, safely changing the local database profile state to INACTIVE.

Handling Connection Failures​

Because synchronization involves real-time cross-network handshakes across public infrastructure, occasional transient timeouts can happen.

If an error or network drop occurs during any step of the sequence, the A-Cube system records a public business milestone error log. Thanks to our stateful passport flow, you can simply prompt your system or browser client to hit the step again. The system will inspect your session token and seamlessly resume processing from the exact point it left off.

Last updated on