Introduction

This document provides information on the various iVend Retail POS transactions that are integrated between iVend Retail (iVend) and Microsoft Dynamics NAV (NAV).

There are four (4) articles in total in the series on the integration between Microsoft Dynamics NAV and iVend Retail. Please refer to Knowledge Base Articles section on the iVend Retail portal at: http://knowledge.citixsys.com/ and search for these other documents in the series:

1. iVend Retail and Microsoft Dynamics NAV - Integration Overview and Architecture

2. iVend Retail - Masters Integration between Microsoft Dynamics NAV and iVend Retail

3. iVend Retail - Management Console transaction Integration between Microsoft

Dynamics NAV and iVend Retail

Note: - This Integration is available with iVend Retail versions 6.5 and above and Microsoft Dynamics NAV version 2013 R2.

POS Transaction Integration List

The following represents the list of iVend POS Transactions that the Integration has been completed for between iVend Retail and Microsoft Dynamics NAV.

· Sales Invoices

· Sales Orders

· Layaways (Laybys)

· Sales Refunds

· Sale Exchanges

· Advance Payments

· Incoming/Outgoing Payments

· Gift Certificates

Note: - The direction of integration is from iVend to NAV.

Business Scenario

For the ease of understanding the solution better, we will take a simple business scenario to see how and what documents will be created in the respective applications. The scenario taken is that a Sale transaction will be performed at the iVend POS and then we will see its corresponding documents that will be generated in NAV from the integration.

At the iVend POS

1. Log into the iVend POS and then perform a simple Cash Sale transaction with the Cash Customer (also referred to as the One Time or Walk-In Customer).

Integration Monitor

There are two sections in this monitor:

1. Microsoft Dynamics NAV to iVend – this section will show details that will flow from NAV to iVend

2. iVend to Microsoft Dynamics NAV – this section will show details that will flow from iVend to NAV

If there are no line items in any of the sections, then it means that there is no pending data to be integrated and the service is running fine.

To navigate to the Integration Monitor screen – In NAV, go to: Departments > iVend Retail > iVend Integration > Integration Monitor (Administration)

At NAV

In NAV, go to: Home > Posted Documents > Posted Sale Invoices. From the list available, select and click on the [View] button from the Menu Bar for the respective documents.

Note: A posted Sale Invoice in NAV is the corresponding document for the iVend POS Sale transaction document.

On opening the screen, the system will show the details with which the Sale transaction was performed at the POS.

Viewing Payment details for the Posted Sale Invoice

Once the base process is done we will now see how to view the Payment details for the posted Sale Invoice.

To view the details of the posted sale invoice, click on the [Navigate] button when you are on the Details page (refer to the above screenshot) to open the Posted Sale Invoice window, now in the next step select the [Cust. Ledger Entry] lookup button […] to open the next screen, i.e. View – Customer Ledger Entries.

In the View - Customer Ledger Entries screen select the Applied Entries.

On clicking the Applied Entries (refer to the aforementioned screen) it will open the View – Applied Customer Entries – Invoice <invoice  no> screen.

Clicking on the [Navigate] button will open “Edit – Navigate – Selected – G/L Entry” screen, click on the G/L Entry lookup button […] in the No. of Entries column to open the View – General Ledger Entries – <document no.> Cash screen.

On the “View – General Ledger Entries – < document no.> Cash” screen, the system will have the G/L entry with the Tender with which the transaction was performed at the iVend POS - in our example, this was Cash. 

Based on the account mappings setup in NAV for the corresponding tender type, it will be posted to the mapped G/L account – refer to the following screen image for further clarity: