| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Invoicing (account)
• Discuss (mail) |
| Lines of code | 1151 |
| Technical Name |
account_payment_split |
| License | OPL-1 |
| Website | https://www.vauxoo.com |
| Versions | 16.0 17.0 18.0 |
Payment Split
This module allows to specify the amount paid on each invoice in a multi-invoice payment.
Usage
Create and validate more than one invoice for the same partner.
Select the invoices in the tree view and use the Register Payment action.
Select currency, journal and amount.
You can change the rate using the custom rate for all lines ( or the rate field for a specific line - This feature is not supported in this version).
Check the payment lines for each invoice.
Blue lines mean a correct partial payment
Normal lines mean a correct total payment
Red lines mean the payment amount is bigger than the due amount.
Change the payment amount or the payment currency amount if it's necessary.
Validate the payment.
Important Notice: Be aware that when running for the first time the wizard it will try to pay in full at the invoices. By doing so, when multi-currency invoices is involved, a special case is performed. We try the most to pay in full the invoices in the invoice currency too, to avoid leaving small cents to be paid later. For example: - Be your company currency MXN. - Be the invoice your are going to pay in MXN too: MXN 627.68 - Be your payment currency in USD. That is, you have selected a Journal in USD. - Set a custom_rate of 23.00 MXN / USD - Check for the computed rate in the line: 23.000366434591
Why is this done this way? Get your calculator on hand. Make the division: 627.68 / 23.00 => 27.290434782608696 which you would round to two digits, yielding 27.29. Now this amount in USD must be booked in MXN (company currency at the rate of your selection with two digits for rounding): 627.67. As you can see the conversion yields almost the same value that is to be paid for your invoice. But this will leave a small amount to be reconciled: MXN 0.01. Thus we, by design, have decide to round up to the full amount of the invoice. This only happens when half of a cent of the foreign currency converted to local currency is greater than the reamining value to be paid in full. That is, 0.01 / 2 * 23.00 => MXN 0.12 is greater than MXN 0.01. Then if we do this for greater or lesser values you would realize about this: - 27.28 * 23 = 627.44 - 27.29 * 23 = 627.67 --> This is our value which is the closes one to 627.68 - 27.30 * 23 = 627.90
This only applies for the edge case when the invoice is intended to be paid in full.
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