An invoice has an invoice date (the day it was issued) and a due date (the day it's supposed to be paid).

In the normal world, an invoice is static. If you create an invoice, it doesn't care if it's overdue and unpaid. A normal invoice is just a number in your accounting system, saying that a customer is supposed to owe you something.

Flows

In Likvido, this is different. In Likvido, we consider an invoice to have a lifecycle with the following 3 flows:

When you create a new invoice in Likvido, this enters an invoice flow. The invoice flow means Likvido is sending out the invoice with a friendly message to the customer, just like sending out the invoice from the accounting system.

However, if an invoice becomes overdue, the invoice can be assigned a reminder flow. A reminder flow is a series of messages to the customer that you can automate in Likvido.

If the customer is not paying after your reminder flow, it can be assigned to debt collection. Debt collection is very different from invoice and reminder flow, as 'Likvido Inkasso' is the sender. That means all letters/e-mails/SMS is not sent in your name but from our debt collection agency.

States

While the flow explains the high-level lifecycle of the invoice, the state gives more details. An example of 'State' could be Paused. An invoice can be paused in both the reminder flow or during debt collection. The state will in both scenarios be 'Paused,' but the flows are different.

There are more than 20 states in Likvido, but here are some of the most common ones: