Installments and recurrence
Payables support two modes beyond a plain one-off payment: installments and recurrence.
The three types
The Type field, required, offers:
| Type | What it is |
|---|---|
| One-time | A single bill, no repetition |
| Installment | Split into N installments with sequential due dates |
| Recurring | Repeats on its own at a fixed interval |
Installment
Pick the type and the Installments field appears, for the number of installments: from 2 to 120.
The amount is per installment, not the total. In Amount (R$) you enter what each installment is worth — 12 × R$ 100 is entered as amount 100 and 12 installments, not as 1,200. The summary next to the form shows both: Each installment and Total over 12 installments.
On save, the system creates all N bills at once, with monthly due dates starting from the first due date (one month per installment) and sequential numbering — Installment 1/12, Installment 2/12… When the day doesn't exist in a month (the 31st in February), that installment falls on the month's last day.
Each installment is an independent bill: it can be paid on its own, and its due date or amount can be adjusted later, one by one.
Installments are chosen at creation. On a bill that is already part of a series, Type and Installments are locked — "Part of a series: the type and the number of installments can't change." A saved One-time bill can become Recurring, but not Installment.
Moving between installments
On an installment's detail screen, the arrows take you to the previous and the next one in the same series. The Installments action, in the row menu, lists the whole series.
Recurring
Pick the type and the Recurrence field appears, required, with five periods:
| Option | Interval |
|---|---|
| Every week | 7 days |
| Every two weeks | 14 days |
| Every month | 1 month |
| Every 3 months | 3 months |
| Every year | 12 months |
The label gets shorter in the listings — the same recurrence shows up as Weekly, Biweekly, Monthly, Quarterly or Yearly. Same thing, written short to fit the row.
The next ones are recorded ahead
A recurrence is born with the coming months already recorded. On creation the system stores the occurrences up to 12 months ahead (the default), and the window moves by itself: every day the series are filled up to the new limit. Each occurrence is a real bill — it enters the cash flow, its amount can be changed, and it can be settled before the previous one.
The horizon lives in Recurrence settings, the gear on the payables or receivables listing: Months to provision, from 0 to 36. Raising it fills the series at once; lowering it doesn't delete what is already recorded, it only stops recording beyond the new horizon. With 0, each series keeps only the next bill open, and the following one is born when it is settled.
With payment approval on, every occurrence of a new series enters the approval queue.
Occurrences count from the first one. A monthly series that starts on the 31st falls on the last day of shorter months and goes back to the 31st when the month has 31 days. Moving one occurrence's due date affects only that one: the following ones stay on the series' original day.
Each recorded occurrence copies the latest one in the series — amount, category, classification center, payment method, taxes and withholdings, document and notes.
A saved One-time bill can become Recurring: change the type and pick the recurrence, and the system starts the series from it.
Repeat until (optional, next to the recurrence) is the series' last due date; empty, the series never ends. The date applies to the whole series: shortening it removes the open bills after the new end, and extending it records again. It can't be before the due date of the bill you are editing. On an imported series (Fintera, Nibo), the end comes from the source and the field doesn't show.
To change the amount of the coming months, edit an occurrence: the propagation dialog lets you choose which others in the series inherit the change. Occurrences recorded from then on follow the latest one.
Beyond the horizon, the cash-flow projection continues the series at display time, without storing it. See Dashboard.
The Recurrences action, in the row menu, lists the recorded occurrences of the series. On the bill's detail, Previous due date and Next due date move through them.
Deleting
When you delete a bill that belongs to a group, the system offers:
- Delete only this one — removes just the current occurrence. On a recurrence it isn't recorded again: the series goes on from the next one.
- Delete this and future ones — removes the current one and every following one in the group. On a recurrence it also ends the series there: the removed bills aren't recorded again.
What was already paid stays. "Occurrences already paid or reconciled are kept." If any of the following ones can't be deleted, the notice says how many were left.
An imported series isn't deleted from here. On a series that came from an integration (Fintera, Nibo), Delete this and future ones is refused — "This series comes from an integration; delete it at the source". Its end also comes from the source.
The scope isn't exclusive to recurrences. The picker looks at the group, so installment and recurring bills behave the same. On a standalone bill it doesn't appear.
The picker lives in the listing. Delete from the detail screen and only that one bill goes.