The invoice object

# Invoice details

Each payment method with attached apps will get an invoice for each service period (monthly) - after the service period ends. The invoice contains all the apps, their environments and booked components.

• Invoice number - An individual number.
• Invoice date - The day, the invoice was printed.
• Service period - The backdating month.
• Invoice address - Postal address from payment method.
• Invoice email - Email address from payment method.
• VAT - See VAT article.

# States

Invoices have a lifetime, going through various phases:

# Draft

During an ongoing service period, an invoice draft is kept and updated daily and with each booking. The invoice draft helps customers to keep track of current costs. During the DRAFT state the invoice will have a column to display current costs so far.

# Paid

At the enf of the service period, the invoice will be finalized, send to customers. The payment credentials of the payment method will be used to automatically pay the invoice. When successful, the invoice is paid.

# Bounced

When the payment credentials on file fail, the invoice will be marked as bounced. If that will not resolved after various automatic retries, service cancellation is next. See late payments.

# Invoice item rows

Each invoice contains a number of rows. They are grouped by environment as each has a set of booked components. Each invoice row contains the booked component and it's plan and how many days it is billed for by days. The table gives you an idea how components and plans appear on an invoice.

In this example PHP XS was booked for a couple of days and then replaced by PHP S. See the postpaid billing article for more on that.

The printed invoice document may look a bit different.