Breadcrumbs

IMOS - Tax Portal Workflow

image-20251021-063431.png

Invoice Data Exchange Documentation

1. Overview and Constraints

This document details the data exchange workflow for invoice processing. The entire communication process is based on XML messages that must adhere to standard message schemas.

Key Constraints

  • Format: All messages sent and received must be in XML format.

  • Veson Role: Veson does not provide any data transformation services. Client systems are responsible for ensuring that all inbound data meets the standard Veson API message schemas.

2. System Responsibilities

The overall process is divided into two primary areas of responsibility: Veson (IMOS) and the Client.

System

Responsibility

Role

IMOS

VESON

Initiates the invoice flow, validates the invoice status, post the invoice, and transmits the final XML.

Middleware

Client

Receives the initial invoice XML, transforms the message as required and return IRN and QRN to IMOS.

Accounting System

Client

Receives the final, posted invoice XML from IMOS for downstream processing.

3. End-to-End Invoice Processing Flow

The following steps describe the sequential flow of an invoice from creation in IMOS through final distribution to Shipnet.

3.1. Invoice Initiation and Status Check (IMOS)

  1. IMOS Processing: IMOS receives or processes an invoice message.

  2. Status Decision Point: IMOS performs a check to determine the invoice's status: "Is Invoice Final?"

    • If No (Non-Final): The message is blocked from sending, and the workflow terminates for this message.

    • If Yes (Final): IMOS proceeds to Save Invoice.

3.2. Transmission and Processing by EY

Once the invoice is final and saved in IMOS, the process moves to the client's system, EY.

  1. Send Invoice XML: IMOS transmits the invoice XML message to Middleware.

  2. Receive and Transform: Middleware receives the Invoice and executes a Transform message step to adapt the data as needed for its internal systems.

  3. Return Data to IMOS: Middleware is responsible for sending the unique IRN and QRN back to IMOS by consuming the IMOS API invoiceImport XML. Middleware then Sends IRN and QRN back to IMOS.

3.3. IMOS Finalization

Upon receiving the necessary reference numbers from EY, IMOS completes its internal posting process.

  1. Ingest References: IMOS Ingests the QRN and IRN received from Middleware.

  2. Post Invoice: IMOS officially Posts the Invoice.

3.4. Final Transmission to Shipnet

Following the successful posting, the final invoice data is distributed to Accounting System.

  1. Send Final Invoice XML: IMOS transmits the final, posted invoice XML message to Middleware.

  2. Middleware Reception: Middleware Receives the Invoice for its final step in the process.

4. Specific Transmission Filters

The communication from IMOS to Middleware is governed by a strict filter to maintain data quality and compliance:

  • Xpath Filter: IMOS will only send messages to Middleware if the invoice possesses a Final status. This status check is enforced by an Xpath Filter within IMOS.