Use Case Matrix
This matrix is a guide for customers and partners building an API integration against the Amili platform. It outlines which of the main use cases you must, should, or may implement via the API — and where the Amili App can complement your solution for use cases you choose not to integrate via API.
How to read this matrix
The API column indicates the recommended level of implementation for each use case in your integration.
| Value | Meaning |
|---|---|
| Mandatory | Must be implemented for a functioning integration |
| Recommended | Strongly recommended; if not implemented via API, it will often require manual handling in the Amili App, even for a standard debt collection process |
| Optional | Can be automated via API for additional value, or handled manually in the Amili App |
The Amili App column indicates whether the use case is available in the Amili App interface, giving you visibility into what your end users can handle manually when it is not covered by your integration.
| Value | Meaning |
|---|---|
| Supported | Available in the Amili App as a complement to your integration |
| N/A | Not applicable or not available in the Amili App |
Integration types — which use cases are mandatory depends on your integration type:
- Full-service integration: You handle both invoicing and collection via Amili.
- Collection-only integration: You issue invoices yourself and hand over to Amili for collection.
- Partner/platform integration: Your platform provisions and manages multiple accounts as an Amili partner.
See Integration Types for a full overview, or API Integration Process for setup steps.
Matrix
| Category | Use Case | API Integration | Amili App | Notes |
|---|---|---|---|---|
| Invoice Management | Invoice Registration | Mandatory¹ | Supported | Send invoices to customers through Amili, covering the full lifecycle from issuance to collection if unpaid |
| Case Management | Case Registration | Mandatory² | Supported | Register a claim for collection; supports both reminder and direct debt collection actions |
| Case Management | Supporting Document Upload | Recommended | Supported | Attach the original invoice PDF |
| Case Tracking | Single Case Status Lookup | Optional | Supported | View the current state and details of a specific case on demand |
| Case Tracking | Open Case Batch Export | Optional | Supported | View all active cases for reporting or reconciliation in your system |
| Case Tracking | Closed Case Batch Export | Optional | Supported | View completed/closed cases — including paid cases (triggers payout) and loss cases (write-off, bankruptcy, cancellation) that should be written off in your system |
| Creditor Actions | Payment Registration | Recommended | Supported | Notify Amili of a payment received directly from the debtor |
| Creditor Actions | Partial Crediting | Recommended | Supported | Credit part of the capital amount on a case |
| Creditor Actions | Case Cancellation | Recommended | Supported | Cancel an active case entirely |
| Creditor Actions | Case Respite (Postponement) | Optional | Supported | Postpone further collection activity on a case for a specified period of time |
| Finance | Payout Specification | Optional | Supported | Track capital and fees collected by Amili and paid out to you, at transaction level — for invoice-level reconciliation |
| Finance | Revenue Tracking | Optional | Supported | Track interest income and commissions that Amili pays out to you, at summary level |
| UI Integration | Deep Linking to Cases | Optional | N/A | Embed direct links from your own system (ERP, CRM) into the Amili App case view |
| User Management | User Management | Optional | Supported | Create users and assign access roles |
| Partner / Platform | Account and Creditor Management | Optional³ | Supported | Create and configure accounts and creditors |
Notes
¹ Invoice Registration is mandatory for full-service integrations, where Amili handles both invoicing and any subsequent collection. It is not applicable for collection-only integrations.
² Case Registration is mandatory for collection-only integrations, where the creditor issues invoices independently and hands over to Amili only when a claim needs to be collected. For full-service integrations, cases are created automatically from registered invoices.
³ Account and Creditor Management via API is mandatory only for partner/platform integrations that provision and manage multiple accounts and creditors programmatically. For single-creditor setups, these are handled once in the Amili App during onboarding.
Product modules — Amili's functionality is packaged in three modules. The mandatory use cases in this matrix correspond to the module(s) your integration activates:
| Module | Description | Activated by |
|---|---|---|
| FS (Faktura Service) | Invoicing and payment service | Full-service integrations |
| PM (Påminnelse) | Reminder service for overdue invoices | Collection-only integrations (reminder track) |
| IK (Inkasso) | Debt collection | Collection-only integrations (collection track) |
Full-service integrations activate FS and may progress automatically to PM/IK when an invoice goes unpaid. Collection-only integrations activate PM and/or IK directly, without FS.