Terms of service
Last updated draft — not yet published
This is a working draft prepared ahead of general availability. It has not been reviewed by legal counsel and is not a final, binding agreement. During the early-access phase, the actual terms of engagement are whatever is agreed directly with each design partner in writing; this page describes the shape those terms are expected to take.
1. What the service is
AE Compliance is middleware that ingests invoice data, normalizes it to the PINT-AE format, validates it against the official MoF mandatory field set and the Peppol PINT-AE VAT codelist, persists it to a tenant-isolated ledger, and routes it to the tenant’s own chosen MoF-Accredited Service Provider (ASP) for signing, exchange, and FTA reporting. We do not connect to Peppol or the FTA directly, and we are not ourselves an Accredited Service Provider — the tenant must hold that relationship with their chosen ASP independently.
2. Tenant responsibilities
- Tenants are responsible for the accuracy of the data they submit to the API, and for holding a valid relationship with their chosen ASP.
- Tenants are responsible for keeping their API keys confidential and for using the key-rotation flow if a key is compromised.
- A validation pass (an
is_valid: trueresult) reflects conformance to the checks this service runs. It does not itself constitute legal advice or a guarantee that the FTA will accept the invoice.
3. Service availability
During the early-access phase, this service is offered without a published service-level agreement. An invoice is never silently dropped by design — every non-terminal outcome results in a persisted status, an audit record, and a failure webhook to the tenant — but no specific uptime commitment is made until a formal SLA is agreed with a given tenant.
4. Data handling
Data submitted through the API is handled as described in our privacy policy. We act as a processor of any personal data embedded in submitted invoices, on the tenant’s instructions.
5. Fees
No public pricing is published as of this draft. Fees, if any, during the early-access phase are agreed individually and in writing with each design partner.
6. Changes
This is a pre-launch draft. It will be reviewed by legal counsel, revised, and re-published with a real effective date before general availability.