Many retailers order the same goods every week or every month. A standing order saves you from typing the same invoice again. Reyuko's Recurring Sales feature creates repeat documents from a saved template. It does not run on its own, and the documents it creates are simpler than a normal invoice.
Key takeaways
- Recurring Sales creates Invoices or Quotations from a template. It does not create Sales Orders or Delivery Orders.
- Nothing runs in the background. Someone must click Execute each time.
- Generated lines carry SKU, name, quantity, unit and price only. Tax, discount, payment term, due date and location are not copied.
- Turn Auto-post off while you learn the feature, so you can check each draft first.
- Auto-email only saves a setting. You send the email yourself.
Turning the feature on
Recurring Sales needs the Advanced level and the Recurring module. The module is on by default. To check it, go to Settings > Customization and look at Optional Modules. Turning a module off only hides its menu, and your data stays safe.
Creating a template
Go to Sales > Recurring Sales and create a template. The main fields are:
- Template Name and Module, which is Invoice or Quotation.
- Recipient: a single customer, or a customer group. A group matches the Customer Group text on each contact and creates one document per customer.
- Frequency (Daily to Yearly) with Every n, plus Start Date and End Condition.
- Auto-post, which posts each generated invoice to the journal at once.
- Lock price, Lock qty and Auto-email customer, then the item lines.
Illustration: Harbor Wholesale is a fictional business; numbers are examples. A retail customer takes 50 cartons of rice every month at 300,000 per carton. The template line is 50 times 300,000, which is 15,000,000 before tax.
Running it is manual
Reyuko does not create documents on a schedule. On the Recurring Sales page, click Execute, Execute Now or Execute Selected. You can also Skip one occurrence, with an optional reason, or Pause and Resume a template. Execution History lists past runs. Due-today and overdue schedules show as cards. The same run can also start from the Calendar. The Execute dialog also offers Price Mode: Use contract price or Update price manually.
Each generated document is dated the day you run it. It is a Draft (or Open, for a Quotation) unless Auto-post is on. Its note reads "Recurring {template} — occurrence #n". A group run creates one document per customer, and skips a duplicate for the same date.
A generated invoice has no tax, no discount, no payment term and no due date. If you post it unchanged, it has no tax and no due date, so it stays in the Not Due bucket of the aging report. Check every draft before posting.
A safe review routine
Use this routine each time you execute a template:
- Set Auto-post to off, so each run creates drafts only.
- Open each draft and add the tax lines the customer should carry.
- Choose the payment term, so the due date and any installments are set. See Setting Customer Payment Terms.
- Check the price against your current price list, because the template price is copied to each document.
- Set the location on the header if the goods come from a specific warehouse. Location is not copied from the template.
- Post the invoice, then email it yourself.
- Go to Sales > Recurring Sales, open the template, and click Execute or Execute Selected.
- Open each draft in Sales > Invoice. Add tax, then choose the Payment Terms card and check the due date.
- Click Post. Use Finalize only when the invoice is right.
A generated invoice is not linked to a Delivery Order, so Reyuko creates no dispatch step for it. Arrange the delivery yourself, and check stock before you post. Use Pause when a customer stops ordering, and Skip for a single period. The Repeat annually (marked in Calendar) checkbox on a payment term only marks a Calendar date. It does not create a template.
Check yourself: what does a template copy to each invoice?
The SKU, name, quantity, unit and price on the template line. Tax, discount, payment term, due date and location are not copied, so add them to each draft before you post.
Reyuko