Skip to content

Electronic Invoicing ​

Backlog fieldValue
Story IDAP-GS-005
EpicGeneral Settings
Story typeBusiness workflow
Review statusDraft - business analyst and business owner review required
Source evidenceAppsPortal.Apis controller, application command/query handlers, validators, domain entities, and matching MFE workflow where available
Last source review2026-07-10

User story ​

As tax administrators, I want to configure ETA/ZATCA connectivity, devices, tokens, and sending options so that eligible invoices can be submitted and tracked.

Acceptance criteria ​

  1. Only authorized users can view or execute the feature's actions.
  2. Required business data, active dependencies, tenant/branch scope, and current document state are validated.
  3. Invalid requests return actionable validation errors without applying a partial change.
  4. Search, list, view, print, and export operations use the same authorized business scope.
  5. Material create, edit, status, approval, posting, reversal, and integration actions are auditable where applicable.
  6. Financial or stock effects are applied atomically and no more than once.

Business rules ​

Required ​

Country authority configuration, credentials/token/device/signature service, taxpayer identity, environment, and enabled document types are required.

Optional or conditional ​

Sending mode, scheduling, notifications, and optional channels are configurable.

Action behavior ​

Submit validates eligible posted documents, signs/maps them, sends once, and stores request/response/status/history.

Blocking rule or downstream effect ​

Failed/rejected submissions do not alter ERP posting and must remain retryable without duplicate authority documents.

Frontend page coverage ​

The following UI coverage is sourced from the pulled MFE route configuration. A Module-level supporting artifact mapping is evidence of a reachable screen, but requires BA confirmation that it belongs to this story rather than a more specific feature story.

Route/pageComponentModeRoute permission/guardMapping confidenceSource
electronic-integrationZatcaComponentList/navigationPermission: AppGeneralSettingsPermissions.ElectronicIntegration_View,; Guards: PolicyAuthGuardFeature token matchapps/erpHome/src/app/remote-entry/admin/admin-routing.module.ts:95

Observed frontend fields and validation ​

ComponentControlObserved frontend ruleComponent source
ZatcaComponentactivationCodeRequired in component validatorapps/erpHome/src/app/remote-entry/admin/pages/zatca/zatca/zatca.component.ts
ZatcaComponentenvironmentRequired in component validatorapps/erpHome/src/app/remote-entry/admin/pages/zatca/zatca/zatca.component.ts

Observed frontend actions ​

ComponentClick action/handlerBusiness review requirementComponent source
ZatcaComponentdeactivateDeviceDocument the enabled state, permission, input context, resulting API or navigation effect, success refresh, and concrete failure behavior for this handler.apps/erpHome/src/app/remote-entry/admin/pages/zatca/zatca/zatca.component.ts
ZatcaComponentonConfirmDocument the enabled state, permission, input context, resulting API or navigation effect, success refresh, and concrete failure behavior for this handler.apps/erpHome/src/app/remote-entry/admin/pages/zatca/zatca/zatca.component.ts

Page-specific frontend acceptance criteria ​

  1. electronic-integration - List/navigation: Load an authorized paged/searchable list or navigation page; preserve filters/sort/paging and expose only permitted row and bulk actions. Security observed: Permission: AppGeneralSettingsPermissions.ElectronicIntegration_View,; Guards: PolicyAuthGuard

Internal Documentation — Microtec