Skip to main content

Introduction

Contasol is a Spanish accounting software developed by Software DELSOL (part of the TeamSystem group). It is used by SMEs and accountants to manage bookkeeping, VAT and financial reporting, and belongs to a wider suite of products alongside FactuSOL (invoicing) and Bilin. Contasol is installed on premise, but its database can be stored in the cloud and its data can be queried through a built-in API once that API has been activated.
Invoices are not created in Contasol itself but in FactuSOL. When both products are purchased and the integration is configured, FactuSOL invoices can be imported into Contasol as journal entries.

Configure Contasol

Prerequisites

The end user must have Contasol installed with its API access enabled. Activating the API relies on a developer account (“cuenta de fabricante”) registered with Software DELSOL, which provides two identifiers used to activate the API inside Contasol:
  • CodigoFabricante — the developer/manufacturer code tied to the account.
  • EmailFabricante — the email address linked to that developer account. Software DELSOL sends the generated API credentials to this address.
Who owns that developer account is what defines the two activation options below.

Activation process

When connecting your end users to Contasol, you can choose between two approaches depending on who holds the developer account. In both cases the API credentials are ultimately sent by email by Software DELSOL and are then entered in the Chift connection settings.

Option 1 — Use your own developer account

You (the Chift customer) create a single developer account with Software DELSOL and encode your CodigoFabricante and EmailFabricante on the connector page in Chift. Your end users enter these same identifiers in their Contasol API access screen. The credentials email is then sent to your developer email address, and you pass the resulting credentials on to the end user (or use them to set up the connection on their behalf).
With this option the end user is not autonomous — they depend on you to share the API credentials. Choose it when you prefer to centralize developer-account management.

Option 2 — Let the end user use their own developer account

The end user creates their own developer account with Software DELSOL, obtains their own CodigoFabricante, activates the API in Contasol and receives the credentials email directly. They then enter those credentials in the Chift connection.
With this option the end user is fully autonomous — no identifiers need to be shared with you.
The end-user steps for this option (create the developer account, activate the API in Contasol, fill in the Chift connection) are described in the Help Center article linked below.

Test Contasol

You can create a free test account here. After completing the steps you will receive an installer and credentials valid for one month.

Connect Contasol

To activate a connection with Contasol, end users go through the following steps:

Technical limitations & specificities

Bank feed

Contasol does not support a bank feed.

Attachments

Contasol does not store files, so attachments are not supported on all endpoints.

Clients & suppliers

  • Filtering on updated_after date is not supported.
  • On creation (POST), only a single address object is supported.

Analytic plans & accounts

  • A single default analytic plan is returned (“Departamentos contables”).
  • Analytic accounts cannot be split: departments and their sub-departments are returned as a flattened list.

Invoices

  • Invoices are derived from journal entries.

Journal entries

  • All entries are posted by default, so the unposted_allowed filter has no effect.

Financial entries

  • No tax_info object is returned.

Payment terms

Unlike other Spanish connectors, Contasol does not build due dates from a payment-term template (the “tipo cartera” is purely informative). To keep a consistent behaviour, Chift returns a standard list of payment terms (30, 60 and 90 days and the possible combinations) that mirrors the Contasol interface. When a payment term is set on an invoice, Chift computes the due dates from the invoice date; if they do not match the recorded due date, an error is returned.

Coverage