> ## Documentation Index
> Fetch the complete documentation index at: https://docs.chift.eu/llms.txt
> Use this file to discover all available pages before exploring further.

# a3factura

> Connect a3factura to your product through Chift's unified Invoicing API.

Chift connector information - invoicing

> [accordion] Overview legend
>
> > <table><thead><tr><th>Column</th>
> > <th>Value</th>
> > <th>Meaning</th></tr></thead>
> > <tbody><tr><td>Geography</td>
> > <td>🇫🇷 FR · 🇧🇪 BE · …</td>
> > <td>Countries where the connector is officially supported.</td></tr>
> > <tr><td rowSpan="3">Software type</td>
> > <td>SaaS</td>
> > <td>Through API.</td></tr>
> > <tr><td>On-premise (local agent)</td>
> > <td>Software running locally — installation of a local agent is
> > required.</td></tr>
> > <tr><td>On-premise (API)</td>
> > <td>Software running locally — API available.</td></tr>
> > <tr><td rowSpan="2">Status</td>
> > <td>🔵 Live</td>
> > <td>Connector is generally available and production-ready.</td></tr>
> > <tr><td>🟣 Beta</td>
> > <td>Connector is in beta — usable in production but may still evolve.</td></tr>
> > <tr><td>Multi folder</td>
> > <td>✅ Yes / ❌ No</td>
> > <td>Connection to multiple accounting folders at the same time (see
> > [accounting folders guide](https://docs.chift.eu/unified-apis/accounting/concepts/folder/multi-folder.md)
> > ).</td></tr>
> > <tr><td>Rate limits</td>
> > <td>✅ No / ❌ Yes</td>
> > <td>Whether the target software sets rate limits on API calls.</td></tr>
> > <tr><td rowSpan="3">API keys</td>
> > <td>❎ No</td>
> > <td>No API keys required (OAuth2 client secret and client ID). No
> > requirements to activate the connector — you can create a
> > connection.</td></tr>
> > <tr><td>🔑</td>
> > <td>Keys are required to activate the connector. Chift cannot act as
> > intermediary to obtain them; we can still assist with steps to get
> > keys directly from the software provider.</td></tr>
> > <tr><td>🔑 ☑️ via Chift</td>
> > <td>Keys are required to activate the connector. You can go through
> > Chift to get the keys (intermediary or partnership keys). An
> > approval process may still apply, but you do not need to request
> > keys from the vendor on your own.</td></tr>
> > <tr><td rowSpan="3">Approval / certification process</td>
> > <td>⚡ Instant</td>
> > <td>No keys required, or Chift can encode their keys for you when
> > requested. Activation is instantaneous.</td></tr>
> > <tr><td>🟢 Approval</td>
> > <td>Approval will be granted. The vendor may require information or app
> > configuration in a developer portal before issuing keys.</td></tr>
> > <tr><td>🟠 Approval</td>
> > <td>Approval is not guaranteed — often due to integration strategy; the
> > vendor may do a deeper assessment (competitors, partnership
> > requirements, and similar).</td></tr>
> > <tr><td rowSpan="2">Activation lead time</td>
> > <td>⚡ Instant</td>
> > <td>If no keys are required, or Chift has keys ready to share with you.</td></tr>
> > <tr><td>Time</td>
> > <td>Estimated time to get the connector activated in production as a
> > result of the approval or certification process (e.g. ⏱️ 2 days, 1
> > week).</td></tr>
> > <tr><td rowSpan="3">Extra fees — software editor</td>
> > <td>❎ No</td>
> > <td>No fees charged by the software editor.</td></tr>
> > <tr><td>💰 🕹️</td>
> > <td>Fees associated with obtaining a testing account.</td></tr>
> > <tr><td>💰 🔑</td>
> > <td>Fees charged to get API keys.</td></tr>
> > <tr><td rowSpan="2">Extra fees — end-user</td>
> > <td>❎ No</td>
> > <td>The end-user does not pay extra to get integrated.</td></tr>
> > <tr><td>💰 Yes</td>
> > <td>The end-user must pay extra to get integrated.</td></tr>
> > <tr><td>Comments on costs</td>
> > <td>—</td>
> > <td>Additional notes on fees or pricing when relevant.</td></tr>
> > <tr><td rowSpan="4">Sandbox account</td>
> > <td>✅ via Chift</td>
> > <td>Chift can provide you with a sandbox.</td></tr>
> > <tr><td>🟠 Only through integrator</td>
> > <td>Only the software's integrator can provide a sandbox.</td></tr>
> > <tr><td>✅ Self-service</td>
> > <td>You can create your own sandbox.</td></tr>
> > <tr><td>✅ Trial account</td>
> > <td>It is possible to create a trial account.</td></tr></tbody></table>

[See what this connector supports ↓](#coverage)

## Introduction

a3factura is a cloud invoicing software by Wolters Kluwer for freelancers and small businesses in Spain. It is used to issue quotes and invoices, manage collections and payments, and share data with the accountant's Wolters Kluwer accounting software.

## Activate a3factura

### Partner keys

Chift's app is already approved by Wolters Kluwer: no developer account, no approval and no lead time.

The subscription key is not a partner key. Each end user copies their own from My Wolters Kluwer and enters it in the connection form (see [Connect a3factura](#connect-a3factura)).

> [card] [Activate a3factura in your Chift account](https://chift.app/connectors?search=a3factura)
>
> One click in **Connectors**, then create connections straight away.

### Connector settings

No connector-specific settings.

## Test a3factura

| | |
| - | - |
| **Environment** | Production: Wolters Kluwer offers no public sandbox for the a3factura API. |
| **How to get it** | Chift can share its test environment with you: ask your Chift point of contact. Otherwise, you need an a3factura licence with the Conectia module, as Wolters Kluwer explains on [a3developers](https://a3developers.wolterskluwer.es/doc/sif/escenario-1/licencias-a3factura/). |
| **Demo data** | No: the test company starts empty. |

## Vendor fees

> [card] Software editor (you)
>
> No fee for API access. To test on your own a3factura company, you need a paid a3factura licence with the Conectia module.

> [card] End user
>
> The Conectia module, Wolters Kluwer's API module, on top of their a3factura subscription. Its price is not published: the end user asks Wolters Kluwer or their distributor.

a3factura starts at €9.95 per month (a3facturago) and €39 per month (a3facturapro). For plans and pricing, see Wolters Kluwer's [pricing page](https://www.wolterskluwer.com/es-es/solutions/a3factura/precios-y-versiones).

## Connect a3factura

> [card] [a3factura setup guide for end users](https://docs.chift.eu/help/connectors/7029.md)
>
> The full step-by-step, with screenshots.

**Before they start, your end users need:**

* an a3factura subscription (a3facturago or a3facturapro)
* the Conectia module on that subscription
* a Wolters Kluwer user with access to the company to connect

**To connect, they:**

* copy their Conectia API key from My Wolters Kluwer
* paste it in the **Subscription Key** field of the connection form
* sign in with their Wolters Kluwer account
* pick the company to connect

## Rate limits

a3factura applies a fixed quota per subscription key, set by the end user's API plan. Each end user has their own subscription key: all the connections they create with the same key share its quota.

| Plan | Calls per minute | Calls per day | Companies |
| - | - | - | - |
| Conectia | 3,000 | 150,000 | No limit |
| S | 100 | 5,000 | 1 |
| M | 1,000 | 50,000 | 10 |
| L | 3,000 | 150,000 | 30 |

The daily window does not reset at a fixed hour. It runs from the time the subscription was activated.

When the limit is exceeded, Wolters Kluwer returns HTTP `429 Too Many Requests`, with the wait time in the message and a `Retry-After` header. Chift automatically manages these limits to optimize performance and prevent interruptions. However, once the API rate limit is reached, Chift cannot bypass these limitations.

See Wolters Kluwer's [rate limit documentation](https://a3developers.wolterskluwer.es/doc/a3factura/caracteristicas-tecnicas/limites/).

## Limitations & specificities

> [accordion] Invoices
>
> * Sales invoices and purchase documents are both returned. Without an invoice type filter, a list returns the sales invoices first, then the purchase documents.
> * Filtering invoices by last update date (`updated_after`) is not supported, for any invoice type.
> * On the invoice list, the customer memo and the payment method are only returned when the invoice lines are included (`include_invoice_lines=true`), or for an invoice with an IRPF withholding. a3factura only gives them in the invoice detail.
> * The IRPF withholding is returned in `spanish_specificities`, as a negative amount. The invoice's tax amount is net of it.
> * A refund is a rectifying invoice, or an invoice with a negative total. Its amounts are returned positive: the invoice type gives the direction.
> * Status: paid once a3factura marks the invoice as charged, posted otherwise, including when it is partially charged.
> * The due date is the last due date of the invoice. The outstanding amount is the total of its unpaid dues.
> * The exchange rate is always 1.
> * The PDF is the sales invoice PDF, or the file attached to the purchase document. It is empty when there is none.

> [accordion] Chart of accounts & VAT
>
> * A VAT rate that changed over time is returned once per version. Its ID holds the a3factura code and the date the version starts. A version that has ended is inactive.
> * An invoice line points to the VAT version in force on the invoice date.
> * With a reverse-charge operation type (`CCEE`, `PISRD`, `SUJPAS`, `SUJPASIG`, `SUJPASR` or `VCEE`), the VAT amount is 0. The operation type and its description are returned as the exemption reason of each line.

> [accordion] Contacts (clients & suppliers)
>
> * A partner that is both a customer and a supplier in a3factura is returned once, with both roles.
> * Prospects do not exist in a3factura: the list is empty.
> * A contact is an individual when its Spanish tax ID (NIF) is the one of a natural person (DNI or NIE). Otherwise, it is a company, including when it has no NIF.
> * The VAT number is also returned as the company number.
> * The list also returns generic collective accounts, which a3factura lists among its customers and suppliers. They represent customers or suppliers as a whole, not one partner. They are not filtered out, because they can be used on invoices.

> [accordion] Multi-folder
>
> Not supported: a connection reads one company, chosen at login. To read another company, connect it separately.

## Coverage

Open in new tab

Chift Coverage Matrix - invoicing

> **Matrix Legend 🧭**
>
> <table><thead><tr><th>Status</th>
> <th>Meaning</th></tr></thead>
> <tbody><tr><td>✅ Implemented</td>
> <td>Endpoint is implemented and available.</td></tr>
> <tr><td>❌ Not supported</td>
> <td>Endpoint is not supported by the target software (connector
> limitation). Cannot be implemented.</td></tr>
> <tr><td>💬 On request</td>
> <td>Endpoint is not implemented but feasibility is validated. Can be
> implemented on request — contact your Chift point of contact to
> discuss scope and timing.</td></tr>
> <tr><td>🔎 To be analyzed</td>
> <td>Endpoint is not implemented and feasibility has not yet been fully
> assessed. Analysis is pending.</td></tr></tbody></table>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.