Document template · eu.trade.intracomm_listing
Intra-Community Transactions Listing
- Render-verified
- Official document
- Version 1.0.0
Periodic recapitulative statement of intra-community supplies, grouped by customer VAT ID and transaction code. Filed monthly or quarterly depending on member state and turnover threshold.
JSON Schema
Fields in this template
Data sent to the API is validated against the template’s JSON Schema before anything is rendered. This template defines 27 fields:
| Field | Required | Type | Description |
|---|---|---|---|
| declarant | Required | object | |
| declarant.name | Required | string | |
| declarant.vat_id | Required | string | |
| declarant.country_code | Required | string | |
| declarant.address | Optional | string | |
| declarant.contact_name | Optional | string | |
| declarant.contact_email | Optional | string | |
| period | Required | object | |
| period.frequency | Required | enum | |
| period.year | Required | integer | |
| period.month | Optional | integer | |
| period.quarter | Optional | integer | |
| entries | Required | array of object | |
| entries[].customer_vat_id | Required | string | |
| entries[].customer_country_code | Required | string | |
| entries[].customer_name | Optional | string | Optional — not all national authorities require the name; included for audit trail. |
| entries[].transaction_code | Required | enum | L = intra-community supply of goods; T = triangular transaction (Art. 141); S = supply of services under reverse charge. |
| entries[].amount | Required | number | |
| entries[].correction_of_period | Optional | string | If this line corrects a previous period, the YYYY-Qn or YYYY-MM identifier. |
| totals | Required | object | |
| totals.currency | Required | string | |
| totals.total_L | Optional | number | |
| totals.total_T | Optional | number | |
| totals.total_S | Optional | number | |
| totals.grand_total | Required | number | |
| filed_on | Optional | date | |
| reference | Optional | string |
POST /render
Generate it
One POST /render call: send your JSON, get the finished PDF back. Or skip the JSON entirely and describe the document in plain language on chut.app.
curl -X POST https://api.papii.eu/render \
-H "X-API-Key: YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"template": "eu.trade.intracomm_listing",
"data": { ... },
"options": {"language": "en"}
}' -o intracomm-listing.pdf Frequently asked questions
What is “Intra-Community Transactions Listing”?
Periodic recapitulative statement of intra-community supplies, grouped by customer VAT ID and transaction code. Filed monthly or quarterly depending on member state and turnover threshold. On papii this document is available as template eu.trade.intracomm_listing: a JSON Schema plus a deterministic PDF renderer, so the same data always produces the same document.
Can I generate a Intra-Community Transactions Listing with AI?
Yes. chut.app — the AI back office papii powers — fills this template from a plain-language description: you describe the document in one sentence, the AI structures the data, papii validates it against the schema and renders the PDF. Developers can also call the papii API directly with structured JSON.
Is the Intra-Community Transactions Listing template legally compliant?
This template is render-verified: its schema, sample data and PDF output are automatically tested on every release. It is published with status “ready”, meaning it has not yet been through papii’s final legal review. Where it references specific legislation, that is stated in the template description — always have a professional check documents with legal effect before relying on them.