NorthScope 2026.01.29

Software Version: 2026.01.29 Database Version: 2026.01.29

Release Date: January 29th, 2026

Improvement

Financial

NS-11931 & NS-11978 - Payment Reports: Clearer, Smarter, and No More Cut-Off Data

We’ve given the FN Payment Remittance NS, FN Payment Remittance2 NS, AP Check NS, and FA Check Stub NS reports a well-deserved tune-up. Previously, these reports displayed Transaction IDs for AP-type transactions—a perfectly fine NorthScope number, but not so great when trying to reconcile with external invoices or vendor paperwork. Now, they’ll display the Document Number instead, so what you see in NorthScope matches what you see from your vendors.

While we were under the hood, we also fixed an issue where the Purchase Order ID field in the FN Payment Remittance NS and FN Payment Remittance2 NS reports could get truncated if the ID was particularly long. The reports now accommodate the full 150 characters, because your Purchase Order IDs deserve to be seen in their entirety.

Together, these updates make payment reporting cleaner, more accurate, and much easier to line up with the real-world documents you’re reconciling against—no detective work required.

Bug

Financial

NS-12439 - Payment Remittance Reports: Credit Memos Stay with Their Payments

When printing a Payment Remittance report for a specific batch from the Checkbook Register inquiry, credit memos were getting a little too social. Instead of showing up only with the remittance they applied to, they appeared on every remittance in the batch—helpful in spirit, but wildly confusing in practice.

We’ve fixed the logic so credit memos now display only on the remittance they actually apply to. No more repeated credits, no more second-guessing which payment they belong to.

The result: cleaner remittance reports, accurate information per payment, and far less head-scratching when reconciling batches.

NS-13141 - Reverse & Correct Journals: The Link That Actually Links

On the Reverse and Correct Journal record view, clicking the Journal hyperlink was supposed to take you straight to the related Journal. Instead, it sent you to an unhelpful Access Denied message—like being told you weren’t allowed to open your own book.

That’s been fixed. The Journal link now correctly opens the associated Journal Record View, exactly as intended.

NS-13302 - Receipts & Currency Gain/Loss: When “A Few Journals” Became Way Too Many

In a very specific (and thankfully uncommon) scenario, Receipt transactions that had applications added, removed, and reworked multiple times could trigger a cascade of currency gain/loss journals. The accounting net effect was technically correct—everything was reversed—but the way NorthScope recorded it was… enthusiastic.

Instead of creating one gain/loss journal and one reversal, the system sometimes created them over and over again, exponentially. The result was a flood of journal entries cluttering up the GL Journal Line Inquiry, even though account balances themselves weren’t actually wrong. Accurate math, very noisy paperwork.

While untangling that, we also found a related issue: when an application that generated a currency gain/loss was later removed, the reversing journal wasn’t always being created. That’s been fixed too.

NS-13553 - Cash Receipts: Defeated by a Single Letter (Now Fixed)

Cash receipts were failing to post whenever discounts or writeoffs were involved because of a typo. Yes, really. One missing “S” in the wrong place was enough to bring the whole process to a dramatic halt.

We’ve fixed it. Cash receipts with discounts and writeoffs now apply and post correctly again, and NorthScope has been reminded that spelling counts.

Fisherman Accounting

NS-13068 - Fish Ticket Items: Sold Condition Finally Stands on Its Own

In the Fish Ticket Item setup, the Sold Condition field was accidentally mapped to the Condition field behind the scenes. That meant no matter what value you entered for Sold Condition, NorthScope quietly used whatever was in Condition instead.

We’ve fixed the mapping so Sold Condition now points to the correct field and saves its own value independently. You can now define both Condition and Sold Condition exactly as intended—no mix-ups, no overwriting.

NS-13384 - Fish Ticket Taxes: Getting the Signs (and the Accounts) Right

Here’s one that could hit where it hurts—your ledger. When a Fish Ticket included negative lines with taxes or premiums, NorthScope was happily calculating the tax amount as if it were positive. That made the Journal Details look balanced, but the amounts in each account were wrong, meaning the credits and debits technically lined up while still lying to you.

We’ve fixed the logic so the tax amount now reflects the true sign of the line and be negative when it should be negative. The result: accurate postings to every GL account, balanced journals that are correct, and far less confusion for anyone double-checking the math.

Framework

NS-10548 - Kendo Grids: Less Lag, More Speed (and Fewer Shades of Black)

When it came to massive datasets, NorthScope’s Kendo grids were behaving like they’d just been asked to do long division in their heads while balancing on one foot. Pages slowed down, browsers froze, and CPUs cried for mercy. The culprit? Our well-meaning but slightly overzealous RowColor feature.

Here’s what was happening: every time a grid loaded, it ran twice through every single row to assign a text color. That’s fine for a handful of rows, but for giant datasets, it was like coloring a football field one blade of grass at a time. Worse yet, in most cases, the color being applied was... black, which happens to already be the default.

We’ve fixed the issue by teaching NorthScope to be a little smarter (and lazier, in the good way). The RowColor logic now only runs when it’s actually needed. The result: grids with many rows load way faster, pages stay responsive, and your CPU can finally stop doing interpretive dance routines every time you open a big dataset.

NS-12648 & NS-12938 - Message Queue Alerts: Silent Treatment Fixed

After the NorthScope 20250421 upgrade, NorthScope’s List Views stopped talking. Message Queue alerts, the popups that let you know when something important has happened in the background, weren’t showing up at all on Kendo List Views. Meanwhile, Record Views were still happily chiming in like nothing was wrong.

We’ve fixed that communication breakdown. Additionally, we fixed a related problem where Message Queue alerts were not displayed when they arose while using Mass Update.

NS-13498 - Mass Update: No More Date Conversion Meltdowns

In a really infrequent scenario, using Mass Update and then clicking the Delete button from a List View that included a Last Updated column could trigger a dramatic SQL error about failing to convert dates and times, usually right when you were just trying to delete a row and move on with your day.

We’ve fixed the issue. Deleting rows after Mass Update will no longer throw a cryptic date conversion error.

Inventory

NS-13409 - Company Defaults: No More Cross-Company Side Effects

In multi-company NorthScope environments, changing the Default Inventory Transaction Class for one company had an unfortunate side effect: it also updated the default for every other company in the instance. Not ideal if you expect Company A and Company B to mind their own business.

We’ve fixed that behavior so the default transaction class is now updated only for the current company. Other companies in the same NorthScope instance are left untouched, exactly as intended.

Purchasing

NS-12379 – Purchase Orders: Mass Delete Finally Means Mass Delete

Deleting multiple Purchase Orders from the list view was supposed to be simple: select a few, click delete, and watch them vanish. Instead, NorthScope politely ignored your request and deleted… nothing.

That’s been fixed. You can now select and delete multiple Purchase Orders at once directly from the Purchasing → Purchase Orders List View, just like you always should have been able to.

NS-12917 – Purchase Orders: Summary Calculations Finally Add Up

Some users noticed that the Purchase Order List View wasn’t quite telling the truth when invoices involved multiple POs for the same vendor. Specifically, when one PO was linked in the invoice header and another PO line was added from the grid, the AP Qty Posted and AP Qty Unposted columns decided to improvise their math.

We’ve straightened them out. Now, when an invoice includes lines from multiple purchase orders, the quantities shown in the Purchase Order Summary will calculate correctly—no more misleading totals, no more head-scratching reconciliations.

NS-13197 – Process Payments: No More Empty Dropdown Guessing Games

In a timing-sensitive edge case, launching Process Payments from Vendor Balances could occasionally leave the Batch ID and Checkbook dropdowns empty. Close the screen, reopen it, try again; sometimes it worked, sometimes it didn’t. The inconsistency made it especially fun to track down.

We’ve fixed the underlying timing issue, so those dropdowns now populate reliably when the screen opens.

NS-13354 – Fisherman and Vendor Payments: Busting the Cross-Company Ghosts

Sometimes, opening a new Process Payments batch from the Fisherman Balances or Vendor Balances list views would reveal a strange sight: payees appearing in the detail grid even though no selections were made and no batches were open. Spooky—but not supernatural. Those “ghost” payees were actually coming from another company in the same NorthScope installation.

We’ve fixed the mix-up. Check Batches and their payees will now display only for the company you’re currently working in. No more cross-company apparitions, no more confusion.

Sales

NS-11235 – Sales Orders: No More Silent Overwrites (or Double-Click Drama)

In earlier versions of NorthScope, Sales Orders had a built-in safeguard: if someone else updated a transaction while you had it open, the system would stop you from saving and warn you first. That protection quietly went missing, which meant it was possible for one save to overwrite another or for an enthusiastic double-click on the Save button to cause some unexpected results.

That safety net is back. Now, if a Sales Order has been updated by any user after you opened it (yes, even you), NorthScope will block the save and show a clear validation message instead of blindly overwriting data.

NS-13306 - Sales Item History: Long Notes No Longer Break the System

If your Production Instruction notes ran a little long—say, over 100 characters—NorthScope decided that was simply too much information and threw a SQL error worthy of a dramatic exit: “String or binary data would be truncated…”

That’s been fixed. The Sales Item History Inquiry can now handle Sales Orders with lengthy Production Instruction notes without crashing or complaining. Whether your note is one word or a full novella, NorthScope will now display it in its entirety and keep the inquiry running smoothly.

NS-13350 - Sales Orders: Find Item Now Plays Nice with Units and Weights

When adding units-only or weight-only items to a Sales Order using Find Items, NorthScope was a little too stubborn, it wouldn’t save the item unless you entered a quantity first. That’s not how it’s supposed to work. Sometimes you just want to select the item and save it as-is.

We’ve fixed the issue so you can now add units-only and weight-only items using Find Items or Find Lots without having to enter quantities first. Of course, if you want to type in a unit or weight quantity, you still can—NorthScope just won’t demand it anymore.

NS-13405 - Sales Orders: Mass Updates Without the Accidental Amnesia

When running a mass update on multiple Sales Orders, NorthScope got a little forgetful. In the process of updating, it sometimes “helpfully” cleared out your Inside Salesperson, Outside Salesperson, and Default Certification settings.

We’ve reminded NorthScope to keep its memory intact. Now, when you perform a mass update, those salesperson and certification settings stay right where they belong. The updates go through as expected, and your Sales Orders remain fully staffed and properly certified.

System

NS-11906 - Inquiries: Auto Refresh Finally Means What It Says

The “Auto Refresh on Open” setting was supposed to be your time-saver, letting you open an inquiry, see your saved filters, and then decide when to load the data. Unfortunately, NorthScope had other ideas and was ignoring that checkbox like a teenager ignoring chores. Even when “Auto Refresh on Open” was unchecked, inquiries were still happily loading all their data the moment you opened them.

We’ve straightened things out. Now, when “Auto Refresh on Open” is unchecked:

• Your saved filter options still appear as usual.

• The inquiry grid will not automatically refresh or run its query until you click Refresh yourself.

In other words, NorthScope will finally wait for you to say “go” before pulling a mountain of data you didn’t ask for yet. Faster opens, fewer delays, and one less reason to get coffee while waiting for an inquiry to load.

Technical Changes

• No schema changes.

• No config file changes.