| Module Highlights |
| |
 |
The Electronic Data Interchange (EDI) allows the automatic, electronic transmission and reception of purchase orders and invoices to and from your clients. |
|
|
 Top |
| Setup |
| |
|
Customer Setup |
| |
Customer information can be entered and stored and each customer is provided with a unique ID, which cannot be edited. Customer information includes customer id, customer name, address, invoice terms, credit limit, bank information, shipping information and further details. |
|
Customer EDI Information |
| |
Enters and stores EDI information for unique customers, allowing EDI transactions to occur with greater ease. |
|
Customer – Item Price |
| |
By using the Customer Item Price, a user can enter special prices for customers or different customer categories for a particular style/item or for a group of item/style. The Customer SKU# and UPC# is also defined for the customer for a particular style, which is required at the time of receiving EDI orders from the customer. The price entered is picked while reading 850.dat file. |
| |
|
|
| Top |
| Transactions |
| |
|
Receive PO & Changes (850 & 860) from EDI s/w |
|
User can directly receive purchase orders from the EDI Module with the Receive PO feature from the EDI option. This feature allows the 850.dat file to be imported and the purchase order to be received using EDI. Users can specify the file path from where the file is to be imported. Data is taken through EDI and extracted for further processing. |
|
PO Changes Entry Screen |
|
Users can make changes to purchase orders that are received through EDI. |
|
Send PO & Changes To Sales Module |
|
When the 850 & 860 (purchase orders) are received, they are sent to the sales module for further processing. A range of purchase orders can be transferred by specifying the range based on either of the following: |
|
|
Accounting Period |
|
Transaction Date |
|
Customer ID. |
|
Transaction Number. |
|
|
Receive Invoice from Sales Module |
|
The Invoice at the sales module is imported to EDI, after the purchase order files are processed and the item is shipped. Invoices that are generated are initiated and allotted with a sequential number (for e.g. E0001). |
|
Invoice Entry Screen |
|
User can either receive the invoices from the sales module or enter invoices manually. |
|
Send Invoice (810) to EDI s/w |
|
Invoice (810) is a transaction set used to claim payment for the goods or services supplied by the user, using EDI. |
|
Receive Invoice Ack (997) from EDI s/w |
|
The buyer can acknowledge receipt of invoice and its accuracy with this feature. It is a standard functional acknowledgement (997) made by the buyer on receipt of sales invoice through EDI. |
| Top |
| Reports |
| The following list of reports can be viewed and printed at the EDI Interface module |
|
Purchase Order Report |
| |
The user can view, at a glance, details of all the purchase orders (850) received. The report can be viewed by accounting year or by customer(s). |
|
Invalid PO List |
| |
A list of invalid purchase orders, with detailed explanations for the order incompletion. |
|
PO Change Report |
| |
A list of purchase orders (860) that have been changed by buyer. |
|
Invoice Report |
| |
Invoice reports show the user a detailed view of all the sales invoices generated for the sales orders received through EDI. |
|
Un-posted SO Report |
| |
A detailed list of sales orders that are un-posted. |
|
| Top |
