> For the complete documentation index, see [llms.txt](https://docs.younium.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.younium.com/payments-integrations/aritma.md).

# Aritma

## Synchronisation scope

| Synchronisation      | Direction        | When it runs                                                            |
| -------------------- | ---------------- | ----------------------------------------------------------------------- |
| Company registration | Younium → Aritma | On demand, when the company is registered from the integration settings |
| Company status       | Aritma → Younium | When the integration settings are opened                                |
| Bank accounts        | Aritma → Younium | On demand from the integration settings                                 |
| Incoming payments    | Aritma → Younium | Scheduled; or on demand for a single bank account                       |

Not in scope: invoices, outgoing payments.

***

## Overview

Aritma connects Younium to Aritma’s banking and receivables platform for company onboarding, bank statement retrieval, and **import of incoming payments** into Younium payment batches. The integration does not post invoices to Aritma on `InvoicePosted` and is not listed in `IntegrationStartup` workflow actions.

Operational flow: register company → wait for company active → link bank accounts → run import payments job or manual import → payment matching creates batches in Younium.

***

## Authentication

There is nothing to connect and no credentials to enter. Younium reaches Aritma with service credentials held for Younium as a whole, so the connection exists before you configure anything.

What you do instead is register your company with Aritma, which is described below. Until that registration is submitted and Aritma activates the company, the integration is configured but not yet usable.

***

## Activation and disconnect

You register your company with Aritma from the integration settings: Younium sends your organisation details, Aritma creates the company, and the registration is marked as submitted.

Registration is not the same as being active. Aritma activates the company at its end, and Younium refreshes that status when you open the settings — so a company can be registered and still not able to import payments. Onboarding each bank happens through a page Aritma provides, which Younium opens for you.

Disconnecting removes the registration and the bank accounts Younium had recorded for the company, and payment import stops.

***

## Save and setup

No invoice custom fields or `InvoicePosted` subscriptions in Aritma integration code.

***

## Import payments workflow

**Runs when:** the scheduled payment import runs, or an import is started manually.

### Request validation

| Input            | Rule                                          |
| ---------------- | --------------------------------------------- |
| `AccountId`      | Must parse to GUID; Aritma account must exist |
| Company settings | `CompanyId` present; company active           |
| Aritma account   | `IsActive`, has `AccountNumber`               |

### Receivables fetch (Younium → Aritma API)

GET `{ApiUrl}/receivables/{companyId}/{Queued}` with paging (`PageSize` = 100).

Each receivable becomes an incoming payment for matching, carrying its amount, currency, reference and dates.

### Write-back (Younium)

| Aritma / process field | Younium field                                |
| ---------------------- | -------------------------------------------- |
| Import timestamp       | `AritmaAccount.YouniumLastReceivablesImport` |
| Count imported         | `YouniumLastReceivablesImportCount`          |
| Matched payments       | Grouped into payment batches for posting     |

The linked Aritma account records when it was last synchronised, and each run writes a batch log you can review.

### Statements (supporting APIs)

Each bank account imports its incoming payments from one of two sources, chosen by its **Integration endpoint** setting: receivables (described above) or bank statements. Bank statements is the default for newly imported bank accounts. With statements, Younium reads the account's statements for the period and each statement transaction becomes an incoming payment for matching.

***

## Field mapping — company registration (Younium → Aritma)

| Younium / request field | Aritma API field     |
| ----------------------- | -------------------- |
| `OrganizationNumber`    | `OrganizationNumber` |
| `Name`                  | `Name`               |
| `Address`               | `Address`            |
| `ZipCode`               | `ZipCode`            |
| `ZipArea`               | `ZipArea`            |
| `Country`               | `Country`            |

Response: company GUID stored as `AritmaSettings.CompanyId`.

***

## Eligibility

* Import only when company registration active.
* Receivables state filter: `AritmaInpaymentState.Queued`.
* Parts of the integration may be enabled or disabled per tenant.

***

## Post invoice workflow

**Not applicable.** No ERP invoice export to Aritma.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.younium.com/payments-integrations/aritma.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
