Code Lists

Code Lists

Overview

This page defines all code lists (enumerations / value sets) used across the phoss-ap data model and APIs.

---

Transaction Type

Distinguishes the purpose of an outbound transaction.

Name	Value	Description
Business Document	business_document	A regular Peppol business document sent from Sender Backend to a remote AP
MLS Response	mls_response	A Message Level Status response sent back to the original sending AP

---

Document Type

Indicates how the outbound document was submitted by the Sender Backend.

Name	Value	Description
Raw XML	raw_xml	Raw business document — the AP creates the SBDH envelope
Pre-built SBD	prebuilt_sbd	Complete Standard Business Document with SBDH already present

---

Outbound Transaction Status

Lifecycle status of an outbound transaction (business document or MLS response).

Name	Value	Description
Pending	pending	Stored in DB, awaiting processing
Rejected	rejected	Failed optional verification — no sending attempt will be made
Sending	sending	AS4 sending is currently in progress
Sent	sent	Successfully sent via AS4 and receipt confirmed
Failed	failed	Last sending attempt failed — scheduled for retry
Permanently Failed	permanently_failed	Max retries exhausted — no further attempts

---

Inbound Transaction Status

Lifecycle status of an inbound transaction.

Name	Value	Description
Received	received	Received via AS4 and stored in DB, awaiting processing
Rejected	rejected	Failed optional verification — no forwarding attempt will be made
Forwarding	forwarding	Forwarding to Receiver Backend is currently in progress
Forwarded	forwarded	Successfully forwarded to Receiver Backend
Forward Failed	forward_failed	Last forwarding attempt failed — scheduled for retry
Permanently Failed	permanently_failed	Max retries exhausted — no further attempts

---

Attempt Status

Outcome of a single sending or forwarding attempt.

Name	Value	Description
Success	success	The attempt completed successfully
Failed	failed	The attempt failed

---

Reporting Status

Whether a Peppol Reporting record has been created for a transaction.

Name	Value	Description
Pending	pending	Reporting record has not yet been created
Reported	reported	Reporting record has been created

---

MLS Reception Status

Status of MLS response reception for an outbound business document (as C2).

Name	Value	Description
Pending	pending	MLS response has not yet been received
Received AP	received_ap	MLS response received with code AP (Approved)
Received AB	received_ab	MLS response received with code AB (Accepted Blind)
Received RE	received_re	MLS response received with code RE (Rejection)
Not Applicable	not_applicable	MLS is not expected for this transaction (e.g., MLS response transactions)

---

MLS Sending Strategy

Controls when the AP (as C3) sends an MLS response back to C2. Configured per AP instance, captured per inbound transaction at reception time.

Name	Value	Description
Failure Only	FAILURE_ONLY	MLS response is sent only on rejection (RE)
Always Send	ALWAYS_SEND	MLS response is sent for all outcomes (RE, AP, or AB)

---

MLS Response Code

The response code included in an MLS message sent by C3 back to C2.

Name	Value	Description
Rejection	RE	Document failed verification or permanent delivery failure to Receiver Backend
Approved	AP	Successful delivery with confirmation from Receiver Backend
Accepted Blind	AB	Document forwarded without delivery confirmation capability

---

Duplicate Detection Mode

Configurable behavior when a duplicate is detected on either detection level.

Name	Value	Description
Reject	reject	Duplicate message is rejected at the AS4 level
Store and Flag	store_and_flag	Duplicate is stored in the DB but flagged per detection level

---

Forwarding Mode

The method used to deliver received documents to the Receiver Backend. Configured per AP instance.

Name	Value	Description
HTTP POST (async)	http_post_async	SBD is POSTed to the Receiver Backend; reporting is triggered asynchronously later
HTTP POST (sync)	http_post_sync	SBD is POSTed to the Receiver Backend; C4 country code is returned synchronously in the response
S3 + Link	s3_link	SBD is stored in S3; a link/reference is forwarded to the Receiver Backend
SFTP	sftp	SBD is uploaded to the Receiver Backend via SFTP

---

Submit Response Status

Response status returned by the outbound submit APIs.

Name	Value	Description
Queued	queued	Document was accepted and stored for processing
Not Queued	not_queued	Document was not accepted (e.g., verification failure, shutdown in progress)