# Sellsy integration mapping

### Connection to Sellsy

[Follow this guide](https://help.fincome.co/en/guide/sources/connect-my-sellsy-account) to establish the connection to the Sellsy API.

### Synchronized data

| **Entity**                  | **Synchronized key fields**                                                                                                 |
| --------------------------- | --------------------------------------------------------------------------------------------------------------------------- |
| Customers                   | id, name, email                                                                                                             |
| Products                    | id, name\_or\_reference                                                                                                     |
| Prices                      | id, amount\_excl\_tax, currency                                                                                             |
| Invoices                    | id, linked\_client, issue\_date, status, number, quantity, amount\_excl\_tax, discounts, VAT, period, currency, description |
| Credit Notes (Credit Notes) | same structure as invoices but with negative amounts                                                                        |

***

### Detailed operation of the integration

* Structured mapping: each Sellsy entity is translated according to a field-by-field mapping
* Intelligent product filtering: only non-archived and compatible-type items are imported
* Invoice lines: each line is analyzed individually to detect discounts, VAT, quantity, description, etc.
* Converted amounts: amounts excl. tax and discounts are also returned in the base currency
* Billing periods: Fincome identifies periods (period\_start / period\_end) when they are provided in Sellsy
* Credit note import: credit notes are imported with their lines and associated with their original invoices

***

### Note

* Duration of the first synchronization: a few minutes to several hours depending on volume
* Daily synchronization: every night automatically
* Manual changes: never overwritten by a resynchronization
* Sellsy API rate limit: managed automatically by Fincome
* Negative amounts for credit notes: interpreted automatically

***

### Integration overview

| **Item**                | **Detail**                                              |
| ----------------------- | ------------------------------------------------------- |
| Integration method      | OAuth 2.0 or API token                                  |
| Supported entities      | Clients, Products, Prices, Invoices, Credit notes       |
| Sync frequency          | Daily (night)                                           |
| Scope of initial import | All data available in Sellsy                            |
| Synchronization method  | REST API + pagination                                   |
| Deletion of Sellsy data | Not propagated (deletions in Sellsy are not replicated) |

***

### Data settings

| **Behavior / Setting**               | **Operation in Fincome**                                 |
| ------------------------------------ | -------------------------------------------------------- |
| Archived products                    | Automatic exclusion                                      |
| Invoice lines                        | Full import with discounts, VAT, periods, descriptions   |
| Excl. tax and incl. tax calculations | Automatic (field amount\_tax\_exc, tax\_amount)          |
| Currency conversion                  | Applied based on the currency\_code field + invoice date |
| Handling of credit notes             | Amounts reversed, but structure identical to invoices    |
| Manual data                          | Editable without being overwritten during a new sync     |

***

### Technical mapping (Sellsy → Fincome)

#### Customers

| Sellsy field | Fincome field |
| ------------ | ------------- |
| id           | original\_id  |
| name         | name          |
| email        | email         |

#### Products & Prices

| Sellsy field      | Fincome field       |
| ----------------- | ------------------- |
| id (product)      | original\_id        |
| name or reference | name                |
| price\_excl\_tax  | amount              |
| currency\_code    | currency\_code      |
| id                | product\_id (price) |

#### Invoices

| Sellsy field | Fincome field   |
| ------------ | --------------- |
| id           | original\_id    |
| date         | date            |
| number       | invoice\_number |
| status       | status          |
| company\_id  | customer\_id    |

#### Invoice lines

| Sellsy field     | Fincome field                           |
| ---------------- | --------------------------------------- |
| id               | original\_id (line)                     |
| quantity         | quantity                                |
| amount\_tax\_exc | amount\_excluding\_tax\_after\_discount |
| tax\_amount      | tax\_amount                             |
| description      | description                             |
| period\_start    | period\_start                           |
| period\_end      | period\_end                             |
| currency\_code   | currency\_code                          |

#### Credit Notes (Credit Notes)

Same structure as invoices, with:

* Negative amounts
* Statuses specific to credit notes
* References to the same types of lines

***

### Next steps

* View your KPIs in the MRR, Churn, and Cohorts views
* Add other billing sources (Stripe, Chargebee, etc.)
* Enrich your customer data (segmentation, company size...)
* Schedule a session with your Customer Success to go further


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://help.fincome.co/en/resources/integration-mapping-and-api/sellsy-integration-mapping.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.