NetSuite Bill and Purchase Order Matching with Lightyear

NetSuite Bill and Purchase Order Matching

Do you use POs in NetSuite? 

Would you like your POs in NetSuite to automatically link to the bill and close when the bill is exported from Lightyear? Our new custom SuiteBundle may be just what you’re looking for!

What is a SuiteBundle?

A SuiteBundle is a group of custom scripts or objects that are grouped together to facilitate ease of distribution and installation of custom functionality in NetSuite.

What will be installed in NetSuite?

As part of this SuiteBundle, the following customisations will be installed in your NetSuite account to facilitate the bill to PO matching functionality:
  1. Custom transaction body fields on the standard vendor bill form:
    1. Lightyear Bill PO Match Status - text field on the bill to show the PO match status.
    2. Lightyear NS PO Reference - link on the bill to the matched NetSuite PO.
  2. Custom transaction body field on your nominated PO form/s:
    1. Lightyear Review PO - checkbox field on the PO to indicate whether the PO requires manual review.
  3. Custom subtab on your nominated PO form/s called Lightyear Bills to show the details of the bill/s matched to the PO.
  4. Two custom saved searches/reports:
    1. Lightyear bills linked to purchase order - this will show all bills in NetSuite that are linked to a NetSuite PO.
    2. Lightyear purchase orders for review [for closure] - this will show all NetSuite POs that are flagged as requiring review.
A NetSuite PO is flagged as requiring review when it is matched to bill/s but the total values don't match.

Bill to PO Matching Functionality

Please Note: This SuiteBundle is designed to match bills to purchase orders within NetSuite based on PO number and value only, there is no logic to check that the supplier/vendor between the bill and PO are the same. There is also no line-level matching within NetSuite. You can achieve line-level bill to PO matching within Lightyear if required. Read more about that here.
When a bill is exported from Lightyear to NetSuite with a value in the PO number field, the SuiteBundle will immediately check if there are any open POs in NetSuite with that same PO number and total value.
  1. If the PO number and value match between a bill and PO in NetSuite the bill and PO will be linked together and the PO will be closed.
    1. On the PO you will see the bill details and link to the bill in NetSuite via the custom Lightyear Bills tab.

    2. On the bill you will see the Bill to PO Match Status and link to the matched PO within NetSuite.

  2. If there is a match to the PO number, but the values do not match, the bill and PO will still be linked together, but the PO will remain open and a custom checkbox on the PO Lightyear Review PO will be ticked, to indicate a user needs to review it and manually close it off as required.

    1. The bill will reflect a variance in the Lightyear Bill PO Match Status field.

The two saved searches/reports facilitate an efficient mass review of POs that require review, which users can add to their NetSuite dashboard as a reminder and prompt for action.






Please Note: to facilitate the bill to PO matching in NetSuite, you will also need to ensure you have the custom PO number field added to your standard vendor bill form in NetSuite. Here is our knowledge base article on how to add this field.

Multiple Bills Matching to One PO

Where multiple bills are created in NetSuite with the same PO number assigned to all of them, the SuiteBundle will link each bill to the PO. 
  1. It checks if the total of all bills combined matches the PO value.
  2. Until the full amount on the PO is reflected in bills, the PO will remain open and the custom checkbox on the PO Lightyear Review PO will be ticked.
  3. Once the total value of all bills matched to the PO equals the total value of the PO, it will automatically close and be removed from the POs for review saved search.

Receipting Goods and Updating Inventory in NetSuite

As Lightyear exports to expense lines on bills in NetSuite and not item lines, this SuiteBundle cannot automate your inventory updating or receiving goods on the PO automatically.
If you need to receipt goods or update inventory in NetSuite from your PO, you will need to follow the NetSuite standard process to complete this:
  1. NetSuite users will need to press Receive on the open PO, update the quantity of items received and save.
  2. This will create the below GL impact.  This will cater to Serialised/lot numbered inventory, inventory statuses and bin management.
    1. Debit Inventory/Stock on Hand
    2. Credit Accrued Purchases account
  3. NetSuite users can run the standard Post Vendor Bill Variances program under Transactions > Payables to move the amount to the price and quantity variance accounts set on the item record (usually these accounts are cost of goods sold type accounts).
  4. Users can set up non inventory items linked to a variance/clearing/cost of goods account and that item should be used on the vendor bill created via Lightyear.
  5. At month end, users can clear out the price and quantity variance accounts to cost of goods sold via a journal.
If you need to receive goods or update inventory on a PO after it is already closed, you can edit the PO, open the lines, update the quantity of items, close the lines and save.

Variance Tolerance on PO Number Matching

While the PO number on the bill and PO in NetSuite must be the same, it will still match if there are casing differences. For example PO-123 and po-123 will match.
Any character differences will not result in a match. For example PO-123 and PO 123 will not match.

In case your suppliers are unable to quote the exact PO number on your bills, there are various ways to solve for slight differences in the PO number on your bills:
  1. Correct the PO number on the bill manually within Lightyear before it’s exported to NetSuite.
  2. Edit the bill within NetSuite and correct the PO number manually. Once the bill is saved it will trigger the auto-matching to the PO in NetSuite.

How to Get Started?

Please Note: This SuiteBundle is a chargeable feature. Our team will provide you with a quote prior to arranging the installation.

If you would like more information on this SuiteBundle, or this sounds like a solution you’d like installed in your NetSuite account, please email us at support@lightyearap.com and we will be happy to answer your questions or organise the installation for you.



      

    Check out our
    to stay up to date

      • Related Articles

      • Purchase Order Matching using Bills Exported from Lightyear

        Do you raise POs in Sage Intacct? If you use the Purchase Order module within Sage Intacct, you can automatically match and close the PO against any Bills exported from Lightyear by making use of Sage Intacct's Smart Events feature. If this sounds ...
      • Connecting to Netsuite

        Make sure you're logged into NetSuite as an admin There's quite a few steps required to get your NetSuite integration up and running, but this is only a one time set up and will not need to be completed again unless you wish to connect another ...
      • Sending a URL from Lightyear to NetSuite

        If you want to have your NetSuite files receive and present the URL linking back to the image file in Lightyear, you will need to configure NetSuite to accept it. Keep in mind, Lightyear currently only writes to two forms in NetSuite, the "Standard ...
      • Sending Product Code and Quantity from Lightyear to NetSuite

        If you want the extracted Product Code and Quantity on bills and credit notes to export into your NetSuite account, you will need to configure NetSuite to accept it first. Keep in mind, Lightyear currently only writes to two forms in Netsuite, the ...
      • How does my data appear in NetSuite?

        Where to find your bills in NetSuite Once you've exported your bills from Lightyear into Netsuite, head over to Transactions > Payables > Enter Bills > List in NetSuite to bring up the list of bill records.  Here, you'll be able to search or click ...