Terms of service

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

Kodowo 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.

Kodowo is also not a registered Tax Agent and does not provide tax advisory, tax return preparation, or FTA representation services. It is software; customers remain responsible for engaging their own tax professionals.

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: true result) 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.
• Submissions made through an automated channel, whether the API or an SFTP connector, are the tenant’s responsibility to the same extent as a submission the tenant confirms manually in the dashboard. This includes files the tenant or its systems place in the tenant’s SFTP directory, and the consequences of whichever auto-submit policy the tenant has selected for that channel.

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. Business verification

Access to live invoice transmission is conditional on completing business verification: providing a valid UAE Trade License and FTA TRN Certificate and passing our internal review. We may decline, or later suspend, verification at our discretion where documents are incomplete, expired, inconsistent with the tenant’s account details, or where we have reasonable grounds for concern. Sandbox validation remains available while verification is pending.

Submitting forged, altered, or misleading documents is a material breach of these Terms and grounds for immediate termination. We may require re-verification when documents expire or account details change materially.

5. 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.

6. 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.

7. 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.