Peppol UBL Invoice Generator
Pricing
from $10.00 / 1,000 invoice generateds
Peppol UBL Invoice Generator
Generate Peppol BIS Billing UBL from strict JSON and pass both the active 3.0.20-hotfix and announced 3.0.21 rule gates.
Pricing
from $10.00 / 1,000 invoice generateds
Rating
0.0
(0)
Developer
Kamer Ozkan
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
2 days ago
Last modified
Categories
Share
Strict JSON in. A generated and technically validated Peppol BIS Billing 3.0.20-hotfix + 3.0.21 forward gate artifact out.
The Actor calculates totals with decimal arithmetic, generates the target invoice, runs an independent pinned validation stack, stores only accepted artifacts, and returns a SHA-256 evidence record. A rejected artifact is not delivered or charged under pay-per-event pricing.
Input
Use invoice for one document or invoices for a batch of up to 100. Amounts and
quantities must be JSON strings such as "19.00", not floating-point numbers.
The input schema exposes the complete production v1 canonical model and the strict
product extension. Unknown fields are rejected instead of being silently ignored.
Production v1 capabilities
- Generate UBL Invoice and UBL CreditNote documents.
- Support negative invoices, line and document adjustments, prepayments, rounding, attachments, references, delivery, payment, and multiple VAT groups.
- Validate UBL Schema, CEN EN 16931, active Peppol rules, and the announced mandatory-transition rules in one call.
Required product context
Seller and buyer endpoint identifiers are required. Each document also needs a buyer reference or purchase-order reference.
Output
Each dataset row contains the technical assessment, artifact key, evidence key, hash, byte count, generator version, standard version, pinned ruleset, and bounded findings. The artifact and evidence JSON are private key-value store records.
For pay-per-event deployment, configure invoice-generated at exactly USD 0.01
and keep the synthetic apify-default-dataset-item event at USD 0. The
synthetic apify-actor-start event may have any nonnegative configured price;
every other event must remain free. The runtime refuses hosted non-PPE runs and
unsafe event maps before reading input. Local non-PPE execution remains
available for offline tests. A paid run charges only an artifact that was
validated, stored, and delivered.
Operational boundary
This Actor generates and validates the document. It does not submit to Peppol,
KSeF, SdI, or a French platform. It does not authenticate to an authority, create
a qualified signature, perform legal archival, assign an official network
identifier, or guarantee recipient or tax-authority acceptance. ACCEPTED means
the generated artifact passed the documented pinned offline technical gate.
