Recurring invoices in Klaq: a draft for each billing cycle

Repeat work often needs repeat billing, but the details still deserve a review. Klaq's recurring profiles prepare invoice drafts on a monthly or yearly schedule. You keep control of the moment a draft becomes an issued invoice.

The short version

Recurring invoices require Pro. Choose a source invoice, a monthly or yearly cadence, and a first occurrence date. When background processing is configured and runs, eligible occurrences create drafts. Review, finalize, and share those drafts separately.

Start with a source you can trust

Check the customer, descriptions, quantities, prices, currency, and payment details in the invoice you want to reuse. A recurring profile repeats a billing structure; it cannot know whether this month's work still matches the earlier agreement.

For a maintenance engagement, keep the recurring line specific enough to identify the service. Record a change in the engagement before relying on the next draft.

A void invoice cannot be selected as the recurring source. The first occurrence date must be today or later.

Choose the billing rhythm

Klaq supports monthly and yearly recurrence. Select the cadence that matches your existing arrangement and set the next occurrence date carefully.

Month-end schedules are adjusted to valid calendar dates. Still, review the generated occurrence rather than assuming every month contains the same day number.

The recurring worker protects an occurrence from being generated twice. A repeated background run should not create an extra draft for the same billing cycle.

Review each generated draft

Automatic draft preparation is the boundary of this workflow. Generated drafts are not automatically finalized, emailed, or collected.

Check whether the work is still active, the amount is still appropriate, and the recipient details are current. Finalize only when the document is ready to issue. Then download the PDF or explicitly queue the email.

Pause when the engagement changes

Pause a profile when repeat billing should stop. A profile is not a substitute for reviewing the customer's arrangement, and it does not create a payment-provider subscription.

If the workspace no longer has the required plan, recurring generation is restricted. Existing billing history remains available; that history does not imply future occurrences will continue to be created.

Common questions

Why has a due occurrence not appeared?

Check whether the profile is active, the date is due, the workspace is eligible, and background processing is configured. Ask the workspace administrator to inspect processing before creating a duplicate manually.

Will Klaq send reminder emails for these invoices?

Recurring draft generation does not schedule payment reminders. Use a deliberate manual follow-up workflow.

Explore Invoice or review reusable billing items.