Recurring invoices: a reliable schedule still needs a review
Choose billing dates, check month-end behaviour and separate invoice creation from delivery and payment collection.
By the Novaveliq team

The useful bit
A recurring schedule describes when an invoice should exist. Sending it and collecting the payment are separate decisions.
Start with the service period, not the repeat button
Before choosing a frequency, decide what each invoice covers. Is the customer paying in advance for the coming month, or after the month of service has ended? Does the first invoice cover a full period or only the remaining days? These commercial decisions should lead the schedule rather than being guessed from a convenient date picker.
Write the service period into the description or line items. A customer who receives several similar invoices should be able to distinguish one period from the next without comparing email timestamps. Confirm any part-period pricing with them before the first invoice is issued.
Check the dates that do not fit every month
A schedule anchored on the 31st needs a clear rule for shorter months. Check how your invoicing tool handles February, leap years and months with 30 days. Also distinguish a calendar-month frequency from a fixed number of days: repeating every 30 days will not consistently land on the same day of each month.
Preview several upcoming dates, including at least one awkward month-end. Review the invoice due dates as well as issue dates. A billing schedule that is convenient for you may still conflict with a customer's agreed approval cycle.
Set up the schedule in Novaveliq
Start in Invoices and create an invoice with the correct customer, currency, line items, issue date and due date. In the invoice editor, use Repeats to choose Weekly or Monthly for the secure workspace. For a monthly arrangement, review the month-end option where appropriate and inspect the upcoming dates before saving or sending.
For an existing invoice, open its automation controls and review Recurring invoice and Next invoice date. A generated child invoice directs schedule changes back to its original invoice. Check the customer and collection method as well as the dates, then save the automation changes deliberately rather than assuming an edited invoice also changes every future collection.
Review whether recurring invoices should be emailed automatically using the controls available for that invoice. Confirm that the relevant service is configured before relying on unattended processing. Run through the first complete cycle and check the created invoice, delivery status and payment outcome separately.
- Confirm the agreed service period, amount, customer and due date.
- Choose a supported weekly or monthly schedule and review upcoming dates.
- For an existing schedule, check the next date and manage it on the original invoice.
- Review automatic delivery separately from the selected collection method.
- Check the first actual invoice and receipt rather than only the saved schedule.
Give the template a proper owner
Recurring templates can repeat a mistake very efficiently. Assign someone to review the contact, price, quantity, currency, tax treatment and payment instructions when the arrangement changes. A corrected customer record does not automatically prove that every old template is up to date.
Use invoice numbers that remain unique as the schedule progresses. Keep the description current when the service changes, and agree any fee increase before the next invoice is issued. A recurring setting should not replace the underlying customer agreement.
Separate creation, sending and collection
There are three separate questions: will a draft be created, will an issued invoice be sent, and will money be collected? A repeating date does not answer all three. A manual invoice can follow a monthly schedule while still requiring a person to send it and a customer to make a bank transfer.
If automation is enabled, check its settings, dependencies and current status. Direct Debit additionally needs a suitable provider connection, mandate and collection process. Do not mark the invoice paid just because its creation date or collection date has passed.
- Creation: confirm whether the next item is a draft or an issued invoice.
- Delivery: confirm the recipient and whether sending is manual or configured automatically.
- Collection: confirm the selected payment method and any required mandate.
- Review: inspect the actual invoice and payment outcome, not only the schedule.
Plan the pause and the final invoice
Set an end date where the agreement has one, and define how a pause or cancellation should affect future invoices. Check whether any already-created draft or pending collection also needs attention. Stopping a schedule does not necessarily cancel every action previously created from it.
In Novaveliq, review the recurring schedule's upcoming dates and the invoice's collection method, then check the available automation controls before relying on unattended processing. After the first complete cycle, verify the invoice, delivery and receipt records. Repeat that review whenever the arrangement changes.
Further reading
NovaveliqLess paperwork. More room to build.
Keep your invoices, contacts and payment instructions organised in Novaveliq.
Create your workspace
