CINCH Software
What's New
Version 16.0 M15
March 2017


Introduction
Supported Version
Dynamics GP
AgWorks
Feed Mill Manager
Chapter 1: Cinch Document Exchange
New AgXML 4.0 Sales Contract Export
New AgXML 4.0 Sales Contract Import
New OneWeigh Ship Company Export
New AgXML 4.0 In Transit-In Export
Chapter 2: Sales Miscellaneous
New Inventory Inquiry
Changes to Sales Setup
Chapter 3: Grain Miscellaneous
New Grain Series Post
New Contract Underfill Void
Changes to Load Order Inquiry
Changes to Accounting Reports
Changes to Outbound Setup
Changes to Bulk Shipment Entry
Chapter 4: Vendor Return
Changes to Next Number Maintenance
Changes to Batch Entry
New Vendor Return Setup
New Vendor Return Entry
New Vendor Return Inquiry
New Vendor Return Inquiry Zoom
Changes to Inventory Transactions Inquiry
Changes to Payables Transaction Entry Zoom
Appendix
New Windows
New Reports
New Tables
Changes that may affect Reports or Data

Introduction

What's New is your guide to enhancements in CINCH Software.
We add enhancements based on feedback we receive from customers, as well as on market research. Your willingness to help us build better products makes this a more complete solution, putting you in a better position to manage your organization successfully. We encourage you to share your thoughts and reactions with us at any time.
Some enhancements described in this documentation are optional and can be purchased through your CINCH software sales representative. If you currently have a license for one of these modules and have an active enhancement program, you will automatically receive the enhancements contained in that module.
This document describes enhancements that were added to CINCH Software since General Release 16.0.
Descriptions of the enhancements are divided into the following chapters:
Chapter 1, "Cinch Document Exchange," describes the miscellaneous changes made to Cinch Document Exchange.
Chapter 2, "Sales Miscellaneous," describes the miscellaneous changes made to Cinch Sales.
Chapter 3, "Grain Miscellaneous," describes the miscellaneous changes made to Cinch Grain.
Chapter 4, "Vendor Return," describes the Vendor Return processes where a user can enter returns to a Vendor for product that has been transferred to other locations or sold to customers and returned.

Supported Version

The following is a list of the Dynamics GP version we will be supporting for this release.

Dynamics GP

Software Version: 16.0 (16.00.0579 R2)
KB3218072
Dex Version: (16.00.0034)

AgWorks

AgWorks AgOS v3

Feed Mill Manager

Is currently not supported.

Chapter 1: Cinch Document Exchange

This chapter describes the miscellaneous changes made to Cinch Document Exchange.
This chapter contains the following modifications:

• New AgXML 4.0 Sales Contract Export
• New AgXML 4.0 Sales Contract Import
• New OneWeigh Ship Company Export
• New AgXML 4.0 In Transit-In Export

New AgXML 4.0 Sales Contract Export

AgXML 4.0 Sales Contract Export has been created to generate an XML file for the Sales Contract and pricing records for selected customers.

1. AgXML 4.0 Sales Contract Export

(Creates file for the Sales contract pricing records for selected customers.)

1. 1. Supported Exchange Partner Filters
      1. LOCNCODE is optional.
         1. Blank or * will send all sites.
         2. Enter a Site ID filters all documents on an exact Site match. Only one Site ID can be entered per service partner.
      2. IRRegionID is optional.
         1. Blank or * will send all regions.
         2. Enter a Region ID filters all documents on an exact Region match. Only one Region ID can be entered per service partner.
      3. IRBranchID is optional.
         1. Blank or * will send all branches.
         2. Enter a Branch ID filters all documents on an exact Branch match. Only one Branch ID can be entered per service partner
   2. Service Line Setting
      1. Cinch Consumer
         1. Yes, will add CINCH specific fields. Default = Yes
         2. No, will conform to AgXML version 4 specifications AgXML_v4.0.xsd (schema).
      2. Company ID Source
         1. This value specifies how the seller address is determined in the export file. Valid values are Company, Branch and Location. If the setting does not exist, or doesn't match one of the valid values, the Company ID will be sent.
            1. Company will translate to the GP Company main address. Default = Company
            2. Branch will translate to the Cinch Branch address.
            3. Location will translate to the address on the Site ID.
      3. Export Posted Changes
         1. Yes, when selected updates to a posted sales contract will export.
         2. No, when selected updates to a posted sales contract will NOT be exported. Default = No
      4. Export Sub Items
         1. Yes, will add CINCH specific fields.
         2. No, will conform to AgXML version 4 specifications AgXML_v4.0.xsd (schema). Default = No
      5. Message Label Extension
         1. The file extension of the export file.
            1. This extension can be anything but recommended to use XML for easy viewing in IE. (Example contract 1234 will write a file called 1234.xml).
      6. XML Namespace Prefix
         1. Recommended to leave this field blank.
            1. For specific XML naming requirements. Prefixes each tag with this value.
      7. XML Namespace URL
         1. Recommended to leave this field blank.
            1. Puts the XML namespace URL in the header of each document.

New AgXML 4.0 Sales Contract Import

AgXML 4.0 Sales Contract Import has been created to create Sales Contracts and contract pricing records based on the XML file.

1. AgXML 4.0 Sales Contract Import

(Processes file to create or update Sales contract pricing records for selected customers.)

1. 1. Supported Exchange Partner Filters
      1. No filters apply.
   2. Service Line Settings
      1. Batch Hours
         1. Represents the number of hours the batch is good for before a new batch number will be created. Used to limit batch sizes by creating multiple batches per day.
         2. If set to "0" the hours will not be included in the batch number.
      2. Batch Number
         1. If a batch number is entered it will be saved in that batch.
         2. If Batch Number is entered, Batch Prefix will not be used.
         3. Maximum number of characters 15.
         4. If the batch does not exist it will be added.
      3. Batch Prefix
         1. Default = AGXML
            1. If a batch prefix is entered it will be saved in a batch with a format of XXMMDDHH (XX is the Batch prefix, and MMDDHH is the user date (MM= Month, DD= Day and HH = Hour) of the transaction import if Batch hours is set.)
            2. If Batch Number is entered, Batch Prefix will not be used.
            3. Maximum number of characters is 15. This includes the branch prefix, the batch prefix and the date time suffix.
            4. If the batch does not exist it will be added.
      4. Consume Pricing Info
         1. Yes when selected allows the basic pricing information to be imported with the contract.
            1. Contract will be created with basic pricing (net price only, no basis or board) and the zero basis checkbox will be marked.
         2. No when selected no pricing record will get created. No is the default value and should only be changed if importing contracts generated from the Excel Purch Ctr Import 01 adapter.
      5. Default Branch
         1. A valid branch ID can be selected. If default branch is specified any unresolved seller/buyer addresses will be forced to this specified branch.
         2. If blank, the seller/buyer address in the AgXML must resolve to a location in the current company or the record will be rejected.
      6. Put Partner Doc# in Reference
         1. Yes, the contract number from the xml document will be placed in the "Reference No" field on the Sales Contract Entry window.
         2. No, the Reference No from the xml document will be placed in the "Reference No" field on the Sales Contract Entry window.
      7. Use Partner Doc#
         1. Yes, the contract will be created with the contract number from the xml document.
         2. No, the contract number will be auto generated based on the Sales Contract Number Setup (General Setup>Additional Setup>Sales Contract Type Numbering).
      8. User ID
         1. Document is created/updated on behalf of the specified user. This must be a valid Microsoft Dynamics GP user.
         2. If blank, User ID specified in CinchX Global Settings will be used.

Processing Note:

• Spot and Other Contract Types are not currently supported.
• Edits are only allowed for unposted contracts. Edits sent to a posted contract will be stopped within Document Monitor stating "Editing of posted Contracts is not supported in this version of eConnect."
• During import of contract records generated from the Excel Purch Ctr Import 01 adapter:
  • The discount schedule on the contract will get defaulted from Branch/Item Default maintenance.
    • This will only happen if the Consume Pricing Info setting is set to "Yes", and if it hasn't been included in the xml.
  • The program schedule on the contract will get defaulted from the Vendor extensions.
    • This will only happen if the Consume Pricing Info setting is set to "Yes", and only if it hasn't been included in the xml.
      • • The Contract Type will default to Cash.

New OneWeigh Ship Company Export

OneWeigh Ship Company Export has been created to export Cinch Ship Companies in the OneWeigh Name/Address record format.

1. OneWeigh Ship Company Export
   1. Service Settings
      1. Message Label Extension
         1. The file extension of the export file. It is recommended to use FIL.
      2. Name ID Type
         1. Choose which character to use for the Name/Address record "Name ID Type".
            1. This will default to S, but can be changed to whatever is setup in OneWeigh. Possible OneWeigh values are:
               1. C – Customer
               2. F-Farmer
               3. J- Joint
               4. S-Shipper
      3. Send ID Number
         1. Determine which identification number from the vendor (if any) to send.
            1. Choose EIN for the Electronic Identification Number to be sent, Employer ID# from Vendor Extensions Maintenance.
            2. Choose SSN for the social security number to be sent, Social Security # from Vendor Extensions Maintenance.
            3. Leave set to None to not export an identification number.
      4. User Defined1
         1. Used to map OneWeigh's user defined fields to Cinch's user defined/contact fields. Valid values are USERDEF1, USERDEF2, and CONTACT.
      5. User Defined2
         1. Used to map OneWeigh's user defined fields to Cinch's user defined/contact fields. Valid values are USERDEF1, USERDEF2, and CONTACT.
      6. User Defined3
         1. Used to map OneWeigh's user defined fields to Cinch's user defined/contact fields. Valid values are USERDEF1, USERDEF2, and CONTACT
      7. Vendor Class Filters
         1. If entered this must be a valid Microsoft Dynamics GP vendor class and each imported vendor will be assigned to this class
            1. Blank – all customer classes will be sent. Default = Blank
            2. * – all customer classes will be sent.
            3. Enter a single customer class or enter a comma separated list of customer classes.

Processing Note:

• The following will trigger a Ship Company Export
  • Add/Change of the Ship Method Detail Maintenance, the system will look to Cinch Ship method Companion table to see if a Vendor ID exists, if it does, then system will export the Shipper Information.
  • Change of Vendor Primary Address, if the Primary address for a vendor is tied to Ship Method Detail Maintenance, then any change to the address information will be exported.
• File Translation for record type of "NAMA1":
  • Record Type (Position 1-5) = NAMA1
  • Name ID (Position 6-15) = Cinch Vendor ID (translated)
  • Name (Position 16-65) = Vendor Name
  • Address Line #1 (Position 66-95) = Address 1
  • Address Line #2 (Position 96-125) = Address 2
  • City (Position 126-145) = City
  • State (Position 146-154) = State
  • Zip Code (Position 155-164) = Zip Code
  • Country (Position 165-184) = Country
  • Phone Number (Position 185-204) = Phone 1
  • User Defined #2 (Position 205-229) = Contact, UD1 or UD2
  • User Defined #3 (Position 230-254) = Contact, UD1 or UD2
  • User Defined #1 (Position 255-264) = Contact, UD1 or UD2
  • Social Security/Fed ID (Position 265-275) = Soc Sec # or Employer ID number
  • Active/Inactive/Temporary (Position 276-276) = Vendor Status
    • Use A if Active, I if Inactive.
  • Name ID Type (Position 300-300) = "S" (shipper)
    • Setup inside OneWeigh by default C – Customer, F-Farmer, J- Joint, S-Shipper
  • Add/Update Option (Position 347-347) = 3
    • Set to 3. Agris will add the Shipper if it does NOT exist or if it does exist, Agris will update the existing.

New AgXML 4.0 In Transit-In Export

AgXML 4.0 In Transit-In Import has been created to export Inbound In Transit Ticket records for selected customers.

1. AgXML 4.0 In Transit-In Export
   1. Supported Exchange Partner Filters
      1. Vendor filters apply
         1. Vendor ID is required. Only one vendor can be entered per service partner.
            1. Vendor can be vendor on the ticket or any ticket split owner. When a ticket for this vendor is entered in Cinch, it is exported by this service partner.
   2. Service Line Settings
      1. Cinch Consumer
         1. Yes, will add CINCH specific fields. Default = yes
         2. No, will conform to AgXML version 4 specifications AgXML_v4.0.xsd (schema).
      2. Company ID Source
         1. This value specifies how the buyer address is determined in the export file. Valid values are Company, Branch and Location. If the setting does not exist, or doesn't match one of the valid values, the Company ID will be sent. Default = Company
            1. Company will translate to the GP Company main address.
            2. Branch will translate to the Cinch Branch address.
            3. Location will translate to the address on the Site ID.
      3. Export Comments
         1. Yes, comments will be exported from the ticket. Default = yes
         2. No, comments will not be exported from the ticket.
      4. Export Notes
         1. Yes, notes will be exported from the ticket.
         2. No, notes will not be exported from the ticket. Default = no
      5. Internal Vendors Only
         1. Yes, only tickets vendors marked as Internal Customer will be exported.
         2. No, will have no effect on the exports.
      6. Message Label Extension
         1. The file extension of the export file.
            1. This extension can be anything but recommended to use XML for easy viewing in IE. (Example ticket 1234 will write a file called 1234.xml).
      7. Send All Updates
         1. Yes, system checks if the ticket has been previously exported and will send it again.
         2. No, system checks if the ticket has been previously exported and will not send updates to the exported tickets. Default = No
      8. Skip Freight
         1. Yes, will not send freight information from ticket. Default = yes
         2. No, will send freight information from ticket.
      9. Skip Gross Weight
         1. Yes, will not send gross weight from ticket. Net weight is sent regardless of this setting.
         2. No, will send gross weight from ticket. Net weight is sent regardless of this setting. Default = no
      10. Skip Tare Weight
          1. Yes, will not send tare weight from ticket. Net weight is sent regardless of this setting.
          2. No, will send tare weight from ticket. Net weight is sent regardless of this setting. Default = no
      11. Vendor Class Filters
2. If entered this must be a valid Microsoft Dynamics GP vendor class and each imported vendor will be assigned to this class.
3. Blank – all customer classes will be sent. Default = Blank
4. * – all customer classes will be sent.
5. Enter a single customer class or enter a comma separated list of customer classes.
   1. 1. XML Namespace Prefix
         1. Recommended to leave this field blank.
            1. For specific XML naming requirements. Prefixes each tag with this value.
      2. XML Namespace URL
         1. Recommended to leave this field blank.
            1. Puts the XML namespace URL in the header of each document.

Processing Note:

• In-Transit records will export on and insert or update, without any filtering on the posted or printed flags. The Setup All Updates can be used to limit the number of times the ticket gets exported.

Chapter 2:Sales Miscellaneous

This chapter describes enhancements made to the CINCH Sales processes.
This chapter contains the following sections:

• New Inventory Inquiry
• Changes to Sales Setup

New Inventory Inquiry

Inventory Inquiry has been created to more clearly display the item inventory quantities and break out, in detail, the allocated quantities and quantities not posted.

1. Open Inventory Inquiry

(Inquiry>Cinch Sales>Inventory Inquiry)

1. Restriction fields limit the data that is displayed in the list view portion of the window.
2. Item Range, enter the items for the start and end of your range.
3. Results to Return, defaults to 256, limits the number of results that are displayed in the list view of the window.
4. Zero Quantities, when checked, allows the user to show results with zero quantities.
5. Quantity Unit of Measure to Display determines the unit of measure that is used when displaying quantities in the results view. The selling unit of measure is the default option but it can be changed to the base unit of measure.
6. Branch defaults to the user's branch but can be changed.
7. Details to Display controls how the quantities for items are summarized and displayed.
   1. 1. Item; column summarizes all lot and site quantities per item. Any lot tracked items that have quantities not assigned will be included in the summarization.
      2. Site; columns will display depending on what has been selected within the Branch dropdown field. Each column will summarize the quantities for each item and site combination. Any lot tracked items that have quantities not assigned will be included in the summarization.
      3. Lot; columns will display depending on what has been selected within the Branch dropdown field and if the items has multiple lot numbers. Each column will summarize the quantities for each item, site and lot number combination. Any lot tracked items that have quantities not assigned to lots will not be included in this summarization.
8. List View, contains quantity information for all items matching the restriction criteria and scrolls vertically.
   1. Details to Display, based on the restriction criteria selected either Item, Item and Site or Item, Site and Lot will be displayed.
   2. On Hand displays the quantity available plus quantity allocated for the item.
   3. Un-Posted Incoming Quantities
      1. Purchase Receipts displays the total of inventory for all un-posted Purchase Receipts.
      2. Scale Tickets displays the total of inventory for all scale tickets that have not been posted.
      3. Mfg. Receipts displays the total of inventory for all un-posted Mfg. Receipts.
      4. Returned Not Posted displays the total of inventory for all un-posted returns.
      5. Sub-Total displays the total of all Un-Posted Incoming Quantities.
   4. Un-Posted Outgoing Quantities
      1. Committed to Mfg. displays the total of all inventory committed to manufacturing.
      2. Shipped Not Posted displays the total of all inventory (Grain and Bulk Shipments) shipped but not yet posted.
      3. Shipped Posted Not Invoiced displays the total of all inventory (Grain, Bulk and Shipment Invoicing Shipments) shipped and posted but not yet invoiced.
      4. Counter Sales not Posted displays the total of all inventory sold via the Counter Sales Entry window but not yet posted.
      5. Invoiced Not Posted displays the total of all inventory sold via the Invoice Maintenance window but not yet posted.
      6. Sub-Total displays the total of all Un-Posted Outgoing Quantities.
   5. IV Adjustments Not Posted displays the total of inventory for all un-posted inventory adjustments.
   6. IV Transfers Not Posted displays the total of inventory for all un-posted inventory transfers.
   7. Sub-Total displays the total of all inventory adjustment and transfers.
   8. Grand Total displays the total of On Hand plus Un-Posted Incoming Quantities minus Un-Posted Outgoing Quantities plus all inventory adjustments and transfers.
   9. Committed to Sales Orders displays the total of all inventory committed via the Sale Order Entry window.
9. Choose Clear to clear the screen.
10. Choose Redisplay to update the display based on selected criteria.
11. Choose Print to print the Sales Inventory Position Report.
12. Choose Export to export the results to Microsoft Excel.

Changes to Sales Setup

Sales Setup has been modified with the ability to Suppress the Zero Price Warning.

1. Open Sales Setup

(Microsoft Dynamics GP>Tools>Setup>Cinch Sales>Sales Setup)

1. Suppress Zero Pricing Warning checkbox, when marked, will suppress the warning in the following windows and will default to be un-marked.
   1. Order Entry.
   2. Counter Sales.
   3. Invoice Maintenance.

Chapter 3: Grain Miscellaneous

This chapter describes enhancements made to the CINCH Grain processes.
This chapter contains the following sections:

• New Grain Series Post
• New Contract Underfill Void
• Changes to Load Order Inquiry
• Changes to Accounting Reports
• Changes to Outbound Setup
• Changes to Bulk Shipping Entry

New Grain Series Post

The Grain Series Post window allows users to post by series, all batches that have been marked in the Grain Series Post window will be posted.
Series posting is performed as a background process, so you can enter, add, edit or delete transactions while posting is underway; however, you can't enter transactions in batches that currently are being posted, that are marked for posting, or that are being edited.

1. Open Grain Series Post

(Transactions > Cinch Grain > Grain Series Post)

1. Choose whether to display Inbound Tickets and or Outbound Shipment batches.
   1. Both will be marked when the window is opened.
   2. Checkboxes will be enabled/disabled based upon posting permissions in User Extensions Setup.
2. Choose whether to view all batches or just the ones marked for posting.
3. Mark any batches to post by selecting them individually or by using the Mark All or Unmark All buttons.

Note: If you are running on a network, choose redisplay before posting. The contents of the window will be updated to show any batches that have been added or changed by your coworkers since you opened the window.

1. 1. Batch ID, displays the ID for each batch created. Use the drill down on the Batch ID to open the Batch Entry window.
   2. Origin, indicates the batch Type
   3. Status, displays the posting status of the batch.
      1. Available indicates that the batch is available to be marked for posting.
      2. Marked indicates that the batch has been marked for posting.
      3. No Transactions indicates that the batch doesn't have any transactions to post.
      4. Busy indicates that the batch is in use.
      5. Post Failed on MMDDYY HH:MM:SS AM/PM indicates that someone attempted to post the batch, but it didn't completely post.
   4. Comment, displays any comments for the batch.
   5. User ID, displays the ID of the user who originally created the batch.
   6. No of Trx, displays the number of transactions in each batch.
   7. DPR Date, displays the date that the transactions will have an effect on the DPR Report.
2. Sorting Options:
   1. By Batch ID, displays batches in alphabetical order by Batch ID.
   2. By Origin, displays batches in alphabetical order by Origin.
3. Branch Options:
   1. Current Branch, displays all Batch IDs for the current branch.
   2. My Branches, default, displays only Batch IDs assigned to current user.
   3. All Branches, displays all Batch IDs for each branch.
4. Choose Post to post all batches that have been marked. Posting journals may be printed, depending on how posting options have been setup in the Posting Setup window.
5. Choosing Redisplay will update the window, displaying any information that has been added or changed by you or another user since you opened this window.

New Contract Underfill Void

This provides the ability for a Contract Underfill to be voided once it has been created.

1. Open Contract Underfill Void

(Transactions>Cinch Grain>Contract Underfill Void)

1. Choose either Sales or Purchase from the Source Type dropdown.
2. Enter or select the Contract Number.
   1. The system will validate if the original underfill created a Payable or Receivable transaction.  If it did, the user will be warned and stopped.
      1. The underfill can be reversed by deleting the unposted Payable or Receivable transaction.
3. Select Process to void the underfill.
   1. The under fill will be removed from the contract, the contract totals will be updated and the contract will be reopened.
4. Select Cancel to clear the screen without voiding the underfill.

Changes to Load Order Inquiry

Load Order Inquiry has been modified with the ability to Hide Voids.

1. Open Load Order Inquiry

(Inquiry>Cinch Grain>Sales/Outbound>Load Order Inquiry)

1. The ability to Hide Voided Load Orders has been added to the Load Inquiry display.
   1. The default filter will be set to Hide Voids but can be changed to Include Voids or Voids Only.

Changes to Accounting Reports

Accounting Reports has been modified with the addition of the Include Rejected Tickets option.

1. Open Accounting Reports

(Reports>Cinch Grain>Accounting)

1. Include Rejected Tickets checkbox when selected will include rejected scale tickets within the Unpaid Scale Tickets by Customer or Item reports.

Changes to Outbound Setup

Outbound Setup has been modified with the Require Seal Numbers option.

1. Open Outbound Setup

(Microsoft Dynamics GP>Tools>Setup>Cinch Grain> Sales/Outbound User)

1. Require Seal Numbers checkbox, when marked Bulk Shipments will not be allowed to be saved until a Seal Number is entered.

Changes to Bulk Shipment Entry

Bulk Shipment Entry has been modified to look to the Outbound Setup, Require Seal Numbers checkbox to determine if Seal Numbers are required on the shipment.

1. Open Bulk Shipment Entry

(Transactions>Cinch Grain>Sales/Outbound>Bulk Shipping)

1. The Save process will look to Outbound Setup, Require Seal Numbers checkbox, when marked:
   1. If a seal number exists the user can save the shipment.
   2. If a Seal Number does not exist user will be prompted "Seal Numbers must be entered. Do you wish to enter them now"
      1. Yes when selected will open the Load Shipment Seal Entry to allow user to enter the seal number(s).
      2. No, when selected return the user to the Bulk Shipment Entry window.

Chapter 4: Vendor Return

This chapter describes the Vendor Return processes where a user can enter returns to a Vendor for product that has been transferred to other locations or sold to customers and returned. The new functionality automates the current process most Cinch customers perform today.
This chapter contains the following sections:

• Changes to Next Number Maintenance
• Changes to Batch Entry
• New Vendor Return Setup
• New Vendor Return Entry
• New Vendor Return Inquiry
• New Vendor Return Inquiry Zoom
• Changes to Inventory Transactions Inquiry
• Changes to Payables Transaction Entry Zoom

Changes to Next Number Maintenance

Next Number Maintenance has been modified to include the Module, Vendor Return.

1. 1. 1. 1. Open Next Number Maintenance

(Microsoft Dynamics GP > Tools>Setup>Cinch Grain/Sales > Numbers Maintenance)

1. 1. 1. 1. Select Vendor Return to setup the document numbers to be used in Vendor Return Entry.
            1. Select the Document Prefix and Document Number to create for an individual Branch.

Changes to Batch Entry

Batch Entry has been modified to include the Module, Vendor Returns.

1. Open Batch Entry

(Transactions>Cinch Sales>Batch Entry)

1. Type, Vendor Returns has been added.
2. Posting process has been updated for Vendor Return. See Posting Vendor Returns.
3. Vendor Returns has been added to the Batch Print Options window.

1. 1. Print:
      1. Documents, when selected will print the Vendor Return Receipt.
      2. Edit List, when selected will print the Vendor Return Edit List.
   2. Include, will default to Vendor Returns marked.

New Vendor Return Setup

The Vendor Return Setup window allows the user to setup the user defined prompts that will display on the Vendor Return Entry window.

1. Open Vendor Return Setup

(Microsoft GP > Tools > Setup > Cinch Sales > Vendor Return Setup)

1. Two header user define prompts can be add to the Vendor Return Entry window.
2. Two detail user define prompts can be add to the Vendor Return Entry window.

New Vendor Return Entry

The Vendor Return Entry window allows users to enter returns to a Vendor. The return will generate two transactions, an inventory adjustment for the quantity of the return and an accounts payable return for the dollar amount of the return.
This section is divided into the following:

• Entering, Saving & Deleting a Vendor Return
• Posting Vendor Returns

Entering, Saving & Deleting a Vendor Return

1. Open Vendor Return Entry

(Transactions > Cinch Sales > Vendor Return Entry)

1. The Return Number will default in the next Vendor Return number based on the setup information entered in the Next Number maintenance window. The lookup button will open the Vendor Return Lookup window, which can be sorted by Return Number, Vendor ID or Date.

1. Return Date will default to the user date.
2. Enter a description for the Vendor Return.
3. Enter a Batch Number.
4. Lookup or enter the Vendor ID for the return.
5. Vendor Name will default for the selected Vendor.
6. Lookup or enter the Currency for the return. The expansion button will open the Currency Info window.
7. Enter an Authorization Number for the return.
8. Lookup or enter a Shipping Method for the return.
9. Lookup or enter a Reason Code for the return.
10. Tax Schedule defaults to the Tax Schedule assigned to the Vendor and is used only to default a Tax Schedule to the lines. If it is removed, the system will look to the vendor when calculating taxes.
11. Enter or select the Location/Site the return will be returned from. This site will then default to each line item but can be changed.
12. Address defaults to the vendor's Primary Address ID.
13. Header User Defined Prompt 1
14. Header User Defined Prompt 2
15. Lookup or enter an Item Number. Item Number and Vendor Item Number work in conjunction with each other. If an Item Number matches the Vendor's Item Number it will default. The lookup button will present a drop list with the following options:
    1. Item Lookup opens the Item window and allows the user to select from all items.
    2. Receipt Lookup opens the Purchase Receipt Item Lookup window and will default all purchase receipts for the selected vendor created in the past six months.

1. 1. 1. Enter or select a Receipt Date.
      2. Enter or select a Receipt Type. Defaults to Both but can be changed to Work (open receipts) or History (posted receipts).
2. Lookup or enter a Vendor Item Number. Vendor Item Number and Item Number work in conjunction with each other. If a Vendor Item Number matches an Item Number, it will default. The lookup button will present a drop list with the following options:
   1. Vendor Item Lookup opens the Vendor Items window and will display all items attached to the Vendor ID.
   2. Receipt Lookup opens the Purchase Receipt Item Lookup window and will default all purchase receipts for the selected vendor created in the past six months.
3. Enter the Qty to return, defaults to one.
4. Enter or select the U of M, defaults to the Purchasing U of M within Item Purchasing Options Maintenance window.
5. Cost defaults to the item's current cost.
6. Price defaults to the item's current cost but can be changed.
7. Enter or select the Price UOM, defaults to the Purchasing U of M within Item Purchasing Options Maintenance window.
8. Return Amount is calculated by taking the Qty * Price but can be edited.
9. Enter or select the Location/Site the return will be taken from. Defaults to the location selected in the header but can be changed and is required.
10. Extended Cost is calculated by taking the Qty * Cost and is not editable.
11. Lot Number, optional field, enter or lookup a lot number.
12. Tax Schedule ID, optional field, defaults to the Purchase Tax Schedule ID for the item.
13. Detail User Defined Prompt 1, the label will come from User Def Prompt 1 in the detail section on the Vendor Return Setup window.
14. Detail User Defined Prompt 2, the label will come from User Def Prompt 2 in the detail section on the Vendor Return Setup window.
15. Comment ID, enter or select a Comment ID.
16. Subtotal equals the total of all the line items entered for the return before taxes, freight and miscellaneous charges are added to the costs and the trade discounts are subtracted from the costs.
17. Trade Discount, enter a discount to be deducted from the Total.
18. Freight Amount, enter a freight expense to be added to the Total.
19. Misc Amount, enter additional deductions to be added to the Total.
20. Tax Amount displays the amount of tax that was calculated for the document. The expansion button opens the Vendor Return Tax Entry window, where you can view or change the amounts distributed to individual tax details.

1. Total, displays the total document amount, including the subtotal, trade discount, freight, miscellaneous and tax amounts. The total is calculated as follows: Subtotal – Trade Discount + (Freight + Miscellaneous + Tax).
2. Distributions opens the Vendor Return Distributions window.
   1. User will not be able to change Debit or Credit amounts.
3. Save, saves the changes you've made in this window.
4. Delete, deleted the vendor return.
5. Post, see Posting Vendor Returns
6. Print Icon, prints either the Vendor Return Receipt or a batch edit list.

Posting Vendor Returns

Posting can be done via the Post button on the Vendor Return Entry window or via Batch Entry. The posting process will create two transactions.

1. 1. 1. 1. 1. 1. 1. Accounts Payable Return
                     1. Debit:
                        1. Accounts Payable from the vendor.
                        2. Trade Discount account from the vendor if applicable
                     2. Credit:
                        1. Inventory Offset account from the item.
                        2. Tax account if applicable.
                        3. Miscellaneous account from the vendor if applicable.
                        4. Freight account from the vendor if applicable.
                  2. Inventory Adjustment
                     1. Debit:
                        1. Inventory Offset, Accrued Purchases account from the Vendor.
                     2. Credit:
                        1. Inventory, Inventory account from the item.

New Vendor Return Inquiry

This inquiry allows the user to view Vendor Returns for a vendor.

1. Open Vendor Return Inquiry

(Inquiry>Cinch Sales>Vendor Return Inquiry)

1. Select Range Restrictions:
   1. Vendor ID
   2. Return Date
2. Choose OK to close the window.
3. Choose Clear to clear the range values and the scrolling window.
4. Choose Redisplay to view the desired documents.
5. Choose Export to export displays information to a Microsoft Excel spreadsheet.

New Vendor Return Inquiry Zoom

This inquiry allows the user to view a Vendor Return.

1. Open Vendor Return Inquiry Zoom

(Inquiry>Cinch Sales>Vendor Return Inquiry: Expansion button next to the Return Number)
(Inquiry>Inventory>Transaction: Additional>E-Markets Additional Detail)

1. Choose OK to close the window.

Changes to Inventory Transactions Inquiry

The inquiry allows you to view detailed information about transactions create via Vendor Returns Entry that have been posted.

1. Open Inventory Transactions Inquiry

(Inquiry>Inventory>Transactions: Additional>E-Markets Additional Detail)

1. Choose E-Markets Additional Detail to open the Vendor Return Inquiry Zoom window, if the line item selected in Inventory Transaction Inquiry matches a Vendor Return.

Changes to Payables Transaction Entry Zoom

This inquiry allows you to view detailed information about transactions create via Vendor Returns Entry that have been posted.

1. Open Payables Transaction Entry Zoom

(Inquiry>Purchases>Transactions by Vendor: Drill down on Document Number opens the Payables Transaction Entry Zoom > Additional > Commodity Trx)

1. Choose Commodity Trx to open the Vendor Return Inquiry Zoom window, if the Number of the line selected in Payables Transaction Entry Inquiry matches a Vendor Return.

Appendix

This section lists the new windows and reports added to this release. Based on the Microsoft Dynamics GP security model, access will need to be determined per security task.
New Tables added to this release are also listed below.

New Windows

New Reports

New Tables

Changes that may affect Reports or Data