| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Invoicing (account)
• Discuss (mail) |
| Lines of code | 99 |
| Technical Name |
hrl_advance_payment |
| License | OPL-1 |
| Website | https://www.lemacore.com |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Invoicing (account)
• Discuss (mail) |
| Lines of code | 99 |
| Technical Name |
hrl_advance_payment |
| License | OPL-1 |
| Website | https://www.lemacore.com |
Advance Payment
Record advance payments before any invoice exists — directly from the
Payment
menu. Simply check
Advance Payment
and the amount posts to a dedicated outstanding account — ready to match when the invoice arrives.
Email Us
LinkedIn
Configure Advance Payment Account
Set a dedicated Advance Payment Account for both Customer and Vendor payments via Accounting Settings — advance amounts post to the configured outstanding account instead of directly settling an invoice.
Customer Payments
Vendor Payments
Input Advance Payment & Journal Entry
Check Advance Payment on the payment form — the system automatically posts the amount to the configured outstanding account as a draft journal entry, ready to be matched against an invoice later.
Check Advance Payment on Payment Form
On the Vendor Payment form, tick the
Advance Payment
checkbox. The payment will not settle any existing bill — it records the advance separately.
Draft Journal Entry — Posted to Outstanding Account
A draft journal entry is created automatically — debiting
11120003 Outstanding Payments
as configured in Accounting Settings. The advance is now tracked and ready to be matched when the vendor bill arrives.
Dedicated Advance Payment Checkbox
A single Advance Payment checkbox on the payment form separates
advance transactions from regular settlements — no risk of accidentally closing an open invoice.
Separate Outstanding Account per Payment Type
Configure a dedicated Advance Payment Account for both
Customer Payments (11120002) and Vendor Payments (11120003)
— keeping advance funds clearly separated in your Chart of Accounts.
Auto Draft Journal Entry
Upon saving, a draft journal entry is generated automatically — debiting the configured outstanding account. No manual journal entry required, your books stay balanced from day one.
Invoice-Independent Payment Flow
Pay vendors or receive from customers before any invoice exists. The advance sits in the outstanding account until you're ready to reconcile it against the actual bill or invoice.
Supports Both Send & Receive Payment Types
Works for outgoing advance payments to vendors (Send) and incoming advance receipts from customers (Receive) — covering the full cycle of prepayment scenarios in one module.
Native Odoo Integration
Built on top of Odoo's native account.payment model —
fully compatible with your existing journal setup, payment methods,
multi-currency configuration, and bank reconciliation workflow.
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