$ 60.00
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Invoicing (account)
• Discuss (mail) |
| Lines of code | 683 |
| Technical Name |
payment_processing_omax |
| License | OPL-1 |
| Website | https://www.omaxinformatics.com |
| Versions | 13.0 14.0 15.0 16.0 17.0 18.0 |
Vendor & Customer Payment Processing
Overview
The Payment Processing module enables your company to manage mass payments efficiently for both vendors and customers. Users can quickly identify unpaid bills, invoices, refunds, and receipts and initiate payments for multiple records at once.
Payment drafts can be created and submitted for validation/approval. Assigned validators/approvers (Accounting Access: Invoicing = Billing OR Billing Administrators) receive automatic email notifications to review, validate/approve payments.
Once validated, the system reconciles refunds against related invoices/bills and receipts and generates payments according to Odoo’s standard financial workflows.
This module streamlines your end-to-end payment processing, improves control with approval, and saves time when managing large volumes of vendor and customer payments.
Features
2. Separate menu for vendors and customers Payment Processing.
3. Users can initiate Payment for Unpaid Bills/invoices & Refunds & Receipts with Payment-method, Amount.
Vendor Payment Processing functionality perform with the menu..
Menu A: Unpaid Bills & Refunds & Purchase Receipt:
It's for vendor payments. Unpaid Bills, Refunds, Purchase Receipts available here. User can select records and initiate payment processing and prepare Payment drafts.
Menu B: Register Payment for Vendors :
Its contains Payment drafts with unique sequence number. User can send request for validation/approval.
Accounting Users(requested users from Accounting Users) can validate the Payment-Draft.
If refunds are available for a vendor, the system automatically reconciles refunds with bills & purchase receipts in ascending order by bill date. Older refunds are matched to older bills first. Any remaining unpaid amounts are then settled by creating a new vendor payment, which is also reconciled with the remaining bills and receipts accordingly.
If refunds not there, simply vendor payment will created and it will reconciled with the bills and receipts.
Similarly Customer Payment Processing functionality perform with the menu..
A. Unpaid Invoices & Credit Notes & Sales Receipt.
B. Register Payment for Customers.
4. Supports full and partially payments.
5. Maintain history of performed operation for easy traceability.
6. User validations while multiple Validators available.
How It Works
Accounting Access: Invoicing = Billing or Billing Administrator
Navigate to: Invoicing > Payment Processing
Menu Path:
Invoicing > Payment Processing > Vendor Payment Queue > Unpaid Bills & Refunds & Purchase ReceiptLogin with David User (Invoicing User).
Menu:
Unpaid Bills & Refunds & Purchase ReceiptIt's for vendor payments. Unpaid Bills, Unpaid Refunds, Unpaid Purchase Receipts available here. User can select records and initiate payment processing and prepare Payment drafts. User can register mass payments for multiple vendors here.
: Initiate Payment for Multiple Vendors/CustomersSelect records and click on the action Initiate Payment for Multiple Vendors/Customers
Wizard Explanation
Records Grouping & Sorting
- Records are grouped by Vendor’s name in alphabetical (ascending) order.
- Within each group, records are sorted by Bill Date in ascending order.
Wizard UI
The height and width of the wizard have been extended for better visibility.
Fields Description
- Payment Journal & Payment Date : Users can select the journal and payment date for the mass payment.
- Show Selected Partners (Boolean) : When selected, the Partners field becomes visible.
- Partners : Displays a list of unique vendors selected for mass payment.
- Partner : Shows vendor names, sorted alphabetically in ascending order.
- Reference : Displays the Bill Reference.
- Number : Indicates the Bill Number, Refund Number, or Purchase Receipt Number.
- Date : Shows the Bill Date.
- Due Date : Displays the Due Date of the bill, refund, or purchase receipt.
- Total : The total amount of the related bill, refund, or purchase receipt.
- Amount Due : Shows the remaining due amount for the record.
- Payment Method : By default, it is set to Manual Payment, but it is editable, and users can change it (e.g., to Check).
- Payment Amount : Displays the remaining payment amount for the record. It is editable, allowing users to change the payment amount if needed.
- Memo : Set from the Reference or Name of the related record. This field is editable for users to modify if required.
Prepare Draft Button :
: It will create a unique payment-draft under menu name Register Payment for Vendors.Payment Draft Creation
A new payment draft is created with a unique sequence number, such asVRP/2025/00001, and is set to Draft status.✅ Menu Path:
Payment Processing > Vendor Payment Queue > Register Payment for Vendors
Note: All payment information from the wizard will be passed to this record. Now Open this Payment Draft
VRP/2025/00001. Explanation available below this screenshot.
Payment Draft Descriptions: VRP/2025/00001
- Payment Journal & Payment Date: Its editable fields.
- Prepared By: Automatically assigned the user who created the payment draft. It's readonly field.
Validators
- Users can assign one or multiple validators.
- Only Invoicing Users (Accounting Access: Billing or Billing Administrator) are available in the Validators list.
- One of the validator from the assigned list can validate this payment draft.
- Note: A user can also assign themselves as a validator.
Buttons
- Request for Validate: To Validate this payment draft, it sends an email notification to assigned validators. If no validators are assigned when sending the validation request, the system will auto-assign all Invoicing Users to the Validators field.
- Cancel: The record can be cancelled only when it is in
DraftorIn Approvalstatus.
Payment Info Tab
- The Payment Method fields remain editable until the record reaches Validated status.
- Payment Amount will be readonly. Delete Option available until Validated status.
STEP 1: Assign Validators & Request for Validate
Once validators are assigned, click the "Request for Validate" button.
A. Email notifications will be sent to assigned validators: Marc and Parth.B. Status Change : The status of
VRP/2025/00001 is updated to In Approval.Email to Marc:
Email to Parth:
Validation Access Control
If a user who is not in the validators list tries to validate the payment draft, the system will restrict the action.
Example: Mitchell user tries to validate
VRP/2025/00001.
STEP 2: Login as Marc and Validate
Now login as Marc (an assigned validator) and validate the record.
Current Status: In Approval
After validation, the status of VRP/2025/00001 changes to Validated.
The record becomes read-only, and users can now track the completed transaction here.
System Result: Vendor Payment Processing
Total 5 vendor payments were created with Paid status and automatically reconciled with related bills.
Azure Interior
3 Bills: BILL/2025/07/0004, BILL/2025/07/0009, BILL/2025/07/0010
1 Refund: RBILL/2025/07/0001
Payment Method: Manual Payment
Amount: $3,646.50
Equation: $931.50 + $1,966.50 + $760.00 - $11.50 = $3,646.50
Note: Refund RBILL/2025/07/0001 is reconciled with Bill BILL/2025/07/0004, following the rule that older refunds are matched to older bills first..
- Memo: Vendor Register Payment
VRP/2025/00001is set in each payment - Bills & Refunds: Linked to corresponding payment (e.g.,
PBNK1/2025/00005) - Activity Logs: Visible in each payment record
Deco Addict
2 Bills: BILL/2025/07/0002, BILL/2025/07/0006
Payment Method: Manual Payment
Amount: $307.00
Equation: $207.00 + $100.00 = $307.00
Lumber Inc
3 Bills: BILL/2025/07/0003, BILL/2025/07/0007, BILL/2025/07/0008
- First two bills have Payment Method: Manual Payment
- Last bill has Payment Method: Checks
Grouped Payments by Payment methods:
• $1,840.00 → BILL/2025/07/0003 + BILL/2025/07/0007 ($920 + $920)
• $936.10 → BILL/2025/07/0008
OpenWood
1 Bill: BILL/2025/07/0005
Payment Method: Manual Payment
Amount: $1,380.00
Reconciliation Status of Bills & Refunds
Detailed Vendor Bill Records & Refunds
Azure Interior
BILL/2025/07/0004
Deco Addict
Lumber Inc
OpenWood
We can see here the payments have been successfully created and automatically reconciled with the corresponding vendor bills.
End of the Vendor Payment Processing flow.
Similarly User can execute Customer Payment Processing flow.
✅ Menu Path: Payment Processing > Customer Payment Queue
1. Unpaid Invoiced & Credit Notes & Sales Receipt
2. Register Payment for Customers
Free Support
Recommended & Suggested Apps
Get In Touch
| Our Odoo Services |
| For support, query and question contact us. |
Thank you for visiting
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