Show Partner Balance in Sale Order
by Fasil https://www.bytesraw.com , Bytesraw https://www.bytesraw.com$ 8.98
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Invoicing (account)
• Discuss (mail) |
| Lines of code | 27 |
| Technical Name |
sale_show_partner_due |
| License | OPL-1 |
| Website | https://www.bytesraw.com |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Invoicing (account)
• Discuss (mail) |
| Lines of code | 27 |
| Technical Name |
sale_show_partner_due |
| License | OPL-1 |
| Website | https://www.bytesraw.com |
The Sale Show Partner Due module enhances Odoo's sales workflow by displaying the total amount due from a customer directly within the sales order interface. This critical information helps sales representatives make informed decisions about credit limits and payment terms before confirming new orders.
By providing immediate visibility of outstanding customer balances, this module helps businesses manage credit risk effectively, reduce overdue accounts, and maintain healthy cash flow while still providing flexible payment options to valued customers.
Key Features
- Real-time Due Amount: Displays the customer's current total due amount in the sales order
- Instant Visibility: Shows outstanding balance without navigating to other screens
- Risk Management: Helps control credit exposure by highlighting customers with large outstanding balances
- Decision Support: Enables informed decisions about payment terms and order approvals
- Seamless Integration: Works within the standard Odoo sales workflow
- Clean User Interface: Presents critical financial information without cluttering the sales form
Viewing Customer Due Amount in Sales Orders
- Navigate to Sales → Orders → Quotations
- Create a new quotation or select an existing one
- After selecting a customer, the module automatically displays:
- Total Receivable: The customer's current outstanding balance

Making Informed Sales Decisions
- Review the customer's outstanding balance shown in the "Total Receivable" field
- Consider the customer's payment history and credit limit
- Based on this information, decide whether to:
- Proceed with the standard sales process
- Request advance payment
- Adjust payment terms
- Seek approval for exceeding credit limits
Managing Credit Risk
- For customers with high outstanding balances:
- Consider requesting partial or full payment in advance
- Discuss settlement of existing invoices before processing new orders
- Consult with the finance team if necessary
Confirming Orders
- When confirming an order for a customer with outstanding balances:
- The module continues to display the total receivable amount
- This information remains visible throughout the sales process
- Sales teams maintain awareness of the customer's financial position
The module extends the standard Odoo sales workflow through the following modifications:
- Adds a total receivable field to the sale.order model
- Creates a computed field that fetches the current partner's due amount
- Displays this information prominently in the sales order form view
- Automatically updates the field when the customer is changed
- Reduced Credit Risk: Awareness of customer debt helps control credit exposure
- Increased Cash Flow: Encourages collection of outstanding invoices before new orders
- Informed Decision Making: Sales teams can consider financial factors when processing orders
- Streamlined Process: Eliminates the need to check customer accounts separately
- Preventive Approach: Helps identify potential payment issues before they escalate
- Better Customer Relationships: Enables proactive discussions about outstanding payments
- Enhanced Financial Control: Supports company credit policies at the point of sale
For issues, feature requests, or questions, please contact:
- Email: codeforme@bytesraw.com
Bytesraw
Researching Tomorrow's Bytes Today
Who We Are
We are a team of experienced Odoo freelancers dedicated to helping businesses customize, integrate, and optimize Odoo for their unique needs. Our initiative brings together experts in ERP solutions, development, and automation to deliver high-quality, cost-effective Odoo services.
Our Expertise
- Odoo Development (v11-v18)
- Functional Training (v11-v18)
- Community Upgradation's(v11-v18)
- Python & PostgreSQL
- Hosting, Automation & Security
- API & 3P Integrations
- E-commerce & POS Solutions
A Coffee with Us
Let's discuss your Odoo needs over a virtual or in-person coffee!
BytesRaw
No Running Away—Deal?
We build it, you love it, then you pay. Simple! If it doesn't work because of us, we'll take the hit as a learning experience (don't worry, we don't cry). And don't worry—we won't vanish after the job is done... but if you disappear, we might just shed a tear or two!
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