Buying Team:  Responsible for placing orders, monitoring inventory levels and reviewing any pricing or delivery discrepancies.  Buying team also updates SharePoint documents to identify inventory items for cycle counts and validates the final physical inventory counts.   

Warehouse Leads:  Create Stock Counts based on bins. A spreadsheet tracking bins counted and uncounted is in SharePoint. 

Warehouse Team: Receives product at the warehouse, verifies item counts and pricing on orders.  Identifies items for return to vendors (damaged, wrong item, etc.) and manages the return process.  Assigns inventory to specific bins and manages transfer of inventory to store locations.  Ensures inventory security at the warehouse and conducts assigned cycle counts in the warehouse regularly.

Warehouse Manager: Approves stock counts and stock count recounts.

Store Location Staff:  Assist in completing inventory cycle counts and annual physical inventory.  Monitors inventory on the sales floor. 

Inventory Associate: Responsible for processing inventory adjustments for the store locations.  

NetSuite System Analyst: Responsible for reviewing and exporting file to provide to the inventory service provider and importing inventory results for inventory service provider into NetSuite. 

Security Coordinator:  Reviews security protocols and monitors inventory in the main store and the Commons’ locations through surveillance camera footage. 

Inventory Service Provider: Complete annual physical inventory and provides reporting to store management to review and adjust inventory balances if needed. 

Financial Transaction Center (FTC):  Responsible for processing vendor invoices and credits timely and recording inventory adjustment entries.

• NetSuite  
• SharePoint Excel files 
• Kuali Financial System 
• Invoices, credits, returns and packing slips from vendors 

• NetSuite 
• RF-SMART (NetSuite)
• Kuali Financial System (KFS) 
• OAS Reporting Dashboard (KDW) 

• Credits and returns can make tracking and reconciliation challenging. 
• Physical inventory counts could contain errors. 
• Pricing issues may exist in item records in NetSuite. 

Ordering Product: 

1. The Buying Team places an order(s) with a vendor for inventory items to replenish what is sold based on inventory records in NetSuite, or orders special items.  
2. Buying team may need to source items not carried by established store vendors. 
3. If new vendor, buying team initiates vendor setup in NetSuite and notifies FTC to issue new vendor packet to the vendor. FTC issues new vendor packet. 
4. Once vendor returns the vendor packet, the FTC confirms the vendor is in KFS. If vendor is in KFS, FTC confirms if any updates are needed.  If vendor is not in KFS, FTC sends vendor invite via PaymentWorks. 
5. FTC receives vendor number confirmation from KFS for any updates and new vendor setup. FTC enters the KFS vendor number in the vendor record in NetSuite to link to KFS. 
6. If orders exceed establish buying limits, orders are directed to a secondary approver. 
7. PO is submitted electronically to vendor through NetSuite. 
8. Vendor fulfills the PO order and delivers product to the CRS Warehouse. 
9. When orders are delivered, the product is checked against the PO in NetSuite and the packing slips by warehouse staff to ensure accuracy of item SKU, pricing, UPC code and counts match. Shipping locations are verified, and item labels are printed if needed.   
10. Warehouse staff enter quantities received on the order in NetSuite.  NetSuite assigns a unique receiving number to the transaction and creates a GL entry to debit inventory and credit Accounts Payable based on quantity x unit cost on the PO. 
11. If PO does not match order as received, warehouse staff contact the Buying team to resolve with the vendor. 
12. Warehouse team identifies all product to be returned and Buying Team creates a VRMA in NetSuite that is available to match to the vendor credit. 
13. Vendor bills the store with hard copy or electronic invoicing.  All vendors not enrolled in electronic invoicing, are instructed to submit invoices with purchase order reference via email to: The Cornell Store 150 Ho Plaza, Ithaca, NY 14850 Email: cbsbo@cornell.edu. Include the PO number on the subject line and may include instructions in the body of the email. The purchase order is the contractual basis on which the supplier is paid for merchandise furnished. 
14. Manual invoices are entered through the Bill Purchase Order process. Electronic billing is sent via SPS Commerce (EDI) and processed through a verification system before going through the Bill Purchase Order process.  All Vendor credits are manually entered in Accounts Payable, via Refund VRMA process.   
15. In the event that no purchase order is created for an invoice, (for example when Apple Inc bills the store for the purchase of parts used by the Computing Center for repairs made to student computers), the Enter Bills or Enter Credits process is used.   
16. FTC team verifies 3-way match of vendor invoices to the receiving documents and PO in NetSuite.  If the item price or quantity billed differs from what was received, the item price or quantity may NOT be adjusted.  Adjustments are only handled through the appropriate Expense account:  quantity variance – Over/Short – Inventory; cost variance – COS – Vendor Price Variance.  The adjustments are to be within the established threshold. Large discrepancies warrant discussion with Store team (buyers or receivers) and/or researched with the vendor for appropriate credits prior to invoice entry and payment.  
17. Freight and Tickets (tag costs, color charges) are entered as a line item to record the appropriate COS account. Note: Federal Interstate Commerce Commission / Department of Transportation regulations require that all invoices for freight be paid within fifteen (15) days. Failure to comply can result in termination of carrier service or possible court action against Cornell University. It is extremely important that all freight bills be processed promptly! 
18. FTC creates a weekly payment file to process invoices for payment and sends to KFS via an integration. 
    1. Vendors are not paid if they have an outstanding credit balance or if a return has been made and the credit has not been received from the vendor. 
    2. Payment file is reviewed & approved by FTC Financial Manager for all invoices. Any invoices over $200K will be approved by the Associate Director Financial Transaction Center. Copy of the approval for invoices over $25K will be attached in NetSuite on bill record.  Approval for invoices under $25K will be saved in payment file record.  
    3. Invoices over $1M need additional approval attached by the University Controller (Karen Mahalo) OR need to be processed in KFS though a DV so proper approval routing occurs per university and audit requirements. 
19. Invoices are paid according to payment terms established by the university.

Inventory Stock Counts:

1. Store Locations
   1. Buying Team identifies items for stock count based on risk.
   2. Each location is assigned specific items and times to complete their stock counts created in NetSuite (RF-SMART Stock Count) by the Buying Team.
   3. Store location staff perform stock counts on a weekly basis.
   4. Counts are recorded using handheld mobile devices scanning items using RF-SMART Stock Count Directed (Scan Item).
   5. Stock Counts are approved by assigned supervisors / managers and stock count recounts are created for discrepancies and recounted by store staff. Once recounts are completed, they are approved by assigned supervisors / managers and adjustments created as needed.
   6. RF-SMART -> Stock Count -> View Counts (using the “rde35 Directed Counts” view), shows the following.
      1. Location
      2. “Owner” is the person who created the count
      3. Last Modified
      4. Date Created
      5. Name (name of the count)
      6. Status
         1. Open – Created but not started
         2. Started – Started in NetSuite and being counted
         3. Complete – Count is complete and approved
         4. Closed – All counts and recounts are complete.
      7. Warehouse Location
         1. A spreadsheet of all active bins showing bin number and date completed is located on SharePoint at Stock Count Tracker 3.2026.xlsx
         2. Weekly (sometime bi-weekly) Warehouse Leads create new stock counts based on uncounted bins. All items in those bins are counted.
         3. Warehouse staff are assigned bins to count using handheld mobile devices scanning items using RF-SMART Stock Count Directed.
         4. Stock Counts are approved by the Warehouse Manager or Warehouse Lead and stock count recounts are created for discrepancies and recounted by staff. Once recounts are completed, they are approved and adjustments created as needed.
         5. RF-SMART -> Stock Count -> View Counts (using the “rde35 Directed Counts” view), shows, in addition to what is listed above under “Store Locations”, the bins that were counted under “Bin Counting Groups”.

Annual Physical Inventory Count: 

1. Merchandise is prepped for physical inventory, missing tags are replaced and SKU’s are organized to facilitate inventory counts by frontline staff, supervisors, and managers. 
2. NetSuite inventory file reviewed for errors prior to physical inventory counts by the Store’s NetSuite System Analyst and SSIT.  
3. Store Managers review negative on hand report and research prior to inventory count being completed. All pending returns and pending transfers are received to store locations and damaged items are marked out.   
4. Once the inventory data has been scrubbed for errors, the master product file is exported by the NetSuite System Analyst.  There are 2 files provided to the external inventory service provider, one for store locations and one for the warehouse which uses bin management. 
5. The external inventory service provider completes the physical count of all items in each location. 
6. For the warehouse location only, inventory on the upper racks is pre-counted. Inventory sheets are provided to the external inventory service company to input into their system.  
7. Electronic service provider file sent electronically to the store NetSuite System Analyst. 
8. Store NetSuite System Analyst imports the physical count file into NetSuite. 
9. Variances are reported on discrepancy reports by the Buying Team and sent to store location staff to research. 
10. Store location staff forward result of research and recounts to the Buying Team for review. 
11. Buying team reviews research and the Store’s Inventory Associate updates NetSuite accordingly. 
12. Final inventory results extracted and presented by the Store’s Financial Manger to Senior Leadership, the Buying Team, and location managers.  
13. Extract of financial data each month updates KFS with inventory changes. 

Cornell Finance Staff

• Monitor inventory values, adjustments and fluctuations to identify possible fraud 
• Monitor inventory value on hand to ensure inventory is being managed appropriately (is value on-hand consistent with best practices). 
• Monitor inventory turns to identify slow moving merchandise that may need to be eliminated from the inventory portfolio. 
• Monitor profit margins on individual inventory items to identify pricing issues. 

• KFS – Kuali Financial System 
• OAS – Oracle Analytics Server, financial reporting tool (formerly known as OBIEE) 
• GL – General Ledger 
• FTC – Student and Campus Life Financial Transaction Center that processes financial transactions for Cornell Retail Services
• Stock Count = Cycle Count