Peppol UBL to JSON Parser
Pricing
from $5.00 / 1,000 document processeds
Peppol UBL to JSON Parser
Parse Peppol BIS Billing UBL invoices and credit notes into stable JSON with document-level technical conformance findings. Transport is not included.
Pricing
from $5.00 / 1,000 document processeds
Rating
0.0
(0)
Developer
Kamer Ozkan
Maintained by CommunityActor stats
0
Bookmarked
1
Total users
0
Monthly active users
a day ago
Last modified
Categories
Share
Validate Peppol BIS Billing UBL Invoice and CreditNote documents and return the shared EN 16931-oriented JSON contract.
What it does
- Accepts UBL 2.1 Invoice and CreditNote documents.
- Detects Peppol CustomizationID, ProfileID, document type, and source digest.
- Runs XSD, CEN EN 16931, and Peppol document rules through the pinned KoSIT runtime.
- Uses the active Peppol BIS Billing
3.0.20-hotfixruleset, including the mandatory0245electronic-address scheme update. - Keeps upcoming
3.0.21disabled until its effective date and artifact pin are active. - Normalizes the full declared UBL binding with business-term trace entries.
- Can unwrap exactly one business document from an SBDH envelope when
unwrapSbdhis enabled. - Can store KoSIT XML and XHTML reports as opt-in KVS artifacts.
When SBDH is unwrapped, the result explicitly reports
UNWRAPPED_NOT_VALIDATED. The SBDH header is not silently treated as
validated.
Product boundary
Peppol here means Peppol BIS Billing document rules only. This Actor does
not provide:
- an Access Point;
- SMP or SML participant discovery;
- AS4 transport;
- invoice sending or receiving;
- a delivery receipt or network-status service;
- Peppol certification or accreditation.
The Actor also does not make legal, tax, authenticity, signature, or recipient acceptance decisions.
Release state
The processing engine and Actor contract are feature-complete. The source
contains a fail-closed pay-per-event charge path for document-processed at
exactly $0.005 per evaluated document. Local non-PPE results remain
billable: false; a hosted run stops before processing unless the event and
price contract are active. The synthetic apify-actor-start event is allowed,
while apify-default-dataset-item must cost USD 0. Apify Console
configuration, a Docker image build, and hosted lifecycle, charge-count, and
budget-limit smoke tests remain before Store publication.
