The 4 Onboarding Steps Explained
When the onboarding engine is triggered by EmaraTax, it processes your network alignment sequentially. Below is the technical and operational breakdown of what happens at each stage of the connection pipeline.
Step 1: Verification Gateway
The integration begins by validating your identity and establishing a secure communication context with the government nodes.
Operational Logic
-
Gateway Handshake: A-Cube securely transmits the identity parameters received from EmaraTax to the official UAE Federal Tax Authority (FTA) validators:
TIN(Tax Identification Number)Admin EmailAdmin Mobile(Optional parameter)authCode
-
Intent Mapping: When EmaraTax executes the redirect, the A-Cube Landing Page intercepts the URL parameters at runtime to determine the correct user experience and drive the orchestration:
- Implicit
LINK: If the redirect payload contains only theauthCode(without aTIN), the system automatically flags the intent as a first-time account registration. - User-Driven Option (
REVERIFY/DELINK): If the redirect payload already contains theTIN, it signals that the organization is already mapped. The A-Cube onboarding interface prompts the Account Admin to explicitly choose between two advanced lifecycle options:REVERIFY: To execute an existing account data update. Status remainsACTIVEto avoid trade interruption.DELINK: To request a graceful network offboarding. Status is kept active temporarily to offload routing.
- Implicit
-
Session Security: Once the government gateway approves the credentials and the intent is resolved, a secure, time-bound Integration Passport token is issued to track your specific session.
Step 2: Initialization
Once identity is verified, the system sets up your local tenant profile and local data routing configurations.
Operational Logic
- Lazy Rollback Guard: If you have an incomplete or crashed registration attempt from the past under the same
TIN, the provisioning engine automatically performs a cleanup, resetting stale network configurations before continuing. - Tax Identifier Validation: The system runs internal structure checks on your tax identifiers (such as enforcing the strict 15-digit layout rule for
TRNentries, while safely allowing null values for Non-VAT taxpayers). - Local Database Commit: Your legal entity schema is generated or updated, locking in the baseline state required to join the wider transactional framework.
Step 3: Peppol Network SMP Sync
With local profiles secured, your organization needs to become visible to other electronic invoicing participants globally.
Operational Logic
- SMP Registration: A-Cube connects to the global Peppol Service Metadata Publisher (SMP) infrastructure layer.
- Capability Mapping: The system registers your organization's unique participant identifier and maps its electronic document capabilities (e.g., standard invoices, credit notes, and business responses).
- Global Inbound Readiness: Once Step 3 concludes, your business profile becomes discoverable by any certified Access Point (AP) in the world, enabling automated inbound document routing straight to your node.
Step 4: Central Government Registry Activation
The final step completes the synchronization by binding your live profile directly to the central government network hooks.
Operational Logic
- Registry Synchronization: The network synchronization command is issued to the official UAE Government Central Registry to activate your live production compliance status.
- Status Promotion: Your company profile status transitions permanently to its final production state:
- Becomes
ACTIVEfor aLINKorREVERIFYaction. - Becomes
INACTIVEfor aDELINKaction.
- Becomes
Handling Retries During Failures
Because Steps 3 and 4 communicate in real time with external global and government network registries, a transient network lag or public gateway timeout can occasionally pause the sequence.
If a step fails to complete, do not restart the flow from EmaraTax. Thanks to the stateful architecture:
- The system keeps your exact progress saved inside the session token.
- You can simply hit the Retry action in our wizard.
- The pipeline will read your session status and automatically resume processing from the exact step that experienced the timeout.