Ropo’s reminder and collection service is now available through the Maventa API. Transfer overdue invoices to Ropo for reminder sending and debt collection in Finland, Sweden, and Norway. Track each assignment’s collection status through the Receivables API, and report direct payments and credit notes back to Ropo to keep balances up to date. For full details, see the integration guide.
Service activation
Activate the service using PUT /v2/services/ropo/receivables with the agreement_contact_email parameter. Ropo sends a wizard form to the provided email where the authorised person provides company details and signs the agreement electronically. In Finland, a separate KYC verification step is required.
Check the activation status with GET /v2/services/ropo/receivables. Activation typically takes 1–2 business days after the agreement is signed.
Transferring invoices
Transfer overdue invoices using POST /v2/invoices/{id}/assignment/ropo. B2B invoices can be transferred 7 days after the due date; B2C invoices after 14 days.
Key parameters:
-
collection_type—reminder_and_collection(full process) orcollection(skip reminders) -
receivables_type—b2b,b2c,b2b_rental, orb2c_rental -
payers— array of payer objects with full address details -
assignment_summary— description of what the assignment refers to
Check the transfer status with GET /v2/invoices/{id}/assignment. Possible statuses: pending, sent, or error.
Tracking assignments and reporting events
Each transferred invoice creates an assignment that can be tracked through the Receivables API:
-
GET /v1/assignments— list all assignments -
GET /v1/assignments/{assignment_id}— fetch details for a specific assignment -
GET /v1/assignments/{assignment_id}/events— get events for the assignment to see detailed status progression -
POST /v1/assignments/{assignment_id}/events— post events to inform Ropo of direct payments or connect credit notes
Assignments have a collection_status that progresses through stages such as reminder_sent, debt_collection, legal_collection, and payment_plan.
Use the POST events endpoint to report:
-
paid— a direct payment to the company’s own account (fields:sum_paid,booked_at) -
credit_note— a credit note to cancel or partially credit an assignment (fields:credit_sum,booked_at)
Automating these events from the ERP is strongly recommended so that Ropo can update balances and close assignments correctly.
Closing the service
Close the service with DELETE /v2/services/ropo/receivables. Ropo continues to handle any open assignments after the service is closed.