Invoices and payments
Send reminders and invoices, and handle payments from an automation.
Last updated on
These steps are in the Invoices and payments group. How the exits work is explained under Exits of an action.
Send payment reminder
Sends the payment reminder of an invoice to the customer, just like the reminder button on the invoice does.
| Field | What you fill in |
|---|---|
| Invoice | The id of the invoice. {invoice.id} by default. Required |
Note that the field expects the internal id of the invoice ({invoice.id}) and not the invoice number ({invoice.displayId}).
The step fails if:
- the invoice is not booked
- nothing is outstanding any more, so the invoice has already been paid
- the customer has no email address, phone number and complete postal address
The run then gets the status Failed and the rest of the flow is not executed. So put an If / else before the reminder that checks whether the invoice is still outstanding, as in the Follow up unpaid invoices template.
The step also skips an invoice if it has been taken out of automated reminders, or if the customer has Exclude from automated reminders turned on.
Sync bank transactions
Fetches new bank transactions and waits until the import has finished. Put this step before Send payment reminder, so that an invoice that has just been paid does not get a reminder. If Ponto is not connected, the step is skipped.
Save the automation from the office network. Tillor then remembers the IP that the bank connection needs. Without that IP the sync cannot start.
Disable automated reminders for customer
Turns on Exclude from automated reminders in the customer's invoicing settings. Reminder flows then skip all of that customer's invoices. A manual reminder remains possible.
| Field | What you fill in |
|---|---|
| Customer | The id of the customer. Required |
Disable automated reminders for invoice
Takes one invoice out of overdue reminder flows and automated reminders. Staff can still send a reminder manually.
| Field | What you fill in |
|---|---|
| Invoice | The id of the invoice. Required |
Send invoice
Sends an invoice to the customer, in the same way as the send button on the invoice.
| Field | What you fill in |
|---|---|
| Invoice | The id of the invoice. {invoice.id} by default. Required |
The step fails if the invoice is not booked or if the customer has no email address, phone number and complete postal address.
Book invoice
Books a draft invoice, so that it gets its invoice number.
| Field | What you fill in |
|---|---|
| Invoice | The id of the invoice. {invoice.id} by default. Required |
If the invoice is already booked, nothing happens and the flow continues via Skipped. After booking, the action returns {bookedInvoice.displayId}, the invoice number. You can use it in a message or task. Combine the step with Send invoice to book and send a draft invoice in one go.
Print invoice
Prints an invoice, or shows it on the tablet at reception.
| Field | What you fill in |
|---|---|
| Invoice | The id of the invoice. {invoice.id} by default. Required |
| Where | A4 printer (default), Receipt printer or Tablet |
You set up the printers under Print settings. An invoice that you print a second time with this step is simply printed again.
Create payment link
Creates an online payment link for the amount that is still outstanding on an invoice.
| Field | What you fill in |
|---|---|
| Invoice | The id of the invoice. {invoice.id} by default. Required |
| Payment method | Let the customer choose (default), Bancontact, iDEAL, Credit card or Payconiq |
The link only exists for a booked invoice with something still outstanding. If the invoice is not booked or already paid, the flow continues via Skipped. After that, the action returns {paymentLink.url}. Put it in a text, for example in a message via Message a guest.
Request SEPA mandate
Sends a customer an email asking them to sign a SEPA mandate, or a reminder for a request that is still open. See Mandate for the mandate itself.
| Field | What you fill in |
|---|---|
| Customer | The id of the customer. {customer.id} by default. Required |
| Send | A new request (default) or A reminder |
A new request is skipped if one is already open. A reminder is skipped if there is no open request, or if the request has expired. In both cases the flow continues via Skipped.
Collect by direct debit
Collects what is still outstanding on an invoice using the customer's active SEPA mandate.
| Field | What you fill in |
|---|---|
| Invoice | The id of the invoice. {invoice.id} by default. Required |
| After days | How many days Tillor waits before collecting. At 0 it is collected straight away. The maximum is 7 days, a higher number becomes 7. 0 by default |
The step collects the whole outstanding amount. If the invoice is not booked or already paid, or the customer has no active mandate, nothing happens and the flow continues via Skipped. If the customer has more than one active mandate, the step uses the newest.
Invoice consumption
Invoices a customer's outstanding meter consumption, books the invoice and sends it.
| Field | What you fill in |
|---|---|
| Customer | The id of the customer. {occupation.customerId} by default. Required |
| Send by e-mail | On by default |
| Send by text message | Off by default |
If there is nothing outstanding to invoice, no invoice is made and the flow continues via Skipped. Otherwise the action returns {consumptionInvoice.id}. See Meter management for how consumption is tracked.
Draft extension invoice
Creates a draft invoice that extends an occupation, ready to be checked. The invoice is not booked yet. It is the same kind of invoice you get with Extend occupation (invoice) on the customer profile.
| Field | What you fill in |
|---|---|
| Occupation | The id of the occupation. {occupation.id} by default. Required |
| Add open consumption | Puts the customer's outstanding meter consumption on the same invoice. Off by default |
The action returns {extendInvoice.id}. If you want to book and send the invoice straight away, then use Book invoice and Send invoice with {extendInvoice.id} as the invoice.