Payment Calendar

v 17.0 Third Party 2

Availability	Odoo Online Odoo.sh On Premise
Odoo Apps Dependencies	• Expenses (hr_expense) • Invoicing (account) • Sales (sale_management) • Discuss (mail) • Employees (hr)
Lines of code	880
Technical Name	`kw_payment_calendar`
License	LGPL-3
Website	https://kitworks.systems/

You bought this module and need support? Click here!

Availability	Odoo Online Odoo.sh On Premise
Odoo Apps Dependencies	• Expenses (hr_expense) • Invoicing (account) • Sales (sale_management) • Discuss (mail) • Employees (hr)
Lines of code	880
Technical Name	`kw_payment_calendar`
License	LGPL-3
Website	https://kitworks.systems/

Payment Calendar report

Wizard-driven HTML cash-flow calendar for posted invoices and bills, grouped by partner, article or product. Available on Odoo 17.0 only.

Pick date range, journal type, group-by axis. Result is a printable HTML calendar with cash inflow and outflow rows.

Group by partner, by article, by product or by analytic budget post. Multiple groupings nest in the same report.

Calendar reads only posted account.move records. Drafts and cancelled entries are excluded automatically.

Optional overlay of account.budget.post line items on the same calendar grid. Compare planned vs actual cash flow.

Wizard configuration preview — payment calendar grouping options.

Odoo 17.0 only. Module depends on hr_expense, analytic and account.budget.post APIs that changed significantly in 18.0+. Forward-port to 18.0 / 19.0 is on the roadmap.
Report-only. No new business logic or new account models. Reads existing posted records and renders an HTML calendar.
Wizard-driven. Each report run requires explicit wizard input (date range, group-by, optional budget overlay). No background pre-generation.
SCSS asset. Bundles a single SCSS file inside web.report_assets_common for the calendar table styling.

Payment Calendar lives alongside KitWorks UA print forms, FOP suite and accounting utilities.

Kitworks Systems supports the Payment Calendar module. Reach out for installation help, bug reports or forward-port enquiries.

The author can leave a single reply to each comment.
This section is meant to ask simple questions or leave a rating. Every report of a problem experienced while using the module should be addressed to the author directly (refer to the following point).
If you want to start a discussion with the author, please use the developer contact information. They can usually be found in the description.