Product referenceTCA Peppol UAE

TCA Peppol UAE for Business Central

Functional coverage, operating behavior, requirements, and responsibilities.

A native AL extension for connecting Microsoft Dynamics 365 Business Central directly to the TCA e-invoicing platform.

Business Central prepares supported invoice and credit-note data, validates it against the implemented UAE PINT AE rules, builds the XML and sends it directly to TCA. There is no Lab0-hosted middleware between the customer’s Business Central environment and the ASP.

Lab0 develops and maintains the Business Central extension in partnership with TCA. The accredited ASP platform and network service are operated by TCA/Suntech Business Solutions DMCC. An active TCA account and separate TCA service agreement may be required.

Current functional coverage

Outbound documents

The extension currently handles:

  • Tax Invoice — document type 380.
  • Tax Credit Note — document type 381.
  • Commercial or out-of-scope Invoice — document type 480.
  • Commercial or out-of-scope Credit Note — document type 81.
  • Self-Billed Tax Invoice — document type 389.
  • Self-Billed Tax Credit Note — document type 261.
  • Dedicated deemed-supply processing using document type 380.

The extension determines the final filed document type from the document, VAT treatment, company registration and related configuration.

VAT and transaction handling

The extension supports the following UAE VAT categories:

  • S — standard-rated.
  • Z — zero-rated.
  • E — exempt.
  • O — out of scope.
  • AE — reverse charge.
  • N — margin scheme.

Supported transaction characteristics include:

  • Free Trade Zone.
  • Deemed supply.
  • Margin scheme.
  • Summary invoice.
  • Continuous supply.
  • Disclosed agent.
  • E-commerce.
  • Export.

Conditional information such as beneficiary identifiers, principal TRNs, invoicing periods, delivery addresses, exemption codes and reverse-charge classifications is validated when applicable.

Pre-posting validation

The extension can check supported documents while they are still editable.

When validation before posting is enabled, an in-scope document with missing or inconsistent e-invoicing information can be stopped before posting. Documents marked outside the UAE e-invoicing scope continue through normal Business Central posting without being filed.

The validation is an implementation safeguard. Final acceptance is determined by TCA and the applicable UAE network and authority processes.

Automatic and manual submission

Supported posted documents can be:

  • Sent manually from the posted document.
  • Sent automatically after posting.
  • Previewed and validated before a live submission.

Network failure does not reverse the accounting posting. Submission follows a separate lifecycle that can be investigated and retried safely.

Status tracking

The extension records:

  • Submitted.
  • Processing.
  • Delivered to the buyer’s Access Point.
  • Completed by TCA.
  • Rejected.
  • Error.

It also records separate buyer-Access-Point and authority-processing information when TCA provides it.

Background jobs can:

  • Poll the status of outbound documents.
  • Stop polling terminal documents.
  • Retrieve newly received documents.
  • Surface rejected or failed documents to users.

Inbound documents

The extension retrieves received documents from TCA and stores their original XML before parsing.

It can:

  • Stage incoming supplier invoices and credit notes.
  • Match a supplier to a Business Central vendor using the TIN.
  • Match an order reference to an open purchase order.
  • Route inbound self-billed documents as the company’s sales, rather than incorrectly treating them as purchases.
  • Require user verification.
  • Create draft purchase or sales documents after approval.
  • Preserve malformed documents for manual handling.

Inbound conversion creates a draft. It never automatically posts the resulting accounting document.

Accepting or rejecting an inbound document in Business Central is currently an internal decision only. It does not send an Invoice Response to the supplier.

Corrections and safe retries

The extension prevents uncontrolled duplicate submission.

It distinguishes between:

  • A document still being processed.
  • A completed document that requires a credit note.
  • A rejected document that TCA permits to be resubmitted.
  • A submission whose registration outcome is unknown and must be reconciled before retrying.

Credit notes inherit the relevant filed history from their original invoice instead of recalculating that history using configuration that may have changed.

Security and data handling

  • The TCA client secret is stored using Business Central Isolated Storage.
  • Access tokens are handled as secret values.
  • Authorization headers are not written to the local API log.
  • Presigned storage credentials are removed from logged URLs.
  • Business Central communicates directly with TCA and storage URLs supplied by TCA.
  • Operational telemetry does not intentionally contain invoice XML, customer details, credentials or access tokens.

Requirements

Customers require:

  • Microsoft Dynamics 365 Business Central Online.
  • A supported Business Central version. The current build targets application version 28.0 or later.
  • An active TCA organization.
  • TCA API credentials with the necessary permissions.
  • Completed seller, customer, vendor, item and VAT configuration.
  • Permission for the extension to make outbound HTTP calls.
  • Business Central Job Queue configuration for unattended status and inbound polling.
  • Appropriate Lab0 permission sets assigned to users.

Important limitations

  • The extension supports UAE PINT AE processing through TCA; it is not a general-purpose global e-invoicing application.
  • The extension does not itself operate an Accredited Service Provider network.
  • A successful API request does not, by itself, prove final network or authority acceptance.
  • The customer remains responsible for source-data accuracy, tax setup and review of rejected documents.
  • Inbound drafts are never automatically posted.
  • Business Central accept/reject decisions for inbound documents are currently local only.
  • The connector does not provide tax, legal or accounting advice.

Ownership

TCA Peppol UAE for Business Central is developed and maintained by Lab0. TCA/Suntech provides and operates the connected ASP service. Microsoft Dynamics 365 Business Central and Microsoft Marketplace are products and services of Microsoft. Each party remains responsible for its own product or service.