Recurring documents

Goal

Schedule recurring sales invoices or purchase bills that generate pending documents for human review. Schedules never post automatically.

Who it is for

accounting.view to list; accounting.manage to create, edit, activate/pause, and Run now.

Do not confuse with Recurring Journals under the ledger (those post journal templates and need accounting.post to create).

Preconditions

• Party (customer or supplier) and line items/accounts ready.
• For stockable sales lines, a warehouse is required before save (same client checks as invoices).
• Optional: analytical dimensions if lines require them at later post.

Steps

1. Open Trade → Recurring → Recurring documents (/recurring-schedules).
2. New schedule: name, document type (sales_invoice / purchase_bill), frequency (daily / weekly / monthly), interval (≥ 1), start date, optional end date, active flag.
3. Set party, currency (base if empty), notes, display options, and lines (same editors as invoices/bills).
4. Save — Schedule saved.
5. Run now (POST /recurring-schedules/run, optional as_of) creates up to 60 pending documents per run — toast Generated {count} pending document(s).
6. Open Pending documents to review, edit, and post each draft through the normal sales/purchasing lifecycle.

Result

Pending drafts appear for clerks; nothing hits AR/AP/stock/GL until a human posts the pending document.

Hard stops

• Client: warehouse required for stockable sales lines; below-minimum price checks mirror sales invoices.
• Cap of 60 occurrences per run.
• End date must be on/after start date.

Related

• Pending documents
• Sales invoices
• Purchase bills
• Dimensions