| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Invoicing (account)
• Purchase (purchase) • Sales (sale_management) • Discuss (mail) |
| Lines of code | 995 |
| Technical Name |
sp_post_dated_cheque_mgt |
| License | OPL-1 |
| Website | https://speeduplight.com |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Invoicing (account)
• Purchase (purchase) • Sales (sale_management) • Discuss (mail) |
| Lines of code | 995 |
| Technical Name |
sp_post_dated_cheque_mgt |
| License | OPL-1 |
| Website | https://speeduplight.com |
Post Dated Cheque (PDC) Payment Management
Manage Post Dated Cheques for Customer Invoices and Vendor Bills with full accounting journal entry support.
FREE 90 DAYS SUPPORT
Speeduplight will provide FREE 90 Days Support for any doubts, queries, and bug fixes (excluding data recovery). This support is applicable from the date of purchase.
Control access using dedicated PDC Payment user group
Configure the PDC holding account from Accounting Settings
Register PDC payment directly from customer invoice — enter cheque reference, due date, agent and bank
Invoice is marked as In Payment once the PDC payment is created
PDC payment form shows full cheque details with journal entry link

Automatic journal entry on PDC confirmation — Dr PDC Account / Cr Receivable
Dedicated PDC Payments menu under Customers for easy access
PDC Payments list view with cheque reference, due date, PDC state and payment state badges
Collect Cash creates a clearing journal entry — Dr Bank / Cr PDC Account
PDC state changes to Cleared and payment state to Paid — shows Collection Journal and PDC Clearing Entry
Complete audit trail — all journal entries visible for the full PDC cycle
Bounce reason is mandatory before bouncing a cheque — validation prevents incomplete records
Enter bounce reason before clicking Bounce — reason is tracked in chatter for full audit trail
PDC state changes to Bounced and payment state to Rejected — shows bounce date, bounce entry and reason
Bounce journal entry reverses the original PDC entry — invoice goes back to unpaid
Register PDC payment directly from vendor bill — same wizard with PDC checkbox
Vendor bill marked as In Payment once PDC is created
Vendor PDC payment form with journal entry link

Vendor PDC journal entry — Dr Payable / Cr PDC Account (opposite direction from customer)
Dedicated PDC Payments menu under Vendors — separate from customer PDC
Vendor PDC Payments list view showing all vendor cheques with status badges
Release Payment button for vendor PDC — select Payment Journal and release when cheque is deposited by vendor
Vendor PDC cleared — state changes to Paid, shows Payment Journal and PDC Clearing Entry
Complete vendor PDC journal entries — full audit trail from creation to release
Automatic activity notifications — get alerted 3 days before cheque due date and for overdue cheques
PDC Payment Report — separated into Customer Payments and Vendor Payments sections with status badges
Our Odoo Services
Consulting
Development
Migration
Support
Integration
Training
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module