<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[NetSuite: From Zero to Hero - Medium]]></title>
        <description><![CDATA[Explore the world of NetSuite through practical guides, helpful tips and tricks, real-world solutions, and the latest product updates. From fundamentals to advanced functionality, learn how to navigate, optimize, and make the most of NetSuite. - Medium]]></description>
        <link>https://medium.com/netsuite-from-zero-to-hero?source=rss----a42f5cc5dedf---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>NetSuite: From Zero to Hero - Medium</title>
            <link>https://medium.com/netsuite-from-zero-to-hero?source=rss----a42f5cc5dedf---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 08:25:24 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/netsuite-from-zero-to-hero" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[NetSuite Saved Search: Item vs. Item On Any Line — What’s the Difference?]]></title>
            <link>https://medium.com/netsuite-from-zero-to-hero/netsuite-saved-search-item-vs-item-on-any-line-whats-the-difference-847c3fdb996d?source=rss----a42f5cc5dedf---4</link>
            <guid isPermaLink="false">https://medium.com/p/847c3fdb996d</guid>
            <category><![CDATA[erp-software]]></category>
            <category><![CDATA[erp]]></category>
            <category><![CDATA[accounting-software]]></category>
            <category><![CDATA[netsuite]]></category>
            <dc:creator><![CDATA[AJ Bernardino, CPA, CISA]]></dc:creator>
            <pubDate>Mon, 19 Oct 2026 06:06:38 GMT</pubDate>
            <atom:updated>2026-10-19T06:06:38.890Z</atom:updated>
            <content:encoded><![CDATA[<h4>How to find transactions that include a specific item while showing all other items on the same transaction.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*027bldrt2bi9IlOgkGU5SQ.png" /></figure><p>One thing I enjoy about NetSuite is that even after 12 years of working with the system, I still discover features that make my work easier.</p><p>Recently, I encountered a Saved Search requirement that seemed straightforward at first.</p><p><strong>The requirement:</strong> Find all sales orders containing a particular item, but display every item on those sales orders — not just the item being searched for.</p><p>This is particularly useful when investigating transactions that include specific items, such as warranty or discount items, while also reviewing the other items in those transactions.</p><p>If you’ve worked extensively with NetSuite Saved Searches, you’ve probably encountered something similar.</p><p>Normally, we would add the <strong>Item</strong> filter under the <strong>Criteria</strong> subtab. However, that creates a problem: NetSuite returns only the transaction lines containing the specified item.</p><p><strong>What if we need the entire transaction, including the other items?</strong></p><h3>Understanding the Regular Item Filter</h3><p>Let’s start with a simple example.</p><p>Suppose we have three sales orders containing the following items:</p><ul><li>SO64523 — Find Item 1, Find Item 2, Main Item X</li><li>SO64524 — Find Item 1, Main Item Y</li><li>SO64525 — Find Item 2, Main Item Y, Main Item Z</li></ul><p>Our objective is to find all sales orders containing <strong>Find Item 2 </strong>and display every item in those sales orders.</p><blockquote><strong><em>Note:</em></strong><em> All examples and screenshots in this article use a Transaction saved search filtered to </em><strong><em>Type = Sales Order</em></strong><em>. The screenshots show only the item-related criteria.</em></blockquote><p>Normally, we would create a Transaction Saved Search and add the following criteria:</p><p>Item → any of → Find Item 2</p><p>The results will be:</p><ul><li>SO64523 — Find Item 2</li><li>SO64525 — Find Item 2</li></ul><p><strong>But here’s the problem: How do we show the other items?</strong></p><p>SO64523 also contains Find Item 1 and Main Item X, while SO64525 contains Main Item Y and Main Item Z. However, none of these items appear in our results.</p><p>This happens because the regular <strong>Item</strong> filter evaluates each transaction line individually. NetSuite returns only the lines that match our criteria.</p><p>In other words, we’re filtering <strong>transaction lines</strong>, not identifying transactions that contain<strong> the item</strong>.</p><p>And that’s an important distinction.</p><figure><img alt="Figure 1: Saved Search Results Using the Regular Item Filter" src="https://cdn-images-1.medium.com/max/1024/1*aukoVD-h__WiX0BW5qXCMQ.png" /><figcaption>Figure 1: Saved Search Results Using the Regular Item Filter</figcaption></figure><h3>Introducing Item On Any Line</h3><p>Now, here’s where things get interesting.</p><p>Instead of using the regular <strong>Item</strong> filter, NetSuite offers another Saved Search filter: <strong>Item On Any Line</strong>.</p><p>Let’s go back to our previous example.</p><p>This time, we’ll replace our existing Item criterion with:</p><p><strong>Item On Any Line → any of → Find Item 2</strong></p><p>With this simple change, our Saved Search will return both sales orders, including their associated items. Looking specifically at the item lines, our results will include:</p><ul><li>SO64523 — Find Item 1</li><li>SO64523 — Find Item 2</li><li>SO64523 — Main Item X</li><li>SO64525 — Find Item 2</li><li>SO64525 — Main Item Y</li><li>SO64525 — Main Item Z</li></ul><p>Notice the difference?</p><p>We’re still retrieving only sales orders containing <strong>Find Item 2</strong>, but this time, NetSuite returns all the item lines on those sales orders, provided they meet our other Saved Search criteria.</p><p>SO64524 is excluded because it doesn’t contain Find Item 2.</p><p><strong>The key difference is how NetSuite evaluates the criteria.</strong></p><ul><li><strong>Item:</strong> Returns only the transaction lines containing the specified item.</li><li><strong>Item On Any Line:</strong> Identifies transactions containing the specified item, allowing other transaction lines — including item, main, and tax lines — to appear in the results.</li></ul><p>In other words, instead of filtering individual transaction lines, we filter transactions based on whether the specified item appears anywhere on them.</p><p>And the best part? <strong>No formulas, scripts, or complicated workarounds are required.</strong></p><figure><img alt="Figure 2: Saved Search Results Using the Item On Any Line Filter" src="https://cdn-images-1.medium.com/max/1024/1*zjCTofLlBNaEEzZ5cWBDeA.png" /><figcaption>Figure 2: Saved Search Results Using the Item On Any Line Filter</figcaption></figure><p><strong>One important thing to remember:</strong> Our Saved Search results include more than just the item lines. In Figure 2, NetSuite returns <strong>10 transaction lines:</strong> six item lines, two main lines, and two tax lines. This is because <strong>Item On Any Line identifies transactions containing the specified item without automatically excluding their other transaction lines. </strong>We can still control which lines appear by adding additional Saved Search criteria, such as <strong>Main Line = False</strong>, <strong>Tax Line = False</strong>, AND <strong>Shipping Line = False</strong>.</p><p>The important distinction is that <strong>Item On Any Line identifies the qualifying transactions</strong>, while our other Saved Search criteria determine which lines from those transactions appear in the results.</p><h3>Using Multiple Items with Item On Any Line</h3><p>So far, we’ve demonstrated how <strong>Item On Any Line</strong> works when searching for a single item.</p><p>But what happens when we want to search for multiple items?</p><p>Interestingly, <strong>selecting two items within a single criterion and adding two separate criteria can produce different results.</strong></p><p>Let’s use our previous sales orders:</p><ul><li>SO64523 — Find Item 1, Find Item 2, Main Item X</li><li>SO64524 — Find Item 1, Main Item Y</li><li>SO64525 — Find Item 2, Main Item Y, Main Item Z</li></ul><h4>Scenario 1: One Item On Any Line Criterion with Multiple Items</h4><p>Suppose we want to identify sales orders containing either Find Item 1 or Find Item 2.</p><p>We’ll configure our criteria as follows:</p><p><strong>Item On Any Line → any of → Find Item 1, Find Item 2</strong></p><p>Our Saved Search will return:</p><ul><li>SO64523</li><li>SO64524</li><li>SO64525</li></ul><p>Why? Because the <strong>any of</strong> operator means a transaction must contain <strong>at least one of the selected items</strong>. It doesn’t need to contain both.</p><p>In our example, all three sales orders qualify.</p><figure><img alt="Figure 3: One Item On Any Line Criterion with Multiple Items (Any Of)" src="https://cdn-images-1.medium.com/max/1024/1*Zsc6cT7FFBzoPhwHhy7bIQ.png" /><figcaption>Figure 3: One Item On Any Line Criterion with Multiple Items (Any Of)</figcaption></figure><h4>Scenario 2: Two Separate Item On Any Line Criteria</h4><p>Now, let’s change the requirement.</p><p>What if we want to identify sales orders containing <strong>both Find Item 1 AND Find Item 2</strong>?</p><p>Instead of selecting both items within a single criterion, we can add two separate criteria:</p><ul><li><strong>Item On Any Line → any of → Find Item 1</strong></li><li><strong>Item On Any Line → any of → Find Item 2</strong></li></ul><p>Our Saved Search will just return SO64523.</p><p>Why?</p><p>Because we require the sales order to meet <strong>both conditions</strong>.</p><p>SO64524 is excluded because it doesn’t contain Find Item 2, while SO64525 is excluded because it doesn’t contain Find Item 1. Only SO64523 contains both items.</p><figure><img alt="Figure 4: Two Separate Item On Any Line Criteria (AND)" src="https://cdn-images-1.medium.com/max/1024/1*eF_GPYvkcLZY9QUKj5EmuQ.png" /><figcaption><strong>Figure 4:</strong> Two Separate Item On Any Line Criteria (AND)</figcaption></figure><h4>Scenario 3: One Item On Any Line Criterion Using All Of</h4><p>Here’s another interesting feature.</p><p>In Scenario 2, we added two separate <strong>Item On Any Line</strong> criteria to identify sales orders containing both Find Item 1 and Find Item 2.</p><p>But did you know we can achieve the same result using just <strong>one criterion</strong>?</p><p>Instead of adding two separate criteria, we can use the <strong>includes all of</strong> operator.</p><p>Our criteria would be:</p><p><strong>Item On Any Line → includes all of → Find Item 1, Find Item 2</strong></p><p>Our Saved Search will still return SO64523.</p><p>Why?</p><p>Because the <strong>includes all of</strong> operator requires the transaction to contain every selected item.</p><p>SO64524 is excluded because it doesn’t contain Find Item 2, while SO64525 is excluded because it doesn’t contain Find Item 1. Only SO64523 contains both items.</p><p><strong>The best part?</strong> We can achieve the same result as Scenario 2 without adding multiple criteria.</p><figure><img alt="Figure 5: One Item On Any Line Criterion with Multiple Items (All Of)" src="https://cdn-images-1.medium.com/max/1024/1*DaPYubK4sv6WzGjNlsrBew.png" /><figcaption>Figure 5: One Item On Any Line Criterion with Multiple Items (All Of)</figcaption></figure><h4>Scenario 4: Combining Item On Any Line with the Regular Item Filter</h4><p>Here’s another interesting scenario.</p><p>What if we want to identify sales orders that contain a particular item, but display only another specific item from those sales orders?</p><p>For example, suppose we want to identify sales orders that contain <strong>Find Item 2</strong>, but display only the lines containing <strong>Main Item Y</strong>.</p><p>Let’s revisit our previous sales orders:</p><ul><li>SO64523 — Find Item 1, Find Item 2, Main Item X</li><li>SO64524 — Find Item 1, Main Item Y</li><li>SO64525 — Find Item 2, Main Item Y, Main Item Z</li></ul><p>To achieve this, we’ll combine two criteria:</p><ul><li><strong>Item On Any Line → any of → Find Item 2</strong></li><li><strong>Item → any of → Main Item Y</strong></li></ul><p>Our Saved Search will only return SO64525.</p><p>Why?</p><p>Because we’re applying two different conditions:</p><p><strong>First</strong>, the transaction must contain <strong>Find Item 2 </strong>somewhere on its lines.</p><p><strong>Second</strong>, we only want to display transaction lines containing <strong>Main Item Y</strong>.</p><p>Let’s examine what happens to each sales order:</p><ul><li><strong>SO64523:</strong> Contains <strong>Find Item 2</strong> but not <strong>Main Item Y.</strong> Therefore, no lines are returned.</li><li><strong>SO64524:</strong> Contains <strong>Main Item Y</strong>, but doesn’t contain <strong>Find Item 2.</strong> Therefore, it’s excluded.</li><li><strong>SO64525:</strong> Contains both items, so it qualifies. However, only the <strong>Main Item Y</strong> line appears in our results.</li></ul><p>Notice the difference?</p><p>Although SO64525 contains three items, NetSuite only returns Main Item Y because that’s what we specified in our regular <strong>Item</strong> filter.</p><p>The important distinction is that <strong>Item On Any Line</strong> determines whether the transaction qualifies, while the regular <strong>Item</strong> filter determines which item lines from that transaction are displayed.</p><figure><img alt="Figure 6: Combining Item On Any Line and Item Criteria" src="https://cdn-images-1.medium.com/max/1024/1*Zv-9J-u8BMSbRAXZNWcB9Q.png" /><figcaption>Figure 6: Combining Item On Any Line and Item Criteria</figcaption></figure><h3>Practical Business Applications</h3><p>Now that we’ve explored the different ways to use <strong>Item On Any Line</strong>, let’s look at some real-world applications.</p><h4>1. Warranty Analysis</h4><p>Identify sales orders that include warranty items while retrieving the other products in those transactions. This can help analyze products sold alongside warranty coverage.</p><h4>2. Discount and Promotional Analysis</h4><p>Find transactions that include specific discount or promotional items on their lines while showing the other products purchased. This can help evaluate promotional performance and purchasing patterns.</p><h4>3. Cross-Selling Opportunities</h4><p>Retrieve all items from transactions containing a specific product, then analyze the results to identify products frequently purchased together. This can help uncover cross-selling and product-bundling opportunities.</p><p><strong>The key takeaway:</strong> Item On Any Line isn’t just another Saved Search filter. It lets us analyze transactions by the items they contain, without limiting results to those specific item lines.</p><h3>Using Item On Any Line in SuiteScript</h3><p>Another point: <strong>Item On Any Line isn’t limited to Saved Searches created through the NetSuite UI.</strong></p><p>We can also use this filter in <strong>SuiteScript 2.x</strong> through the N/search module.</p><p>The internal ID of the Item On Any Line filter is anylineitem. NetSuite&#39;s <a href="https://www.netsuite.com/help/helpcenter/en_US/srbrowser/Browser2022_2/script/record/transaction.html">SuiteScript Records Browser</a> confirms this.</p><p>For example, suppose we want to retrieve all sales orders containing a specific item, including their other transaction lines.</p><p>The following example assumes that the N/search module has already been imported as search:</p><pre>const salesOrderSearch = search.create({<br>    type: search.Type.TRANSACTION,<br>    filters: [<br>        [&#39;type&#39;, &#39;anyof&#39;, &#39;SalesOrd&#39;],<br>        &#39;AND&#39;,<br>        [&#39;anylineitem&#39;, &#39;anyof&#39;, [12345]]<br>    ],<br>    columns: [<br>        &#39;tranid&#39;,<br>        &#39;item&#39;,<br>        &#39;quantity&#39;,<br>        &#39;amount&#39;<br>    ]<br>});</pre><p><strong>Note</strong>: Replace 12345 with the item&#39;s internal ID.</p><h3>Final Thoughts</h3><p>Sometimes, the simplest NetSuite features can significantly shape how we approach reporting requirements.</p><p>The distinction between <strong>Item</strong> and <strong>Item On Any Line</strong> may seem small, but understanding how these filters work helps us build more flexible, effective Saved Searches.</p><p>The key is knowing whether you want to filter individual transaction lines or identify transactions by the items they contain.</p><p>As we’ve shown, combining these filters can open up even more possibilities.</p><p><strong>Sometimes, we don’t need complicated formulas, scripts, or workarounds. We just need to know which native NetSuite features to use.</strong></p><p>And that’s another step toward going from <strong>NetSuite Zero to Hero!</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=847c3fdb996d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/netsuite-from-zero-to-hero/netsuite-saved-search-item-vs-item-on-any-line-whats-the-difference-847c3fdb996d">NetSuite Saved Search: Item vs. Item On Any Line — What’s the Difference?</a> was originally published in <a href="https://medium.com/netsuite-from-zero-to-hero">NetSuite: From Zero to Hero</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[12 Years in NetSuite, and I Just Discovered Payment Runs!]]></title>
            <link>https://medium.com/netsuite-from-zero-to-hero/12-years-in-netsuite-and-i-just-discovered-payment-runs-9206db337dde?source=rss----a42f5cc5dedf---4</link>
            <guid isPermaLink="false">https://medium.com/p/9206db337dde</guid>
            <category><![CDATA[erp-software]]></category>
            <category><![CDATA[erp]]></category>
            <category><![CDATA[netsuite]]></category>
            <category><![CDATA[accounting-software]]></category>
            <dc:creator><![CDATA[AJ Bernardino, CPA, CISA]]></dc:creator>
            <pubDate>Mon, 12 Oct 2026 12:41:14 GMT</pubDate>
            <atom:updated>2026-10-12T12:41:14.769Z</atom:updated>
            <content:encoded><![CDATA[<p>Exploring NetSuite&#39;s new Payment Run feature in 2026.2 and how it changes vendor payment processing.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rpLVOmnH1rrHj1wpsMKQCQ.png" /></figure><h3>Introduction</h3><p>I’ve been working with NetSuite for 12 years. Throughout my career, I’ve implemented and supported Procure-to-Pay processes, including Accounts Payable, vendor bill management, and payment processing.</p><p>I thought I already knew how NetSuite handles vendor payments. But recently, while exploring NetSuite, I came across something I hadn’t encountered before: <strong>Payment Runs</strong>.</p><p>My initial reaction was simple: <em>How did I miss this after 12 years?</em></p><p>Turns out, I hadn’t missed anything. Payment Runs are actually a new transaction type introduced in NetSuite 2026.2!</p><p>Naturally, I became curious. How does this differ from the existing Pay Bills functionality? What problems does it solve? And when should businesses consider using it?</p><p>Let’s explore.</p><h3>What Is a Payment Run?</h3><p>A <strong>Payment Run</strong> is a new, non-posting transaction introduced in NetSuite 2026.2 that allows businesses to group multiple payable transactions and process vendor payments through a single workflow.</p><p>Think of it as a <strong>payment proposal</strong>. Instead of creating vendor payments immediately, users can prepare a list of transactions to pay, review the amounts, and obtain approvals before generating the actual payments.</p><p>A Payment Run can include these transactions:</p><ul><li>Vendor bills</li><li>Vendor credits</li><li>Journal entries with qualifying A/P lines</li><li>Expense reports</li><li>Bill payments with a remaining negative amount</li><li>Other transaction types that post to an Accounts Payable account may also be eligible</li></ul><p>When creating a Payment Run, users can select the payment account, specify the payment date, and choose which transactions to include. NetSuite then calculates the total payment amount, accounting for applicable credits and discounts.</p><p><strong>One important distinction is that a Payment Run itself does not affect the General Ledger.</strong> It serves as a payment proposal, while the resulting vendor payments post to the General Ledger.</p><p>Once the Payment Run is ready and any required approvals are completed, users can generate the corresponding vendor payments through the <strong>Create Payments</strong> action.</p><h3>Payment Run vs. Pay Bills: What’s the Difference?</h3><p>If you’ve been using NetSuite for a while, you’re probably familiar with <strong>Pay Bills</strong>. It allows users to select multiple outstanding vendor bills, apply available credits and discounts, and create vendor payments in a single process.</p><p>So, if Pay Bills already does this, why did NetSuite introduce Payment Runs?</p><p>The key difference lies in <strong>how payments are prepared, reviewed, approved, and processed.</strong></p><p>With <strong>Pay Bills</strong>, users select the transactions they want to pay and click <strong>Save</strong>. NetSuite then processes the selected transactions and creates the corresponding vendor payment records.</p><p>With <strong>Payment Runs</strong>, users can prepare and save a payment proposal without immediately creating the actual vendor payments. This lets users review, modify, and approve the payment proposal before creating the payments.</p><p><strong>Another advantage of Payment Runs is their support for custom approval workflows through SuiteFlow.</strong> Businesses can configure workflows to route payment proposals to designated approvers before generating the actual vendor payments. This provides an additional layer of internal control and supports segregation of duties.</p><p><strong>Payment Runs also support SuiteScript</strong>, allowing developers to implement custom business logic, validations, and integrations based on specific business requirements. They also support custom transaction body fields, custom forms, and REST integrations.</p><p>These capabilities make Payment Runs particularly useful for businesses requiring more sophisticated Accounts Payable processes and internal controls.</p><h3>Creating Your First Payment Run in NetSuite</h3><p>Now that we understand how Payment Runs differ from Pay Bills, let’s explore how to create one in NetSuite.</p><p><strong>Step 1: Navigate to Payment Runs</strong></p><p>Navigate to <strong>Transactions &gt; Payables &gt; Enter Payment Run.</strong></p><p><strong>Step 2: Enter the Payment Run Details</strong></p><p>Select the payment account under the <strong>Account</strong> field and specify the <strong>Payment Date</strong>. Select the <strong>Posting Period</strong> and enter any required classification values, such as <strong>Department</strong>, <strong>Class,</strong> or <strong>Location</strong>.</p><p>The selected payment account determines the <strong>Subsidiary </strong>and<strong> Currency</strong> of the Payment Run. NetSuite also displays the account’s balance and available balance.</p><p><strong>Step 3: Select the Transactions to Pay</strong></p><p>Under the <strong>Transactions</strong> subtab, click <strong>Add Transactions</strong>.</p><p>NetSuite displays a list of eligible payable transactions. You can narrow down the results using filters such as Payee, Transaction Type, Currency, A/P Account, and Due Date.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CN_PTQo414NF4S41d3NhOA.png" /><figcaption>Payment Run — Add Transactions</figcaption></figure><p>Select the transactions you want to include, review their payment amounts, and click <strong>Add</strong>.</p><p><strong>Step 4: Review the Payment Run</strong></p><p>After you add the transactions, review the payment amounts, applicable discounts, credits, and the total payment amount in the Summary panel.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IVBginTxuTpoKSAmN86a7g.png" /><figcaption>Payment Run — Transaction Details</figcaption></figure><p>Remember: <strong>The total Payment Run amount must be greater than zero.</strong> Otherwise, NetSuite will prevent you from saving the record.</p><p><strong>Step 5: Save the Payment Run</strong></p><p>Click <strong>Save</strong>.</p><p>NetSuite creates a Payment Run record with its own transaction number.</p><p>Unlike Pay Bills, saving a Payment Run does not immediately create vendor payments. The Payment Run remains available for further review and modification, subject to its status and approval configuration.</p><p>If an approval workflow is configured, the Payment Run may need approval before the system can generate payments.</p><h3>Processing a Payment Run: Creating Vendor Payments</h3><p>After you create and review a Payment Run, you can generate vendor payments. If approval is required, the Payment Run must first be approved. An Open Payment Run is eligible for the <strong>Create Payments</strong> action.</p><p><strong>Step 1: Create Payments</strong><br>Open the Payment Run and review the selected transactions, payment amounts, and total payment amount. Once everything is correct, click <strong>Create Payments</strong>.</p><p>NetSuite processes the Payment Run asynchronously, meaning it creates vendor payments in the background rather than immediately. During processing, the Payment Run status changes to <strong>In Progress</strong>.</p><p><strong>Step 2: Review the Payment Run Status</strong><br>Once processing is complete, the Payment Run displays one of the following statuses:</p><ul><li>Completed — All applicable payments were successfully created.</li><li>Completed with Errors — Some payments were successfully created, while others failed.</li><li>Failed — All payment creation attempts failed.</li></ul><p>If errors occur, NetSuite displays a warning icon beside the affected transactions. Users can go to the Payment Run status page (<strong>Transactions</strong> &gt; <strong>Payables</strong> &gt; <strong>Enter Payment Run</strong> &gt; <strong>Status</strong>) to check the errors.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cjSt-6FUnpywmgszJTdb2Q.png" /><figcaption>Payment Run — Transaction Error</figcaption></figure><p><strong>Step 3: Review the Generated Vendor Payments</strong></p><p>Navigate to the <strong>Related Records &gt; Payments</strong> subtab of the Payment Run.</p><p>Here, you can review the vendor payments NetSuite generated, including payment amounts, dates, and approval statuses.</p><p><strong>One important thing to remember:</strong> A single Payment Run can generate multiple vendor payments. NetSuite groups transactions by payee, currency, A/P account, exchange rate, and billing address.</p><p>Even transactions for the same vendor can produce separate payments if their billing addresses differ. Review the billing addresses on the underlying transactions before processing the run.</p><h3>Frequently Asked Questions</h3><h4><strong>Can I customize the document numbering for Payment Runs?</strong></h4><p>Yes! Payment Runs support custom document numbering, which can be configured by navigating to <strong>Setup</strong> &gt; <strong>Company</strong> &gt; <strong>Auto-Generated Numbers.</strong></p><p>You can define a prefix, starting number, and minimum number of digits to establish a consistent numbering format. For example, you can use PR-000001, PR-000002, PR-000003, and so on.</p><p>Payment Runs also support <strong>Advanced Numbering</strong>, allowing businesses to configure more complex numbering rules based on criteria such as subsidiary, location, or transaction date.</p><h4>Can I configure an approval workflow for Payment Runs?</h4><p><strong>Yes!</strong> Payment Runs support custom approval workflows through <strong>SuiteFlow</strong>, allowing businesses to route payment proposals to designated approvers before creating the actual vendor payments.</p><p>To enable approval routing, navigate to <strong>Setup &gt; Accounting &gt; Accounting Preferences &gt; Approval Routing</strong>, check the <strong>Payment Runs</strong> box, and click <strong>Save</strong>. Once enabled, businesses can create custom workflows to manage the approval process based on their specific requirements.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/910/1*0DYAs9NSJx1ByKyOUNalww.png" /><figcaption>Approval Routing — Payment Runs</figcaption></figure><p><strong>Note:</strong> Payment Run approvals are separate from standard Vendor Payment approvals. Depending on your configuration, the resulting vendor payments may still require additional approval.</p><h4>Can I include transactions from a rejected Payment Run in a new Payment Run?</h4><p><strong>Yes!</strong> When you reject a Payment Run, its open transactions become available for selection when you create a new Payment Run. However, take care when reapproving a previously rejected Payment Run.</p><p>If you include its transactions in a new Payment Run and then reapprove the original run first, NetSuite prevents approval of the new run and displays this error:</p><blockquote><strong><em>Transactions that are already included in a payment run in progress cannot be included.</em></strong></blockquote><p>Before reapproving a rejected Payment Run, check whether another run already includes its transactions and decide which run should proceed.</p><h4>Can I cancel or delete a Payment Run?</h4><p>Yes! NetSuite allows users to cancel or delete a Payment Run with an Open status. However, there are important differences between these two actions:</p><ul><li><strong>Canceling a Payment Run</strong> — Users with Edit permission can cancel an Open Payment Run by clicking Cancel Run. Canceling a Payment Run retains the record in NetSuite but releases its selected transactions, making eligible transactions available for inclusion in another Payment Run.</li><li><strong>Deleting a Payment Run</strong> — Users with the appropriate permissions can also delete an Open Payment Run. Unlike cancellation, deleting a Payment Run removes the record from NetSuite.</li></ul><p><strong>Important</strong>: A Payment Run cannot be deleted if its generated vendor payments still exist. You must first delete these payments, if permitted, before you can delete the Payment Run.</p><h4>When will transactions become available again for selection in a new Payment Run?</h4><p>Transactions previously included in a Payment Run may become available again under the following circumstances:</p><ol><li><strong>Payment Run is Canceled</strong> — Canceling a Payment Run (by clicking the <strong>Cancel Run</strong> button) releases the selected transactions, making them available for inclusion in a new Payment Run.</li><li><strong>Payment Run is Rejected</strong> — When a Payment Run is rejected, its transactions become available for selection in a new Payment Run.</li><li><strong>Payment Run is Completed with Errors or Failed </strong>— If payment processing encounters errors, transactions for which payments were not successfully created may become available again. For a Payment Run completed with errors, you can select only the unpaid transactions again.</li><li><strong>Payment Run is Completed, but the Vendor Payment is Voided or Deleted </strong>— Even after a Payment Run has been successfully completed, its underlying transactions may become available again if the corresponding vendor payments are subsequently voided or deleted, provided the transactions have an outstanding balance.</li></ol><h4>Are Payment Runs compatible with Electronic Bank Payments (EFT)?</h4><p><strong>Yes!</strong> Payment Runs can be used alongside the <strong>Electronic Bank Payments SuiteApp</strong> to generate payment files for vendor payments.</p><p>Traditionally, users can navigate to <strong>Payments &gt; Payment Processing &gt; Bill Payment Processing</strong> to create vendor payments and generate the corresponding payment file in a single process.</p><p>With Payment Runs, users can separate these activities into the following steps:</p><ol><li><strong>Create a Payment Run</strong> — Select the payable transactions, review the payment amounts, and obtain the necessary approvals.</li><li><strong>Create Vendor Payments</strong> — Once the Payment Run is approved, click <strong>Create Payments</strong> to generate the corresponding Bill Payment transactions.</li><li><strong>Generate the Payment File</strong> — Navigate to <strong>Payments &gt; Bank File Generation &gt; Generate Bill Payment File</strong> to generate the EFT payment file using the previously created Bill Payments.</li></ol><p>This approach lets businesses use <strong>Payment Run approval workflows while continuing to use Electronic Bank Payments for bank file generation</strong>.</p><p><strong>Important:</strong> The generated Bill Payments must be configured for electronic bank payment, including having the <strong>For Electronic Bank Payment</strong> checkbox selected. The appropriate bank details and transaction saved search must also be configured to ensure the payments are included in the generated file. Payment Run creation does not automatically guarantee EFT eligibility.</p><h3>Final Thoughts</h3><p>For me, the biggest benefit of Payment Runs is the ability to save and review a payment proposal before creating vendor payments. <strong>Pay Bills</strong> still has its place, but Payment Runs offer another option when your process needs proposal approval, an audit trail, or time to review the selected payables.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9206db337dde" width="1" height="1" alt=""><hr><p><a href="https://medium.com/netsuite-from-zero-to-hero/12-years-in-netsuite-and-i-just-discovered-payment-runs-9206db337dde">12 Years in NetSuite, and I Just Discovered Payment Runs!</a> was originally published in <a href="https://medium.com/netsuite-from-zero-to-hero">NetSuite: From Zero to Hero</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[NetSuite 2026.2: Smarter AR & AP Bank Matching]]></title>
            <link>https://medium.com/netsuite-from-zero-to-hero/netsuite-2026-2-smarter-ar-ap-bank-matching-bc65860b1c54?source=rss----a42f5cc5dedf---4</link>
            <guid isPermaLink="false">https://medium.com/p/bc65860b1c54</guid>
            <category><![CDATA[accounting]]></category>
            <category><![CDATA[erp]]></category>
            <category><![CDATA[erp-software]]></category>
            <category><![CDATA[netsuite]]></category>
            <dc:creator><![CDATA[AJ Bernardino, CPA, CISA]]></dc:creator>
            <pubDate>Sun, 11 Oct 2026 15:31:11 GMT</pubDate>
            <atom:updated>2026-10-11T15:31:11.272Z</atom:updated>
            <content:encoded><![CDATA[<h4>How NetSuite’s new payment suggestions simplify bank matching for accounts receivable and accounts payable.</h4><figure><img alt="NetSuite 2026.2: Smarter AR &amp; AP Bank Matching" src="https://cdn-images-1.medium.com/max/1024/1*SsGRp65rTT8RDPH9isM34w.png" /><figcaption>NetSuite 2026.2: Smarter AR &amp; AP Bank Matching</figcaption></figure><h3>Introduction</h3><p>Bank reconciliation is essential to managing a company’s financial records. However, matching bank transactions to outstanding invoices and bills can take multiple steps, especially when payments haven&#39;t been recorded in NetSuite yet.</p><p>With the release of <strong>NetSuite 2026.2</strong>, NetSuite introduced two enhancements to the bank matching process:</p><ul><li><strong>Generate Match Suggestions for Accounts Receivable</strong></li><li><strong>Generate Match Suggestions for Accounts Payable</strong></li></ul><p>These features allow NetSuite to suggest payment applications for eligible open invoices and payables based on imported bank transactions.</p><p>Let’s explore how these enhancements work, where to find them, and what you should know before using them.</p><h3>What’s New in NetSuite 2026.2 Bank Matching?</h3><p>Previously, users generally had to create the corresponding Customer Payments or Bill Payments before matching them to imported bank transactions, or use alternative functionality, such as Automated Cash Application, for eligible customer receipts.</p><p>With these enhancements, NetSuite can suggest creating payments directly from the bank matching process.</p><ul><li><strong>Generate Match Suggestions for Accounts Receivable</strong> — Suggests applying imported bank transactions to eligible open customer invoices.</li><li><strong>Generate Match Suggestions for Accounts Payable</strong> — Suggests applying imported bank transactions to eligible open payables.</li></ul><figure><img alt="Match Bank Data — Payment Application Suggestions" src="https://cdn-images-1.medium.com/max/368/1*4Cyh2Y2TBI1iriWcLQpcGw.png" /><figcaption>Bank Matching and Reconciliation Preferences</figcaption></figure><p>The primary benefit is that users can review and submit suggested payment applications without separately creating the corresponding payment transactions.</p><h3>How Accounts Receivable Match Suggestions Work</h3><p>When NetSuite identifies an eligible open customer invoice corresponding to an imported bank transaction, it can suggest creating a Customer Payment. NetSuite uses information such as the <strong>Payor/Payee</strong> and <strong>Memo</strong> to help identify potential matches.</p><h4>Prerequisites</h4><p>Before using this feature:</p><ul><li>The accounting preference <strong>Generate Match Suggestions for Accounts Receivable </strong>is enabled. This preference is enabled by default.</li><li>The invoice must be open and posting, and its subsidiary and currency must match the bank account.</li><li>The user needs the relevant reconciliation and payment-creation permissions.</li></ul><h4>How the process works</h4><p><strong>Step 1 — Import the bank transaction</strong></p><p>A cash inflow banking transaction is imported into NetSuite.</p><p><strong>Step 2 — Identify an eligible open invoice</strong></p><p>NetSuite uses information from the imported bank transaction, including <strong>Payor/Payee</strong> and <strong>Memo</strong> details, to identify potential matches with eligible open customer invoices.</p><p><strong>Step 3 — Generate a payment application suggestion</strong></p><p>The imported transaction appears under <strong>Match Suggestions</strong>, with <strong>Apply Payment</strong> as the suggested action when NetSuite identifies a single eligible invoice.</p><p><strong>Step 4 — Create and match the Customer Payment</strong></p><p>Once the user submits the suggestion, NetSuite creates a Customer Payment, applies it to the invoice, and matches it with the imported bank transaction.</p><p>This reduces the need to create the Customer Payment separately before matching it.</p><h3>How Accounts Payable Match Suggestions Work</h3><p>The Accounts Payable enhancement follows a similar process, but it applies to vendor payments.</p><h4>Prerequisites</h4><p>Before using this feature:</p><ul><li>The accounting preference <strong>Generate Match Suggestions for Accounts Payable </strong>is enabled. This preference is enabled by default.</li><li>The payable must be open and posting, and its subsidiary and currency must match the bank account.</li><li>The user needs the relevant reconciliation and payment-creation permissions.</li></ul><h4>How the process works</h4><p><strong>Step 1 — Import the bank transaction</strong></p><p>A cash outflow banking transaction is imported into NetSuite.</p><p><strong>Step 2 — Identify an eligible open payable</strong></p><p>NetSuite uses information from the imported bank transaction, including <strong>Payor/Payee</strong> and <strong>Memo</strong> details, to identify potential matches with eligible open vendor payables.</p><p><strong>Step 3 — Generate a payment application suggestion</strong></p><p>The imported transaction appears under <strong>Match Suggestions</strong>, with <strong>Apply Payment</strong> as the suggested action when a single eligible payable is identified.</p><p><strong>Step 4 — Create and match the Bill Payment</strong></p><p>Once the user submits the suggestion, NetSuite creates the Bill Payment, applies it to the payable, and matches it to the imported bank transaction.</p><p>Like the Accounts Receivable enhancement, this provides a more streamlined way to record and match payments.</p><h3>What You’ll See in Match Bank Data</h3><p>The new payment application suggestions appear directly within the <strong>Match Bank Data</strong> interface under the <strong>Match Suggestions</strong> subtab.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8rrwBCoFTYyFYcdMS6wbJw.png" /><figcaption>Payment Application Suggestions in Match Bank Data</figcaption></figure><p>When reviewing bank transactions, there are three important elements to understand:</p><ul><li><strong>Match Suggestions </strong>— This is where NetSuite displays potential matches for imported bank transactions.</li><li><strong>Suggested Action </strong>— Depending on the available matches, NetSuite may display either <strong>Apply Payment</strong> (when one eligible invoice or payable is identified) or <strong>Review Payment Options</strong> (when multiple possible invoices or payables are identified).</li><li><strong>View / Review / Submit</strong> — These actions allow users to review the suggested payment application and submit it. Importantly, a payment suggestion does not mean NetSuite has already created or applied the payment. NetSuite creates the payment transaction when the suggestion is submitted.</li></ul><h3>Frequently Asked Questions</h3><h4>Are payment application suggestions submitted automatically?</h4><p>No. Payment application suggestions require user review and submission, even when <strong>Automatically Accept Exact Matches</strong> is enabled.</p><h4>Can these features handle partial payments?</h4><p>No. Payment application suggestions currently support one-to-one matches for the full outstanding amount. Partial payments are not supported through this functionality.</p><h4>Can one payment be applied to multiple invoices or bills?</h4><p>No, not through payment application suggestions. For Accounts Receivable, consider using Automated Cash Application. For Accounts Payable, create manual bill payments and match them under <strong>Transactions to Match</strong>.</p><h4>How do these features differ from Automated Cash Application?</h4><p>Automated Cash Application provides additional flexibility for Accounts Receivable workflows, including:</p><ul><li>Partial payment applications.</li><li>Payments involving multiple invoices.</li><li>Matching using invoice identifiers.</li><li>More flexible customer mapping.</li></ul><p>The new payment application suggestions, by contrast, focus on eligible one-to-one matches for the full outstanding amount.</p><h4>How does NetSuite identify potential payment matches?</h4><p>NetSuite compares the <strong>Payor/Payee</strong> and <strong>Memo</strong> details from the bank transaction to identify customers or vendors. These details help NetSuite determine which open invoices or payables may correspond to an imported bank transaction.</p><h4>What happens if I reject a payment suggestion?</h4><p>When the user rejects the suggestion, NetSuite removes the suggestion, and the associated imported bank transaction appears under <strong>Transactions to Match</strong> for manual matching.</p><h3>When Should You Use These Features?</h3><p>Payment application suggestions are particularly useful when imported bank transactions match individual outstanding invoices or bills in full.</p><p>However, for partial payments, multiple invoices, or more complex payment scenarios, alternative functionality such as Automated Cash Application (for Accounts Receivable) may be more appropriate.</p><p>Understanding the differences between these features can help you choose the most suitable workflow for processing payments and reconciling bank transactions.</p><h3>Final Thoughts</h3><p>The introduction of the Accounts Receivable and Accounts Payable payment application suggestions in NetSuite 2026.2 is a useful enhancement to the bank matching process.</p><p>Instead of requiring users to create payment transactions separately before matching them, NetSuite can now suggest payment applications directly from imported bank transactions.</p><p>Although the functionality currently focuses on one-to-one matches and requires user review, it offers an opportunity to simplify payment processing and reconciliation.</p><p>For organizations handling a significant volume of customer receipts or vendor payments, understanding when to use these suggestions — and when to use alternative workflows such as Automated Cash Application — can help improve the efficiency of their banking processes.</p><p><strong>Have you explored the new features in NetSuite 2026.2?</strong></p><p>Share your experiences, observations, or questions in the comments.</p><p><em>Happy learning!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bc65860b1c54" width="1" height="1" alt=""><hr><p><a href="https://medium.com/netsuite-from-zero-to-hero/netsuite-2026-2-smarter-ar-ap-bank-matching-bc65860b1c54">NetSuite 2026.2: Smarter AR &amp; AP Bank Matching</a> was originally published in <a href="https://medium.com/netsuite-from-zero-to-hero">NetSuite: From Zero to Hero</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Welcome to NetSuite: From Zero to Hero!]]></title>
            <link>https://medium.com/netsuite-from-zero-to-hero/welcome-to-netsuite-from-zero-to-hero-7d84508952da?source=rss----a42f5cc5dedf---4</link>
            <guid isPermaLink="false">https://medium.com/p/7d84508952da</guid>
            <category><![CDATA[accounting-software]]></category>
            <category><![CDATA[oracle-netsuite]]></category>
            <category><![CDATA[netsuite]]></category>
            <category><![CDATA[erp-software]]></category>
            <dc:creator><![CDATA[AJ Bernardino, CPA, CISA]]></dc:creator>
            <pubDate>Sat, 10 Oct 2026 13:30:36 GMT</pubDate>
            <atom:updated>2026-10-10T13:30:36.462Z</atom:updated>
            <content:encoded><![CDATA[<h4>A journey of learning, discovering, and making the most of NetSuite.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PIXXA19vVc6gy2NTFDOCsg.png" /></figure><p>NetSuite is a powerful ERP platform, but with so many features, configurations, and updates, there’s always something new to learn.</p><p>That’s exactly why I created this publication.</p><p>My goal is simple: <strong>Share practical NetSuite knowledge that helps others learn, solve problems, and find better ways to do things.</strong></p><h4>What can you expect?</h4><p>Through this publication, I’ll be sharing:</p><ul><li><strong>Tips &amp; Tricks:</strong> Useful features, shortcuts, and ‘hacks’ you might not know about.</li><li><strong>NetSuite Solutions:</strong> Practical approaches to common challenges and real-world business requirements.</li><li><strong>Step-by-Step Tutorials:</strong> Guides to help you navigate and configure NetSuite.</li><li><strong>Accounting &amp; Finance:</strong> Practical insights into managing accounting processes, financial transactions, reporting, taxation, and financial controls in NetSuite.</li><li><strong>Risk Management &amp; Audit</strong>: Exploring how to identify and manage risks, strengthen internal controls, maintain compliance, and perform audits in NetSuite.</li><li><strong>NetSuite Updates:</strong> New features, enhancements, and product announcements.</li></ul><h4>A journey of continuous learning</h4><p>I believe there’s always room to grow, regardless of how long we’ve been working with NetSuite.</p><p>Even after years with the platform, I know I still have plenty<strong> </strong>to learn. NetSuite is constantly evolving, and there’s always something new to discover, explore, or understand better.</p><p>Through this publication, I hope to share the knowledge and experiences I’ve gained over the years and document my own learning journey. I believe that sharing what we know and learning from one another are some of the best ways to grow.</p><p>I hope you’ll find something useful here, whether you’re taking your first steps or already have years of experience.</p><p><strong>After all, becoming a NetSuite hero doesn’t mean knowing everything. It means never stopping learning.</strong></p><p>Happy learning!</p><p><strong>AJ Bernardino</strong><br><em>CPA | CISA | Certified NetSuite Consultant</em></p><p><strong><em>Disclaimer:</em></strong><em> NetSuite: From Zero to Hero is an independent educational publication and is not affiliated with, sponsored by, or endorsed by Oracle NetSuite. All trademarks and product names belong to their respective owners.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7d84508952da" width="1" height="1" alt=""><hr><p><a href="https://medium.com/netsuite-from-zero-to-hero/welcome-to-netsuite-from-zero-to-hero-7d84508952da">Welcome to NetSuite: From Zero to Hero!</a> was originally published in <a href="https://medium.com/netsuite-from-zero-to-hero">NetSuite: From Zero to Hero</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>