---
title: "Ropo's reminder and collection service"
canonical: https://documentation.maventa.com/integration-guide/accounts-receivable/ropo-debt-collection/
---
With Ropo's reminder and collection service, you can transfer overdue invoices to Ropo for reminder and debt collection.
* B2B invoices can be transferred 7 days after the due date.
* B2C invoices can be transferred 14 days after the due date.
Ropo handles reminder sending and all debt collection activities. The service is available in Finland, Sweden, and Norway, with additional countries such as Denmark and Germany planned (timeline TBD).
The service supports EUR (Finland), SEK (Sweden), and NOK (Norway) currencies.
> [!WARNING]
> Only one currency can be used per account. For example, if an account uses EUR, it cannot also use SEK or NOK. If you need to use multiple currencies, please contact Maventa support.
The service is provided by Ropo and delivered through Maventa as part of the Maventa service, with no separate usage fee. Reminder and collection fees are paid by the debtor (the recipient of the reminder or collection letter), not by the client. However, costs may arise in the later stages of the debt collection process. If a case proceeds to legal collection, any official authority fees incurred are charged from the client (service user). The client must specifically authorise whether a case should progress to legal collection — Ropo does not start this automatically. In addition, if the client is VAT liable, Ropo invoices the VAT portion of reminder and collection fees paid by the debtor. Costs may also occur if assignments are cancelled.
Ropo settles capital to the company's account on a daily basis. In Finland, there are two settlements each weekday: the morning settlement covers payments that can be matched directly, and the afternoon settlement covers the rest once any manual allocation or other investigation has been completed. Finnish settlements appear on the company's bank statement with *Ropo Suomi Oy* as the payer name. In Norway and Sweden, settlements occur once per day. Late payment interest is settled on the last Wednesday of each month. All settlement reports are accessible and downloadable via the Ropo One user interface.
Once an invoice has been successfully transferred to Ropo, Maventa automatically creates an assignment. ERPs can track these assignments using the [Receivables API](https://swagger.maventa.com/?urls.primaryName=STAGE%20-%20AutoInvoice%20Receivables%20API), display assignment information to users within the ERP, report direct payments, or cancel assignments via credit invoices. To be notified as the collection progresses instead of polling, you can also subscribe to [Receivables webhooks](https://documentation.maventa.com/integration-guide/accounts-receivable/webhooks/).
## Opening the Ropo's reminder and collection service service
To activate the Ropo's reminder and collection service service, call [`PUT /v2/services/ropo/receivables`](https://swagger.maventa.com/?urls.primaryName=STAGE%20-%20AutoXChange%20API#/services/putV2ServicesRopoReceivables). Use [`GET /v2/services/ropo/receivables`](https://swagger.maventa.com/?urls.primaryName=STAGE%20-%20AutoXChange%20API#/services/getV2ServicesRopoReceivables) to check the activation status.
Parameters for the PUT /v2/services/ropo/receivables call
| Parameter | Description |
| ------------------------------|--------------------------------------------------------------------------------------------------------------------------------------|
| agreement_contact_email | Email for a person authorised to act on behalf of the company. Used to send the request to sign the electronic agreement. Mandatory. |
To complete the activation process, Ropo sends an email with a link to a wizard form to the address specified in `agreement_contact_email`. Through the wizard form, the recipient provides the required company details and electronically signs an agreement with Ropo.
The authorisation can be based on the individual's role within the company or on a power of attorney, which must be attached to the form if applicable. Completing the form requires strong electronic identification (such as online banking credentials, Mobile ID, or BankID depending on the country).
### Activation steps
1. **Wizard form** — The invoicing company fills in the company details required to open a Ropo One profile. The form also collects the details of the contract approver (a person with signing authority). In Finland, the form additionally asks for a separate **KYC form completer** (also with signing authority), who can be a different person from the contract approver.
2. **KYC verification (Finland only)** — After the wizard form is submitted, Ropo sends a KYC email link to the KYC form completer. The KYC form is a separate electronic form outside of Ropo One. In accordance with the Money Laundering Act, Ropo is required to identify its customers and understand their activities.
3. **User credentials** — After the wizard form is submitted, Ropo sends the Ropo One user credentials.
4. **Agreement signing** — The contract approver accepts the agreements the first time they log in to Ropo One. The service cannot be used until the agreements are signed.
5. **Service activation** — Once the agreement is signed and verified by Ropo, the service is activated, typically within 1–2 business days. After activation, invoices can be transferred to Ropo for reminders and debt collection.
> [!NOTE]
> If the activation process is not completed within one week, Ropo sends a reminder email.
## Transferring invoices to reminder and debt collection
Transfer overdue invoices to the Ropo's reminder and collection service service using the following API method:
[`POST /v2/invoices/{id}/assignment/ropo`](https://swagger.maventa.com/?urls.primaryName=STAGE%20-%20AutoXChange%20API#/invoices/postV2InvoicesIdAssignmentRopo)
Provide the invoice ID (UUID) for an overdue invoice along with the following parameters:
| Parameter | Required | Description |
| -------------------|----------------------------------------|----------------------------------------------------------------------------------------------|
| collection_type | Yes | `reminder_and_collection` or `collection` |
| receivables_type | Yes | `b2b`, `b2c`, `b2b_rental`, or `b2c_rental` (see note on rental receivables below) |
| amounts | No | Detailed breakdown of amounts (see below). Cannot be used in combination with `collectable_amount`. |
| payers | Yes | Array of payer objects (see below) |
| reminder_date | When collection_type = `collection` | Date (YYYY-MM-DD) when the reminder was sent by the sender |
| assignment_summary | Yes | Description of what the assignment refers to (see below) |
> [!NOTE]
> Rental receivables collection (`b2b_rental` and `b2c_rental`) is currently only supported for Finnish customers. In Sweden and Norway, rental receivables require a more complex setup and are not supported at this time. If you need rental receivables collection in Sweden or Norway, please contact Maventa support.
> [!NOTE]
> Duplicate invoice numbers are not allowed. Ensure that each invoice number is unique, avoiding any reuse.
> [!NOTE]
> B2B invoices can be transferred 7 days after the due date.
> B2C invoices can be transferred 14 days after the due date.
### Collection_type
* **reminder_and_collection** — transfer the invoice to a full reminder and debt collection process
* **collection** — transfer the invoice directly to the collection process when you have already handled the reminder sending yourself. When using this type, `reminder_date` is mandatory.
### Amounts
Capital, costs, and interest must always be reported separately. They must not be combined into a single capital amount.
| Field | Required | Description |
|-----------------|----------|--------------------------------------------------------------------------------------------------|
| capital_amount | Yes | Amount of capital invoiced. Must be a positive number (e.g. 100.50). |
| reminder_amount | Yes | Amount of reminder fees invoiced. Must be a positive number (e.g. 5.00). |
| interest_amount | Yes | Carried-over interest (*siirtyvä korko*) — interest from a previous invoice that has been added to the current invoice. Must be a positive number (e.g. 10.50). |
> [!WARNING]
> Always report carried-over interest in `interest_amount` — don't add it to the capital. The Finnish Interest Act (Korkolaki 633/1982) only allows late payment interest on the overdue principal, not on interest that has already accrued. Keeping it in its own field lets Ropo track the amount without charging new interest on top of it.
> [!NOTE]
> Ropo uses the late payment interest rate (*viivästyskorko*) specified in the original invoice XML if one is provided. If no rate is specified, or if the rate on the invoice exceeds what is permitted under the Finnish Interest Act (Korkolaki 633/1982), Ropo applies the statutory industry-standard rate instead — the prevailing reference rate plus seven percentage points for consumer debts, or plus eight percentage points for commercial debts. The rate must be in the invoice XML — including it only on the invoice image is not sufficient.
### Payers
Each payer in the array requires the following fields:
| Field | Required | Description |
|------------|------------------------------------------------|--------------------------------------------------------------------------------|
| type | Yes | `main_debtor` or `co_debtor` |
| name | Yes | Payer's full name |
| bid | For `b2b` and `b2b_rental` | Business ID |
| ssn | Required for `b2c_rental` | Payer's social security number, used for the legal collection process |
| address | Yes | Address object (see below) |
#### Address fields
| Field | Required | Description |
|------------|----------|-------------------|
| line1 | Yes | Street address |
| line2 | No | Additional address line |
| post_code | Yes | Postal code |
| city | Yes | City |
| country | Yes | Country code |
Main debtor and co-debtor details must be provided separately in the API. For consumer rental receivables (`b2c_rental`), the payer's SSN is mandatory — if SSN is missing, the assignment cannot be transferred to Ropo.
> [!WARNING]
> The debtor's full address must be provided. If any address details are missing, the invoice cannot be forwarded to Ropo.
### Assignment_summary
Provide a specific description of what the assignment refers to:
* Avoid vague descriptions like "purchase of groceries" or "goods"
* Use clear terms, e.g. "purchase of umbrellas"
* "Worked hours" is acceptable
* Row description from the invoice can be used as an alternative
* If several services are invoiced together, specify them clearly: "waste management services & water/sewage fees"
### Transfer status
Check the status of the transfer using [`GET /v2/invoices/{id}/assignment`](https://swagger.maventa.com/?urls.primaryName=STAGE%20-%20AutoXChange%20API#/invoices/getV2InvoicesIdAssignment):
* **Pending** — Waiting for the transfer
* **Sent** — Transfer successful and an assignment has been created. The response also contains a link and assignment id to the newly created assignment.
* **Error** — Transfer failed. The most common reason is missing receiver address details. Error reason is visible in `error_reason` field.
### Possible errors
If the invoice is not yet past due, the API returns a 400 error. The due date must be yesterday or earlier; an invoice that is due today cannot be transferred yet:
```json
{
"code": "invalid_parameters",
"message": "Request parameters are invalid",
"details": [
"Invoice not expired"
]
}
```
### Creating assignments manually
Invoices that have not been sent through Maventa can also be transferred to the Ropo's reminder and collection service service by creating an assignment manually.
To do this, create the invoice using [`POST /v1/invoices`](https://swagger.maventa.com/#/invoices/postV1Invoices) with the `prevent_routing` parameter set to `true`. This marks the invoice immediately as SENT without actually delivering it to the receiver. After the invoice is created, use the Ropo's reminder and collection service APIs described above to transfer it to the reminder and/or debt collection process.
> [!NOTE]
> Transferring an invoice to Ropo is free of charge. The `POST /v1/invoices` call itself is billed as a normal invoice sending (debit action) according to your existing price list, even though the invoice is not delivered to the receiver (`prevent_routing` parameter used).
### Reminder and debt collection schedule
When an invoice is transferred for the reminder and collection process, Ropo sends the first reminder 10 days after the due date for B2B invoices and 14 days after the due date for B2C invoices. If the invoice is transferred directly to the collection process, a payment demand is sent first.
Letters are not sent during weekends or public holidays, which may add a few additional days to the schedule in some cases.
Reminders and collection letters use Ropo's bank account and reference details. When funds are collected, they are settled to the client using the original invoice reference.
#### Delivery method of reminders and collection letters
The delivery method depends on the country and how the original invoice was delivered.
**Finland**
- **B2B** — Reminders and collection letters are sent electronically to the same delivery address as the original invoice (e-invoice or email). If the original invoice was sent by post, or if the electronic delivery route is no longer available, the letters are sent by post.
- **B2C** — Always sent by post.
**Norway and Sweden**
- If the original invoice was sent by email, reminders and collection letters are also sent by email.
- In all other cases, they are sent by post.
You can find the detailed and most up-to-date schedule on Ropo’s website:
- [Finland](https://ropo.fi/hallitse-maksujasi/perintamenettely/)
- [Norway](https://ropo.no/handtere-dine-betalinger/innfordringsprosess/)
- Sweden — link coming soon
#### Language of the reminder and debt collection letters
The language used for reminders and debt collection letters is determined from the invoice data:
1. `POST /v1/invoices` parameter `lang`
2. Invoice format language field (e.g. Finvoice `InvoiceRecipientLanguageCode`)
3. If not defined explicitly, the language defaults based on the sender's country
## Assignments
For each invoice transferred to Ropo's reminder and collection service, Maventa creates an assignment. The assignment allows the company to follow up on the collection process and serves as a communication channel between the sender and the collection agency.
To link the sent invoice and the assignment together, the assignment contains `reference_ids` including `invoice_id` with the UUID of the original invoice.
> [!NOTE]
> If Ropo needs information or action from the sender before they can continue processing an assignment, they put the assignment on hold and contact the sender by email. This includes disputed invoices — if a debtor disputes a payment, Ropo puts the invoice on hold and forwards the complaint to the client for investigation. Once the client provides a response, Ropo resumes the process. The assignment continues once the matter is resolved.
The collection process can be stopped at any time by notifying Ropo through the Ropo One user interface.
An assignment can have one of the following statuses:
1. **Open** — The assignment is active and Ropo handles the reminder sending and debt collection process depending on the chosen collection type.
2. **Closed** — The assignment is closed. The invoice has been paid and no charges are open. Ropo has transferred the money to the company's account.
Assignment content
| Parameter | Description | Applicable to Ropo's reminder and collection service |
| ---------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------|
| id | Assignment ID | Yes |
| status | Open (unpaid) / closed (paid or cancelled) / partially_closed | partially_closed status does not exist with Ropo |
| collection_status | Collection status of the assignment. Set based on events added by the agency. | Yes |
| service_level | default (normal process) / premium / vip. Does not apply to Ropo, always default with Ropo | No |
| debtor | `name`: Name of the customer (receiver of the invoice) and `bid`: customer's business ID | Yes |
| due_date | Due date from the original invoice | Yes |
| issued_at | Invoice date from the original invoice | Yes |
| number | Invoice number from the original invoice | Yes |
| sum | Total sum of the invoice (taken from the invoice data if not given in the API when transferring the assignment) | Yes |
| paid | Amount that is paid or credited | Yes |
| currency | Currency from the original invoice | Yes |
| created_at | When the assignment was created | Yes |
| updated_at | When the assignment was last updated (e.g. when the paid sum was updated) | Yes |
| partially_closed_at | When the assignment was partially closed | No |
| closed_at | When the assignment was closed by Ropo | Yes |
| reference_ids | Contains three IDs: `agency_id` = Ropo ID, `invoice_id` = ID of the original invoice (UUID), `number` = reference number from the original invoice | Yes |
JSON example of an assignment and its event
```json
[
{
"id": "fa9781ba-20d1-4677-a125-f04bff7bbac0",
"status": "open",
"collection_status": "reminder_sent",
"service_level": "default",
"debtor": {
"name": "Test receiver Oy"
},
"due_date": "2020-04-20",
"issued_at": "2020-04-01",
"number": "64488",
"sum": 12.3,
"paid": 10,
"currency": "EUR",
"created_at": "2020-04-15T05:47:07Z",
"partially_closed_at": null,
"updated_at": "2020-04-15T21:01:18Z",
"closed_at": null,
"reference_ids": [
{
"type": "agency_id",
"value": "078dbb88-ef8e-4115-8260-c8a542aaa87c"
},
{
"type": "invoice_id",
"value": "f6dcf18d-a1bd-4e72-bb8a-80908527b6c8"
},
{
"type": "number",
"value": "356241887794"
}
],
"events": [
{
"id": "c0c56722-a28b-49d1-aa87-1c4d7f3cf1af",
"type": "paid",
"data": {
"sum_paid": 10,
"booked_at": "2020-04-16",
"archive_number": "12345"
},
"party_id": "938fc79f-9c00-47af-8507-cdf15838aa96",
"seens": [
{
"seen_at": "2020-04-15T22:00:06Z",
"seen_by": "938fc79f-9c00-47af-8507-cdf15838aa96"
}
],
"created_at": "2020-04-15T21:01:18Z",
"happened_at": "2020-04-16T00:00:00Z"
}
]
}
]
```
[Receivables API](https://swagger.maventa.com/?urls.primaryName=STAGE%20-%20AutoInvoice%20Receivables%20API#/assignments) for assignment handling.
Collection status of the assignment
| collection_status | Events that set the collection status |
| ----------------------|-----------------------------------------------------------------------------------------------|
| unknown | Default value until a reminder is sent or collection activities are started |
| reminder_sent | reminder_sent / second_reminder_sent |
| debt_collection | collection_started (first payment demand is sent) / second_demand_sent / tratta |
| legal_collection | legal_collection_started |
| recovery_proceedings | application_for_enforcement |
| debt_surveillance | credit_loss_suggestion (note: the credit_loss event does not change the collection status) |
| lack_of_means | lack_of_means |
| payment_plan | payment_plan |
## Events
Events are added to assignments once something happens on the Ropo side, such as a payment made by the debtor. The sender can also add events to communicate information to Ropo, like direct payments to the sender's own account or a request to credit the invoice.
> [!NOTE]
> To be notified when Ropo adds an event to an assignment — a reminder sent, a payment received, the case moving to collection, or the assignment closing — subscribe to [Receivables webhooks](https://documentation.maventa.com/integration-guide/accounts-receivable/webhooks/) instead of polling the API. Events your integration is responsible for, such as `paid` (direct payments) and `credit_note`, must still be sent by the ERP.
Automating these events from the ERP is highly recommended. At minimum, automate `paid` and `credit_note` events to ensure they are always communicated to Ropo without relying on end users to remember to do this manually.
[Receivables API](https://swagger.maventa.com/?urls.primaryName=STAGE%20-%20AutoInvoice%20Receivables%20API#/events) for event handling.
### Events added by Ropo
| Event type | Description |
|------------------------------|------------------------------------------------------|
| reminder_sent | Reminder has been sent to the debtor |
| second_reminder_sent | Second reminder has been sent |
| collection_started | First payment demand sent, debt collection begins |
| second_demand_sent | Second payment demand sent |
| tratta_sent | Tratta sent (B2B) |
| legal_collection_started | Legal collection started |
| application_for_enforcement | Application for enforcement filed |
| lack_of_means | Enforcement authority has declared the debtor insolvent |
| payment_plan | Payment plan agreed with the debtor |
| paid | Payment received by Ropo |
| close | Assignment closed by Ropo |
### Events added by the sender
| Event type | Required fields | Description |
|--------------|------------------------------|----------------------------------------------------------|
| paid | `sum_paid`, `booked_at` | Direct payment received on the company's own account |
| credit_note | `credit_sum`, `booked_at` | Credit the assignment to cancel it |
| credit_loss | | Mark the assignment as a credit loss |
### Event details
Handling payments
`paid` – Used to report payments made by the customer and to notify direct payments.
Usage scenarios:
1. Customer payment through Ropo.
Ropo sends a paid event when the customer pays the assignment, either fully or partially.
- If the assignment is fully paid, Ropo will automatically close it (`close` event added).
- If the customer pays more than the invoice amount, the excess is refunded to the customer. Ropo does not retain overpayments for future invoices.
2. Reporting direct payments
Use this event to inform Ropo when the customer pays directly to the sender company's account. Payments may be full or partial.
- If additional details are needed, they can be provided using a comment event.
- If the assignment is fully paid, Ropo will close it (`close` event added).
> [!WARNING]
> It is very important that direct payments are reported through this event so that Ropo can update the open balance or close the assignment correctly.
> Automating this event in the ERP is strongly recommended to ensure direct payments are always reported.
The `paid` event updates the paid field in the assignment, but does not modify the sum value.
```json
{
"type": "paid",
"data": {
"sum_paid": 200.5,
"booked_at": "2019-01-04",
"archive_number": "12345"
}
}
```
**Both the company and Ropo can create this event type.**
Closing an assignment
`close` – Ropo uses this event to mark an assignment as closed. An assignment is closed when any of the following occurs:
- the customer has fully paid the assignment
- you report that it has been fully paid (direct payment)
- you report that it has been fully credited
- you request cancellation of the assignment
Once closed, no further collection activity is carried out for that assignment.
**Only Ropo can create this event type.**
Connecting a credit note to an assignment
`credit_note` – Use this event to link a credit note to an assignment. Provide the credit note number and the credit sum when sending this event. The credit sum should be entered as a positive value.
- If the credit note fully covers the assignment, Ropo will close the assignment (`close` event added).
- If only part of the assignment is credited, Ropo will continue monitoring payments and follow the debt collection process for the remaining amount.
Automating this event in your ERP is strongly recommended to ensure that a `credit_note` event is always sent when credit notes are created.
**Only the company can create this event type.**
When the first reminder is sent to the customer
`reminder_sent` – Ropo adds this event when the first payment reminder for an unpaid invoice has been sent. If the assignment's `collection_status` is not already set to `reminder_sent`, the event will update it accordingly.
**Only Ropo can create this event type.**
When the second reminder is sent to the customer
`second_reminder_sent` – Ropo adds this event when the second payment reminder for an unpaid invoice has been sent. If the assignment's `collection_status` is not already set to `reminder_sent`, the event will update it accordingly.
**Only Ropo can create this event type.**
When the first payment demand is sent to the customer
`collection_started` – Ropo adds this event when the first payment demand for an unpaid invoice has been sent. If the assignment's `collection_status` is not already set to `debt_collection`, the event will update it accordingly.
**Only Ropo can create this event type.**
When the second payment demand is sent to the customer
`second_demand_sent` – Ropo adds this event when the second payment demand for an unpaid invoice has been sent. If the assignment's `collection_status` is not already set to `debt_collection`, the event will update it accordingly.
**Only Ropo can create this event type.**
When the tratta is sent
`tratta_sent` – A tratta has been issued for an unpaid invoice. This event will update the assignment's `collection_status` to `debt_collection` if it has not already been set.
**Only Ropo can create this event type.**
Legal collection is started
`legal_collection_started` – A summons application has been submitted and the legal collection process for the assignment has begun. This event will update the assignment's `collection_status` to `legal_collection`.
Ropo does not automatically start legal collection. The client must specifically decide and authorise whether a case should progress to legal collection. When legal collection is required, Ropo requests your confirmation before proceeding.
**Only Ropo can create this event type.**
An application for enforcement is sent
`application_for_enforcement` – An application for enforcement has been submitted and the assignment has been transferred to the enforcement authority. This event will update the assignment's `collection_status` to `recovery_proceedings`.
**Only Ropo can create this event type.**
The enforcement authority has found the debtor insolvent
`lack_of_means` – The enforcement authority has declared the debtor insolvent. This event will update the assignment's `collection_status` to `lack_of_means`.
**Only Ropo can create this event type.**
A payment plan has been agreed on the invoice
`payment_plan` – A payment plan has been agreed on the invoice. This event will set the `collection_status` of an assignment to `payment_plan`.
**Only Ropo can create this event type.**
Marking an assignment as credit loss
`credit_loss` – You can mark the assignment as a credit loss for accounting purposes. Reporting a credit loss does not affect payment control or monitoring, and Ropo will continue the collection process as usual.
Once submitted, a credit loss entry cannot be reversed or modified.
Ropo provides credit loss recommendations in the Ropo One financial report when collection is no longer viable. Ropo also monitors and notifies clients of bankruptcies or corporate restructurings.
**Only the company can create this event type.**
## Closing the service
Ropo's reminder and collection service can be closed by calling [`DELETE /v2/services/ropo/receivables`](https://swagger.maventa.com/?urls.primaryName=STAGE%20-%20AutoXChange%20API#/services/deleteV2ServicesRopoReceivables). Ropo will still handle any open assignments.
> [!NOTE]
> Even after closing the service, the APIs remain available for following up on remaining open assignments and adding events as needed.
## Frequently asked questions
### What currencies are supported?
Ropo supports local currencies: EUR (Finland), SEK (Sweden), and NOK (Norway). Only one currency can be used per account — if an account uses EUR, it cannot also use SEK or NOK. If you need to use multiple currencies, please contact Maventa support.
### Is rental receivables collection available in all countries?
Rental receivables collection (`b2b_rental` and `b2c_rental`) is currently only supported for Finnish customers. In Sweden and Norway, rental receivables require a more complex setup and are not supported at this time. If you need this service in Sweden or Norway, please contact Maventa support.
### How are complaints and disputed invoices handled?
If a debtor disputes a payment, Ropo puts the invoice on hold and forwards the complaint to the client for investigation. Once the client provides a response, Ropo resumes the process.
### Can the collection process be stopped once it has started?
Yes. The process can be stopped at any time by notifying Ropo through the Ropo One user interface.
### Does Ropo automatically start legal collection?
No. The client must specifically decide and authorise whether a case should progress to legal collection. Ropo always requests the client's confirmation before proceeding.
### How are credit losses and bankruptcies handled?
Ropo provides credit loss recommendations in the Ropo One financial report when collection is no longer viable. Ropo also monitors and notifies clients of bankruptcies or corporate restructurings.
### What payment details are used on reminder letters?
Reminders and collection letters use Ropo's bank account and reference details. When funds are collected, they are settled to the client using the original invoice reference.
### What is the settlement schedule for collected funds?
In Finland, there are two settlements each weekday: the morning settlement covers payments that can be matched directly, and the afternoon settlement covers the rest once any manual allocation or other investigation has been completed. Finnish settlements appear on the company's bank statement with *Ropo Suomi Oy* as the payer name. In Norway and Sweden, settlements occur once per day. Late payment interest is settled on the last Wednesday of each month.
### Which late payment interest rate does Ropo use?
Ropo uses the late payment interest rate (*viivästyskorko*) specified in the original invoice XML if one is provided. If no rate is specified, or if the rate on the invoice exceeds what is permitted under the Finnish Interest Act (Korkolaki 633/1982), Ropo applies the statutory industry-standard rate instead. The rate must be in the invoice XML — including it only on the invoice image is not sufficient.
### Who is responsible for reminder and collection fees?
These fees are paid by the debtor (the recipient of the reminder or collection letter), not by the client.
### What happens if a debtor pays the client directly?
If a debtor pays directly after a reminder has been sent, the client can report this direct payment through the ERP system (if the integration supports this feature) or through the Ropo One interface. It is important to always report direct payments so that Ropo can update the open balance or close the assignment correctly.
### Are settlement reports available for review?
Yes, all settlement reports are accessible and downloadable via the Ropo One user interface.
### Is there a dedicated portal for debtors to manage payments?
Yes. Debtors can use MyRopo (myropo.fi / myropo.se / myropo.no) around the clock to make payments, request due date changes, or contact support.
### Who should Maventa partners contact for reminder and collection questions?
For implementation, integration, and API-related questions, contact Maventa support. All communications regarding reminder and debt collection processes and financial transactions should be made directly to Ropo. Contact details and further information are available in the Ropo One user interface.