Shared Transactions Release Notes 07/23/26

Overview

This article collects every Shared Transactions change since the 06/25/25 release notes, covering Netgain Tools versions 2025.1.43 (June 30, 2025) through 2026.1.42 (July 17, 2026). Cross-Validation Rules changes ship in the same Netgain Tools updates but are documented in their own release notes.

Highlights

• Allocate bills that post their expense through an Item Receipt. When a non-inventory item has Generate Accruals turned on, the expense hits the Item Receipt rather than the Bill. Shared Transactions now allocates against the Item Receipt, so the receiving subsidiary gets the actual expense and intercompany balances reconcile.
• Complete a shared payment straight from the bill. A "Shared Payment Complete" button lets you mark a bill paid in full and kick off the Shared Payments process without leaving the bill. Useful for teams paying through a third-party system like Ramp.
• Shared Payments handles partial bill settlements. When a bill is partly settled by a vendor prepayment or an earlier payment, the generated journal now covers only the remaining unpaid amount.
• Import allocations by CSV. A Data Import Wizard for Shared Transactions lets you load allocations in bulk instead of entering them one transaction at a time.
• More accurate allocation journals. Allocations now respect your entered exchange rate (when both subsidiaries share a base currency) and use each currency's real rounding precision instead of assuming two decimals.
• Legacy custom segments allocate cleanly. Custom segments created before NetSuite 2019.1 no longer throw a search error during allocation.
• Locked-period safeguards. The allocation worksheet and Shared Transactions journals now recognize a locked period and stop the save with a clear message instead of appearing to succeed.

Segment Allocations

New

• Item Receipt as an allocation source. For non-inventory items with Generate Accruals enabled, the expense posts on the Item Receipt, not the Bill. Allocation now runs against the Item Receipt so the actual expense account moves across subsidiaries. This closes the gap where a receiving subsidiary got no expense and the intercompany sides did not reconcile. (2025.2.41)
• CSV import for Shared Transactions. A Data Import Wizard lets you import allocations by CSV for bulk entry. (2026.1.41)
• Reject an allocation when its source is rejected. A new global setting rejects the linked Shared Transactions allocation journal when you approve a source transaction and later reject it, so the allocation no longer stays behind. (2026.1.30)
• Default Intercompany Line Value now covers copied columns. The default intercompany line value applies to Memo and other copied columns, so those values carry through onto intercompany allocation lines automatically. (2025.1.50)
• Show segment values without their full hierarchy. A Show Hierarchy setting on the sourcing record lets the allocation worksheet display department, class, and location values without the full parent path, so nested values are easier to read. This only changes the worksheet display, not the values written to transactions. (2025.2.03)

Fixed

• Correct exchange rate and rounding on allocation journals. When your entered exchange rate differs from NetSuite's and both subsidiaries share the same base currency, the allocation journal now uses your rate. Allocation amounts also use each currency's actual rounding precision instead of a hardcoded two decimals. (2025.2.03)
• Legacy custom segments allocate without error. Custom segments created before NetSuite 2019.1 use different field-ID prefixes than newer ones, which caused a search error during allocation. A field-ID override on the sourcing record lets those segments allocate normally. (2025.2.11)
• Book-Specific Advanced Intercompany Journals allocate correctly. Reordered how the account is set when building the allocation journal, fixing an error on book-specific allocations. (2025.2.03)
• No duplicate allocation journals on retry. The system checks whether the allocation type changed between attempts, preventing a second allocation journal from being created. (2025.2.32)
• Reversal journals allocate and clean up correctly. When you allocate a journal that has a reversal, the reversal's allocation journal is now linked back to its source. Deleting the original or the reversal removes the matching allocation journal instead of leaving an orphan. (2025.1.43)

Intercompany Billing

Premium tier. Speak to your account manager if you would like to add it.

New

• Deleting an intercompany invoice deletes its vendor bill. When you delete an intercompany invoice, the automatically generated intercompany vendor bill is deleted with it, keeping the two sides in sync. (2025.2.00)

Fixed

• Bill credit takes the credit memo date. When a credit memo drives the automation, the resulting bill credit now posts on the credit memo's date so both sides match. (2025.2.01)
• No $0 tax line error on vendor credits. When Ignore Tax is off and an invoice has no tax, creating the vendor credit from a credit memo no longer tries to add a $0 tax line with no account. (2025.2.11)
• Entity lookup matches the transaction type. The lookup now pulls vendors for payable transactions and customers for receivable transactions, matching the actual financial relationship. (2025.2.06)

Shared Payments

Premium tier. Speak to your account manager if you would like to add it.

New

• Complete a shared payment from the bill. With the global setting enabled and a Shared Payments Bank Account set, a "Shared Payment Complete" button appears on eligible bills. Clicking it marks the bill paid in full and runs the Shared Payments process from the bill. Built for teams paying through a system like Ramp. (2025.2.40)
• Partial bill settlements. When a bill is partly settled by a vendor prepayment or bill payment, the generated journal covers only the remaining unpaid amount rather than the full bill. (2026.1.30)
• Location on Shared Payments journals. Shared Payments now sources Location onto the journal: the originating subsidiary's lines take the location from the bill or invoice, and the receiving subsidiary's lines take it from the location sourcing record. This unblocks Shared Payments where Location is a required field. (2025.2.01)

Fixed

• Bills re-open when a shared payment is deleted or voided. The associated bill now re-opens correctly instead of staying closed. (2025.2.41)
• Correct date and period when approvals are on. With approvals enabled and the source period still open, the shared payment journal now uses the source bill's transaction date and posting period instead of the creation date. (2026.1.20)
• Editing a payment no longer double-applies it. A partial payment on a shared payment journal was being applied to the source bill a second time whenever the payment was edited and re-saved, reducing the remaining balance again. The zero-dollar application now happens only once, on the initial save. (2026.1.21)
• Inline edits no longer delete the journal. An inline or mass edit that did not touch the shared payment subsidiary field was being misread as the subsidiary having been cleared, which silently deleted the linked journal and re-opened the bill. Fixed. (2026.1.30)
• Support for older intercompany vendor setups. Shared Payments now handles customers on an older intercompany vendor configuration. (2026.1.12)
• Recovery for bills missing their journal. A background process scans for transactions that carry Shared Payments fields but never got their journal (for example after a script error, a data import, or enabling the feature after the fact) and re-drives journal creation, respecting partial-settlement amounts. (2026.1.42)

Reliability and period controls

• Clear error on locked-period saves. Saving a Shared Transactions journal into a locked period now returns a clear message on save. (2025.2.01)
• Worksheet respects locked periods. The allocation worksheet checks lock status when it loads, disables the save button, and shows a notice, so it no longer appears to save successfully into a locked period. (2025.2.08)
• Softer handling of allocation errors. When an allocation journal fails to create, the system no longer throws a hard error that could produce duplicate transactions. A new global setting can delete the source transaction on an allocation error, and the latest error is recorded on the transaction so it can still post with the error captured. (2025.1.52)
• Fuller audit log for deleted transactions. The audit log for deleted transactions now records the transaction ID, amount, and related bill, not just the date. (2026.1.10)
• Updated worksheet help link. The worksheet's "More information" link now points to the current Shared Transaction error-message article. (2025.2.05)

Release history

For questions or support regarding these releases, please contact the Netgain support team.