Hi everyone, I have one following requirement/prob...
# general
v
Hi everyone, I have one following requirement/problem: “*If one Project has multiple Sales Orders and the customer makes a lump-sum payment, we cannot allocate the payment received against a specific Sales Order.*” Our understanding is that the transaction flow is: Project → Sales Order → Invoice → Customer Payment For example, suppose a Project has: • SO-001 → ₹10,000 → Invoice-001 • SO-002 → ₹15,000 → Invoice-002 • SO-003 → ₹25,000 → Invoice-003 If the customer makes a lump-sum payment of ₹20,000 without specifying which SO the payment is for, the payment is applied at the Invoice level, but there is no direct way to identify/allocate the payment back to the relevant Sales Order(s). We are trying to understand the best way to handle this requirement in NetSuite. One approach we are considering is to store the related Sales Order number on each Invoice in a custom field, and then make that SO reference available in the Customer Payment → Apply sublist next to each Invoice. This would allow users to see which SO each payment application relates to. However, we are not sure whether this is the best approach, or whether there is a better standard NetSuite functionality, configuration, or customization that can handle this scenario. What would be the recommended approach to solve this requirement? How have others handled similar cases where a lump-sum payment needs to be associated/allocated back to the relevant Sales Order(s) when multiple SOs exist under the same Project?
p
You can handle this, but I wouldn’t make the payment itself “belong” to an SO—NetSuite’s standard Customer Payment is applied at the invoice/cash-sale level. A $20k lump sum can be manually split across multiple open invoices, which is the standard workflow. For visibility, your custom SO reference on the Invoice is a sensible approach. I’d automate the SO number onto the invoice and expose it in the payment Apply view/reporting, so users can see the originating SO while allocating the payment. If the business needs automatic allocation rules, a Saved Search + SuiteScript/workflow would be a better customization than trying to change NetSuite’s underlying payment relationship. I can help design the cleanest NetSuite setup for this, including the custom field, payment Apply view, and optional automated allocation logic. @Vaibhav Patil
v
Yes, that’s exactly the approach I was expecting. Thank you very much for your kind help, @Praise Heritage Abayomi. I really appreciate it.