Accounts receivable
Maventa offers accounts receivable services that handle payment monitoring, reminders, and debt collection on your behalf. These services are provided by collection agencies and delivered through Maventa as part of the Maventa service, with no separate usage fee — you only pay for the invoices you send. However, costs may arise in the later stages of the debt collection process or if assignments are cancelled. Each service page describes the specific cost structure in detail.
Available services
Reminder and debt collection provided by Ropo. Select individual overdue invoices to transfer to Ropo for reminder handling and collection. Available in Finland, Sweden, and Norway, with more countries coming (timeline TBD).
Full-cycle payment monitoring and collection for Finnish companies. Once activated, all invoices are automatically routed through the service. Visma Amili handles payment monitoring, reminders, and debt collection on the sender’s behalf.
Manual reminder and debt collection for Finnish companies. Select individual overdue invoices to hand over to Visma Amili for reminder handling and collection.
How it works
All accounts receivable services follow the same general flow:
-
Activate the service — Start the activation via the API. A company representative completes a KYC (Know Your Customer) check and signs an electronic agreement with the collection agency. Activation is typically completed within 1–2 business days.
-
Invoices enter the collection process — Depending on the service, invoices are either routed automatically through the collection agency (Amili Kassavirta) or transferred manually when they become overdue (Ropo’s reminder and collection service, Amili Perintä).
-
Assignments are created — Each invoice that enters the collection process generates an assignment. Assignments represent the invoice’s lifecycle within the collection agency and are the central data model for tracking progress.
-
Events track what happens — Both the collection agency and the sender communicate through events on assignments. Events cover payments, reminders sent, credit notes, due date changes, cancellations, and more. Automating event handling from the ERP is strongly recommended.
-
Payments are settled — The collection agency collects payments from debtors and settles them to the sender’s account.
Automatic vs. manual collection
The key difference between the services is how invoices enter the collection process:
-
Automatic (Amili Kassavirta) — Once activated, all invoices are automatically routed through the service. Visma Amili modifies the invoice payment details, monitors payments, and handles reminders and collection without any manual action from the sender.
-
Manual (Ropo’s reminder and collection service, Amili Perintä) — The sender selects which overdue invoices to transfer to the collection agency. This gives more control over which receivables are handed over for collection. The original invoice is sent to the receiver as usual, and the transfer happens separately after the due date has passed.
Choosing the right service
| Ropo’s reminder and collection service | Amili Kassavirta | Amili Perintä | |
|---|---|---|---|
| Collection model | Manual transfer | Automatic for all invoices | Manual transfer |
| Provider | Ropo | Visma Amili | Visma Amili |
| B2B and B2C | Both | Both | Both |
| Country | Finland, Sweden, Norway (expanding further, timeline TBD) | Finland | Finland |
| Best for | Companies that want to choose which invoices go to collection, or operate across multiple Nordic countries | Companies that want hands-off receivables management for all invoices | Companies that want to selectively outsource collection for specific overdue invoices |
Ropo’s reminder and collection service and Amili Perintä both use the manual transfer model, but they use different collection agencies and API endpoints. Ropo’s reminder and collection service is available in Finland, Sweden, and Norway with more countries coming (timeline TBD), while Amili Perintä is available in Finland only.
A company can use only one debt collection service at a time. Ropo’s reminder and collection service, Amili Kassavirta, and Amili Perintä are mutually exclusive: while one is active, activating another is rejected. To switch, close the current service first, then activate the new one. Assignments created before closing continue to be handled.
API overview
All accounts receivable services share the same Receivables API for managing assignments and events. This means the integration for tracking collection progress is largely the same regardless of which service is used.
Service-specific operations — activation, configuration, and invoice transfers — use dedicated endpoints in the AutoXChange API:
| Operation | Ropo’s reminder and collection service | Amili Kassavirta / Amili Perintä |
|---|---|---|
| Activate service | PUT /v2/services/ropo/receivables |
PUT /v2/services/amili/receivables |
| Check activation status | GET /v2/services/ropo/receivables |
GET /v2/services/amili/receivables |
| Transfer invoice | POST /v2/invoices/{id}/assignment/ropo |
POST /v2/invoices/{id}/assignment/amili |
| Close service | DELETE /v2/services/ropo/receivables |
DELETE /v2/services/amili/receivables |
For Amili Perintä, the legacy POST /v1/invoices/{id}/assignment endpoint is deprecated in favour of POST /v2/invoices/{id}/assignment/amili and will be shut down in Summer 2027. See Amili Perintä for the migration details.
For detailed API documentation, see the Receivables API page and the Swagger documentation.
Integration recommendations
At a minimum, automate the following from the ERP:
-
paidevents — Report direct payments (payments received on the sender’s own account) so the collection agency can update or close the assignment. -
credit_noteevents — Notify the collection agency when a credit note is issued against an invoiced assignment.
Relying on end users to manually report these through the UI is error-prone and can lead to unnecessary collection actions on invoices that have already been paid or credited.
To keep your ERP in sync without polling, subscribe to Receivables webhooks and receive events shortly after they occur.