General Information
Version 2.19.3 was released on the 3rd of February and contains multiple enhancements and bug fixes. Below you can find more information related to the changes introduced in the new version. We will update your live account automatically and the sandbox account can be updated from the customer's end at any given time.
Enhancements
SC-3776 Transaction Line Defaulting Rules based on the header fields
The Transaction Line Defaulting Rule screen has been enhanced with a new field: Header Fields for Matching.
This new functionality allows you to create rules where, based on the value captured in a selected header field, the chosen value is automatically populated across all transaction lines.
The Header Fields for Matching field is optional. Existing rules continue to work as before, using the captured memo description on the lines. However, if you want the value selection on all lines to depend on a header field, simply specify the internal field ID of the header field you want to use.
Example use case:
If the captured document number contains the text "hire", all captured vendor bill lines can be automatically allocated to the GL account Outside Services.
To implement this, the header field for matching was set to "tranid" — the internal field ID of the document number field in my NetSuite account.
This enhancement provides greater flexibility when defining defaulting rules.
SC-4692 Extend subsidiary matching in the e-invoicing based on received tax ID
When receiving an e-invoice for a subsidiary registered in PEPPOL with multiple identifiers (for example, organization number and VAT ID), the matching logic has been enhanced. In addition to matching on the endpoint ID stored in the subsidiary setup, the system now falls back to matching based on the Tax ID to ensure more reliable subsidiary identification.
Bug Fixes
SC-4502 – Projects not available for selection on Transaction Line Default Rules
The Customer field introduced in the previous release on the Transaction Line Default Rule screen did not allow selection of Projects, even though they were available on vendor bill lines. The underlying dropdown query has been extended to support selection of both customers and projects.
SC-4546 – PO-related transaction flag not set during autoprocessing
The newly introduced custom field ZC PO Related Transaction, which indicates whether a vendor bill is PO-related or standalone, was not populated correctly for automatically created (autoprocessed) bills. This issue has been resolved.
SC-4588 – Due Date not calculated correctly during autoprocessing
When user preferences were set to calculate the Due Date based on vendor terms (instead of using the captured Due Date), the calculation did not trigger correctly for autoprocessed bills. This behavior has been fixed.
SC-4650 – Discounts on e-invoices: Credit Memo support
When discounts were applied to Credit Memo document types and sent through the e-invoicing network, line amounts became unbalanced, causing e-credit memo failures. This issue has been fixed.
SC-4651 – Discounts on e-invoices: Support for zero-value documents
When a 100% non-posting discount resulted in an invoice total of zero, an incorrect amount was sent in the e-invoice. The correct values are now sent.
SC-4666 – Vendor not recognized when separate vendor records exist per subsidiary
For customers using separate vendor records per subsidiary (instead of a single multi-subsidiary vendor), the vendor matching algorithm has been improved. The system now correctly filters and selects the vendor based on the matched subsidiary.
SC-4677 – Discounts on e-invoices: SuiteTax support
When sending invoices with discounts from NetSuite accounts with SuiteTax enabled, e-invoice validation could fail. This issue has been resolved.
SC-4678 – Outbound e-invoicing fails on single-currency accounts
In NetSuite accounts with the multi-currency feature disabled, outbound e-invoices failed due to incorrect currency retrieval. This has been fixed.
SC-4683 – Vendor matching fails when subsidiary is not matched initially
If the subsidiary could not be matched for a received e-invoice but the vendor was matched, the system previously left both fields empty. For single-subsidiary vendors, the subsidiary is now automatically derived from the vendor record.
SC-4684 – Outbound e-invoices: Items with Income Type = Expense
When an invoice included an item configured with an Expense-type account under Income Account preferences, a negative quantity was incorrectly sent in the e-invoice. The logic has been corrected to handle this scenario properly.
SC-4689 Extension of permissions for Technical Application role
NetSuite accounts with the Advanced Employee Permissions feature enabled were encountering an unexpected error when processing bills with 3-way matching turned on. The issue has been resolved by adding the missing permissions to the technical role under which the script handling this logic runs.
SC-4703 – E-invoice sending fails due to End of Item Group lines
When NetSuite’s technical End of Group item was present on an invoice, it was included in the e-invoice and caused validation failures. These technical lines are now excluded from e-invoice output.
SC-4706 – Invalid number or percentage error on standalone bills
When customers used standalone bills with items where we populate captured item line rates (instead of native NetSuite item rates), an “Invalid number or percentage” error was shown if the rate was not captured. Item lines can now be created without triggering this error despite rate being empty.
SC-4724 – Sales discounts on e-invoices
Certain scenarios involving sales discounts caused PEPPOL validation failures and e-invoice delivery issues. All identified issues have been resolved.