Payment Notification System

Notification template fields:

• Id, e.g., “S001”.
• Name, e.g., “Reminder”.
• Type, single or list. List means table from several invoices.
• Subject, e.g., “Payment reminder ({{#customer}}{{{name}}}{{/customer}})”.
• Body. HTML body example. Rezult example.

The number of rules is not limited, you can create several rules for upcoming payments reminders and several rules for overdue payments notifications (the same notification template can be used for different rules).

Notification rules fields:

• Id, e.g., “T001”.
• Template id, e.g., “S001”.
• Replay to, e.g., “my@mycompany.com” (default – noreply@avanotify.com).
• Days remaining (Number. Can be negative), e.g., “1” means condition “send one day before the payment due (payment is not overdue)”, -1 means condition “send one day after the payment due (payment is overdue)”.

Invoice data consist from 3 blocks:

1. Customers:
   • Id, e.g., “5cd58ba1-4127-4f2b-adbf-dd778d73b6e6” (UID or other unique code from ERP)
   • Name, e.g., “Avakompas, UAB”
   • Registration number, e.g., “126062070′
   • VAT number, e.g., “LT260620716”
   • Address, e.g., “J. Galvydzio str. 5, Vilnius”
   • Email, e.g., “info@avakomp.lt”
2. Documents (invoices):
   • Id, e.g., “dcced82a-b421-497c-a6d8-5bd64612d15c” (UID or other unique code from ERP)
   • Type, e.g., “Invoice”
   • Date, e.g., 2022-08-25
   • Number, e.g., “AVA0501178”
   • Currency, e.g., “EUR”
   • Amount, e.g., 1210,00
   • Customer id, e.g., “5cd58ba1-4127-4f2b-adbf-dd778d73b6e6”
3. Balances (invoice balances):
   • Id (document id), e.g., “dcced82a-b421-497c-a6d8-5bd64612d15c”
   • Amount (left to pay), e.g., 500,00
   • Duedate, e.g., 2022-09-15