Start from the invoice date→Count weekdays when required→Apply the weekly Monday rule→Keep statement cadence separate
The working interface
See it in use.
Explore 1 real view of this workflow. Select a task, show every screen, or enlarge an image to read the original controls.
Inspect the saved two-business-day rule / Actual Odoo screenEnlarge screenshot ↗
01 / Accounts receivable
Inspect the saved two-business-day rule
Read the configured two-business-day term.
Confirm the reference is the invoice date.
Keep statement frequency separate from the due-date rule.
Actual Pro-A-Motors interface captures. Private identities and contact details are covered or outside the crop; screen data has not been replaced.
What improved
Make the payment deadline follow an explicit calendar.
The business problem
“Two days” and “two business days” are not the same over a weekend. A short term label can also hide whether a deadline follows the order date, invoice date or a weekly bucket.
What we changed
Weekday-based terms skip Saturday and Sunday, and the weekly Monday term has its own explicit calculation.
What the team can do now
Accounting can use deterministic due-date rules and explain the calendar behind the customer’s terms.
Read the saved business rule
The term says exactly which calendar it uses.
The saved term requires 100% of the amount two business days after the invoice date.
Amount
100%
Delay
2 business days
Reference
Invoice date
What the screen shows
The actual due-term row says Business days after invoice date. The reviewed implementation skips Saturday and Sunday.
What the team does next
Use this term where a weekday-based deadline matches the agreement. Public holidays are not excluded by this implementation.
What the next team receives
The invoice due date follows the configured rule, while statement cadence remains separate.
How the work moves
Follow the work from one decision to the next.
01
Start from the invoice date
Use Odoo’s payment-term reference date for the calculation.
02
Count weekdays when required
Advance the configured number of days while skipping Saturday and Sunday.
03
Apply the weekly Monday rule
For the custom Monday term, find the invoice week’s Monday and add fourteen days.
04
Keep statement cadence separate
Let statement frequency and the invoice due-date rule retain their distinct meanings.
Built, used, refined
How the workflow improved over time.
Make the Monday rule explicit
Added the custom weekly-bucketed Monday term and related statement refinements.
Support business-day terms
Added weekday-based payment-term calculation and the two-business-day configuration.
About these dates
Dates identify recorded implementation changes, not claimed rollout dates or measured results. Reviewed revisions: 13a6c6a, 3435405.
Build notes and background
Financial workflowsWorkflow automation
The boundaries we made explicit.
Weekdays are not a holiday calendar
The implementation skips weekends; it does not consult a public-holiday calendar.
The invoice date is the reference
A later invoice date can place the item in a different weekly bucket from the sales-order date.
The Monday label needs explanation
Invoices in the same Monday–Sunday week share the Monday two weeks after that week began.
Existing records are shown as captured. Private identities are covered or outside the crop. No business records were changed for this collection. Implementation history supports behavior beyond the visible screen; a still image is not an end-to-end test or a measured productivity result.
Built on Captivea CAP modules and Odoo. This case describes the subsequent Pro-A-Motors extensions and refinements recorded in the reviewed repository; it does not attribute the original CAP implementation to Toro.
