Best Of

Hey @User_68KLQ,

Those are good questions, and it would have been great if NetSuite tracked those important changes.

Currently, it is a limitation, and we can't get that data natively.

Thanks Richard,

I'll reach out to them and report back with their findings.

Hi Jervin,

Thank you so much for your help. that is exactly what I was looking for. you guys are really awesome.

Hi @Tigran Shahnazaryan & @Jervin Nicholas Teopengco-Oracle ,

Thanks for your help.

Your suggestions are very useful to me.

Jet

Hi @Wishal44

When you use a Standard Frequency schedule (like Monthly or Annually) on a $0 Sales Order line, NetSuite's engine calculates the billing mathematically: (Total Line Amount / Number of Periods). Because the engine recognizes that a period needs to be billed, it pushes the line to the "Next Bill" queue, resulting in $0 / 12 = a $0.00 invoice line.

However, when you use a Custom schedule, NetSuite stops auto-calculating periods and relies entirely on the explicit value you put in the AMOUNT column.

• By putting exactly 0.00 in the Amount column, you are effectively telling NetSuite, "The billable value for this milestone is nothing."
• Because the milestone has no defined value to extract, the "Next Bill" queue skips it entirely, assuming there is nothing to bill for that date.

 Change the Custom Schedule amounts to Percentages

If the actual Sales Order line amount is $0.00, you need to trick the Custom Billing Schedule into recognizing a valid milestone without adding monetary value. You can do this by using Percentages instead of flat $0.00 amounts.

1. Edit your Custom Billing Schedule.
2. In the AMOUNT column for the 6 lines, instead of 0.00, enter 16.66% (or whatever percentage divides evenly into 100% based on your count). Make sure the last line rounds up to equal exactly 100% total (e.g., 16.70%).
3. Why this works: When you click Next Bill, NetSuite says, "I need to bill 16.66% of the Sales Order line." It then calculates 16.66% of $0.00, which equals a $0.00 invoice line. Because a percentage was defined, the system recognizes it as a valid, actionable milestone.

https://www.netsuite.com/help/helpcenter/en_US/srbrowser/Browser2016_1/schema/record/account.html

Hey @Tigran Shahnazaryan ,

That's awesome to hear! I was one of 4 founders of FLODocs, now Strongpoint. I designed this tool! It's great to hear that people find it useful - I sure thought so! Thank you

Hi Jervin,

I figured this out. Thanks for your help!

Hello,

Upon checking the related concern, there appears to be an issue with the findSublistLineWithValue() function. In the 2026.1 account, a workaround was implemented by explicitly passing a boolean value (true) instead of the usual string-based lookup value ('T').

Support also indicated that an undocumented change was introduced prior to the release. Internal coordination is currently underway to update the related SuiteAnswers article to reflect this change.

Additionally, if you need further assistance or confirmation specific to your account, I would suggest creating a Customer Support case regarding this matter.

Hi Bry,

Upon checking, there isn't so I created one with the given content you mentioned. Thank you for that!

Before I run gulp deploy, are there any other files that I need to validate first before running it? Like the templates within the suitetalk4node? That way I can avoid posting the same error for a missing file, and validate on my end first.

Hi @User_CGU6V

Set Defaults on the Vendor Record

If the majority of bills for a specific vendor always go to the same expense account, you can set this to default natively, completely bypassing the need for Bill Capture to "guess" or learn it.

• For Expense Accounts: Go to the Vendor Record -> Financial subtab -> Account Information -> Set the Default Expense Account. When Bill Capture processes a bill for this vendor, it will automatically pull this account.
• For Department & Location: NetSuite doesn’t natively default Department and Location onto a Bill from the Vendor record out-of-the-box. However, you can easily fix this with a basic Workflow:
  1. Create custom fields on the Vendor record for "Default Department" and "Default Location."
  2. Create a simple User Event Workflow that runs on Vendor Bill Creation.
  3. Set a "Set Field Value" action to source the Department and Location from the Vendor record to the Bill line items automatically.