MODULES / FINANCE
Recurring Payments
Schedule repeated customer receipts or vendor payments and generate ordinary draft payments for review.
Overview
| Module id | ask_recurring_payments |
|---|---|
| Version | 1.0.0 |
| Who uses it | Anyone who uses the screens listed below. |
| Installed | On demand, from Settings → Modules. Anything it needs is installed with it. |
Where to find it
| Accounting | Recurring payments |
|---|
The menu entries appear once the module is installed and your role allows them.
How it links to other modules
- Needs: Accounting
- Works better with: no other module in particular
- Needed by: no other module
A module that is needed cannot be turned off while the module that needs it is on.
Details
Recurring Payments
Optional ASKERP adaptation of the recurring-payment schedule in D:/Odoo18/sparkosol/addons.odoo18/om_recurring_payments (LGPL-3). No Odoo source code is copied. Install it from Settings → Modules. It depends on Accounting.
Create a plan for a customer receipt or vendor payment, choosing an active bank or cash journal, positive amount, start date, optional end date, and an interval in days, weeks, months or years. Monthly/yearly dates are calculated from the original start date and clamp to the last valid day of shorter months. For example, a monthly schedule starting on January 31 runs February 28/29 and then returns to March 31.
Use Generate due drafts to create due payments through the selected date. This operation is serialised on the plan; a unique occurrence number and company-scoped foreign keys ensure one occurrence maps to one ordinary payment. The generated payment is always a draft and is linked from the plan. Review it in the normal customer/vendor payment screen, allocate it as appropriate, and post it through ASKERP's shared payment workflow. Existing approval thresholds, lock dates, numbering, ledger posting, reconciliation and audit behavior remain authoritative. A late schedule can generate up to 100 occurrences per request; use an earlier through-date to catch up in bounded batches.
Plan terms cannot be edited after creation. Pause and resume are explicit; a plan with an end date becomes completed after its final due occurrence is generated. Generated occurrences and their payment links are immutable. Pausing does not delete prior drafts or posted payments. Disabling the addon hides the register without deleting any schedule or payment history.
Scope limits
- Due payment drafts are generated only when an operator requests it. There is no background scheduler, automatic posting or automatic allocation.
- Only company currency and a fixed amount per occurrence are supported.
- Amount changes, end-date changes and other plan-term edits are not available; create a replacement plan and pause the old one if terms must change.
- The module schedules payments, not recurring invoices or vendor bills.
- Draft payments stay subject to normal accounting permissions and any configured approval requirement at posting time.
The plan and occurrence tables use forced PostgreSQL RLS, tenant-composite foreign keys, database state/content guards and stable parent-row locking. Tests cover date clamping, end-date completion, standard ledger posting, duplicate and concurrent generation, module retention, tenant isolation and immutable terms.