Nav 2013 Finance Essentials
Nav 2013 Finance Essentials
Finance Essentials in
Microsoft Dynamics® NAV 2013
Unless otherwise noted, the examples depicted herein are provided for illustration only and are fictitious. No
real association or connection is intended or should be inferred.
This courseware does not provide you with any legal rights to any intellectual property in any Microsoft
product. Complying with all applicable copyright laws is the responsibility of the user. Without limiting the
rights under copyright, no part of this courseware may be reproduced, stored in or introduced into a retrieval
system, or transmitted in any form or by any means or for any purpose, without the express written
permission of Microsoft Corporation.
Microsoft®, Microsoft Dynamics®, Microsoft® PowerPoint®, Microsoft® SQL Server® data management
software and Microsoft Dynamics® NAV are trademarks of the Microsoft group of companies. All other
trademarks are property of their respective owners.
These license terms are an agreement between Microsoft Corporation (or based on where you live, one of its
affiliates) and you. Please read them. They apply to your use of the content accompanying this agreement which
includes the media on which you received it, if any. These license terms also apply to Trainer Content and any
updates and supplements for the Licensed Content unless other terms accompany those items. If so, those terms
apply.
BY ACCESSING, DOWNLOADING OR USING THE LICENSED CONTENT, YOU ACCEPT THESE TERMS.
IF YOU DO NOT ACCEPT THEM, DO NOT ACCESS, DOWNLOAD OR USE THE LICENSED CONTENT.
If you comply with these license terms, you have the rights below for each license you acquire.
1. DEFINITIONS.
a. “Authorized Learning Center” means a Microsoft IT Academy Program Member, Microsoft Learning
Competency Member, or such other entity as Microsoft may designate from time to time.
b. “Authorized Training Session” means the instructor-led training class using Microsoft Instructor-Led
Courseware conducted by a Trainer at or through an Authorized Learning Center.
c. “Classroom Device” means one (1) dedicated, secure computer that an Authorized Learning Center owns
or controls that is located at an Authorized Learning Center’s training facilities that meets or exceeds the
hardware level specified for the particular Microsoft Instructor-Led Courseware.
d. “End User” means an individual who is (i) duly enrolled in and attending an Authorized Training Session
or Private Training Session, (ii) an employee of a MPN Member, or (iii) a Microsoft full-time employee.
e. “Licensed Content” means the content accompanying this agreement which may include the Microsoft
Instructor-Led Courseware or Trainer Content.
f. “Microsoft Certified Trainer” or “MCT” means an individual who is (i) engaged to teach a training session
to End Users on behalf of an Authorized Learning Center or MPN Member, and (ii) currently certified as a
Microsoft Certified Trainer under the Microsoft Certification Program.
g. “Microsoft Instructor-Led Courseware” means the Microsoft-branded instructor-led training course that
educates IT professionals and developers on Microsoft technologies. A Microsoft Instructor-Led
Courseware title may be branded as MOC, Microsoft Dynamics or Microsoft Business Group courseware.
h. “Microsoft IT Academy Program Member” means an active member of the Microsoft IT Academy
Program.
i. “Microsoft Learning Competency Member” means an active member of the Microsoft Partner Network
program in good standing that currently holds the Learning Competency status.
j. “MOC” means the “Official Microsoft Learning Product” instructor-led courseware known as Microsoft
Official Course that educates IT professionals and developers on Microsoft technologies.
k. “MPN Member” means an active silver or gold-level Microsoft Partner Network program member in good
standing.
m. “Private Training Session” means the instructor-led training classes provided by MPN Members for
corporate customers to teach a predefined learning objective using Microsoft Instructor-Led Courseware.
These classes are not advertised or promoted to the general public and class attendance is restricted to
individuals employed by or contracted by the corporate customer.
n. “Trainer” means (i) an academically accredited educator engaged by a Microsoft IT Academy Program
Member to teach an Authorized Training Session, and/or (ii) a MCT.
o. “Trainer Content” means the trainer version of the Microsoft Instructor-Led Courseware and additional
supplemental content designated solely for Trainers’ use to teach a training session using the Microsoft
Instructor-Led Courseware. Trainer Content may include Microsoft PowerPoint presentations, trainer
preparation guide, train the trainer materials, Microsoft One Note packs, classroom setup guide and Pre-
release course feedback form. To clarify, Trainer Content does not include any software, virtual hard
disks or virtual machines.
2. USE RIGHTS. The Licensed Content is licensed not sold. The Licensed Content is licensed on a one copy
per user basis , such that you must acquire a license for each individual that accesses or uses the Licensed
Content.
2.1 Below are five separate sets of use rights. Only one set of rights apply to you.
2.2 Separation of Components. The Licensed Content is licensed as a single unit and you may not
separate their components and install them on different devices.
2.3 Redistribution of Licensed Content. Except as expressly provided in the use rights above, you may
not distribute any Licensed Content or any portion thereof (including any permitted modifications) to any
third parties without the express written permission of Microsoft.
2.4 Third Party Programs and Services. The Licensed Content may contain third party programs or
services. These license terms will apply to your use of those third party programs or services, unless other
terms accompany those programs and services.
2.5 Additional Terms. Some Licensed Content may contain components with additional terms,
conditions, and licenses regarding its use. Any non-conflicting terms in those conditions and licenses also
apply to your use of that respective component and supplements the terms described in this agreement.
a. Pre-Release Licensed Content. This Licensed Content subject matter is on the Pre-release version of
the Microsoft technology. The technology may not work the way a final version of the technology will
and we may change the technology for the final version. We also may not release a final version.
Licensed Content based on the final version of the technology may not contain the same information as
the Licensed Content based on the Pre-release version. Microsoft is under no obligation to provide you
with any further content, including any Licensed Content based on the final version of the technology.
b. Feedback. If you agree to give feedback about the Licensed Content to Microsoft, either directly or
through its third party designee, you give to Microsoft without charge, the right to use, share and
commercialize your feedback in any way and for any purpose. You also give to third parties, without
charge, any patent rights needed for their products, technologies and services to use or interface with
any specific parts of a Microsoft software, Microsoft product, or service that includes the feedback. You
will not give feedback that is subject to a license that requires Microsoft to license its software,
technologies, or products to third parties because we include your feedback in them. These rights
survive this agreement.
c. Pre-release Term. If you are an Microsoft IT Academy Program Member, Microsoft Learning
Competency Member, MPN Member or Trainer, you will cease using all copies of the Licensed Content on
the Pre-release technology upon (i) the date which Microsoft informs you is the end date for using the
Licensed Content on the Pre-release technology, or (ii) sixty (60) days after the commercial release of the
technology that is the subject of the Licensed Content, whichever is earliest (“Pre-release term”).
Upon expiration or termination of the Pre-release term, you will irretrievably delete and destroy all copies
of the Licensed Content in your possession or under your control.
5. RESERVATION OF RIGHTS AND OWNERSHIP. Microsoft reserves all rights not expressly granted to
you in this agreement. The Licensed Content is protected by copyright and other intellectual property laws
and treaties. Microsoft or its suppliers own the title, copyright, and other intellectual property rights in the
Licensed Content.
6. EXPORT RESTRICTIONS. The Licensed Content is subject to United States export laws and regulations.
You must comply with all domestic and international export laws and regulations that apply to the Licensed
Content. These laws include restrictions on destinations, end users and end use. For additional information,
see www.microsoft.com/exporting.
7. SUPPORT SERVICES. Because the Licensed Content is “as is”, we may not provide support services for it.
8. TERMINATION. Without prejudice to any other rights, Microsoft may terminate this agreement if you fail
to comply with the terms and conditions of this agreement. Upon termination of this agreement for any
reason, you will immediately stop all use of and delete and destroy all copies of the Licensed Content in
your possession or under your control.
9. LINKS TO THIRD PARTY SITES. You may link to third party sites through the use of the Licensed
Content. The third party sites are not under the control of Microsoft, and Microsoft is not responsible for
the contents of any third party sites, any links contained in third party sites, or any changes or updates to
third party sites. Microsoft is not responsible for webcasting or any other form of transmission received
from any third party sites. Microsoft is providing these links to third party sites to you only as a
convenience, and the inclusion of any link does not imply an endorsement by Microsoft of the third party
site.
10. ENTIRE AGREEMENT. This agreement, and any additional terms for the Trainer Content, updates and
supplements are the entire agreement for the Licensed Content, updates and supplements.
12. LEGAL EFFECT. This agreement describes certain legal rights. You may have other rights under the laws
of your country. You may also have rights with respect to the party from whom you acquired the Licensed
Content. This agreement does not change your rights under the laws of your country if the laws of your
country do not permit it to do so.
13. DISCLAIMER OF WARRANTY. THE LICENSED CONTENT IS LICENSED "AS-IS" AND "AS
AVAILABLE." YOU BEAR THE RISK OF USING IT. MICROSOFT AND ITS RESPECTIVE
AFFILIATES GIVES NO EXPRESS WARRANTIES, GUARANTEES, OR CONDITIONS. YOU MAY
HAVE ADDITIONAL CONSUMER RIGHTS UNDER YOUR LOCAL LAWS WHICH THIS AGREEMENT
CANNOT CHANGE. TO THE EXTENT PERMITTED UNDER YOUR LOCAL LAWS, MICROSOFT AND
ITS RESPECTIVE AFFILIATES EXCLUDES ANY IMPLIED WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT.
14. LIMITATION ON AND EXCLUSION OF REMEDIES AND DAMAGES. YOU CAN RECOVER FROM
MICROSOFT, ITS RESPECTIVE AFFILIATES AND ITS SUPPLIERS ONLY DIRECT DAMAGES UP
TO US$5.00. YOU CANNOT RECOVER ANY OTHER DAMAGES, INCLUDING CONSEQUENTIAL,
LOST PROFITS, SPECIAL, INDIRECT OR INCIDENTAL DAMAGES.
It also applies even if Microsoft knew or should have known about the possibility of the damages. The
above limitation or exclusion may not apply to you because your country may not allow the exclusion or
limitation of incidental, consequential or other damages.
Please note: As this Licensed Content is distributed in Quebec, Canada, some of the clauses in this
agreement are provided below in French.
Remarque : Ce le contenu sous licence étant distribué au Québec, Canada, certaines des clauses
dans ce contrat sont fournies ci-dessous en français.
EXONÉRATION DE GARANTIE. Le contenu sous licence visé par une licence est offert « tel quel ». Toute
utilisation de ce contenu sous licence est à votre seule risque et péril. Microsoft n’accorde aucune autre garantie
expresse. Vous pouvez bénéficier de droits additionnels en vertu du droit local sur la protection dues
consommateurs, que ce contrat ne peut modifier. La ou elles sont permises par le droit locale, les garanties
implicites de qualité marchande, d’adéquation à un usage particulier et d’absence de contrefaçon sont exclues.
EFFET JURIDIQUE. Le présent contrat décrit certains droits juridiques. Vous pourriez avoir d’autres droits
prévus par les lois de votre pays. Le présent contrat ne modifie pas les droits que vous confèrent les lois de votre
pays si celles-ci ne le permettent pas.
Introduction
Microsoft Dynamics Courseware Overview…………………………………………………….....0-3
Student Objectives…………………………………………………………………………………………….0-4
Lesson 4: Cash Receipt Journal and Payment Journal Overview .............................................. 4-17
Lab 4.4: Suggest Vendor Payments for a Single Vendor .............................................................. 4-37
Lab 6.2: Apply Posted Partial Customer Payments with Discounts .......................................... 6-24
Lab 6.5: Adjust the Vendor Payment Discount Amount .............................................................. 6-52
Lesson 2: Set Up and Assign Number Series for Reminders and Issued Reminders.......... 7-14
Lesson 5: Set Up and Assign Number Series for Finance Charge Terms ............................... 7-33
Lab 7.4: Create and Issue Finance Charge Memos ......................................................................... 7-44
Module 8: VAT
Lesson 1: VAT Calculation Type ................................................................................................................8-3
Lesson 3: Adjust VAT Amounts in Sales and Purchase Documents and Journals ............... 8-17
Lesson 4: Set Up Prepayment Percentages for Customers and Vendors .................................. 9-8
Lesson 10: Process Prepayment Sales and Purchase Invoices .................................................... 9-28
Lab 9.2: Prepayment Sales Order Process with Payment Discount .......................................... 9-37
Lab 9.3: Prepayment Sales Order Process with Unrealized VAT ................................................ 9-45
Lesson 2: Set Up and Assign Number Series for Reminders and Issued Reminders.......... 7-14
Lesson 5: Set Up and Assign Number Series for Finance Charge Terms ............................... 7-33
Module 9: PREPAYMENTS
Lesson 2: Set Up Unrealized VAT for Prepayments ...........................................................................9-4
Lab 9.2: Prepayment Sales Order Process with Payment Discount .......................................... 9-37
Lab 9.3: Prepayment Sales Order Process with Unrealized VAT ................................................ 9-45
Online Training
Online training delivers convenient, detailed training in the comfort of your own
home or office. Online training provides immediate access to training 24 hours a
day. It is perfect for the customer who does not have the time or budget to travel.
Online training options combine the efficiency of online training with the
thorough product coverage of classroom training.
Classroom Training
Training Materials
Training materials help you learn at your own pace, in your own time, with
information-packed training manuals. The many training manuals features many
tips, tricks, and insights that you can reference continuously.
The Microsoft Dynamics courseware consists of detailed training manuals that are
designed from a training perspective. These manuals include advanced topics, in
addition to training objectives, exercises, interactions, and quizzes.
Look for a complete list of manuals that are available for purchase on
CustomerSource or PartnerSource.
0-1
Microsoft Official Training Materials for Microsoft Dynamics ®
Your use of this content is subject to your current services agreement
Finance Essentials in Microsoft Dynamics® NAV 2013
Lab
Within the Microsoft Dynamics training materials, you will find labs. These labs are
typically offered in two levels to accommodate each student’s variety of
knowledge and expertise. We suggest that you try the High level steps first. If you
need help completing the task, look to the information in the Detailed steps.
Detailed steps
Detailed steps are geared toward new users who require detailed instructions and
explanations to complete the lab. Detailed steps guide you through the whole
task. This includes navigation.
This training material might include content for new features that is specific to this
software version, and to any updated features. To assist in finding the content for
the new features, an icon ( ) is placed next to the heading. The icon identifies
areas that are new and, or changed from the earlier version. However, it is
important to review all content to make sure there is a thorough understanding of
this information.
Student Objectives
What do you hope to learn by participating in this course?
1.
2.
3.
Module Overview
Financial Management Setup describes in detail the following areas that must be
set up to use financials in Microsoft Dynamics® NAV 2013.
• General Ledger
• Accounting Periods
Note: There are other setup areas in the General Ledger, such as No. Series,
Dimensions, and Posting Groups. The setup of these areas is covered in the course
Application Setup in Microsoft Dynamics NAV 2013.
Objectives
• Explain and set up the fields on the General Ledger Setup window.
• Explain and set up Accounting Periods.
The five FastTabs on the General Ledger Setup window are as follows:
• General
• Numbering
• Dimensions
• Reporting
• Application
The General FastTab contains the basic setup defaults and includes the following
fields:
Note: Specific user posting date restrictions are specified in the User Setup
window. If there are no user restrictions, the company defaults are in effect. If there
are no company defaults, there are no restrictions on dates for posting.
• Register Time - Specify whether the system registers the user's time
usage.
• Local Address Format - Specify the address format that is used on
printed documents.
• Local Cont. Addr. Format - Specify where the contact name must
appear in mailing addresses.
• Invoice Rounding Precision (LCY) - Specify the size of the interval
to be used when rounding amounts in local currency (LCY).
• Invoice Rounding Type (LCY) - Specify if invoice amounts are
rounded up or down. The option selected here is used with the
rounding interval specified in the Invoice Rounding Precision (LCY)
field.
• Allow G/L Acc. Deletion Before - The date in this field determines
when G/L accounts can be deleted. G/L accounts that have entries on
or after the date specified in this field cannot be deleted.
• Check G/L Account Usage - Specifies that you want the program to
protect G/L accounts that are used in setup tables from being
deleted.
• EMU Currency - Select this field if the LCY is an European Monetary
Union (EMU) currency. Use this field only when you apply entries in
different currencies.
• LCY Code - Enter the currency code for the LCY. The value is only
used on printouts because the system uses <Blank> as the indicator
for the LCY when displaying information in tables.
• Pmt. Disc. Excl. VAT - Specify whether the payment discount is
based on amounts including or excluding value-added tax (VAT).
Note: In addition to the invoice rounding precision, you can specify the
amount rounding precision and the unit amount rounding precision. However, these
fields are not visible in Microsoft Dynamics NAV 2013 W1. Use the About This
Page function to view the values of these fields.
Numbering FastTab
Bank Account Nos. is the only field on the Numbering FastTab. In this field,
enter the code for the number series that will be used to assign numbers to bank
accounts.
Dimensions FastTab
On the Dimensions FastTab, specify the global and the shortcut dimensions to be
used for financial reporting.
The codes specified here are selected from the dimensions set up in the
Dimension table.
Determine which two dimensions will be analyzed most frequently and select
these as the two global dimensions.
The system automatically creates the first two shortcut dimensions based on the
global dimensions. Users can select the other six shortcut dimensions based on
the company’s preferences and business rules.
Global Dimensions
Note: Changing a global dimension code requires that the system changes
entries which are already posted. Carefully consider which dimension codes are
designated as a global dimension to minimize the need for future changes.
The complete setup process of the additional reporting currency is covered in the
course Finance Advanced in Microsoft Dynamics NAV 2013.
The fields on the Application FastTab are used to specify the following:
Payment Tolerance
Accounting Periods
With accounting periods users can create time references in Microsoft Dynamics
NAV 2013. A fiscal year consists of several accounting periods. The shortest
possible fiscal year consists of one accounting period with one day. This means
that you can set up accounting periods that are different from a calendar year.
You can use accounting periods in reporting. For example, when you are
reviewing posted entries in a Balance/Budget window where the reporting
interval can be specified, one of the options you may specify to report by
accounting period.
• Starting Date – Specifies the date that the accounting period will
begin. This can, but does not have to be the first day of the month.
You can change the starting date of a period manually when the
Date Locked check box is empty.
• Name – Specifies the name of the accounting period. As a default,
the program will enter the name of the month that corresponds to
the starting date.
• Manually
• Automatically, by using the Create Fiscal Year batch job
1. In the Search box, enter Accounting Periods, and click the related
link.
2. Click New.
3. In the Starting Date field, enter the date that the accounting period
begins.
4. In the Name field, the system automatically updates the name of the
month that corresponds to the Starting Date.
5. Select the New Fiscal Year check box to indicate the start of the year.
6. Repeat steps 4 and 5 for each period.
The New Fiscal Year check box must contain a check mark if an accounting
period is the first in a fiscal year. Microsoft Dynamics NAV 2013 uses that period
to determine which periods to close when the Close Year function is run.
To run the Create Fiscal Year batch job, follow these steps.
1. In the Search box, enter Accounting Periods, and click the related
link.
2. Click Create Year.
3. In the Starting Date field, enter the date on which the fiscal year
starts.
4. In the No. of Periods field, enter the number of accounting periods
the fiscal year will be divided into. There can be from 1 to 365
periods.
5. In the Period Length field, enter how long each accounting period
will be, for example, 1M = 1 month, 1Q = 1 quarter, and so on.
6. Click OK.
Note: For more information on date formulas, refer to the online help.
The Accounting Periods window also has the option to print a Trial Balance by
Period. Select the option and enter the parameters for the report.
As the controller at CRONUS International Ltd., you must create a new fiscal year
for 2015. Quickly create the new year by using the following information:
• The fiscal year begins on February 1, 2015 and ends on the January
31, 2016.
• The length of an accounting period is a month.
As the controller at CRONUS International Ltd., you must create a new fiscal year
for 2015. Quickly create the new year by using the following information:
• The fiscal year begins on February 1, 2015 and ends on January 31,
2016.
• The length of an accounting period is a month.
Detailed Steps
1. Create the fiscal year for 2015 as specified in the scenario.
a. Click Departments in the navigation pane.
b. Click Administration, click Application Setup, click Financial
Management and then click Finance.
c. In the Finance window, click Accounting Periods.
d. In the Home tab, click Create Year.
e. In the Starting Date field, enter 2/1/2015.
f. In the No. of Periods field, enter 12.
g. In the Period Length field, enter 1M.
h. Click OK.
After you create the fiscal year for 2015 you realize that a fiscal year should start
on January 1. Make the necessary changes so that both fiscal years 2015 and 2016
start on January 1.
Detailed Steps
1. Manually change the starting date of fiscal years 2015 and 2016.
a. Click Departments in the navigation pane.
b. Click Administration, Application Setup, Financial
Management and then click Finance.
c. In the Finance window, select Accounting Periods.
d. In the Home tab, click Edit List.
e. For the accounting period with the starting date 1/1/2015, select
the New Fiscal Year check box.
f. For the accounting period with the starting date 2/1/2015, clear
the New Fiscal Year check box.
g. Repeat steps 5 and 6 for fiscal year 2016.
h. Click OK.
Module Review
Module Review and Takeaways
Financial Management Setup describes the areas that must be set up to use
Financial Management in Microsoft Dynamics NAV 2013.
The General Ledger Setup window provides a quick and fast view of the options
to set up the general ledger area for a company in Microsoft Dynamics NAV 2013.
You can use accounting periods to open and close the fiscal year. They are used as
a time reference in financial reporting.
The areas discussed in this content are the basis of the general ledger setup. There
are many other areas that must be set up in Microsoft Dynamics NAV 2013, such
as Posting Groups and Dimensions.
2. Where are posting date restrictions set in Microsoft Dynamics NAV 2013?
( )2
( )6
( ) Unlimited
4. Which rule applies when you change the starting date of an accounting
period?
( ) The starting date can only be changed for accounting periods in the
future.
( ) The starting date can only be changed for accounting periods without
a date lock.
( ) When global dimensions are set up, they cannot be changed any
longer.
2. Where are posting date restrictions set in Microsoft Dynamics NAV 2013?
( )2
(√) 6
( )8
( ) Unlimited
4. Which rule applies when you change the starting date of an accounting
period?
(√) The starting date can only be changed for accounting periods in the
future.
( ) The starting date can only be changed for accounting periods without
a date lock.
(√) By running the Change Global Dimensions batch job in the General
Setup window.
( ) When global dimensions are set up, they cannot be changed any
longer.
Module Overview
General Ledger is the central application area of MICROSOFT DYNAMICS ®
NAV 2013 that is used to post, summarize and report financial information.
Two main components of the General Ledger application area are the Chart of
Accounts and G/L Budgets. The Chart of Accounts provides quick access to G/L
accounts and balances, and the budgets feature provides a comparison between
actual amounts and budgeted amounts, by using a combination of G/L accounts,
periods, and dimensions.
Note: Because G/L budgets are used in financial reporting, the setup and use
of G/L budgets is covered in the course Finance Advanced in Microsoft Dynamics
NAV 2013.
Objectives
An account in the income statement and the balance sheet is called a G/L
account, and all the G/L accounts make up the Chart of Accounts list.
You use G/L account cards to create and edit G/L accounts.
The G/L account card has five FastTabs that are explained in the following section.
General FastTab
1. In the Search box, enter Chart of Accounts, and click the related
link.
2. Select the relevant account to view.
3. On the Home tab, click Edit.
Best Practice: You can also double-click the line of the relevant account to
open the G/L account card.
Posting FastTab
The Posting FastTab contains the following fields that determine how the G/L and
value-added tax (VAT) transactions are recorded.
• Gen. Posting Type: Defines whether the account is used only for a
Sale or Purchase transaction or with both types of transactions. This
field is used with the VAT Bus. Posting Group and VAT Prod.
Posting Group fields to determine where the system will posts VAT.
The following options are available:
After the posting types and the posting group codes are assigned to a G/L
account, these codes are automatically inserted in a journal, sales, or purchase line
when the G/L account is selected.
Note: If the general posting groups are set up with default VAT posting
groups, the VAT posting group fields are automatically populated with the default
values when the general posting group(s) is selected.
Consolidation FastTab
The Consolidation FastTab contains the following fields that specify the link with
the consolidated company:
Note: For more information about the fields that appear on the
Consolidation FastTab, refer to the Help.
Reporting FastTab
The Reporting FastTab specifies how general ledger accounts will be adjusted for
exchange rate fluctuations between the local currency (LCY) and the additional
reporting currency, if you post in an additional reporting currency.
The Cost Accounting FastTab specifies a cost type number to establish the cost
type that a general ledger account belongs to.
1. In the Search box, enter Chart of Accounts, and click the related
link.
2. In the Home tab of the ribbon, click New.
3. On the General FastTab, in the No. field, enter the account number.
4. In the Name field, enter a description.
5. In the Income/Balance field, click the drop-down list and select the
relevant option.
6. In the Account Type, field, click the drop-down list and select the
relevant option.
7. If it is necessary, enter the range in the Totaling field.
Note: By running the Indent Chart of Accounts function, the Totaling field
is populated automatically.
1. In the Navigate tab of the ribbon, click Dimensions and then select
Dimensions-single.
2. In the Dimension Code field, click the drop-down list and select the
relevant dimension from the list.
3. In the Dimension Value Code field, click the drop- down list and
select the relevant dimension value from the list.
4. If there are dimension posting requirements, in the Value Posting
field, click the drop-down list and select the appropriate option.
5. Close the Default Dimension and the G/L Account Card.
• Indent the G/L accounts between the begin-total account and the
end-total account.
• Populate the totaling field of the end-total account.
1. In the Chart of Accounts list, locate and select the new account.
2. Click Actions, point to Functions, and then click Indent Chart of
Accounts.
3. Click Yes to run the indent function.
4. Close the Chart of Accounts list.
• Home
• Actions
• Navigate
• Report
Home Tab
From the Home tab, you can view, edit, delete, or create a new G/L account.
The following single-click accesses are also available from the Home tab:
• OneNote
• Notes
• Links
Actions Tab
The Actions button provides the most relevant navigation accesses for the G/L
Account Card.
You can use the Apply Template function to create G/L accounts by using Data
Templates. Data templates are part of the Rapid Start tool. This tool is explained
in the Application Setup in Microsoft Dynamics NAV 2013 content.
Navigate Tab
You can use the Navigate tab to display information about the balances and
transaction amounts for the account. You can also open the set up windows for
the relevant G/L account.
The Navigate tab provides single-click access to the following functions and
overviews:
Report Tab
A new revenue account must be created for miscellaneous sales. Because you are
the accounting manager at CRONUS International Ltd., it is your responsibility to
use the following information to set up the new account by using the G/L Account
Card.
Field Value
Gen Posting Type Sale
Gen. Bus. Posting Group NATIONAL
Make sure that the Account Types are formatted and the hierarchy is established.
Detailed Steps
1. Open a new G/L Account Card page.
a. In the navigation pane, click Departments and then click
Financial Management.
b. In the Financial Management page, click General Ledger, and
then click Chart of Accounts.
c. In the Action Pane, select the New button.
Detailed Steps
1. Run the Indent Chart of Accounts function.
a. In the Chart of Accounts list, in the Home tab of the ribbon,
click Indent Chart of Accounts.
b. Click Yes to run the indent function.
c. Review the new account; notice that it is indented with the other
sales accounts in the same range.
Chart of Accounts
The Chart of Accounts page contains the same fields that are on the G/L Account
Card page but here they are in a table format. In addition to the information on
the individual account cards, the Chart of Accounts list displays the current Net
Change and Balance information for the accounts.
The Chart of Accounts page contains a ribbon with options that resemble the
G/L Account Card:
• Home
• Actions
• Navigate
• Report
Home Tab
Compared with the G/L Account Card, the Home tab of the Chart Of Accounts
contains the following additional functions:
Actions Tab
The Find function helps you find accounts by searching on the fields displayed in
the chart of accounts. The columns added with the Choose Columns function will
also become available in the Find function.
Compared with the G/L Account Card, the Navigate tab of the Chart Of
Accounts contains following additional functions:
• Dimensions:
o Dimensions - Single - The same function as the Dimensions
function on the account card.
o Dimensions - Multiple - Used to assign the same default
dimensions to multiple accounts.
To assign the same dimensions to multiple G/L Accounts, follow these steps.
All sales should be posted to the DEPARTMENT dimension SALES. This should be a
mandatory dimension and dimension value, where SALES is the only possible
dimension value.
Use the value posting to make the dimension and dimension value mandatory.
Detailed Steps
1. Open the chart of accounts page, locate and select the sales G/L
accounts.
a. In the navigation pane, click Departments, and then click
Financial Management.
b. In the Financial Management page, click General Ledger, and
then click Chart of Accounts.
c. Select the lines of accounts 6100 to 6955.
Detailed Steps
1. Open the Default Dimensions-Multiple page and assign the default
dimension.
a. In the Navigate tab, click Dimensions, and click Dimensions-
Multiple.
b. In the Home tab, click New.
Module Review
Module Review and Takeaways
As the core component of a company, the Chart of Accounts lesson covered the
G/L Account Card and the Chart of Accounts page, and the process for creating
G/L accounts. This lesson also covered additional functions such as, indenting the
chart of accounts, and assigning default dimensions to multiple accounts.
1. What function is used to create default G/L account setups for accounts that
are frequently created, such as expenses?
( ) Assign Template
( ) Enter Template
( ) Import Template
( ) Apply Template
2. In the G/L Account Card, what field is used to determine which accounts are
closed during the fiscal year end closing process?
( ) Reconciliation Account
( ) Debit/Credit
( ) Account Type
( ) Income/Balance
( ) You cannot set up a graphical overview of all the G/L accounts with a
negative balance, using the chart of accounts page.
( ) You can create new G/L accounts from the chart of accounts page.
5. Direct posting is typically not enabled for G/L accounts on which only system-
generated transactions are posted. For which of the following G/L account
would you not select direct posting?
( ) Receivables account
( ) Cash account
1. What function is used to create default G/L account setups for accounts that
are frequently created, such as expenses?
( ) Assign Template
( ) Enter Template
( ) Import Template
2. In the G/L Account Card, what field is used to determine which accounts are
closed during the fiscal year end closing process?
( ) Reconciliation Account
( ) Debit/Credit
( ) Account Type
(√) Income/Balance
( ) You cannot set up a graphical overview of all the G/L accounts with a
negative balance, using the chart of accounts page.
(√) You can create new G/L accounts from the chart of accounts page.
5. Direct posting is typically not enabled for G/L accounts on which only system-
generated transactions are posted. For which of the following G/L account
would you not select direct posting?
( ) Cash account
Module Overview
In Microsoft Dynamics® NAV 2013, general journals are used to post information
into the general ledger and other accounts. The general journal is also used to
post cost allocations and other adjustments to the accounts and then users can
reverse and correct incorrect entries, when you have to.
When users frequently have to enter the same journal postings, Microsoft
Dynamics NAV 2013 provides two helpful tools, standard journal and recurring
journals. Standard journals can be created and used to enter journal lines
automatically. Recurring journals can be created and when they are opened they
already contain journal lines that can be reviewed, adjusted and posted on a
recurring basis. Additionally, when you use recurring journals that you can post
cost allocations by using allocation keys based on amounts or percentages.
Note: How to set up journal templates and batches is covered in the course
Application Setup in Microsoft Dynamics NAV 2013.
Objectives
Note: Through the Choose Columns function, the VAT Bus. Posting Group
and VAT Prod. Posting Group fields can be made available on the General
Journal page.
12. In the Amount field, enter the amount for the entry. Positive and
negative amounts in general journals are posted to the account
specified in the Account No. field as follows:
o A positive amount represents a debit to the account.
o A negative amount represents a credit to the account.
Note: Through the Choose Columns function, the Debit Amount and Credit
Amount fields can be made available on the General Journal page. When you
enter an amount in these fields, the Amount field will be automatically filled in.
Note: When the posting group fields are filled in, the amount in the Amount
field is considered eligible for the value-added tax (VAT). After posting, the amount
will be split in the amount excluding VAT. This amount will then be posted on the
account filled in on the journal line, and the VAT amount, that will be posted on the
VAT account, according to the VAT setup of the specified VAT posting groups on the
journal line.
13. In the Bal. Account Type and Bal. Account No. fields, click the
drop-down list to select the balancing account for this entry. These
fields are automatically populated when the controlling general
journal batch is set up with a default balancing account type and
number.
Note: Through the Choose Columns function, the Bal. VAT Bus. Posting
Group and Bal. VAT Prod. Posting Group fields can be made available on the
General Journal page.
Notice that the Balance and Total Balance fields at the bottom of the window are
equal to zero.
When a journal contains multiple entries that are all applied to the same
balancing account, users can enter one final balancing line so that only one
complete line is posted to the balancing account. This is helpful, for example,
when you are reallocating costs.
To create journal entries with a separate balancing line, follow these steps.
Note: The Document No. field contains the same number as the previous
line when the previous lines combined are not in balance. When the previous lines
are in balance the Document No. field will be given the next sequential number,
according to the number series that is set up in the No. Series field on the
corresponding general journal batch.
To view the effect that the journal will have on the accounts set up as reconciling
accounts, you can print a test report before posting. To preview the test report
from a general journal, follow these steps.
You can only post a general journal, when you meet the following conditions:
• The Total Balance field at the bottom of the General Journal page
is equal to zero.
• The general journal lines are balanced by date, based on Posting
Date.
• If the Force Doc. Balance field is selected in the controlling general
journal template, the general journal lines must also balance by
document number and document type.
Note: When the Force Doc. Balance field is clear, you can post transactions
that do not balance by document number. However, you cannot reverse the
resulting entries, because you cannot automatically reverse transactions that do not
balance by document number.
Note: Only visible journal lines, or, in other words, lines that are within the
filter, and are in balance, are posted. The entries that are hidden because the filter is
applied are not posted, even if they balance.
3. Click OK.
4. Click OK to close the General Journal page.
1. In the Batch Name field, click the drop-down list to open the
General Journal Batches page.
2. On the Home tab, click Post.
3. Click Yes to post the journals.
4. Click OK.
5. Click OK to close the General Journal Batches page.
6. Click OK to close the General Journal page.
The results of a journal posting can be viewed on the G/L Registers page. To
access the entries, follow these steps.
Scenario: On January 25, 2014, Cassie, the accountant for CRONUS International
Ltd. had to post a 60.00 local currency (LCY) payment for a cleaning expense.
However, she accidentally posted the expense on the incorrect account, 8120. She
now has to post the expense to the correct account, 8110. This expense must be
posted to the Production department dimension. Notice that the Department
dimension is already added to the General Journal window. Because this is a
single entry, a separate balancing line will not be used. Review the entry after
posting.
Demonstration Steps
As the accounting manager at CRONUS International Ltd., you have to create and
post a debit journal entry that is divided between the Sales and Administration
Departments. But the credit entry must not be separated by department. Use the
following criteria to complete this journal entry:
After you post the entries, review them in the G/L Register and then close all open
windows.
Detailed Steps
1. Enter the necessary lines in the general journal.
a. On the navigation pane, click Departments.
b. Click Financial Management, click General Ledger, and then
click General Journals.
c. In the Batch Name field, click the drop-down list and select the
DEFAULT journal batch.
d. Delete existing lines, if there are any.
e. In the Posting Date field, enter 01/01/14.
f. Do not change the Document No. field.
g. In the Account Type field, click the drop-down list and select G/L
Account.
h. In the Account No. field, enter 8110.
Standard Journals
Standard journals are useful for transactions that are posted frequently with few
or no changes, but do not have a fixed recurrence between two posts. A standard
general journal is a general journal that is saved as a default set of lines. It can be
accessed at a later stage to automatically fill in general journal lines.
Scenario: On January 31, 2014 Phyllis has to process the payroll payments by
using the standard journal, with the following criteria.
Demonstration Steps
Note: If the Force Doc. Balance check box is selected on the controlling
journal template, then you will be obligated to change the document number. All
journal lines must then have the same document number otherwise you cannot
post the general journal.
Recurring Journals
Recurring journals are useful for transactions that are posted frequently with few
or no changes. Some criteria for a recurring journal includes the following:
Note: Only the recurring general journals post to general ledger accounts and
they will be discussed later in this lesson.
The Recurring Method field determines how the amount on the journal line is
treated after posting. The following table shows the various recurring methods.
Recurring Frequency
For example, if the formula 1M is entered with a Posting Date of 01/15/10, after
the journal is posted, the date is changed to 02/15/10.
Use one of the following methods to post an entry on the last day of every month
after the current month:
• Post the first entry on the last day of a month and enter the formula
1D+1M-1D (1 day + 1 month - 1 day). With this formula, the
program calculates the date correctly regardless of how many days
are in the month.
• Post the first entry on any arbitrary day of a month and then enter
the formula: 1M+CM. With this formula, the program calculates one
full month plus the remaining days of the current month.
Note: If you are posting monthly accruals that must be reversed the following
month (Reversing Fixed, Reversing Variable, and Reversing Balance methods), post
them on the last day of each month. The first entry must be posted on the last day
of the current month and the recurring frequency must be either 1D+1M-1D or
1M+CM. This makes sure the reversal is always posted on the first day of the
following month.
Instead of using a number series to determine the value in the Document No.
field, Microsoft Dynamics NAV 2013 provides the option to enter a formula to
create a document number for each posted entry that is then updated
automatically every time that the recurring journal is posted.
Note: Typically, the No. Series field is left blank on the Journal Templates
page and the General Journal Batches page for recurring journals and
corresponding journal batches.
The Posting No. Series field on the journal batch will override the manual
document numbers on the recurring journal line. If you want to use the formulas as
the posted number on the ledger entries, make sure that the Posting No. Series
field is left blank.
Simple text can be combined with the following text codes to form a number
series:
For example, if the entry's document number is R (rent) + current month, enter
R%3 in the field. The document number for January will then be R1.
If there is more than one line in the journal, the program will do the following:
• Automatically keep the same number on the next lines, until the
balance for the journal is zero (0).
• Enter the next consecutive number on the next line.
When the Copy VAT Setup to Jnl. Lines field is selected in the general journal
batch, the following five fields are populated based on the posting setup on the
selected Account No.
Note: Through the Choose Columns function, the VAT Bus. Posting Group
and VAT Prod. Posting Group fields can be made available on the Recurring
General Journal page.
Note: When the posting group fields are filled in, the amount in the Amount
field will be considered to include VAT.
Expiration Dates
Recurring journal lines can be set up with expiration dates. Use the Expiration
Date field to limit the posting period by specifying the last date that an entry can
be repeated.
By using this field, a line can be entered in the journal even though it will only be
posted for a limited period. The line will not be posted after the date entered in
the field.
The advantage of using this field is that the line will not be deleted from the
journal immediately and the present expiration date can be replaced with a later
one so that the line can be used additionally into the future.
If the field is blank, the line will be posted during each posting process until it is
deleted from the journal.
Allocations
Allocations are used to allocate the amount on the recurring journal line to several
G/L accounts and dimensions. Meaning that the allocation is in itself a balancing
account line to the recurring journal line because recurring entries do not have
balancing accounts.
Just as in a recurring journal, an allocation only has to be entered one time. The
allocation remains in the allocation journal after posting. Therefore, you do not
have to re-enter amounts and allocations every time that the recurring journal line
is posted.
Allocate the amount from the line to different accounts and dimensions by using
one of the following allocation methods:
After you enter the lines with the allocations, the Recurring General Journal
page displays the following:
Note: The posting fields can be filled in on either the recurring journal line or
on the allocation line, but not on both. These fields are as follows: Gen. Posting
Type, Gen. Bus. Posting Group, Gen. Prod. Posting Group, VAT Bus. Posting
Group, and VAT Prod. Posting Group.
The demonstrations in this lesson will show how to process recurring journals. The
first demonstration uses a new recurring journal that will be set up first. It will
show how to post recurring payable entries that must be paid but do not require
invoice documents. Different recurring methods are used and the costs are
allocated to multiple departments.
The second demonstration summarizes income and expense accruals. It will show
how to post an accrual by using the Reverse Variable method.
• Cleaning: The amount 500.00 LCY, always due on the fifteenth of each
month, and allocated between these three departments:
o Administration - 50 percent
o Production - 25 percent
o Sales - 25 percent
• Advertising Expenses: Variable, but always due on the twenty-fifth of
each month and allocated only to the Sales Department.
These expenses must be available for payment selection but do not require an
invoice document.
For this demonstration, a new recurring journal batch is created so that manual
document numbers can be used.
Note: Recurring Journals will not post if the workdate is before the Posting
Date or after the Expiration Date.
Note: To record next month’s expenses, update the amount on the second
line and then post the journal. Because the Allocation % field is set to 100 for the
second line, the allocation always calculates based on the value entered in the
Amount field on the recurring journal line. Therefore, it does not have to be
updated.
You can use the recurring journal to record accruals. Income and expense accruals
are entered at the end of an accounting period to make sure that all income and
expenses for the period are included in the financial results. These accruals are
reversed out of the ledger the day after the entry is posted.
On February 1, 2014, CRONUS International Ltd. signed a new vehicle repairs and
maintenance contract for a fixed amount of 1,000.00 LCY, due on the twenty-fifth
of every month.
As the accountant, it is your responsibility to set up and post this expense starting
February 2014 with an expiration date of February 1, 2015. You also want a
document number to reflect an abbreviation of the expense (VRM) and the
number of the month.
Use the RECURRING general journal and DEFAULT batch to credit this expense to
the Cash account (2910) and allocate it to the company departments as follows:
You do not have to review the entries after you post them.
Detailed Steps
1. Use the Recurring Journal to set up the vehicle repair and
maintenance expense.
a. In the navigation pane, click Departments.
b. Click Financial Management, then click Periodic Activities,
then click General Ledger, and then click Recurring General
Journals.
c. On the General Journal Template List page, select the recurring
journal and then click OK.
d. In the Batch Name field, make sure that the DEFAULT batch is
selected.
e. In the Recurring Method field, click the drop-down list and
select F Fixed.
In Microsoft Dynamics NAV 2013, when an incorrect general journal is posted, the
posted ledger entries can be reversed in the corresponding registers. However, to
reverse an entry, the following must be true of the original entry:
After you reverse the entries, you can then post them in the same register.
When you are correcting entries, selecting the Correction check box affects the
way entries are posted.
To use the correction functionality, the following fields must show on the General
Journal page:
• Correction
• Debit Amount
• Credit Amount
Note: The Correction field cannot be added through the Choose Columns
function. It must be added through the design environment.
• The Amount field on the line must have the opposite sign of the
original, incorrect entry.
• Positive amounts in the Amount field are posted as a positive
amount in the Debit Amount field as usual.
• Negative amounts in the Amount field are posted as a positive
amount in the Credit Amount field as usual.
• The Amount field on the line must have the opposite sign of the
original, incorrect entry.
• Positive amounts in the Amount field are posted as a negative
amount in the Credit Amount field.
• Negative amounts in the Amount field are posted as a negative
amount in the Debit Amount field.
The Debit Amount and Credit Amount fields in the journal display the
difference between corrections and usual postings.
After you post a correcting entry in a journal, the effect on the account that is
used for posting is as follows:
Module Review
Module Review and Takeaways
General journals are the basis of many financial functions in Microsoft Dynamics
NAV 2013.
General journals can be posted with and without balancing lines and the user can
set up dimensions.
Recurring journals help users to record frequently posted entries and to allocate
expenses to various departments.
1. What type of journal does not have a balancing account on the line?
( ) Payment Journal
( ) General Journal
( ) Sales Journal
( ) Variable
( ) Reversing Variable
( ) Fixed
( ) Enter the same sign as the original, incorrect entry in the Amount field
on the line.
( ) Enter the opposite sign of the original, incorrect entry in the Amount
field on the line.
6. Which of the following results from posting a correction with the Correction
check box selected?
( ) The original entry and correcting entry are posted to opposite sides of
the account, one as a debit and the other as a credit.
( ) The original entry and the correcting entry are posted to the same
side of the account, either as debits or credits.
1. What type of journal does not have a balancing account on the line?
( ) Payment Journal
( ) General Journal
( ) Sales Journal
( ) Variable
( ) Reversing Variable
(√) Balance
( ) Fixed
( ) Enter the same sign as the original, incorrect entry in the Amount field
on the line.
(√) Enter the opposite sign of the original, incorrect entry in the Amount
field on the line.
6. Which of the following results from posting a correction with the Correction
check box selected?
( ) The original entry and correcting entry are posted to opposite sides of
the account, one as a debit and the other as a credit.
(√) The original entry and the correcting entry are posted to the same
side of the account, either as debits or credits.
Module Overview
Cash management in Microsoft Dynamics® NAV 2013 is used to manage the
company's bank accounts.
One of the main features of cash management is the Bank Account Card. The
Bank Account Card contains all the company's bank details. On the Bank Account
Card, users can perform the following:
Objectives
Additionally, if the user makes a manual or computer check payment, the system
posts an entry to the check ledger to record the check transaction and the current
status of the check.
Each bank account has its own card that contains different kinds of information.
On the bank account card, you enter information that is specific to the individual
bank account, and you can change this information, if this is necessary.
To access the Bank Account window from the navigation pane, click the
Departments button, click Financial Management, click Cash Management,
and then click Bank Accounts.
The Bank Account window provides an overview of all the bank accounts that are
created in Microsoft Dynamics NAV 2013. To create a new bank account, or
change an existing one, double-click the bank account to locate the bank account
card.
• General
• Communication
• Posting
• Transfer
General FastTab
The General FastTab contains all the general information about the bank where
the account is held, such as the name, address, and contact person.
In addition to this information, the General FastTab includes the following fields:
Communication FastTab
Posting FastTab
All the posting information is entered on the Posting FastTab of the bank account
card.
• Currency Code – The currency for the bank account. The following
rules apply for check payments and bank account currencies:
o If the Currency Code field of a bank account is blank, you can
only make check payments in local currency (LCY) for that
account. If a currency code is selected in this field, only use this
bank account to receive and make payments in the currency
selected in this field.
o If a currency code is not selected, you can receive payments by
using any currency including LCY. Non-check payments can use
any currency including LCY. You can only make check payments
in LCY.
• Last Check No. – If you are using checks, specify the last check
number that is used. The program updates this number every time
that a new check is printed.
• Transit No. – An alphanumeric code used to represent the bank
where the account is held.
• Last Statement No – The statement number of the last Bank Account
Statement reconciled in the program.
• Balance Last Statement – The statement ending balance of the last
Bank Account Statement reconciled in the program.
• Bank Acc. Posting Group – The posting group assigned to this bank
account. Microsoft Dynamics NAV 2013 uses this to post the related
G/L entries for each transaction by using the bank account.
Transfer FastTab
The Transfer FastTab contains the following fields that you must have to make
transfers to and from the bank account:
You can use the Bank Account Card ribbon for single-click access to several
functions and overviews. The following tabs are available in the ribbon:
• Home
• Actions
• Navigate
• Report
From the Home tab, you can view, edit, or create a new bank account.
The following single-click accesses are also available from the Home tab:
The Actions tab also provides access to the cash receipts journals and the
payment journals.
You can use the Navigate tab to display information about the balances and
transaction amounts for the bank account.
You can run the following reports on the Report tab and also access them from
the Home tab:
• List
• Detail Trial Balance
• Receivables-Payables
• Check Details
CRONUS International Ltd. recently opened a new account at the Super Krone
Bank in Denmark. As the accounting manager, it is your responsibility to set up
the bank account in Microsoft Dynamics NAV 2013 with the criteria shown in the
following table.
Field Value
Bank No. SK Bank - DK
City Vedbaek
Post Code DK-2950
Country/Region Code DK
Phone No. 46 75 75 34
Additionally, Linda Martin is the resource responsible for all interactions with this
bank. The bank's currency is Danish Kroner (DKK) and the bank must be assigned
to the Currencies posting group.
Close the Bank Account Card when you have finished the setup process.
Task 1: Create the bank account in the Bank Account Card window
Detailed Steps
1. Open the Bank Account Card and insert a new record.
a. In the Search box, enter Bank Accounts and then select the
related link.
b. Click New in the ribbon.
Customer Overview
To manage the total finances of the company, you must be able to manage
customer data. In Microsoft Dynamics NAV 2013, customer master data is
maintained in customer cards. The customer card is used for customers in
receivables management, financial management, and order management.
Customers Window
To access the Customers window from the navigation pane, click the
Departments button, click Financial Management, click Receivables, and then
click Customers.
The customer window provides an overview of the customers who are created in
Microsoft Dynamics NAV 2013. To create a new customer, or change an existing
one, double-click the customer for which you want to locate the customer card.
The Payments FastTab on the customer card is used to define how customer’s
payments are managed.
Analyzing Receivables
When you post transactions to customers in Microsoft Dynamics NAV 2013, the
following customer entries are created:
Customer entries provide more information about customers and sales business.
Customer ledger entries are posted entries from sales documents such as, sales
orders and sales invoices.
Note: The system shows open entries that have past their due date in bold,
italic and red.
To view the detail of a customer ledger entry, you can drill down on the amount
fields to the detailed customer ledger entries.
The detailed customer ledger entries store the actual amounts of the customer
transactions, such as an invoice. The customer ledger entries show the amounts as
FlowFields.
The Detailed Cust. Ledger Entries window figure shows the two detailed customer
ledger entries of one (applied) customer ledger entry.
Vendor Overview
To manage the total finances of the company, you must be able to manage
vendor data and vendor payments. This helps avoid penalty fees if there is a late
payment, maintain a good relationship with the vendors, and to receive a discount
if the company makes an early payment.
Vendor Window
To access the Vendors window from the navigation pane, click the Departments
button, click Financial Management, click Payables, and then click Vendors.
The vendor window shows the most relevant vendor information. You can use the
vendor card to view additional information, to create a new vendor, or to change
an existing vendor.
The Payments FastTab on the Vendor Card is used to define how payments to
vendors are managed.
Analyzing Payables
Vendor entries behave exactly like customer entries. Therefore, for more
information, refer to the topic “Analyzing Receivables” in this module.
The Cash Receipt Journal can be accessed from the following two areas on the
financial management menu:
• Cash Management
• Receivables
Payments to vendors are created and posted in the Payment Journal. You can
use the payment journal to quickly record and post handwritten checks. Computer
checks for open invoices can be entered manually, or by using the Suggest
Vendor Payments batch job.
The Payment Journal can be accessed from the following two areas on the
Financial Management menu:
• Cash Management
• Payables
When payments from customers are received, they are recorded in the cash
receipt journal. You can apply payments to open customer ledger entries, by using
the Apply Entries function.
The following fields are important when you enter and post a cash receipt:
Note: You can set up the balancing account type and balancing account
number on the journal batch. Then they are populated automatically on the journal
line when a payment is entered.
103005 8,269.04
n/a 25,000.00
Because the 25,000.00 LCY is not assigned to an invoice, Arnie decides to apply
the amount to the customer account without applying it to a particular invoice.
Demonstration Steps
The Bal. Account No. field is populated with the WWB-OPERATING bank
account. This is set up on the Bank batch.
a. Click Post.
b. Click Yes to post the journal lines.
c. Click OK.
d. Click OK to close the Cash Receipt Journal.
To review the posted Customer Ledger Entries for this payment, follow these
steps.
Entering Payments
You can use the payment journal to prepare and post payments to vendors. With
the Apply Entries function, you can apply payments to open vendor ledger
entries.
When a vendor is paid by using a handwritten check, you can enter a line in the
payment journal, by using the bank payment type Manual Check. This creates a
corresponding check ledger entry for the amount.
• Manually
• By using the Suggest Vendor Payments batch job
The following fields are important when you enter and post a payment:
The Document No. field represents the check number and is populated based on
the selections in the Bank Payment Type field.
When you process manual checks, the Bank Payment Type is set to Manual
Check, and the check number is entered in the Document No. field.
For computer checks, the Bank Payment Type is set to Computer Check and the
Document No. field is specified as follows:
The currency of the bank account can limit the currency of payments that are
made by using the bank account. The following table provides a summary of
currency restrictions for bank accounts.
Currency Code Checks are only printed for Only payment lines with
payment lines with the same the same currency code
currency code as the bank as the bank account
account. post.
Only payment lines with the same
currency code as the bank
account post.
April enters and posts these checks in the Payment Journal as manual checks.
a. Make sure that the Bal. Account No. field contains the WWB-
OPERATING bank account. This is set up on the Bank batch.
b. In the Bank Payment Type field, click the drop-down list and
select Manual Check.
To enter the second manual check and post the Payment Journal, follow these
steps.
Check No. 1201 and 1203 represent the manual checks posted to this bank
account.
On January 28, 2014, you receive a 154,251. 63 LCY payment from customer
30000, John Haddock Insurance Co. This payment is for the following invoices.
00-13 40,000.00
n/a 38,083.88
After you post it, review the posted customer ledger entries.
Detailed Steps
1. Open the Bank batch in the Cash Receipt Journal.
a. In the Search box, enter Cash Receipt Journals, and then select
the related links.
b. Make sure that the Bank batch is selected.
Detailed Steps
1. Apply the entries.
a. In the ribbon, click Apply Entries.
b. Locate and select the line for Document No. 00-10.
c. In the ribbon, click Set Applies-to ID.
d. Locate and select the line for Document No. 00-13.
e. Click the Amount to Apply field and then enter 40.000.00.
f. Verify that the Balance field at the bottom of the window
is -38,083.88.
g. Click OK.
Detailed Steps
1. Post the journal lines.
a. Click Post.
b. Click Yes to post the journal lines.
c. Click OK.
d. Close the Cash Receipt Journal window.
Detailed Steps
1. Open the Customer Card window and review the posted entries for
this payment.
a. On the Financial Management menu, click Receivables >
Customers.
b. Locate and select customer 30000, “John Haddock Insurance Co.”
The invoice for the check to vendor 60000 is still not received. But because it is
approaching the end of the month, the check must be recorded.
Task 1: Enter both manual checks in the Payment Journal, and apply
if this is possible.
Detailed Steps
1. Open the Payment Journal and apply if possible.
a. In the Search box, enter Payment Journals, and then select the
related link.
b. Make sure that the Bank batch is selected.
c. In the Posting Date field, enter 01/08/14.
d. In the Document Type field, click the drop-down list and select
Payment.
e. In the Document No. field, enter 1200.
f. In the Account Type field, click the drop-down list and select
Vendor.
g. In the Account No. field, enter 10000.
h. Click Apply Entries.
i. Click the line for Document No. 108018.
j. Click Set Applies-to ID.
k. Click OK.
Detailed Steps
1. Post the journal.
a. Click Post in the ribbon.
b. Click Yes to post the journal lines.
c. Click OK.
• Specific vendors
• Due Dates
• Vendor Priority
The Suggest Vendor Payments function can also be run to include payments for
which you can obtain a discount, and to summarize a suggested line for each
vendor, by dimension.
• Vendor
• Options
To open the batch job, click Suggest Vendor Payments in the Home tab in the
ribbon.
To suggest vendor payments for all vendors, do not set filters on this FastTab.
The Options FastTab is used to determine how the batch job is executed and
contains the following fields:
• Last Payment Date – The latest payment date that can appear on
the vendor ledger entries to be included in the batch job.
o Only entries that have a due date or a payment discount date
either before or on this date are included.
Note: If Bank Account is selected and the bank account contained in the Bal.
Account No. field has a currency code other than LCY, only those entries with the
same currency as the bank account are included in the batch job.
• For all open entries that are due on or before January 25, 2014.
• For vendors from Great Britain (GB).
• To search for payment discounts.
The checks are printed to create a single check for each vendor.
Demonstration Steps
1. Run the Suggest Vendor Payments batch job for all local vendors.
a. In the Search box, enter Payment Journals, and then select the
related link.
b. Make sure that the Bank batch is selected.
c. Click Suggest Vendor Payments.
d. Open the Options FastTab.
e. In the Last Payment Date field, enter 01/25/14.
f. Click the Find Payment Discounts check box.
g. In the Posting Date field, enter 01/15/14.
h. In the Starting Document No. field, enter CH001.
i. In the Bal. Account Type field, click the drop-down list and then
select Bank Account.
j. In the Bal. Account No. field, click the drop-down list and select
WWB-OPERATING and then click OK.
Until open entries are closed, they will appear in the Suggest Vendor Payment
process if they are within the set filters and parameters.
To prepare for the "Suggest Payments for a Single Vendor" demonstration, delete
all the Payment Journal lines again.
Use vendor priority when there are limited funds available to pay vendors.
Therefore, you must prioritize the order in which vendors are paid. Vendor priority
is set on the Payments FastTab of the Vendor Card.
This lesson includes a demonstration that will show how to use vendor priorities
that have specified available amounts. To provide a controlled demonstration
environment, only two vendors are included. Typically when you are using vendor
priority, specific vendors are not filtered.
April learns that vendor 10000 has Priority 1 and vendor 20000 has Priority 2. The
following table shows the ledger entries that are ready for payment this month.
Because of the limited funds, April also decides to search for available discounts
when she runs the Suggest Vendor Payments batch job.
Demonstration Steps
1. Run the Suggest Vendor Payments batch job by using vendor priority
and available amounts.
a. In the Search box, enter Payment Journals, and then select the
related link.
b. Click Suggest Vendor Payments.
c. In the Last Payment Date field, enter 01/31/14.
d. Click the Find Payment Discounts check box to insert a check
mark.
e. Select the Use Vendor Priority check box.
f. In the Available Amount (LCY) field, enter 100000.
g. In the Posting Date field, enter 01/24/14.
h. In the Bal. Account Type field, click the drop-down list and
select Bank Account.
i. In the Bal. Account No. field, click the drop-down list and select
WWB-OPERATING.
j. Click OK.
k. In the Bank Payment Type field, click the drop-down list and
select Computer Check.
The batch job suggests payments totaling less than 100,000.00 LCY. The following
table shows how Microsoft Dynamics NAV 2013 applied the vendor priority rules
to suggest the payments in the demonstration.
108025 -1,368.90 No
Note: The payments suggested by the batch job are listed by vendor order in
the Payment Journal. They are not listed in the order of vendor priority or in the
order they are suggested.
Do not delete the suggested vendor payment lines for vendors 10000 and 20000.
These entries are used in the Print Computer Checks demonstration.
On the twenty-fifth of each month, the Suggest Vendor Payments batch job is
run for vendor 30000, CoolWood Technologies, for any credit memos and all
payments that are expected by the end of the month. It is January 25, 2014, and
as the accounts payable coordinator, it is your responsibility to run the batch job
by using the following criteria:
• Print a single check for all invoices to a file that is named CWTChecks
012514.
• Post the checks.
Task 1: Set up and Run the Suggest Vendor Payments Batch Job
Detailed Steps
1. Run the Suggest Vendor Payments batch job.
a. In the Search box, enter Payment Journals, and then select the
related link.
b. Make sure that the Bank batch is selected.
c. Click Suggest Vendor Payments.
d. Enter the following information on the Options FastTab.
i. In the Last Payment Date field, enter 01/31/14.
ii. Make sure that the Find Payment Discounts check box
is selected.
iii. Select the Summarize per Vendor check box.
iv. In the Posting Date field, enter 01/24/14.
v. In the Starting Document No. field, enter CWT 012514.
vi. In the Bal. Account Type field, click the drop-down list
and select Bank Account.
Detailed Steps
1. Print the check as stated in the scenario.
a. Locate the line for vendor 30000.
b. In the Account No. field, right-click on 3000, and choose Filter
to this Value.
c. Click Print Check.
d. In the Options FastTab, do the following:
i. Make sure that the Bank Account field is set to WWB-
OPERATING.
ii. Make sure that the One Check per Vendor per
Document No. check box is not selected.
e. Click Print.
f. In the Check - Print window, click the Print to file check box to
insert a check mark.
g. Click OK.
h. In the Output File Name field, enter CWTChecks 012514.
i. Click OK.
j. Close the Microsoft Office Document Imaging window if it
appears.
Check printing is affected by the settings in the Document No. on the Suggest
Vendor Payments batch job and One Check per Vendor per Document fields
on the Print Check report.
You can print computer checks from the Payment Journal, by clicking Print Check
on the ribbon.
• Options
• Gen. Journal Line
The Options FastTab is used to determine how the batch job is executed and
contains the following fields:
• Bank Account – The bank account that the printed checks are drawn
from.
• Last Check No. – Automatically updated with the last check number
that is used for the selected bank account.
This field is not updated if the Last Check No. field is not populated
on the selected bank account's card.
• One Check per Vendor per Document No. – If this field is selected
only one check for each vendor, for each document number, is
printed.
• Reprint Checks – If printed checks have to be reprinted before you
post, click to insert a check mark to reprint the checks.
• Test Print – If this field is selected the checks are printed on blank
paper.
• Preprinted Stub – If this field is selected it will indicate that check
forms with preprinted stubs are used.
Scenario: In the "Use Vendor Priority and Available Amount" demonstration, April
ran the Suggest Vendor Payments batch job for vendors 10000 and 20000. April
now prints those checks by using the World Wide operating bank account. For
this demonstration, the checks are printed to a file that is named Checks 012514.
Demonstration Steps
The printed check lines are updated, and, depending on the printing setup, the
images of the printed checks can appear in the Microsoft Office Document
Imaging window.
In Microsoft Dynamics NAV 2013, the number of checks to print and the check
amount is determined by the following information:
• Selection of the One Check per Vendor per Document field in the
Check report.
• Contents of the Document No. field in the Payment Journal
window.
These fields affect one another, based on how entries are created in the following
ways:
When you are using the Suggest Vendor Payments batch job to populate the
payment journal lines, the system specifies a starting document number. The
following table shows the results when the batch job is run without selecting the
Summarize per Vendor check box.
If the Summarize per Vendor check box is selected on the Suggest Vendor
Payments batch job, the payment lines are populated as shown in the following
table.
Note: If you add a check mark in the New Doc. No. per Line check box and
enter a document number in the Starting Document No. field, each suggested
payment line has a different document number.
The following table shows how the One Check per Vendor per Document No.
field and Document No. field together affect how payment lines are created and
printed. These payment lines are created and printed based on the assumption
that the payment lines are in the same currency as the bank account contained in
the Bal. Account No. field.
Scenario: Now that all checks printed successfully, April can post the Payment
Journal.
The Payment Journal is still populated from the previous demonstrations with
the payment entries for vendors 10000, 20000, and 30000.
Demonstration Steps
Voiding Checks
Voiding checks is performed when handwritten checks are not cleared by the
bank, or when computer checks must be deleted or reprinted.
In Microsoft Dynamics NAV 2013, you can void checks two ways—financially void
posted checks and void unposted checks.
A posted check that must be voided is known as a financial void. When financially
voiding a check, make sure that all financial transactions that result from the
check payment are also canceled. In Microsoft Dynamics NAV 2013, users can
unapply and void the check and the transactions, void only the check, and enter a
date to use for the void.
In Microsoft Dynamics NAV 2013, financial voids are made from the Bank Account
Card.
Three weeks later, she receives a call from the accounts receivable clerk at London
Postmaster, stating that payment on invoice 108017 is past due. April explains to
the vendor that she sent check number 1204 three weeks ago, and that is must be
lost in the mail. April tells the vendor a new check will be sent by overnight
delivery.
April contacts Phyllis, the accounting manager at CRONUS International Ltd., and
asks Phyllis to financially void the check so that a new check can be issued.
As soon as the check is financially voided, Phyllis reviews the entries to verify that
all the transactions are successfully voided and then she notifies April that the
check can be reissued.
Demonstration Steps
1. Click Void Check in the Home tab of the ribbon. The Confirm
Financial Void window appears.
2. In the Void Date field, enter 02/21/14.
3. Verify that the Type of Void field has the Unapply and void check
option selected.
4. Click Yes.
Before you post a check, if you must delete or reprint a check, you can void it in
the Payment Journal. After you void a check, you can delete or reprint the
payment lines(s) from the journal.
1. In the Search box, enter Payment Journals, and select the related
link.
2. In the Batch Name field, click the drop-down list and select the
appropriate batch.
3. Click OK.
4. In the Payment Journal lines, click the line for the check to be voided.
5. Click Void Check.
6. Click Yes to the message that asks to void the check.
Now that the check is voided, you can delete or reprint it from the payment
journal.
To void all printed but unposted checks in a batch, follow these steps.
After all checks are voided, you can delete or reprint them from the payment
journal.
When you print checks, the Last Check No. in the Check report is updated
automatically with the last printed check number. When you reprint checks, make
sure that the correct check number will be used. For example, if the check number
must be 206, then enter 205 is in this field.
1. In the Search box, enter Payment Journals, and then select the
related link.
2. Select the relevant batch.
3. Click the line with the voided check.
4. Click Print Check.
5. Update the Last Check No.
6. Click to insert a check mark in the Reprint Checks check box.
7. Click Print.
In the “Enter and Post Manual Checks“ lab, a manual check payment of 8,132.00
LCY (number 1200) for invoice 108018, is posted to London Postmaster. On
January 29, 2014, the payables clerk at London Postmaster calls to inquire on the
status of the payment. You review the payments for this vendor and discover you
sent the check weeks ago. As a result, you are asked to resubmit payment.
As the accounting manager, you financially void the check in the World Wide
Bank operating account by using the following criteria:
The check is resubmitted by the accounts payable coordinator in the next check
run.
Detailed Steps
1. Open the Bank Account Card for the World Wide Bank operating
account, access the Check Ledger Entries, and void check number
1200 by using the information specified in the scenario.
a. In the Search box, enter Bank Accounts, and then select the
related link.
b. Locate and select bank WWB-OPERATING.
c. In the Navigate tab of the ribbon, click Check Ledger Entries.
d. Locate and select check number 1200.
e. In the Home tab of the ribbon, click Void Check.
f. In the Void Date field, enter 01/29/14.
g. Verify that the Type of Void field has the Unapply and void
check option selected.
h. Click Yes.
i. Close the Check Ledger Entries window.
Detailed Steps
1. Access the Bank Account Ledger Entries and review the check
entries of check number 1200.
a. In the Navigate tab of the ribbon, click Ledger Entries.
b. Set the Filter field to Document No.
c. In the Type to filter field, enter 1200 and press search.
d. Review the two check entries. The date for the line of the voided
check is 01/29/14.
e. Close the Bank Account Ledger Entries window.
On February 1 2014, invoice F8306 for office supplies for an amount of 800.00
(exclusive VAT), is received from vendor 40000. The invoice is posted and it is
approved for payment on February 10 2014. After you run the Suggest Vendor
Payments batch job for vendor 40000, the check is printed to a file that is named
VOID001.
Before the check is posted, the office manager informs you that there is still a
problem and this invoice cannot yet be paid. Void and delete the payment line.
Detailed Steps
1. Post the purchase invoice from vendor 61000.
a. In the Search box, enter Purchase Invoices, and then select the
related link.
b. In the Home tab, click New.
c. In the Buy-from Vendor No. field, enter 40000.
d. In the Posting Date field, enter 02/01/14.
e. In the Vendor Invoice No. field, enter F8306.
f. In the Lines FastTab, enter G/L Account in the Type field.
g. In the No. field, enter 8210.
h. In the Quantity field, enter 1.
i. In the Direct Unit Cost Excl. VAT field, enter 800.
j. In the Home tab, click Post.
k. Click Yes.
2. Open the Payment Journal window and run the Suggest Vendor
Payment batch by using the criteria that is specified in the scenario.
a. In the Search box, enter Payment Journals, and then select the
related link.
b. Click Suggest Vendor Payments.
c. In the Last Payment Date field, enter 02/20/14.
d. Make sure that the vendor priority fields are empty.
Detailed Steps
1. Open the Check report and print the check based on the criteria that
is specified in the scenario and void the check based on the criteria
that is specified in the scenario.
a. Click Print Check.
b. In the Bank Account field, click the drop-down list and then
select WWB-OPERATING.
c. Press TAB.
d. Make sure that the One Check per Vendor per Document No.
check box does not contain a check mark.
e. Click Print.
f. In the Check - Print window, click the Print to file check box to
insert a check mark.
g. Click OK.
h. In the Output File Name field, enter VOID001.
i. Note the check number.
j. Click Void Check.
k. Click Yes to void the check.
l. Click Delete in the ribbon.
m. Click Yes to delete the line.
n. Close the Payment Journal window.
Applying Payments
Users can apply payments to customer or vendor ledger entries when the
payment is processed and, or after a payment is processed without an application
to an entry.
Some methods to apply payments in the cash receipt journal or payment journal
include the following:
Application Methods
When users post payments without an application to an entry, the option that is
selected in the Application Method field on the Payments FastTab of the
customer's card, determines how the open payment is managed in the customer
ledger entries.
The two application method options are Manual and Apply to Oldest.
When the Manual option is selected, the payment that is posted to a customer's
or vendor’s account is not applied to an invoice and it remains an open payment
in the customer or vendor ledger entries.
Note: Most customers and vendors that are set up in Microsoft Dynamics
NAV use the Manual application method.
When the Apply to Oldest option is selected, the payment that is posted to the
customer’s or the vendor’s account is automatically applied to the customer’s or
the vendor’s oldest open entries.
The option selected does not affect how applications are made when users post a
payment. However, the user must understand how the application method affects
the unapplied entries.
You can use the Apply Customer Entries window to apply open customer ledger
entries for relevant customers. You can access this window from several areas in
Microsoft Dynamics NAV 2013. This includes the Cash Receipt Journal, where
you can apply payments to entries before they are posted, and the Customer
Ledger Entries, where you can apply payments that are posted and but not yet
applied.
To open the Apply Customer Entries window from these windows, click Apply
Entries in the ribbon.
The Apply Customer Entries window contains the following five areas:
• General header
• Ribbon
• Lines
• Balancing application fields
• FactBox
The General Header contains the applying entry information. This entry
determines whether the payment discounts, tolerances, and achieved gains or
losses on currencies are offered for the entry.
The lines area shows each open transaction and it is used to determine the entries
that will be applied to it. You can edit the following fields:
Underneath the lines are the following balancing fields that are used to track the
application:
• Appln. Currency
• Amount to Apply
• Pmt. Disc. Amount
• Rounding
• Applied Amount
• Available Amount
• Balance
The Home tab of the ribbon includes the following three options:
The FactBox on the Apply Customer Entries Card displays the Customer Ledger
Entry Details.
• Invoice 2808
• Invoice 2809
• Credit memo 2810
Phyllis applies and posts the payment using the cash receipt journal.
Demonstration Steps
Scenario: On January 31, 2014, a manual check payment for 70,860.66 LCY is sent
to vendor 30000, CoolWood Technologies. April, the accounts payable
coordinator, manually posts check number 1205 to the vendor account without
applying it to a particular invoice.
Some days later, she realizes that this payment must be applied to document
number 12345.
Demonstration Steps
The Balance field at the bottom of the window displays -35,092.16. This is the
remaining amount.
Close the Apply Vendor Entries and Vendor Ledger Entries windows.
Note: You can only unapply from the bottom up. Therefore, if an entry is
applied by more than one application entry, the last application entry must be
unapplied first.
To unapply a ledger entry from the Customer Ledger Entries window, follow these
steps.
Now you can apply the open amount to the correct entry by using the Apply
Customer Entries functionality.
Note: To view a complete overview of all the entries that resulted from a
transaction, use the Navigate function on the ribbon.
In late January, you receive a 50,778.50 LCY payment from customer 20000,
Selangorian Ltd., for Document No. 00-8. As you start to apply the payment, you
realize that a temporary employee incorrectly applied two credit memos to this
invoice.
After additional investigation, you realize that these credit memos are to be
applied to the invoices that correspond to the credit memo amounts. The
following table shows these credit memos and the invoices in the order in which
they are applied.
The payment for Document No. 00-8 is not posted in this lab.
Detailed Steps
1. Open the Customer Ledger Entries for customer 20000 and unapply
the entries.
a. On the navigation pane, click Departments > Financial
Management > Receivables, and then select Customers.
b. Locate and select customer 20000.
c. Click Ledger Entries.
d. Click the line for credit memo 104003. The amount is -1,145.33.
e. In the ribbon, click Unapply Entries.
f. Click Unapply.
g. Click Yes to unapply the entries.
h. Click OK to the message that the entry is unapplied.
Detailed Steps
1. Open the Apply Customer Entries window for credit memo 104002
and set it as the applying entry.
a. Click the line for Document No. 104002.
b. In the ribbon, click Apply Entries.
2. Set Document No. 103008 as the Applies-to ID and post the
application.
a. Click the line for invoice 103008.
b. Click Set Applies-to ID.
c. Click Post Application.
d. Click OK to post the application.
e. Click OK to the message that the application is posted.
3. Open the Apply Customer Entries window for credit memo 104003
and set it as the applying entry.
a. Click the line for Document No. 104003.
b. In the ribbon, click Apply Entries.
4. Set Document No. 103014 as the Applies-to ID and post the
Application.
a. Click the line for invoice 103014.
b. Click Set Applies-to ID.
c. Click Post Application.
d. Click OK to post the application.
e. Click OK to the message that the application is posted.
f. Close the Customer Ledger Entries.
Before you reverse an applied customer ledger entry, you must unapply the entry.
During the reversal process, you can create and post correcting entries with the
same document number and posting date as the original entry for each line in the
entry. After you reverse an entry, you can enter and post the correct entries
manually.
Because this invoice is already paid (on 1/17/14 with Document No. 2597) and it is
entered through a journal, it must be reversed.
Cassie, the accountant, wants you to make the reversing entry and then later she
will post the correction and refund the customer. Before you can reverse the entry,
you must unapply the payment.
Demonstration Steps
Module Review
Module Review and Takeaways
Receivables and payables management helps keep track of open balances and all
entries that are posted to customers and vendors.
1. When you post a manual or computer check, what is posted to record the
check transaction and the current status of the check?
2. On the Bank Account Card, what makes the program post the related G/L
entries for each transaction by using the bank account?
( ) Customer Card
6. What is not true about the Suggest Vendor Payments batch job?
( ) You can use the Suggest Vendor Payments batch job to summarize
payments by vendor and by dimension.
1. When you post a manual or computer check, what is posted to record the
check transaction and the current status of the check?
2. On the Bank Account Card, what makes the program post the related G/L
entries for each transaction by using the bank account?
6. What is not true about the Suggest Vendor Payments batch job?
(√) The Suggest Vendor Payments batch job always searches for a
payment discount.
( ) You can use the Suggest Vendor Payments batch job to summarize
payments by vendor and by dimension.
Module Overview
Cash management in Microsoft Dynamics® NAV 2013 is used to manage the
company's bank accounts.
Additionally, the bank account administration, and the users must become familiar
with the Bank Acc. Reconciliation window and the bank reconciliation process.
Understanding this process will help make sure that transactions are always
reconciled and that the user can follow the balances on the bank accounts.
Objectives
• Review the Bank Account Reconciliation window and the options for
populating the bank reconciliation lines.
• Show how to process a bank reconciliation.
Bank Reconciliation
Bank accounts maintained in Microsoft Dynamics NAV 2013 must be reconciled
regularly. The bank reconciliation feature is used to check the bank ledger entries
and the balance on the accounts against the statement from the bank.
This lesson will explain the Bank Account Reconciliation window. Additionally, it
will describe how to populate the bank reconciliation lines to prepare for the
"Complete a Bank Reconciliation" demonstration.
In Microsoft Dynamics NAV 2013, bank transactions are posted by using different
journal types, such as the cash receipt journal and the payment journal. A bank
transaction is posted as an open bank account ledger entry. This means that the
bank account ledger entry is not reconciled.
Bank reconciliations are used to compare the open bank account ledger entries
with the bank statement transactions.
When you run the reconciliation batch, for each open bank account ledger entry,
a reconciliation line is created. If all the suggested reconciliation lines match the
bank statement lines for the corresponding date range, the reconciliation can be
posted.
• Ribbon
• General FastTab
• Lines FastTab
• Bank Account No.: Specifies the bank account code of the account
to be reconciled.
• Statement No.: Specifies the number of the bank account statement.
After you enter a statement number and post the bank reconciliation,
Microsoft Dynamics NAV 2013 updates the statement number with
the next consecutive number the next time that the bank
reconciliation for this bank account is performed.
• Statement Date: Specifies the date on the bank account statement.
• Balance Last Statement: Specifies the ending balance that is shown
on the last bank statement that is used in the last posted bank
reconciliation for this bank account.
• Statement Ending Balance: Specifies the ending balance that is
shown on the bank statement.
Note: The reconciliation lines cannot be posted unless the amount in this field
agrees with the amount in the Total Balance field.
On the Lines FastTab, users perform the actual reconciliation by entering and
adjusting the posted transactions and the transactions on the bank statement
until they agree with one another.
When you use the Choose Column feature, the following fields are available in
the lines:
• Value Date: You can use this field to enter the official date when
funds are available and when interest is calculated on the amount on
the reconciliation line.
• Document No.: Shows the document number that is specified on the
original bank account ledger entry.
• Check No.: Shows the check number (specified as the document
number) used on the original check ledger entry.
• Applied Entries: Specifies whether the transaction on the bank's
statement on this reconciliation line is applied to one or more bank
account or check ledger entries.
By clicking Line in the Lines window, the Apply Entries function becomes
available. You use this function to apply reconciliation lines to one or more open
bank account ledger entries.
You can use the Bank Acc. Reconciliation ribbon for single-click access to several
functions and overviews. The Home tab contains the following buttons that are
used in the bank reconciliation process:
From the Navigate tab, the Card button is available. The Card button provides
access to the Bank Account Card.
Typically, the batch job is used to suggest open bank account and check ledger
entries in Microsoft Dynamics NAV 2013. Entries not in the system are entered
manually. They include, but are not limited to the following:
• Bank fees
• Interest earned and charged
• Transaction adjustments
All the transactions on the bank statement must be applied to the open bank
account or the open check ledger entries on the relevant bank account. The batch
job makes these applications automatically, whereas any manual entries must be
applied by using the Apply Entries button.
If you access the Suggest Bank Acc. Recon. Lines batch job from the Home tab
on the Bank Acc. Reconciliation window, it will include the following fields:
• Starting Date: Enter the starting posting date for the ledger entries
to be reconciled.
Leave this blank to have the batch job suggest all open or bank
account and check ledger entries that are not reconciled.
Best Practice: Leave the starting date open to include all open bank account
ledger entries until the ending date.
Note: Typically, the range that is specified in the Starting Date and Ending
Date fields is the same as the date range of the bank statement.
Scenario
April is the accounts payable assistant, and she is responsible for reconciling the
bank accounts every fourteen days.
In this demonstration, April finishes each step of the reconciliation process for the
WWB-OPERATING bank account for the period January 14 2014 through January
31 2014.
The first step of the bank reconciliation process is to fill in the bank reconciliation
header and lines.
Scenario: April opens the Bank Acc. Reconciliation window, fills in the header,
and then uses the Suggest Line function to populate the reconciliation lines.
The Statement No. and the Balance Last Statement fields are automatically
populated based on the information on the bank account card.
Note: If this is the first bank statement and reconciliation for the account,
manually enter the statement number. The program automatically fills in the
Statement No. and the Last Balance Statement for all future reconciliations.
You can use the Suggest Lines function to automatically populate the bank
reconciliation lines with transactions that are posted to the bank account, but are
not yet reconciled.
To fill in the bank reconciliation lines by using the suggest lines function, follow
these steps.
The suggested reconciliation lines consist of all open ledger entries on the bank
account for the period specified in the Suggest Bank Acc. Recon. Lines batch
job.
The Suggest Lines process also applied the reconciliation lines automatically to the
corresponding ledger entries. To verify the applications for each reconciliation
line, follow these steps.
After reviewing, close the Bank Account Ledger Entries or Check Ledger Entries
window.
• Checks that are sent to the vendors, but are not presented to the
bank.
• Cash or checks that are received and entered in the system but not
deposited and cleared in your bank account.
Scenario: After filling in the bank reconciliation header and lines, April compares
the bank statement to the bank reconciliation lines to find entries in Microsoft
Dynamics NAV 2013 that do not appear on the bank statement. All the amounts
on the statement are in local currency (LCY).
The following items are not removed from the bank reconciliation:
After you remove transactions that do not appear on the bank statement, add the
lines for bank-related transactions, such as fees or interest. Because these
transactions are not in the program, the following steps must be performed:
Scenario: April will now view the entries on the bank statement that do not
appear in Microsoft Dynamics NAV 2013. There is a 2,178.83 LCY entry for interest
charged. April must enter this interest charge in Microsoft Dynamics NAV 2013 to
continue with the reconciliation process.
• The Applied Amount and Applied Entries fields are zero because it
has not been applied to an entry in the Bank Account Ledger Entries.
• The Difference field on the line contains the amount entered in the
Statement Amount field because it is not applied to an entry.
• The Total Difference field at the bottom of the window also contains
the difference.
The bank reconciliation cannot be posted unless the contents of the Total
Difference field is either:
• Equal to zero (this is achieved when all lines are fully applied).
• The sum of the Statement Amounts from all reconciliation lines with
a type of Difference.
To achieve either of these results, the new transaction line must be transferred to
a general journal and posted.
The next step is to open the general journal and post the interest entry. To post
the line in the general journal, follow these steps.
The final step in posting the interest transaction is to apply the line in the bank
reconciliation to the posted general journal entry.
To apply the interest entry in the bank reconciliation, follow these steps.
Because the Total Difference field is now zero, the interest reconciliation line no
longer prevents the bank reconciliation from being posted.
Scenario: April notices that the bank recorded the two bank transfers dated
01/16/14 in the amounts of -3,070.45 LCY and -1,489.07 LCY as a single amount
of -4,559.52 LCY on 01/20/14. To make the bank reconciliation entry match the
bank statement, April creates a single bank transfer entry and then applies the
existing bank transfer entries.
Both the Statement Amount and Applied Amount fields are populated with -
4,559.52, the total of both transfer lines. The Difference field on the line and
Total Difference on the window are still 0.00. The reconciliation line will not stop
the bank reconciliation posting process.
Scenario: April also notices that the bank, by mistake, recorded the 121.57 LCY
payment for the Accounting Systems Hotline as a 211.57 LCY payment. Because
of this error, when the bank reconciliation lines are suggested, the 121.57 LCY
payment is suggested and it is applied correctly to the bank ledger entry that is
entered in the program. However, the Statement Ending Balance of -1,281,892.77
LCY is based on a withdrawal of the 211.57 LCY payment. Therefore the
reconciliation cannot be posted.
By removing the application, the ledger entry is still open when the bank
reconciliation is posted, similar to usual outstanding deposit entries.
The Total Difference field shows -121.57 LCY. If this amount is equal to the sum
of all lines where the Type field is Difference, the bank reconciliation can be
posted.
However, the bank reconciliation cannot post until the amount for the
reconciliation line is equal to the incorrect amount in the bank statement. You can
correct this by using either of the following methods:
For this demonstration, a line is added for the difference between the two
amounts.
To add a line for the difference between the two amounts, follow these steps.
With either method, there is still an open ledger entry for -121.57 LCY that must
be applied when the bank corrects the error, typically during the next bank
reconciliation.
When you record transaction differences with this method, the advantage is that
the correct G/L bank account balances are retained in the program.
The final step in the bank reconciliation process is posting. Before you post, you
must verify the following information in the Bank Acc. Reconciliation window,
and the following conditions must be met:
• The value in the Statement Ending Balance field must equal the
value in the Total Balance field.
• The Total Difference field equals the sum of all lines with the Type
field set to Difference.
You can confirm these requirements by printing the bank account statement test
report. To print this report, follow these steps.
Scenario: April finishes all the steps of the bank reconciliation process, and after
she runs the test report to verify all posting requirements, she posts the
reconciliation.
As soon as the reconciliation is posted, related bank account ledger entries are
modified as follows:
Scenario: After April posts the bank reconciliation, she reviews the bank account
entries and the posted statement.
1. In the navigation pane, click Cash Management, and then click Bank
Accounts.
2. Locate and select the WWB-OPERATING account.
3. In the Navigate tab of the ribbon, click Ledger Entries.
4. The following entries are marked as Open:
o The entries that are deleted from the Bank Acc. Reconciliation
window.
o The incorrect entry for -121.57 LCY that is unapplied.
o The entry dated 02/21/14. This entry is not part of this
reconciliation.
5. Close the Bank Account Ledger Entries window.
6. In the Navigate tab of the ribbon, click Statements.
7. Double-click the line for statement number 26.
8. Review the statement and then close the Bank Account Statement
and Bank Account Card windows.
Module Review
Module Review and Takeaways
A company must always be aware of its financial status and have its bank accounts
reconciled. The bank reconciliation process in Microsoft Dynamics NAV 2013
makes sure that a company’s transactions are always reconciled and that a user
can follow the balances on all the bank accounts.
1. Which of the following must occur before you post a bank reconciliation?
( ) The Total Difference field equals the sum of all lines with the Type
field set to Difference.
( ) The value in the Statement Ending Balance field must not equal the
value in the Total Balance field.
( ) The check mark in the Open field is removed for all posted entries.
1. Which of the following must occur before you post a bank reconciliation?
(√) The Total Difference field equals the sum of all lines with the Type
field set to Difference.
( ) The value in the Statement Ending Balance field must not equal the
value in the Total Balance field.
(√) The check mark in the Open field is removed for all posted entries.
4. On which two fields is the amount in the Difference field based on?
Module Overview
Granting payment discounts provides an incentive for customers to quickly pay
their outstanding amounts in full. Microsoft Dynamics NAV 2013 uses payment
terms to keep track of payment discounts that are given to customers or received
from vendors. Additionally, the payments are processed correctly by using the
payment discount amount. Setting up a payment discount includes selecting
between calculating a payment discount on amounts that both include or exclude
the value-added tax (VAT).
Differences can occur when the payment discount date passes, or when the
payment amount or payment discount amount does not match the charged
amount. Microsoft Dynamics NAV 2013 uses the payment discount tolerance and
the payment tolerance to process payment differences in a structured and
automated manner. This setup applies to both the receivables and the payables
application area.
Objectives
Payment discount amounts can also be calculated on credit memos. Then, users
can automatically reduce the payment discount given on invoices that the credit
memo is applied to.
A payment discount can be calculated on amounts that both exclude and include
VAT.
The setup is determined by the fields selected on the General Ledger Setup
page.
Note: On the General Ledger Setup page, the Pmt. Disc. Excl. VAT and the
Adjust for Payment Disc check boxes are mutually exclusive. This means that only
one can contain a check mark. However, both can be empty at the same time.
The general ledger accounts for payment discounts must be set up differently,
depending on whether payment discounts are calculated on amounts including or
excluding VAT:
You must first set up the Microsoft Dynamics NAV 2013 database to calculate
payment discount on amounts excluding VAT. To access the General Ledger
Setup page, follow these steps.
1. In the Search box, enter General Ledger Setup, and then click the
related link.
2. Expand the General FastTab.
Note: If journals are used to enter sales or purchase transactions and the
Pmt. Disc. Excl. VAT check box is selected an amount must be entered in the
Sales/Purch. (LCY) field in the journal. If an amount is not entered, the payment
discount is zero.
4. VAT Tolerance % - When the Pmt. Disc. Excl. VAT check box is
selected, you must also determine the maximum VAT difference that
is allowed to make sure that the VAT suggested on the invoice or the
order is the VAT calculated on the lowered base amount.
Note: Make sure that the percentage filled in in the VAT Tolerance % field is
the largest payment discount percentage.
For example, if you grant a payment discount of two percent to a customer, and
you only allow for a one percent VAT difference, the VAT suggested on the invoice
or the order will only differ one percent from the regular VAT.
If the invoice or the order is for a total amount of 100.00 local currencies (LCY), the
payment discount is 2.00 LCY, and the suggested VAT is 24.75 LCY, instead of the
expected 24.50 LCY.
Note: The VAT Tolerance % field is not available on the General Ledger
Setup page. You must add it through the Object Designer.
To set up the payment discount accounts for customer posting groups, follow
these steps.
1. In the Search box, enter Customer Posting Groups, and then click
the related link.
2. For each customer posting group that uses payment discounts, do the
following:
o In the Payment Disc. Debit Acc. field, click the drop-down list
and select the payment discount account. The general ledger
account is used to post granted payment discount amounts when
you are posting sales payments for the selected customer posting
group.
o In the Payment Disc. Credit Acc. field, click the drop-down list
and select the payment discount account. The general ledger
account is used to post reductions in payment discount amounts
when you are posting sales payments for the selected customer
posting groups.
To set up the payment discount accounts for vendor posting groups, follow these
steps.
1. In the Search box, enter Vendor Posting Groups, and then click the
related link.
2. For each customer posting group that uses the payment discounts, do
the following:
o In the Payment Disc. Debit Acc. field, click the drop-down list
and select the payment discount account. The general ledger
account is used to post reductions in payment discount amounts
To set up the program to recalculate tax amounts when payment discounts are
posted, follow these steps.
1. In the Search box, enter General Ledger Setup, and then click the
related link.
2. Expand the General FastTab.
3. Select the Adjust for Payment Disc. field to so that the feature
becomes available.
1. In the Search box, enter VAT Posting Setup, and then click the
related link.
2. Use the Choose Columns feature to add the Adjust for Payment
Discount field.
3. For each relevant VAT Posting Group combination, select the Adjust
for Payment Discount field.
To set up the payment discount accounts for general posting groups, follow these
steps.
1. In the Search box, enter General Posting Setup, and then click the
related link.
2. For each general posting group combination that uses a payment
discount, do the following:
o In the Sales Pmt. Disc. Debit Acc. field, click the drop-down list
and select the payment discount account. This is the general
ledger account that is used to post granted payment discount
amounts when you are posting payments for sales with the
selected combination of general business and product posting
groups.
o In the Sales Pmt. Disc. Credit Acc. field, click the drop-down list
and select the payment discount account. This is the general
ledger account that is used to post reductions in payment
discount amounts when you are posting payments for sales with
the selected combination of general business and product
posting groups.
1. In the Search box, enter Payment Terms, and then click the related
link.
The only payment term that is currently set up with discount capabilities is
1M(8D). This payment term is set up as follows:
• Payments are due within one month of the Document Date specified
on the posted invoice.
When payment discounts are granted for specific customers or are offered by
specified vendors, the appropriate Payment Terms Code is assigned to the
customer or vendor. Then, when an order or invoice is created the following
actions occur:
1. In the Search box, enter Customers, and then click the related link.
2. Locate and select the customer to assign a payment term.
3. Click Edit to open the Customer Card page.
4. Expand the Payments FastTab.
5. In the Payment Terms Code field, click the drop-down list and select
the relevant payment term.
1. In the Search box, enter Vendors, and then click the related link.
2. Locate and select the vendor to assign a payment term.
3. Click Edit to open the Vendor Card page.
4. Expand the Payments FastTab.
5. In the Payment Terms Code field, click the drop-down list and select
the relevant payment term.
6. Click OK to close the Vendor Card page.
Or, you can also assign payment terms on the order or the invoice header if the
Payment Terms Code is not assigned on the customer or vendor, and, or
different terms must be assigned to a specific sales order or invoice.
Microsoft Dynamics NAV 2013 checks the payment discount date of the applied
customer ledger entry or entries when users apply payments, refunds and credit
memos.
If the posting date of the application is the same or earlier than the payment
discount date of the applied entry, the remaining discount amount is subtracted
automatically from the remaining amount of the applied entry, if the applied
entry is fully applied.
You can adjust the Pmt. Discount Date and the Remaining Disc. Possible
discount fields on the customer ledger entries.
You can adjust the payment discount dates and the amounts when the invoice is
posted without discount information, the discount date passed and you approve
the date change, and the discount amount is calculated incorrectly.
Scenario: The Cannon Group PLC, customer 10000, in CRONUS International Ltd,
is set up with payment terms. These payment terms include a two percent
payment discount if it pays within eight days of the document date that is shown
on the invoices.
The full amount of invoice 103001 is 8,182.35 LCY. However, because The Cannon
Group PLC paid the invoice within eight days, it has taken the two percent
discount and reduced the payment by 163.65 LCY.
1. In the Search box, enter Cash Receipt Journals, and click the related
link.
2. Make sure that the BANK journal batch is selected.
3. In the Posting Date field, enter 01/26/14.
Notice that the Pmt. Disc. Amount field on the bottom of the window contains
the discount amount of -163.65 and the Balance field contains a zero balance.
This is the result of the discount being subtracted from the payment amount.
To review the posted customer ledger entries for this payment, follow these steps.
1. In the Search box, enter Customers, and then click the related link.
2. Locate and select customer 10000.
3. On the Navigate tab, click Ledger Entries.
On December 12, 2013, a payment of 651.15 LCY is sent. This payment is half of
the discounted amount (1,328.88 - 26.58 / 2 = 651.15). On December 17, 2013,
the remaining half of the payment is sent.
Arnie can successfully post both payments, by using the discount, because both
payments are received by December 17, 2013.
1. In the Search box, enter Cash Receipt Journals, and then click the
related link.
2. Make sure that the BANK journal batch is selected.
Note: If an invoice is not fully paid within the discount date period, the
discount is not available. If you still want to grant the discount, you can do the
following:
That same day, invoice 103002 is posted before the terms changed on the
Customer Card. On January 29, 2014, Arnie receives a payment of 6,832.34 LCY.
This payment is 139.44 LCY less than the invoice amount.
When Arnie reviews the invoice, he realizes that the correct payment terms are
not applied and that the difference is the two percent discount. Arnie changes the
discount fields on the customer ledger entries for this invoice and then posts the
discounted payment.
1. In the Search box, enter Customers, and then click the related link.
2. Locate and select customer 20000.
3. On the Navigate tab, click Ledger Entries.
4. On the line for invoice 103002, click the Pmt. Discount Date field.
5. Enter 01/29/14.
6. In the Remaining Pmt. Disc. Possible field, enter 139.44 LCY. Notice
that this amount must be entered in the same currency as the invoice.
7. Click OK to close the Customer Ledger Entries page.
1. In the Search box, enter Cash Receipt Journals, and then click the
related link.
2. Make sure that the BANK journal batch is selected.
3. In the Posting Date field, enter 01/29/14.
4. In the Document Type field, click the drop-down list and select
Payment.
5. In the Account Type field, click the drop-down list and select
Customer.
6. In the Account No. field, enter 20000.
7. In the Amount field, enter -6,832.34.
8. On the Navigate tab, click Apply Entries.
9. Select the line for invoice 103002.
10. On the Navigate tab, click Set Applies-to ID.
11. At the bottom of the page, notice the following:
o The Pmt. Disc. Amount field contains -139.44 LCY, the discount
amount.
o The Balance field contains a zero balance because the discount is
available within this posting date range.
12. Click OK to close the Apply Customer Entries window.
13. On the Actions tab, click Post.
14. Click Yes to post the journal lines.
15. Click OK.
16. Click OK to close the Cash Receipt Journal page.
When you apply a payment or refund to entries while the payment or refund is
posted, Microsoft Dynamics NAV 2013 automatically includes payment discount
information. This payment discount information is included on both invoice and
credit memo entries when it calculates the payment amount or the refund.
Note: When you are applying posted payments and refunds to entries with
payment discount amounts, it is recommended to apply one payment or refund
with each application of posted entries.
After posting the payment, he realizes that the payment is for invoice 103018. The
payment applies as follows:
Arnie also notices that the payment is two days past the discount date. He
discusses the situation with Phyllis, the accounting manager, who instructs him to
give the discount because this is one of the company's best customers.
Because CRONUS International Ltd. currently is not set up with payment tolerance
percentages, Arnie adjusts the Remaining Pmt. Disc. Possible amount to match
the discount taken and also changes the Pmt. Discount Date to January 25, 2014.
To save time, Arnie changes the payment discount values in the Apply Customer
Entries page and then applies and posts the application.
1. In the Search box, enter Cash Receipt Journals, and then click the
related link.
2. Make sure that the BANK journal batch is selected.
3. In the Posting Date field, enter 01/25/14.
4. In the Document Type field, click the drop-down list and select
Payment.
5. In the Account Type field, click the drop-down list and select
Customer.
6. In the Account No. field, enter 10000.
7. In the Amount field, enter -4,019.83.
8. On the Actions tab, click Post.
9. Click Yes to post the journal lines.
10. Click OK.
11. Click OK to close the Cash Receipt Journal page.
1. In the Search box, enter Customers, and then click the related link.
2. Locate and select customer 10000.
3. On the Navigate tab, click Ledger Entries.
4. On the line for invoice 103018, click the Pmt. Discount Date field,
and enter 01/25/14.
5. In the Remaining Pmt. Disc. Possible field, enter 82.05.
6. Select the payment line dated 01/25/14, for -4019.83.
7. On the Actions tab, click Apply Entries.
8. Click the line for Document No. 103018.
9. On the Navigate tab, click Set Applies-to ID.
10. At the bottom of the page, notice the following:
o The Pmt. Disc. Amount field contains the -82.05 LCY, the
discount amount.
o The Balance field contains a zero balance. This results from the
discount being adjusted to match the discount and for i available
within this posting date range.
11. On the Navigate tab, click Post Application.
12. Click OK.
13. Click OK to the message that the application posted.
14. Click OK to close the Customer Ledger Entries page.
When you are posting a credit memo with a payment discount amount that is
applied to an invoice, the Remaining Pmt. Disc Possible amount for the invoice
is reduced by the payment discount amount for the credit memo.
1. In the Search box, enter Customers, and then click the related link.
2. Locate and select the relevant customer.
3. On the Navigate tab, click Ledger Entries.
4. Select the line with the relevant credit memo.
5. On the Home tab, click Apply Entries.
6. Select the line with the relevant invoice.
7. On the Navigate tab, click Set Applies-to ID.
8. On the Navigate tab, click Post Application.
9. Click OK to apply the entries.
10. Click OK to the message that the entries are posted.
On January 8, 2014, the accounts payable clerk for customer 10000, contacts you.
The clerk wants to know whether the two percent discount can still be taken on
Document No. 00-9 if the payment is received on 01/09/14. This date is one day
past the payment discount date. You state that it is acceptable, because this is one
of your best customers.
On January 9, 2014, you receive a payment of 49,762.93 LCY. Adjust the payment
discount date while applying the payment.
Detailed Steps
1. Enter the information as it is specified in the scenario.
a. On the navigation pane, click Departments.
b. Click Financial Management, click Receivables, and then click
Cash Receipt Journals.
c. Make sure that the BANK journal batch is selected.
d. In the Posting Date field, enter 01/09/14.
e. In the Document Type field, click the drop-down list and select
Payment.
f. In the Account Type field, click the drop-down list and select
Customer.
g. In the Account No. field, enter 10000.
Afterward, you learn that the payment is for Document No. 00-16. Because the
payment is made on January 8, 2014, the full discount of 677.05 LCY is available.
However, a small error is made in the discount calculation and this has resulted in
the customer taking a larger discount. Because this is a good customer, adjust the
discount to match the amount taken: 678.00 LCY.
First, post the payment but do not apply it to an invoice. Then, adjust the discount
amount while applying the invoice to the payment.
Detailed Steps
1. Post the payment as it is specified in the scenario.
a. On the navigation pane, click Departments.
b. Click Financial Management, click Receivables, and then click
Cash Receipt Journals.
c. Make sure that the BANK journal batch is selected.
d. In the Posting Date field, enter 01/08/14.
e. In the Document Type field, click the drop-down list and select
Payment.
f. In the Account Type field, click the drop-down list and select
Customer.
g. In the Account No. field, enter 10000.
h. In the Amount field, enter -33,174.35.
i. On the Actions tab, click Post.
You can adjust the Pmt. Discount Date and the Remaining Pmt. Disc. Possible
discount fields on the vendor ledger entries.
You can adjust the payment discount dates and the amounts when the invoice is
posted without discount information, the discount date passed and the vendor
approves the date change, and when the discount amount is calculated
incorrectly.
Scenario: On January 25, 2014, a payment of 298.13 LCY is received from vendor
40000, Lewis Home Furniture, for invoice 55681. The invoice is for nine wooden
doors, item 70010.
This vendor has granted a two percent payment discount if the payment is
received within eight days of the invoice.
On February 1, 2014, April runs the Suggest Vendor Payments batch job for this
vendor with a last payment date of 02/15/14. The first time she runs the batch job,
she forgets to add a check mark in the Find Payment Discounts and the
payment is not suggested. She runs the batch job again and inserts a check mark
in the Find Payment Discounts check box. The discounted payment is suggested.
Note: In the General Ledger Setup page, the Pmt. Disc. Excl. VAT and
Adjust for Payment Discount check boxes are both cleared.
1. In the Search box, enter Purchase Invoices, and then click the
related link.
2. Click New.
3. In the Buy-from Vendor No. field, enter 40000.
4. In the Posting Date field, enter 01/25/14.
5. In the Vendor Invoice No. field, enter 55681.
6. Expand the Invoicing FastTab.
7. In the Payment Terms Code field, click the drop-down list and select
1M(8D).
8. Expand the Lines FastTab.
1. In the Search box, enter Payment Journal, and then click the related
link.
2. Make sure that the BANK journal batch is selected.
3. On the Navigate tab, click Suggest Vendor Payments.
4. Expand the Options FastTab.
5. In the Last Payment Date field, enter 02/15/14.
6. Make sure that the Find Payment Discounts check box is cleared.
7. In the Posting Date field, enter 02/01/14.
8. In the Bal. Account Type field, click the drop-down list and select
Bank Account.
9. In the Bal. Account No. field, click the drop-down list, select WWB-
OPERATING and then click OK.
10. In the Bank Payment Type field, click the drop-down list and then
select Computer Check.
11. Expand the Vendor FastTab.
12. In the No. filter, enter 40000.
13. Click OK to run the Suggest Vendor Payments batch job.
14. Notice that the payment is not suggested. Because the invoice is not
due until 02/25/10, it is not suggested because the Find Payment
Discount check box did not prompt Microsoft Dynamics NAV 2013
to search for any discounts before the due date.
15. Click OK to close the Payment Journal page.
1. In the Search box, enter Payment Journal, and then click the related
link.
2. Make sure that the BANK journal batch is selected.
3. On the Navigate tab, click Suggest Vendor Payments.
4. Expand the Options FastTab.
5. In the Last Payment Date field, enter 02/15/14.
6. Make sure that the Find Payment Discounts check box is selected.
14. In the Amount field, a payment amount for 292.17 LCY is suggested.
The original invoice amount is 298.13 LCY. The two percent discount
of 5.96 LCY is subtracted from the payment amount because the
Posting Date is within the payment discount range.
15. In the Applies-to Doc. No. field, click the drop-down list to open the
Apply Vendor Entries page.
16. Review the amount fields at the bottom of the page.
o Amount to Apply – Contains the full remaining amount of the
invoice, without considering the payment discount.
o Pmt. Discount Amount – When the payment is made within the
discount period, the remaining discount amount will be shown
here.
o Applied Amount – The amount that will be applied to the
journal line, after the journal is posted.
o Available Amount – The amount that is filled in on the journal
line and to which the maximum can be applied.
o Balance – The difference between the applied amount and the
available amount.
17. Click OK to close the Apply Vendor Entries page.
18. Delete the suggested payment journal line.
19. Click OK to close the Payment Journal page.
Scenario: On February 15, 2014, April runs the Suggest Vendor Payments batch
job to find discounts for all payments due on or before February 28, 2014.
She reviews the payment for vendor 40000. Because the payment is not suggested
within the payment discount date, the discount is not applied to the payment.
1. In the Search box, enter Payment Journals, and then click the
related link.
2. Make sure that the BANK journal batch is selected.
3. On the Navigate tab, click Suggest Vendor Payments.
4. Expand the Options FastTab.
5. In the Last Payment Date field, enter 02/28/14.
6. Make sure that the Find Payment Discounts check box is selected.
7. In the Posting Date field, enter 02/15/14.
8. In the Bal. Account Type field, click the drop-down list and select
Bank Account.
9. In the Bal. Account No. field, click the drop-down list, select WWB-
OPERATING and then click OK.
10. In the Bank Payment Type field, click the drop-down list and then
select Computer Check.
11. Expand the Vendor FastTab.
12. In the No. filter, enter 40000.
13. Click OK to run the Suggest Vendor Payments batch job.
14. In the Amount field, a payment amount for 298.13 LCY is suggested.
This is the full amount of the invoice.
15. In the Applies-to Doc. No. field, click the drop-down list to open the
Apply Vendor Entries page.
16. Review the amount fields at the bottom of the page.
17. Click OK to close the Apply Vendor Entries page.
18. Delete the suggested payment journal line.
19. Click OK to close the Payment Journal page.
She changes the payment discount date on the vendor ledger entry and then she
runs the Suggest Vendor Payment batch job again.
1. In the Search box, enter Vendors, and then click the related link.
2. Locate and select vendor 40000.
3. On the Navigate tab, click Ledger Entries.
4. On the invoice line, in the Pmt. Discount Date field, enter 02/03/14.
5. Click OK to close the Vendor Ledger Entries page.
To run the Suggest Vendor Payments batch job, follow these steps.
1. In the Search box, enter Payment Journal, and then click the related
link.
2. Make sure that the BANK journal batch is selected.
3. On the Navigate tab, click Suggest Vendor Payments.
4. Expand the Options FastTab.
5. In the Last Payment Date field, enter 02/28/14.
6. Make sure that the Find Payment Discounts check box is selected.
7. In the Posting Date field, enter 02/03/14.
8. In the Bal. Account Type field, click the drop-down list and select
Bank Account.
9. In the Bal. Account No. field, click the drop-down list, select WWB-
OPERATING and then click OK.
10. In the Bank Payment Type field, click the drop-down list and then
select Computer Check.
11. Expand the Vendor FastTab.
12. In the No. filter, enter 40000.
13. Click OK to run the Suggest Vendor Payments batch job.
14. In the Amount field, a 293.36 LCY payment is suggested. The original
invoice amount is 298.13 LCY. The two percent discount of 4.77 LCY is
subtracted from the payment amount because the Posting Date is
within the payment discount range.
15. Delete the suggested payment journal line.
16. Click OK to close the Payment Journal page.
• Post the payments with a remaining amount. With this option, you
must close the remaining amount using other methods, such as
posting an adjustment and, or by contacting the customer for
additional payment.
• Set up payment tolerances to close entries where there is a difference
between the amount owed and the amount paid. With this option,
parameters of acceptable differences are used to post the amounts to
G/L accounts.
For accounts payables, payment tolerances are used to make payments to vendors
that have a slightly different invoice amount.
In Microsoft Dynamics NAV 2013, there are two types of payment tolerance:
As a default, a payment tolerance can be used for all customers. This default can
be changed for a specific customer.
1. In the Search box, enter Customers, and then click the related link.
2. Locate and select the customer to disable the payment tolerance, and
then click Edit.
3. Expand the Payments FastTab.
4. Select the Block Payment Tolerance check box.
5. You will receive a message that asks whether the payment tolerance is
to be removed from all open entries.
o Click Yes to remove the payment tolerance on open entries and
to restrict it from future invoices.
o Click No to maintain the payment tolerance on open entries but
restrict it from future invoices.
6. Click OK to close the Customer Card page.
Note: The Block Payment Tolerance check box applies to both the payment
discount tolerance and the payment tolerance.
As a default, a payment tolerance can be used for all vendors. This default can be
changed on the Vendor Card.
1. In the Search box, enter Vendors, and then click the related link.
2. Locate and select the vendor to make the payment tolerance
unavailable, and then click Edit.
3. Expand the Payments FastTab.
4. Select the Block Payment Tolerance check box.
5. You will receive a message that asks whether the payment tolerance is
to be removed from all open entries.
o Click Yes to remove the payment tolerance on open entries and
to restrict it from future invoices.
o Click No to maintain the payment tolerance on open entries but
restrict it from future invoices.
6. Click OK to close the Vendor Card page.
Note: The Block Payment Tolerance check box is applied to both the
payment discount tolerance and the payment tolerance.
To post a tolerance to a G/L account that differs from the usual payment discount
account, the accounts must be created in the Chart of Accounts and set up on the
following:
Note: The payment tolerance accounts can be used for both the payment
discount tolerance and the payment tolerance.
To set up the payment discount accounts for customer posting groups, follow
these steps.
1. In the Search box, enter Customer Posting Groups, and then click
the related link.
2. For each customer posting group that uses payment discounts, do the
following:
o In the Payment Tolerance Debit Acc. field, click the drop-down
list and select the payment tolerance account. The general ledger
account is used to post the payment tolerance when you post
payments for sales.
o In the Payment Tolerance Credit Acc. field, click the drop-down
list and select the payment tolerance account. The general ledger
account is used to post the payment tolerance when you post
payments for sales.
To set up the payment discount accounts for vendor posting groups, follow these
steps.
1. In the Search box, enter Vendor Posting Groups, and then click the
related link.
2. For each customer posting group that uses payment discounts, do the
following:
To set up the payment discount accounts for general posting groups, follow these
steps.
1. In the Search box, enter General Posting Setup, and then click the
related link.
2. For each general posting group combination that uses payment
discount, do the following:
o In the Sales Pmt. Tol. Debit Acc. field, click the drop-down list
and select the payment tolerance account. This is the general
ledger account that is used to post the payment tolerance when
you post payments for sales with this particular combination of
business group and product group.
o In the Sales Pmt. Tol. Credit Acc. field, click the drop-down list
and select the payment tolerance account. This is the general
ledger account that is used to post the payment tolerance when
you post payments for sales with this particular combination of
business group and product group.
o In the Purch. Pmt. Tol. Debit Acc. field, click the drop-down list
and select the payment tolerance account. This is the general
ledger account that is used to post the payment tolerance when
you post payments for purchases with this particular combination
of business group and product group.
o In the Purch. Pmt. Tol. Credit Acc. field, click the drop-down list
and select the payment tolerance account. This is the general
ledger account that is used to post the payment tolerance when
you post payments for purchases with this particular combination
of business group and product group.
1. In the Search box, enter General Ledger Setup, and then click the
related link.
2. Expand the Application FastTab.
1. In the Search box, enter General Ledger Setup, and then click the
related link.
2. Expand the Application FastTab.
3. Select the Pmt. Disc. Tolerance Warning check box.
You can adjust the Pmt. Disc. Tolerance Date field on the customer and vendor
ledger entries:
You can adjust the payment discount tolerance dates when the following actions
occur:
Note: You can change the Pmt. Discount Date or the Pmt. Disc. Tolerance
Date field.
When you change the Pmt. Discount Date, the discount amount will be
automatically subtracted and it will be posted on the Payment Discount
Accounts.
When you change the Pmt. Disc. Tolerance Date, the discount amounts must be
manually subtracted. A payment discount warning can appear, depending on the
setup. Additionally, the discount amount will be posted on the Payment Tolerance
Accounts or on the Payment Discounts Accounts, depending on the setup on the
General Ledger Setup page.
Scenario: On January 10, 2014, Arnie, the Account Receivable assistant, receives a
payment of 49,762.93 LCY from The Cannon Group PLC, for invoice 00-9.
However, the invoiced amount is 50,778.50 LCY.
1. In the Search box, enter Cash Receipt Journals, and then click the
related link.
2. Make sure that the BANK journal batch is selected.
3. In the Posting Date field, enter 01/10/14.
4. In the Document Type field, click the drop-down list and select
Payment.
5. In the Account Type field, click the drop-down list and select
Customer.
6. In the Account No. field, enter 10000.
7. In the Amount field, enter -49,762.93.
8. On the Actions tab, click Apply Entries.
9. Select the line for Document No. 00-9.
10. On the Navigate tab, click Set Applies-to ID.
Notice that the Balance field at the bottom of the window contains a difference
of -1,015.57 LCY.
The Payment Discount Tolerance Warning page appears, with the options of
accepting or declining the late payment discount.
12. To accept the late payment discount, select the Post as Payment
Discount Tolerance option.
13. Click Yes to close the Payment Discount Tolerance Warning page
14. On the Actions tab, click Post.
15. Click Yes to post the journal lines.
16. Click OK.
17. Click OK to close the Cash Receipt Journal page.
Scenario: As of February 5, 2014, the invoice for vendor 40000 is not yet paid.
April contacts the vendor who guarantees her that it is fine to take the discount.
Instead of adjusting the discount fields, and because a payment tolerance is set
up, April suggests vendor payments and then changes the amount to the
discounted amount of 292,16 LCY.
1. In the Search box, enter Payment Journal, and then click the related
link.
2. Make sure that the BANK journal batch is selected.
3. On the Navigate tab, click Suggest Vendor Payments.
4. Expand the Options FastTab.
5. In the Last Payment Date field, enter 02/25/14.
6. Make sure that the Find Payment Discounts check box is selected.
7. In the Posting Date field, enter 02/05/14.
8. In the Bal. Account Type field, click the drop-down list and select
Bank Account.
9. In the Bal. Account No. field, click the drop-down list, select WWB-
OPERATING and then click OK.
10. In the Bank Payment Type field, click the drop-down list and then
select Computer Check.
11. Expand the Vendor FastTab.
12. In the No. filter, enter 40000.
13. Click OK to run the Suggest Vendor Payments batch job.
14. In the Amount field, a payment for 296.93 LCY is suggested. This is
the full amount of the invoice. Change the amount to 292.16 LCY and
press TAB or ENTER.
15. To accept the late payment discount, select the Post as Payment
Discount Tolerance option.
16. Click Yes to close the Payment Discount Tolerance Warning page.
17. When the payment is posted, the invoice and the payment are closed
without remaining amounts. However, for the following
demonstrations, delete the payment journal line.
18. Click OK to close the Payment Journal page.
1. In the Search box, enter General Ledger Setup, and then click the
related link.
2. Expand the Application FastTab.
3. Payment Tolerance Warning – If this field is selected, the system
generates a warning message when an application is made and a
balance is within the allowed payment tolerance amount. You can
accept or decline the payment tolerance. If payment tolerances are
usually allowed, clear this check box. Microsoft Dynamics NAV 2013
will then automatically post the application as a payment tolerance.
4. Payment Tolerance Posting – Identifies the G/L accounts to post a
payment tolerance. There are two selections for posting:
o Payment Tolerance Accounts –The payment tolerance is posted
to a special G/L account set up for a payment tolerance.
o Payment Discount Accounts – The payment tolerance is posted
as a payment discount.
If you leave this field blank, the parameters are applicable for the local currency.
The General Ledger Setup page only displays the payment tolerance parameters
set up for the local currency. The payment tolerance parameters set up for the
foreign currencies can be viewed on the Currencies page.
1. In the Search box, enter Currencies, and then click the related link.
2. The Payment Tolerance % and Max. Payment Tolerance Amount
fields are available, but they can only be edited through the Change
Payment Tolerance batch job. (You can access this through the
Ribbon.)
Your company has decided to give a one percent payment tolerance for payment
amounts. However, the tolerance cannot exceed 50.00 LCY.
1. In the Search box, enter General Ledger Setup, and then click the
related link.
2. Expand the Application FastTab.
3. Select the Payment Tolerance Warning check box.
4. Make sure that the Payment Tolerance Posting field is set to
Payment Tolerance Accounts.
5. On the Actions tab, click Change Payment Tolerance.
6. Clear the All Currencies check box.
7. Leave the Currency Code field blank.
8. In the Payment Tolerance % field, enter 1.
9. In the Max. Pmt. Tolerance Amount field, enter 50.
10. Click OK to run the batch job.
11. Click Yes to update the change to existing customer and vendor
ledger entries.
12. Notice that the Payment Tolerance % and Max. Pmt. Tolerance
Amount fields on the General Ledger Setup page contain the values
entered in the Change Payment Tolerance batch job.
13. Click OK to close the General Ledger Setup page.
The Chief Financial Officer (CFO) at CRONUS International Ltd. discovered that the
existing tolerance is too strict and he or she created too many open balances for
amounts that are not significant. As the accounting manager, you are asked to
change the existing tolerance to allow a three percent overpayment, and, or
underpayment of invoices, with a maximum tolerance of 200.00 LCY.
The other tolerance parameters do not have to change. But all open ledger entries
must be updated to reflect the new tolerance.
Detailed Steps
1. Set Up a Payment Tolerance in General Ledger Setup.
a. On the navigation pane, click Departments.
b. Click Administration, and then click Application Setup.
c. On the Application Setup page, click Financial Management,
click Finance, and then click General Ledger Setup.
d. Expand the Application FastTab.
e. Make sure that the Payment Tolerance Warning check box is
selected.
f. On the Actions tab, click Change Payment Tolerance.
g. Clear the All Currencies check box.
h. Leave the Currency Code field blank.
i. In the Payment Tolerance % field, enter 3.
j. In the Max. Pmt. Tolerance Amount field, enter 200.
k. Click OK to run the batch job.
l. Click Yes to update the change to existing customer and vendor
ledger entries.
Notice that the Payment Tolerance % and Max. Pmt. Tolerance Amount fields
on the General Ledger Setup page contain the values entered in the Change
Payment Tolerance batch job.
You can adjust the Max. Payment Tolerance field on the customer and vendor
ledger entries.
You can adjust the payment tolerance amount, when no payment tolerance
parameters are set up and you approve the change for the amount. You can also
adjust the payment tolerance amount when the payment discount is calculated
incorrectly and you approve the change for the amount, and when the payment
tolerance parameters are set up and the payment amount differs from the
parameters, and you approve the change for the amount.
Note: When the paid discount amount is incorrect, you can change the
Remaining Pmt. Disc. Possible or the Max. Payment Tolerance field.
When you change the Remaining Pmt. Disc. Possible the discount amount will be
automatically subtracted, and the discount amount will be posted on the Payment
Discount Accounts.
When you change the Max. Payment Tolerance field, the difference in the
discount amount must be manually subtracted. A payment warning can appear,
depending on the setup, and the difference in the discount amount will be posted
on the Payment Tolerance Accounts or the Payment Discount Accounts,
depending on the setup on the General Ledger Setup page.
Scenario: On January 30, 2014, Arnie receives a payment for 63,470.00 LCY from
The Cannon Group PLC, for invoice 00-11. However, the invoice amount is
63,473.13 LCY.
Although a discount of 1,269.46 LCY existed, the discount due date, and the
discount tolerance due date have expired. Arnie realizes that the difference in the
payment amount is an error. However, because CRONUS International Ltd. set up
a three percent payment tolerance, this payment difference is acceptable.
1. In the Search box, enter Cash Receipt Journals, and then click the
related link.
2. Make sure that the BANK journal batch is selected.
3. In the Posting Date field, enter 01/30/14.
Notice that the Balance field at the bottom of the page contains the 3.13 LCY
difference.
Arnie reviews the possible discount amounts and notices that, although the
payment is received within the discount period, the amount is calculated
incorrectly.
The Cannon Group PLC has taken a two and one quarter percent discount instead
of two percent. However, because CRONUS International Ltd. has set up a three
percent payment tolerance, this discount is acceptable.
1. In the Search box, enter Cash Receipt Journals, and then click the
related link.
2. Make sure that the BANK journal batch is selected.
3. In the Posting Date field, enter 01/07/14.
4. In the Document Type field, click the drop-down list and then select
Payment.
5. In the Account Type field, click the drop-down list and then select
Customer.
6. In the Account No. field, enter 10000.
7. In the Amount field, enter -66,181.31.
8. On the Actions tab, click Apply Entries.
9. Select the line for Document No. 00-6.
10. On the Navigate tab, click Set Applies-to ID.
Notice that the Balance field at the bottom of the page contains the -1,523.36
LCY difference.
Then, the access discount amount is handled as a regular discount amount and it is
automatically subtracted from the initial amount of the invoice, and it posts on the
Payment Discount Accounts.
Scenario: On January 30, 2014, Arnie receives a payment of 116,564.07 LCY from
the John Haddock Insurance Co. for the following invoices:
When Arnie posts the payment, he realizes that the payment is 2.97 LCY less than
the total of the two invoices. However, because this is within the payment
tolerance range, he continues with posting to close the entries.
1. In the Search box, enter Cash Receipt Journals, and then click the
related link.
2. Make sure that the BANK journal batch is selected.
3. In the Posting Date field, enter 01/30/14.
4. In the Document Type field, click the drop-down list and then select
Payment.
5. In the Account Type field, click the drop-down list and then select
Customer.
6. In the Account No. field, enter 30000.
7. In the Amount field, enter -116,564.07.
8. On the Actions tab, click Apply Entries.
9. Select the line for Document No. 00-13.
10. On the Navigate tab, click Set Applies-to ID.
11. Select the line for Document No. 00-15.
12. On the Navigate tab, click Set Applies-to ID.
Notice that the Balance field at the bottom of the window contains
the 2.97 LCY difference.
14. To accept the tolerance, select the Post the Balance as Payment
Tolerance option.
15. Click OK.
16. On the Actions tab, click Post.
17. Click Yes to post the journal lines.
4. Click the payment line and in the Home tab, click Detailed Ledger
Entries.
5. Review the entry lines:
o The first line is the Initial Entry of the payment and it contains the
payment amount.
o The second line is the Payment Tolerance and it contains the
accepted payment tolerance amount.
o The third line is the Application and it contains the net amount of
the two lines that match the actual net amount of the two
invoices.
6. Close the Customer Ledger Entries window.
If the difference is not posted as a payment tolerance, then the 2.97 LCY balance
is displayed as a remaining amount on the line for invoice 00-15 because it is the
last invoice applied. Accept the tolerance to close the invoices and payment.
On January 21, 2014, the Suggest Vendor Payments report is run for this vendor.
You check the amount to make sure that the discount is taken and you find that it
is not set up on the invoice. Because the discount amount is within the tolerance,
you decide to change the amount on the Payment Journal and accept the
tolerance.
1. In the Search box, enter Payment Journals, and then click the
related link.
2. Make sure that the BANK journal batch is selected.
3. On the Navigate tab, click Suggest Vendor Payments.
4. Expand the Options FastTab.
5. In the Last Payment Date field, enter 01/31/14.
6. Make sure that the Find Payment Discounts check box is selected.
7. In the Posting Date field, enter 01/20/14.
8. In the Bal. Account Type field, click the drop-down list and then
select Bank Account.
9. In the Bal. Account No. field, click the drop-down list and then select
WWB-OPERATING.
10. In the Bank Payment Type field, click the drop-down list and then
select Computer Check.
11. Expand the Vendor FastTab.
12. In the No. filter, enter 30000.
13. Click OK.
Notice that the payment is for the full amount of the invoice:
19,500.00 LCY.
16. To accept the tolerance, select the Post the Balance as Payment
Tolerance option.
17. Click OK.
On January 7, 2014, you receive a payment of 37,226.99 LCY for the invoice, and
this payment is within the discount period. Therefore, the discount amount taken
(856.89 LCY) is larger than the granted amount (761.68 LCY).
Although the underpayment falls within the acceptable tolerance range, the
accounting manager decides that the customer is responsible for this difference
because the customer used a two and one quarter percent discount instead of the
allowed two percent.
Therefore, you have to post the payment with a remaining amount. Later, you will
contact the customer for an additional payment and remind the customer of the
discount terms.
Detailed Steps
1. For customer 20000, update the payment discount date and the
amount as it is specified in the scenario.
a. On the Navigation Pane, click Departments.
b. Click Financial Management, click Receivables, and then click
Customers.
c. Select customer 20000.
d. On the Navigate tab, click Ledger Entries.
Notice that the Balance field at the bottom of the page contains a difference of
856.89 LCY.
On January 21, 2014, you run the Suggest Vendor Payments batch job.
However, you are notified that the discount is actually two and one-half percent,
not two percent. You adjust the suggested payment amount from 15,529.08 LCY
to the correct amount of 15,449.85 LCY and accept the payment tolerance
warning.
Detailed Steps
1. Process the vendor payment as it is specified in the scenario.
a. On the Navigation Pane, click the Departments button, click
Financial Management, click Payables, and then select
Payment Journals.
b. Make sure that the BANK journal batch is selected.
c. On the Navigate tab, click Suggest Vendor Payments.
d. Expand the Options FastTab.
e. In the Last Payment Date field, enter 01/31/14.
f. Make sure that the Find Payment Discounts check box is
selected.
g. In the Posting Date field, enter 01/21/14.
h. In the Bal. Account Type field, click the drop-down list and then
select Bank Account.
i. In the Bal. Account No. field, click the drop-down list and then
select WWB-OPERATING.
j. In the Bank Payment Type field, click the drop-down list and
then select Computer Check.
The Entry Types for the tolerance entries include the following:
If Microsoft Dynamics NAV 2013 is set up to adjust VAT amounts for payment
discounts, the VAT amounts are also adjusted for any tolerance that is allowed.
1. In the Search box, enter Customers, and then click the related link.
2. Locate and select customer 10000.
3. On the Navigate tab, click Ledger Entries.
4. Locate and select the ledger entry for invoice 00-9. The Remaining
Amount is zero.
5. On the Navigate tab, click Applied Entries.
If the difference is not posted as a discount tolerance, then the 1,015.57 LCY
balance is displayed as a remaining amount on the invoice line. Accept the late
payment discount to close the invoice and payment.
1. In the Search box, enter Customers, and then click the related link.
2. Locate and select the customer to review.
3. On the Navigate tab, click Statistics.
4. Expand the Sales FastTab. The fields related to discounts and
tolerances are as follows:
o Pmt. Discounts (LCY) – Contains the LCY value of the discounts
that are taken on or before the Pmt. Discount Date.
o Pmt. Disc. Tol. (LCY) – Contains the LCY value of the discounts
that are taken after the Pmt. Discount Date but within the
payment discount grace period.
o Pmt. Tolerances (LCY) – Contains the LCY value of
underpayments and overpayments that are accepted in relation
to the customer.
5. Click Close to close the Customer Statistics window.
Module Review
Module Review and Takeaways
You can use a payment discount in sales and purchases to keep track of granted
payment discounts and to automatically process payments with discounts.
You can use a payment discount tolerance and a payment tolerance in sales or
purchases to set up tolerance parameters to automatically process payment
differences. However, you can still intervene and decide on the most suitable
approach based on each case.
1. On the General Ledger Setup window, what check box must contain a check
mark so that you can enter payment discount accounts in the Customer
Posting Groups window?
2. On the General Ledger Setup window, what check box must contain a check
mark so that you can enter payment discount accounts in the General Posting
Setup window?
( ) Enter 10D in the Discount Date Calculation field, and .03 in the
Discount % Field.
( ) Enter D10 in the Discount Date Calculation field, and .03 in the
Discount % Field.
1. On the General Ledger Setup window, what check box must contain a check
mark so that you can enter payment discount accounts in the Customer
Posting Groups window?
2. On the General Ledger Setup window, what check box must contain a check
mark so that you can enter payment discount accounts in the General Posting
Setup window?
(√) Enter 10D in the Discount Date Calculation field, and 3 in the Discount
% Field.
( ) Enter 10D in the Discount Date Calculation field, and .03 in the
Discount % Field.
( ) Enter D10 in the Discount Date Calculation field, and .03 in the
Discount % Field.
Module Overview
The Receivables Management application area also has a collections management
feature to keep track of reminders and other finance charge memos. It includes
checking whether amounts due are paid on time. If customers have overdue
payments, you must determine when and how to send reminders. Additionally,
you might have to debit their accounts for interest and, or fees.
In Microsoft Dynamics NAV 2013, you can generate reminders and finance charge
memos.
Reminders are used to prompt customers to pay overdue amounts and to inform
them of any additional fees payable.
If customers refuse to pay overdue amounts after they have received the
reminders, a finance charge memo can be issued that contains interest charges
and, or additional fees. However, the interest charges can also be added directly
on the reminders.
Objectives
• Explain why and when Reminders and Finance Charge Memos are
used.
• Set up Microsoft Dynamics NAV 2013 to use reminders.
• Explain how to create and issue reminders.
• Set up Microsoft Dynamics NAV 2013 to use finance charge memos.
• Explain how to create and issue finance charge memos.
A reminder term contains different reminder levels and determines how many
reminders are sent to a customer. Each level will determine when and how the
reminder is created. Typically, the first reminder for an invoice will have a different
look than the second and third reminder.
For example, a Reminder Term Code can be set up with three reminder levels
and it can have no more than five reminders.
Reminder Terms
The Reminder Terms page contains the fields shown in the following table.
Field Description
Code Unique identifier of the reminder.
Post Interest If this check box is selected, any interest listed on the
reminder will be posted to the G/L and customer
accounts when the reminder is issued. The interest
becomes an open customer ledger entry. Then the
reminder can be created, and the interest can be
calculated when the entry becomes overdue.
Post Additional Fee If this check box is selected, any additional fee listed
on the reminder will be posted to the G/L and
customer accounts when the reminder is issued. The
additional fee becomes an open customer ledger
entry. Then the reminder can be created when the
entry becomes overdue.
Reminder levels are used to define when reminders can be created and what
charges and texts they must include.
The Reminder Levels page contains the fields shown in the following table.
Field Description
No. Identifies the level of the selected Reminder Term. The next
consecutive number is automatically generated when a new
level is added. Level 1 is the first reminder that is sent for an
overdue amount. Level 2 is the second reminder, and so on.
• When reminders are created, Microsoft Dynamics NAV 2013
keeps track of how many reminders are created and uses
the current level number to determine which conditions
apply.
• When a reminder is issued on the last level, the terms of this
level apply to any succeeding reminders that are created.
Due Date Indicates the date formula used to determine how the due date
Calculation is calculated on the reminder. The due date is calculated from
the document date.
Additional Identifies the amount of the additional fee in the LCY that will
Fee (LCY) be displayed on the reminder.
The following table shows how grace periods and due date calculations are used
on an invoice due January 29 (01/29).
Note: February 2 is the first date the reminder can be created. The user will
determine when he or she creates the reminder. When the user creates the
reminder on February 5, this date will be the document date of the reminder and
the reminder due date will be February 10, and so on.
The “Create and Issue Reminders” lesson will discuss how the user deals with the
reminder process.
Additional fees can also be created for each reminder level in foreign currencies.
To access the Currencies for Reminder Level page, follow these steps.
Note: The user is responsible and should consider the exchange rate when he
or she updates the Currencies for Reminder Level page, when the exchange rate
changes significantly.
Information related to the beginning and ending text lines includes the following.
• They can be added for each reminder level of each reminder term.
• They contain instructions on the payment and the result of non-
payment.
• They include several predefined text variables.
To access the Reminder Text – Beginning and Reminder Text – Ending page,
follow these steps.
To assign the Reminder Term Code to a customer card, follow these steps.
Scenario: Arnie is informed that a new reminder term must be set up for
customers who consistently pay after the due date. The name of this reminder
term is Late, with a description of Consistently Late Payers.
Additional fees are not posted to customer or G/L accounts and interest must be
calculated for all levels but is also not posted.
When Arnie is finished, he assigns this Reminder Terms Code to customer 20000,
Selangorian, Ltd.
To set up the reminder term and corresponding reminder levels, follow these
steps.
FIGURE 7.5: SET UP REMINDER TERM LATE WITH 3 REMINDER LEVELS AND
REMINDER TEXT
CRONUS International Ltd. has three troublesome customers who are consistently
late on paying invoices. As the accounts receivable administrator, you are asked to
set up a new reminder term named TOP3, with a description of Top 3 Late Payers.
You also have to send a reminder every 14 days, with no more than four
reminders before the account is sent to collections. This reminder only includes
one level with an ending text that informs the customer of the current reminder
number and that after the fourth notice, the account will be sent to collections.
When the Reminder Term is set up, assign it to the following customers: 10000,
40000, and 50000.
Note: Use the appropriate text variable to designate the reminder number in
the ending text.
Detailed Steps
1. Set up the reminder term and corresponding reminder level as
described in the scenario.
a. On the Navigation Pane, click Departments.
b. Click Administration, and then click Application Setup.
c. On the Application Setup page, click Financial Management >
Finance > Reminder Terms.
d. Click New to insert a line.
e. In the Code field, enter TOP3.
f. In the Description field, enter Top 3 Late Payers.”
g. In the Max. No. of Reminders field, enter 4.
h. On the Actions Tab, click Levels.
i. For level 1, in the Grace Period field, enter 14D.
j. On the Navigate tab, click Ending Text.
• Reminders
• Issued Reminders
Note: How to set up the number series is covered in the course Application
Setup in Microsoft Dynamics NAV 2013.
The Create Reminders batch job uses information from the customer card to
determine the relevant terms for the reminder. There are other extensive options,
such as the following.
To create reminders by using the Create Reminders batch job, follow these steps.
Options FastTab
The Options FastTab contains the fields shown in the following table.
Field Description
Posting Date Date that is listed as the posting date on the header of
the reminder.
Document Date Date that is listed as the document date on the header of
the reminder. This date is used for any interest
calculations and to determine the reminder’s due date.
Use Header Level If this field is selected, the reminder level of the reminder
header is used to determine whether to calculate interest
for a specific reminder line.
If this field is clear, the reminder level on each reminder
line is used to determine whether interest must be
calculated.
Use these filter options to filter the information that is used to create the
reminders.
You can manually create reminders directly on the Reminders page. After you
create the header, you can add invoice lines by using the Suggest Reminder
Lines batch job.
Note: To calculate interest based on the reminder level in the header, select
the Use Header Level check box in the reminder header before you run the
Suggest Reminder Lines batch job.
Change the beginning and ending text on reminders by using the Update
Reminder Text batch job. This batch job changes the text that is associated with
the current reminder level of the reminder term, to the text that is associated with
a different level of the same reminder term. The user can also choose to update
the associated additional fee.
Issue Reminders
After the reminder header and associated reminder lines are created, the reminder
must be issued. This is the process for how to post the reminders. Actual posting
to the customer and G/L account will only occur when the Post Additional Fee
and, or the Post Interest check boxes are selected on the reminder term of the
reminder header.
Before issuing reminders, a test report can be run to review the pre-printed
document.
To issue one reminder and run the test report, follow these steps.
Note: You can always (re)print the document from the Issued Reminder List
page.
10. Select the Replace Posting Date check box to change the existing
posting date on the reminder header.
11. If you want to replace the posting date, enter the new posting date in
the Posting Date field.
12. Expand the Reminder FastTab.
13. The No. filter contains the reminder number of the selected reminder.
By changing this filter that you can group reminders and issue them
together.
14. Click OK.
When you issue a reminder, the following results will occur within the database.
It is the beginning of March, 2014, and reminders must be created and issued for
past due customer entries as of February 28, 2014, by using the conditions of the
header level to all reminder lines.
Issue reminders for customers 43687129 and 47563218 only, without printing or
changing the posting date.
Detailed Steps
1. Run the Create Reminders batch job as specified in the scenario.
a. On the Navigation Pane, click Home.
b. Click Reminders.
c. On the Actions tab, click Create Reminders.
d. In the Posting Date field, enter 02/28/14.
e. In the Document Date field, enter 02/28/14.
f. Select the Only Entries with Overdue Amounts check box.
g. Select the Use Header Level check box.
h. On the Customer FastTab, in the No. filter, enter
43687129|47563218.
i. Click OK.
2. Issue the reminders as they are specified in the scenario.
a. On the Navigation Pane, click Home.
b. Click Reminders.
c. Select the two newly created reminders.
d. On the Actions tab, click Issue.
e. Click OK.
The Finance Charge Terms window contains the fields shown in the following
table:
Field Description
Code Unique code of the finance charge term.
Interest Period Identifies the number of days related to the interest rate. For
(days) example, 12 percent for 360 days or one percent for 30 days.
Grace Period Determines the number of days the customer ledger entry
could go unapplied before a finance charge is assessed.
• The first finance charge memo will be created, if the
document date on the finance charge memo header is
after the due date of the customer ledger entry, plus the
grace period.
• Any succeeding finance charge memos are created if the
document date is after the due date of the last issued
finance charge memo plus the grace period.
Due Date Indicates the date formula that is used to determine how the
Calculation due date is calculated on the finance charge memo. The due
date is calculated from the document date.
Post Interest If this check box is selected, any interest listed on the finance
charge memo will be posted to the G/L and customer
accounts when the finance charge memo is issued. The
interest becomes an open customer ledger entry, for which a
finance charge memo can be created and again interest can
be calculated for, when the entry becomes overdue.
Post Additional If this check box is selected, any additional fee listed on the
Fee finance charge memo will be posted to the G/L and customer
accounts when the finance charge memo is issued. The
additional fee becomes an open customer ledger entry, for
which a finance charge memo can be created, when the
entry becomes overdue.
%4 Interest rate
To access the Currencies for Fin. Chrg Terms page, follow these steps.
FIGURE 7.11: CURRENCIES FOR FIN. CHRG TERMS WINDOW FOR FINANCE
CHARGE TERM 1.5 DOM.
3. Create a new line for each foreign currency that you want to set up
additional fees for.
4. In the Currency Code field, enter the foreign currency.
Information related to the beginning and ending text lines includes the following.
3. Add as many text lines as you must have. You can also use predefined
text variables that the program will replace with the appropriate
information before the finance charge memo is printed.
4. Click OK to close the Finance Charge Text page.
To assign the Fin. Charge Term Code to a customer card, follow these steps.
Scenario: Two days ago, Arnie set up new reminder terms for customers who
consistently pay late. He now must set up a Finance Charge Term for these
customers that will use the following criteria.
In this demonstration, the 11 LATE Finance Charge Term is set up and then
assigned to customer 20000.
14. Click OK to close the new Finance Charge Term Card page
To assign the finance charge term to customer 20000, follow these steps.
In Lab 7.1, you set up the TOP3 reminder term. Now, a finance charge term is
being assigned to these customers.
Set up a Finance Charge Term for these customers by using the following criteria.
When the Finance Charge Term is set up, assign it to the following customers:
10000, 40000, and 50000.
Detailed Steps
1. Set up the finance charge term according to the scenario.
a. On the Navigation Pane, click Departments.
b. Click Administration, and then click Application Setup.
c. On the Application Setup page, click Financial Management >
Finance > Finance Charge Terms.
d. Click New to open a new Finance Charge Term Card page.
e. In the Code field, enter 10 TOP3.
f. In the Description field, enter “TOP3 Late Payers.”
g. In the Line Description field, enter %4% finance charge of %6.
h. In the Additional Fee field, enter 20.
Note: How to set up the number series is covered in the course Application
Setup in Microsoft Dynamics NAV 2013.
You can create finance charge memos by using either of the following methods.
The Create Finance Charge Memos batch job creates finance charge memos for
customers who have overdue amounts. This includes the following.
Note: Make sure that all open credit memos are applied to existing open
invoices before you calculate finance charges. Because credit memos have negative
balances, the finance charge function generates an error when you try to calculate
on that open record.
To access the Create Finance Charge Memos batch job, follow these steps.
Options FastTab
The Options FastTab contains the fields shown in the following table.
Field Description
Posting Date Date that is listed as the posting date on the header of the
finance charge memo.
Use these filter options to filter the information that will create the finance charge
memos.
• Finance charge memos only will be created for customers who have
outstanding balances.
• Finance charge memos are created for each currency for which the
customer has overdue customer ledger entries. Finance charge memo
lines are only created for the customer ledger entries that are in the
currency represented by the currency code on the finance charge
memo header.
Finance charge memo lines are created for all overdue open and
closed customer ledger entries, regardless of the document type of
the entry. This means finance charge memo lines are created for
invoices, but also for payments, credit memos, refunds, finance
charge memos and reminders.
Note: The batch job only inserts customer ledger entries that are in the
currency represented by the currency code on the finance charge memo header.
The batch job creates one finance charge memo for each currency that there are
entries that interest is calculated for.
Scenario: Beginning from 2014, Arnie is required to create finance charge memos
for all open customer entries. It is February 1, 2014 and he must run the reminders
for open entries as of January 31, 2014.
After Arnie runs the Create Finance Charge Memos batch job, he reviews the
memo for customer 20000.
You can manually create finance charge memos directly on the Finance Charge
Memo page. After you create the header, you can add invoice lines by using the
Suggest Fin. Charge Memo Lines batch job.
The Suggest Fin. Charge Memo Lines batch job creates finance charge memo
lines by using options similar to those in the Create Finance Charge Memos
batch job.
Note: The batch job first deletes any existing lines in the finance charge
memo before it inserts the new lines that are created when you run the batch job.
Change the beginning and ending text on reminders by using the Update
Reminder Text batch job. This batch job changes the text that is associated with
the current reminder level of the reminder term, to the text that is associated with
a different level of the same reminder term. The user can also choose to update
the associated additional fee.
After the finance charge memo header and associated finance charge memo lines
are created, the finance charge memo must be issued. This is the process for how
to post the finance charge memos. Actual posting to the customer and G/L
account will only occur when the Post Additional Fee and, or Post Interest
check boxes are selected on the finance charge term of the finance charge memo
header.
Before issuing finance charge memos, a test report can be run to review the pre-
printed document.
To issue one finance charge memo and run the test report, follow these steps.
Note: You can always (re)print the document from the Issued Finance
Charge Memos List page.
10. Select the Replace Posting Date check box to change the existing
posting date on the finance charge memo header.
To issue multiple finance charge memos from the Finance Charge Memo List
page, follow these steps.
When you issue a finance charge memo, the following results will occur within the
database.
The entries suggested in finance charge memos, and the amount of interest
calculated in finance charge memos, depends on the selections made in the
Interest Calculation and Interest Calculation Method fields in the Finance
Charge Terms window.
Average All Entries The combined entries for Same base as the
Daily the Open and Closed Open and Closed
Balance Entries options. Entries options.
It is the beginning of March 2014 and finance charge memos must be created and
issued for past due customer entries as of February 28, 2014.
Issue a finance charge memo for customer 42147258 only, without printing or
changing the posting date.
Detailed Steps
1. Run the Create Finance Charge Memos batch job as specified in the
scenario.
a. On the Navigation Pane, click Home.
b. Click Finance Charge Memos.
c. On the Actions tab, click Create Finance Charge Memos.
d. Expand the Options FastTab.
e. In the Posting Date field, enter 02/28/14.
f. In the Document Date field, enter 02/28/14.
g. Click OK.
Set Up Overview
When you combine the interest charges with the reminders, make sure that you
complete the following setup.
• Reminder Terms:
o Select or clear the Post Interest field - If this check box is
selected, any interest listed on the reminder will be posted to the
G/L and customer accounts when the reminder is issued.
o Select or clear the Calculate Interest field on the Reminder
Levels - If this check box is selected, interest is calculated on the
reminder lines and displayed on the reminder. Interest is
calculated based on the Finance Charge Terms Code selected on
the customer card.
o Assign the Reminder Term Code to the customer card.
• Finance Charge Terms:
o Make sure that you assign the Fin. Charge Term Code to the
customer card. Otherwise, interest cannot be charged on the
reminder, even when the reminder term and levels are set up for
interest calculation.
The steps that you must perform when you create and issue reminders with
interest calculation are identical to the steps that you must perform to create and
issue reminders without interest calculation.
The Use Header Level check box on the reminder header or on the Create
Reminders batch job, only has an effect when the reminder includes interest
calculation, because it will determine whether to calculate interest on the
reminder lines.
The reminder terms setup resembles the finance charge terms setup. The setup on
the reminder terms takes precedence for the following fields.
• Post Interest
• Post Additional Fee
• Grace Period
• Due Date Calculation
• Additional Fee Amount
In this situation, the reminder header has a reminder Level of 2, because it uses
the highest level from the lines.
If reminder terms are set up with Level 2 having interest calculated while Level 1
does not and the Use Header Level check box is selected, the following will occur
when the batch job is run.
Unlike finance charge memos, customer ledger entries suggested in reminders are
only open entries at the Document Date of the reminder.
Module Review
Module Review and Takeaways
( ) The beginning and ending text on the reminder is changed. If you use
text variables, they are recalculated.
(√) A reminder term in Microsoft Dynamics NAV always has three levels.
(√) The beginning and ending text on the reminder is changed. If you use
text variables, they are recalculated.
4. You can charge interest to customers either by using finance charge memos
or reminders. What are the advantages and disadvantages of both systems?
MODEL ANSWER:
Module Overview
Value-Added Tax (VAT) is a tax on consumption that is paid by the end consumer.
For the seller, it is a tax only on the value that is added to a product, material, or
service.
All companies are required to calculate and report VAT on sales and
purchases. Therefore, companies must become familiar with the setup process, in
addition to how to calculate, display, and adjust VAT amounts in sales and
purchase documents.
Additional functions that make the required VAT reporting more efficient include
the following:
• Import VAT
• VAT Corrections
• VAT Reporting
• VAT Settlement
• Unrealized VAT
• Payment Discount VAT Adjustments
Note: Although the general concepts of VAT are the same in all countries that
apply VAT, statements and VAT rates differ from country to country. This module
explains VAT based on the Microsoft Dynamics NAV 2013 worldwide (W1)
database. To be compliant with national VAT legislation, most country versions of
Microsoft Dynamics NAV 2013 include localizations on VAT.
Objectives
The VAT posting setup resembles the general posting setup and is covered in the
course Application Setup in Microsoft Dynamics NAV 2013.
The VAT posting setup also includes the VAT Calculation Type field. With the
VAT calculation type field, the method of calculating VAT is defined.
Microsoft Dynamics NAV 2013 has four methods of calculating VAT. The following
table provides a description for these four methods.
Option Description
Normal VAT Use this option to calculate VAT for items sold or
purchased with this particular combination of
business posting group and product posting group
code.
With this option, the seller of the item calculates and
withholds the VAT.
Full VAT Use this option when the amount to post, with this
particular combination of the VAT business posting
group and the VAT product posting group, consists
completely of VAT.
This option is useful, for example, when you record
import VAT, or make an entry to correct a VAT
calculation error. If the correct entry is made by using
Full VAT, the original VAT entries are not referenced.
This can make the preparation of the VAT Statement
more difficult.
Sales Tax Use this option only if United States (U.S.) sales tax is
recorded instead of VAT.
Because JB-Spedition is a European Union (EU) vendor and it does not invoice
VAT, April must make sure that she uses the reverse charge VAT when she is
posting the purchase invoice.
Demonstration Steps
The navigate function shows all the records, linked to this posted purchase
invoice.
To review the VAT entry for this invoice, follow these steps.
Based on the VAT posting setup, the combination of the VAT business posting
group “EU” and the VAT product posting group “VAT25” results in the Reverse
Charge VAT calculation type.
When the VAT invoice from the transport company (vendor 62000 –
WalkerHolland) arrives, it shows a calculated import VAT amount of 25 percent of
the invoice amount (25,000.00 LCY). Therefore, the posting of this VAT invoice
should result in a VAT base of zero (0) and a VAT amount of 25,000.00 LCY.
The first step is to set up a general ledger account and the VAT posting setup to
accommodate the Import VAT. In this demonstration, the import VAT is posted by
using a purchase invoice.
Note: You can view the result of the VAT calculation type FULL VAT before
you post the invoice by going to the Purchase Invoice Statistics page (F7).
k. Click Post.
l. Click Yes to post the invoice.
m. Close the Purchase Invoice window.
The navigate function shows all the records that are linked to this posted purchase
invoice.
There are two G/L entries with the same G/L account. The first entry is for the VAT
base amount and it is zero. The second entry is for the VAT amount.
To review the VAT entry for this invoice, follow these steps.
In the VAT Entries window, the Base field is 0.00 and the Amount field is
25,000.00 local currency (LCY).
• 1,250.00 LCY credit to both the relevant vendor account and the
payables account.
• 250.00 LCY debit to the purchase VAT account.
April later receives the vendor invoice that states the amount including VAT is
1240.00 LCY. Therefore, a 10.00 correction must be posted. April contacts Cassie,
the accountant, to make the correction.
Because this is the first VAT correction that is made at CRONUS International Ltd.,
Cassie sets up the following to prepare for the correction:
As soon as the setup is complete, she posts the correction by using a general
journal and then reviews the posting. As soon as the posting and review are
complete, she removes the Direct Posting features on the G/L accounts.
a. In the Search box, enter G/L Registers, and then select the
related link.
b. Press CTRL+END to move to the last entry.
c. In the ribbon, click General Ledger.
d. Open the Choose Column feature and add the VAT Amount
field.
e. Click OK and reopen the general ledger entries.
When the general journal is posted, the following entries are created:
To remove the direct posting features on the G/L accounts, follow these steps.
Note: Except for retail sales, the Prices Including VAT check box typically is
not selected.
The selection made in the Prices Including VAT check box determines whether
unit prices on sales documents and direct unit costs on purchase documents
include VAT. Set up the Prices Including VAT check box in the following areas:
• Customer Card
• Vendor Card
• Item Card
• Sales document header
• Purchase document header
On the item card, if the Prices Including VAT check box is not selected, VAT is
not included in the unit price, and the unit price is copied directly from the item
card to the Unit Price field on the sales line. If the Prices Including VAT check
box is selected, VAT is subtracted from the price on the item card before it is
entered on the sales line, and the VAT Bus. Posting Gr. (Price) field must be
filled in.
Note: To include VAT in the unit price on items, you must display the Prices
Including VAT and VAT Bus. Posting Gr. (Price) fields on the Item Card window
by using the Object Designer.
The following table provides an overview of how unit price amounts are
calculated for a sales document when prices are not set up in the Sales Prices
window.
No check mark Check mark The VAT amount for each unit is
calculated and added to the Unit Price
on the Item Card. This total Unit Price
is then entered in the Unit Price Incl.
VAT field on the sales lines.
Check mark Check mark The Unit Price on the Item Card is
copied to Unit Price Incl. VAT field
on the sales lines.
If the Prices Including VAT function is set up on customers and vendors, you do
not have to change the settings on the sales or purchase document headers.
However, if amounts on individual documents have to include or exclude VAT, the
Prices Including VAT check box in the header can be changed.
If you change the Prices Including VAT setting in a sales or purchase document
header, you receive a message that asks you to update the unit price or direct unit
cost on the lines. If you change the Prices Including VAT setting, any manual
changes that you make to the unit prices or direct unit costs are overwritten.
Setup
Users can manually enter or adjust VAT amounts, if the calculated amount differs
slightly from the amount calculated by the customer or vendor, for example, a
difference that is caused by rounding.
To set up the VAT difference allowance in the relevant journal, follow these steps.
If you answer No to the message that asks you to update all related batches, then
you must set up individual batches. To set up individual batches, follow these
steps.
After setup is complete, VAT adjustments can be made in the Sales Order
Statistics or Purchase Order Statistics windows.
In both windows, the total VAT amount for the invoice, grouped by VAT identifier,
is displayed in the lines. To make an adjustment, change the amount in the VAT
Amount field on the lines for each VAT identifier.
Note: If the sales or purchase document has a currency code assigned, the
VAT amounts in the Statistics page are displayed in the same currency.
When the VAT Amount field is changed, Microsoft Dynamics NAV 2013 verifies
that the VAT amount has not changed by more than the amount that is specified
as the maximum difference allowed. If this is the case, then, one of the following
actions occurs:
April discusses the difference with Phyllis, the accounting manager, who tells her
to set up a 0.10 LCY maximum VAT correction amount and to allow corrections
for purchases.
April accidentally enters 0.01 LCY as the maximum and then tries to adjust the
VAT amount on the purchase invoice. Because the change is not within the
allowed range, she is prevented from making the change. She checks her setup,
and after correcting the maximum VAT correction amount, she adjusts the VAT
amount accordingly.
The Calculated VAT Amount and VAT Difference fields are also added to the
Purchase Order Statistics window to review the original VAT amount and the
difference between the amounts.
Demonstration Steps
1. Set up Microsoft Dynamics NAV 2013 so that you can make VAT
corrections.
a. On the Navigation Pane, click Departments > Administration
> Application Setup > Financial Management > Finance >
General Ledger Setup.
b. In the Max. VAT Difference Allowed field, enter 0.01.
c. Click OK to close the General Ledger Setup window.
d. Click Purchases & Payables Setup.
e. Add a check mark in the Allow Vat Difference check box.
f. Click OK to close the Purchases & Payables Setup window.
You will receive an error message stating that the VAT difference must not exceed
Max. VAT Difference Allowed = 0.01.
3. Correct the maximum VAT difference allowed and complete the VAT
amount adjustment on the purchase order.
a. On the Navigation Pane, click Departments > Administration
> Application Setup > Financial Management > Finance >
General Ledger Setup.
b. Update the Max. VAT Difference Allowed field to 0.10.
c. Click OK to close the General Ledger Setup window.
d. On the Navigation Pane, click Purchase > Order Processing >
Purchase Orders.
e. Locate and select order 106009.
f. On purchase order 106009, click Statistics.
g. Click the Invoicing FastTab.
h. Click the No. of VAT Lines field.
i. In the VAT Amount field in the lines, enter 226.00.
j. Click OK.
Notice that a message does not appear in the header, and the 25% VAT field in
the General FastTab still contains the original amount of 225.90 LCY.
k. Open the VAT Amount Lines window. Notice that the 25% VAT
field now contains the adjusted amount of 226.00 LCY.
l. In the Choose Column feature, add the Calculated VAT
Amount and VAT Difference.
m. Review the amounts and then close the VAT Amount Lines,
Purchase Order Statistics, and Purchase Order windows.
Calculated VAT amounts can be adjusted in general, sales, and purchase journals.
This might be necessary when an invoice received from a vendor is entered in the
general journal and the VAT amount on the invoice differs from the calculated
VAT amount.
For the journal to accept changes to the VAT amounts, Phyllis sets a 2.00 LCY
maximum VAT difference and allows for a VAT difference in the general journal
and all related batches.
One of the expenses, the 800.00 LCY for Electricity and Heating, calculates VAT at
160.00 LCY. However, the VAT amount she is posting is 162.00 LCY. She
accidentally enters 163.00 LCY and receives an error. After Phyllis enters the
correct VAT amount, she reviews the amount in the VAT Difference field.
Demonstration Steps
A purchase order is received from customer 20000, Selangorian Ltd., for sales
order 101017. The customer has agreed to pay the full amount of the sales order.
However, the customer’s calculated VAT is slightly larger than the calculation that
appears on the sales order. The calculated VAT amount is 277.27 LCY. The
customer has calculated the VAT amount as 280.21 LCY.
To increase the sales order process, you set up a maximum VAT correction
amount of 3.00 LCY and enable the VAT differences on sales documents. After the
setup is complete, you change the VAT amount on the sales order.
Detailed Steps
1. Open the General Ledger Setup window.
a. On the Navigation Pane, click Departments > Administration
> Application Setup > Financial Management > Finance
> General Ledger Setup.
2. Set the maximum VAT difference as it is specified in the scenario.
a. In the Max. VAT Difference Allowed field, enter 3.
b. Close the General Ledger Setup window.
3. Open the Sales & Receivables Setup window.
a. Click Sales & Receivables Setup.
4. Allow the VAT difference for sales documents.
a. Put a check mark in the Allow Vat Difference check box.
b. Close the Sales & Receivables Setup window.
Detailed Steps
1. Open the Sales Order window and locate order 101017.
a. On the Navigation Pane, click Sales & Marketing > Order
Processing > Sales Orders.
2. Open the Sales Order Statistics window.
a. Locate and select order 101017.
b. Click Statistics.
3. Click the Invoicing FastTab and enter the adjusted VAT amount as it
is specified in the scenario.
a. Click the Invoicing FastTab.
b. Click the No. of VAT Lines 1 field.
c. In the VAT Amount field in the lines, enter 280.21.
d. Click OK.
e. Close the Sales Order Statistics window.
In the past, these invoices have contained large differences in VAT calculations.
Therefore, before you enter the expense, you set a 10.00 LCY maximum VAT
difference allowance and then verify that both the purchase journal and Purchase
area are set up to adjust VAT amounts.
• Batch: Default
• Posting Date: January 28 2014
• G/L account: 8530
• Amount: 210.17
• Adjusted VAT amount: 51.49
Detailed Steps
1. Open the General Ledger Setup window.
a. On the Navigation Pane, click Departments > Administration
> Application Setup > Financial Management > Finance >
General Ledger Setup.
2. Set the maximum VAT difference as it is specified in the scenario.
a. In the Max. VAT Difference Allowed field, enter 10.
b. Close the General Ledger Setup window.
Detailed Steps
1. Open the Purchase Journal window.
a. On the Navigation Pane, click Purchase > Order Processing >
Purchase Journals.
b. Make sure that the Default batch is selected.
2. Show the VAT Amount and VAT Difference fields, if this is
necessary.
a. Open the Choose Column feature and add the VAT Amount
and VAT Difference fields.
3. Enter the expense line as it is specified in the scenario.
a. In the Posting Date field, enter 01/28/14.
b. Make sure that the Account Type is set to G/L Account.
c. In the Account No. field, enter 8530.
d. In the Amount field, enter 210.17.
e. In the VAT Amount field, enter 51.49.
f. Press Tab or Enter.
g. Review the amount in the VAT Difference field.
Unrealized VAT
Microsoft Dynamics NAV provides the options to process unrealized VAT.
VAT is typically calculated when the invoice is created but is not due or realized
until the invoice is paid.
To process unrealized VAT, the Unrealized VAT check box must be selected in
the General Ledger Setup page.
You must define how and when VAT is realized in the Unrealized VAT Type field
in the VAT Posting Setup page. If the default value is blank, this indicates that
unrealized VAT is not calculated for the combination of the VAT business and the
VAT product posting groups.
If you must calculate unrealized VAT, the five options that are available are shown
in the following table.
Option Description
Percentage Each payment covers both VAT and the invoice
amount in proportion to the payment's percentage of
the remaining invoice amount. The paid VAT amount is
transferred from the unrealized VAT account to the
VAT account.
Last Payments cover the invoice amount first and then the
VAT. No amount is transferred from the unrealized
VAT account to the VAT account, until the total
amount of the invoice, excluding VAT, is paid.
First (Fully Paid) Payments cover VAT first (as in the First option), but no
amount is transferred to the VAT account until the full
VAT amount is paid.
Last (Fully Paid) Payments cover the invoice amount first (as in the Last
option), but no amount is transferred to the VAT
account until the full VAT amount is paid.
VAT Statements
Most companies are required to periodically submit a VAT declaration. The VAT
statement is used to specify the basis for calculating the VAT that is payable to the
tax authorities. The VAT statement is defined based on the following:
The advantage of using the VAT entries is that you can close these entries by
posting the VAT settlement. When you work with VAT entries, you can locate VAT
correction entries in previous accounting periods, where the VAT statement is
created.
In Microsoft Dynamics NAV 2013, the VAT statement is typically only defined
during the initial company setup, and it is set up with the format that is required
by the tax authorities. Additionally, it can be previewed and printed after it is
defined.
Before you can create a VAT statement, you must create a VAT statement
template.
Sometimes you could have different VAT reporting requirements, such as when
you are reporting to different government authorities or to different
governments. When this is required, you must create different VAT statements.
If different VAT Statements are created based on the same template, different
names are created in the VAT Statement Names window.
VAT Statement
When the VAT business posting group and the VAT product posting group
transaction posts, the system processes the VAT amounts on the G/L accounts
according to how they are defined in the VAT Posting setup. Then the VAT entries
are created.
You can use the VAT Statement window to calculate the VAT settlement amount
for a specific period. By defining the VAT Statement window, you determine how
the statement is calculated and how it appears when it is printed.
Each line in the VAT statement represents a filter on the G/L Entry table or the
VAT Entry table.
After Phyllis sets up the VAT statement, she runs a preview to confirm the setup
and then prints the statement.
Demonstration Steps
To view a calculated VAT Statement before you print it, in the VAT Statement
window, click Preview in the ribbon.
On the General FastTab of the VAT Statement Preview window, specify the
following:
These selections determine the lines that are contained in the actual statement
and the lines that appear in the preview.
On lines where the Type field contains VAT Entry Totaling, you can access the
individual entries that make up the sum in the Column Amount field by clicking
the drop-down list.
VAT Settlement
Periodically, the net VAT must be remitted to the tax authorities. To calculate this
amount, run the Calc. and Post VAT Settlement batch job. The following list
describes some specifics that are related to this batch job:
To run the Calc. and Post VAT Settlement batch job, follow these steps.
1. Click Preview to review the report, or click Print to print the VAT
Settlement.
2. If the Post check box is checked, you will receive a message that asks
whether the VAT Settlement has to be calculated and posted.
o Click Yes to continue posting.
o Click No to prevent posting.
3. Close the Print Preview window.
When you post the Calc. and Post VAT Settlement batch job, it closes open VAT
entries and transfers purchase and sales VAT amounts to the VAT settlement
account.
When VAT entries are closed, the Closed field on the VAT Entry is selected. The
entry number of the settlement entry that closed the VAT entry is automatically
When a VAT amount is transferred to a VAT settlement account, the account for
purchase VAT is credited and the account for sales VAT is debited with the
amount from the VAT statement period. The account for VAT settlement is
credited with the net amount (or, if the purchase VAT amount is larger, it is
debited).
Note: After VAT entries are posted and their status is closed, they cannot be
reopened. However, VAT reports can be created from these closed entries.
Module Review
Module Review and Takeaways
When doing business with EU countries, VAT must be reported. The system can
automatically calculate VAT amounts for sales, purchases and import.
Microsoft Dynamics NAV 2013 can run all the necessary reports related to VAT. To
accurately report VAT to the appropriate authorities, you must understand the
reporting capabilities that are available in Microsoft Dynamics NAV 2013.
( ) G/L accounts
( ) Item cards
2. What happens when the Calc. and Post VAT Settlement batch job is posted?
3. Which of the following is not an option in the VAT Calculation Type field of
the VAT posting setup?
( ) Normal VAT
( ) Full VAT
( ) Sales Tax
( ) EU VAT
5. Which of the following is not required to adjust VAT amounts in sales and
purchase documents?
( ) Item cards
2. What happens when the Calc. and Post VAT Settlement batch job is posted?
(√) Purchase and Sales VAT amounts are transferred to the VAT
settlement account.
3. Which of the following is not an option in the VAT Calculation Type field of
the VAT posting setup?
( ) Normal VAT
( ) Full VAT
( ) Sales Tax
(√) EU VAT
Module Overview
Prepayments are the payments before the final invoicing of a sales or purchase
order. A sales or purchase prepayment invoice should be created for each advance
payment that is requested so that these prepayments can be posted and applied
to the prepayment invoices. By doing this, you will improve the follow-up on the
sales and purchase orders and the tracking of prepayments.
In Microsoft Dynamics 2013, prepayments are available for both sales and
purchases.
After the required setup is complete, a user can generate prepayment invoices
from the sales and purchase orders for the calculated prepayment amount, and
the correct prepayment invoices as they are needed.
Note: For more information about how to set up prepayments and any
known limitations of the prepayments feature, refer to the Prepayments white
paper (May, 2011). (http://go.microsoft.com/fwlink/?LinkId=267545)
Objectives
Note: Value-added tax (VAT) for the prepayment amounts. This means the
prepayment invoice is handled through a combination of the VAT product posting
group set up on the general ledger account for the prepayment and the VAT
business posting group that is set up on the customer or vendor in the sales or
purchase order header. Therefore, a separate general ledger account is required for
each VAT product posting group.
VAT for the prepayment amounts is not handled through the VAT product posting
group on the sales order line.
These general ledger accounts must be assigned to the relevant general posting
setup combinations on the General Posting Setup page. To complete this setup,
follow these steps.
Note: How to set up unrealized VAT is discussed in the “VAT” module in this
course.
When VAT is used with the Prepayment Unrealized VAT check box in the
General Ledger Setup window (this is how it is used in many countries), VAT that
is from the prepayment invoice will be realized as soon as the payment is applied
to it.
The setup in the General Ledger Setup page makes sure that the unrealized VAT
feature is opened and the VAT that is from the prepayment invoice will be
realized as soon as the payment is applied to it.
Note: When the Unrealized VAT check box is selected, the Prepayment
Unrealized VAT check box must also be selected.
You can select the Prepayment Unrealized VAT check box, without having to
select the Unrealized VAT check box.
When the prepayment invoice is not yet applied, when the final invoice is created it
will automatically realize the unrealized VAT posted in the prepayment invoice.
When you use unrealized VAT, you must have different general ledger accounts to
post realized and unrealized VAT. To do this, set up these general ledger accounts
on the VAT Posting Setup page.
These realized and unrealized VAT accounts will be used when the prepayment
invoice is posted, based on the VAT posting groups assigned to the used
prepayments general ledger account.
Alternatively, you can use a different number series. When you use a different
number series, each number series must be unique so that you can browse
effectively on posted transactions.
Various combinations of items and customers can be set up from the Customer
Card or the Item Card. The same Sales Prepayment Percentages page is used
from both locations. However, the preset filters differ, depending on whether the
page is opened from the Customer Card or the Item Card.
Companies can also set up a default prepayment percentage for an item that is
being purchased for a specific vendor. This prepayment percentage will take
precedence over the default prepayment percentage set up for the customer.
The various combinations of items and vendors can be set up from the Vendor
Card or from the Item Card. The same Purchase Prepmt. Percentages page is
used from both locations. However, the preset filters differ, depending on whether
the window is opened from the Vendor Card or from the Item Card.
The Item No. Filter field is automatically populated with the item the Sales
Prepayments Percentages page is opened from.
5. In the Sales Type field, click the drop-down list and select either
Customer, Customer Price Group, or All Customers.
6. In the Sales Code field, click the drop-down list and select the
particular Customer or Customer Price Group for whom this
prepayment percentage applies or leave it blank when the Sales type
field contains the value All Customers.
7. In the Item No. field, click the drop-down list and select the item the
prepayment percentage applies to.
The following steps are identical to steps 6 through 11 when the Sales
Prepayments Percentages page is opened from the Item Card.
Scenario: Because of the delicate material of the item 8924-W server – enterprise
package, the vendor London Postmaster charges CRONUS International Ltd. with
a prepayment of 20 percent for this item, instead of the regular 10 percent for
other items. As the accounts payable coordinator, you are responsible for setting
up prepayments for vendors.
To set up the prepayment default for the vendor-item combination, starting from
the Item Card, follow these steps.
The Item No. Filter field is automatically populated with item 8924-
W.
5. In the Vendor No. field, click the drop-down list and select vendor
10000.
The Vendor No. Filter field is automatically populated with the vendor the
Purchases Prepmt. Percentages page is opened from.
The following steps are identical to steps 6 through 11 when the Purchase
Prepmt. Percentages page is opened from the Item Card.
This feature makes sure that inventory is not shipped to a customer or received
from a vendor before the prepayment invoice is applied.
Now, to realize prepayment VAT, you must apply the prepayment invoice.
To set up the prepayments verification when you post sales, follow these steps.
To set up the prepayments verification when you post purchases, follow these
steps.
As the accounts receivable administrator for CRONUS International Ltd., you are
responsible for setting up prepayments for particular items and customers. You
must charge a prepayment of 10 percent on all orders for Item 1896-S. You must
also charge customer 10000 a prepayment of 20 percent on all orders.
Note: To successfully perform the following detailed steps, the profile and
corresponding role center for the Accounts Receivables Administrator must be
assigned to your user ID.
Detailed Steps
1. Enter the prepayment requirement for the item as it is specified in the
scenario.
a. On the Navigation Pane, click Home.
b. Click Items.
c. Select item 1896-S.
d. In the Sales section of the Navigate tab, click Prepayment
Percentages.
e. In the Sales Type field, enter All Customers.
f. Leave the Sales Code field blank.
The Item No. field is automatically filled in with the item 1896-S.
The following steps list the typical process flow for prepayment sales orders.
The following steps list the typical process flow for prepayment purchase orders.
The sales and purchase order header contains the following fields on the
Prepayment FastTab that are related to prepayments.
Prepayment Status
The Status field on the General FastTab of the order contains an option of
Pending Prepayment. This status is used when the order has one or more lines
with a prepayment amount, and the prepayment invoice is posted, but not yet
paid.
The Status field is set to open when the order is created. However this field can
also be set to the following options.
The sales and purchase order lines contain the following fields that are related to
prepayments. Notice that you must show these fields that have the Choose
Column function.
If the Qty. to Invoice field contains a number that is less than the total quantity
ordered, you can change the amount to deduct you post the invoice.
A sales or purchase order can have a prepayment percentage on the header and a
different percentage for the items on the lines. For each sales or purchase order
line, Microsoft Dynamics NAV 2013 searches for the prepayment percentage and
applies the first default that it finds in the following order.
1. The prepayment percentage for the item on the line and the
customer or vendor on the order header.
2. The prepayment percentage for the item on the line and the
customer price group for the customer.
3. The prepayment percentage for the item on the line for all customers.
4. The prepayment percentage on the sales or purchase header.
5. The prepayment percentage for the customer or vendor on the order
header.
Note: The priority order followed by Microsoft Dynamics NAV 2013 means
that the prepayment percentage that is specified on the customer or vendor only
applies if there is no prepayment percentage set up for the selected item.
Creating prepayment orders resembles creating other sales and purchase orders.
Although there can be different prepayment percentages for each order line, a
single prepayment percentage can be applied to the whole order. Perform this
action after each order line is completed.
To enter a single prepayment percentage that applies to all the order lines, follow
these steps.
To return to the individual prepayment percentages, either delete and re-enter the
lines, or manually enter the Prepayment % on each line.
Note: If the Prices Including VAT check box is clear, you can edit the
Prepayment Amount Excl. VAT field.
If the Prices Including VAT check box on the order header is selected, you can edit
the Prepayment Amount Incl. VAT field.
Note: Before you post the prepayment invoice, you can generate a test report,
by clicking Prepayment on the Action tab, and then by clicking Prepayment Test
Report.
The View - Posted Sales Invoices or View – Posted Purchase Invoices page is
opened, with an automatic filter on the sales or purchase order that the
prepayment invoice is created from.
1. On the order line, review and if it is necessary, adjust the Qty. to Ship
or Qty. to Receive and Qty. to Invoice fields.
2. On the Actions tab, click Post.
3. Select (Ship and) Invoice or (Receive and) Invoice.
4. The posting process will have the following results:
o A posted sales or purchase invoice and corresponding entries are
created.
o On the sales or purchase order lines, the following fields are
updated:
Prepmt Amt to Deduct Excl. VAT
Prepmt Amt Deducted Excl. VAT
Note: In Microsoft Dynamics NAV 2013, the sales or purchase order cannot
post when there are unposted prepayment amounts (the amount in the Prepmt.
Line Amount excl. VAT field is more than the amount in the Prepmt. Inv.
Amount Excl. VAT field on one or more lines).
1. From the sales or purchase order on the Navigate tab, click Invoices.
To create the prepayment purchase order according to the scenario, follow these
steps.
The Prepayment % field is automatically filled in with the default 10 percent that
is from the order header.
The Prepmt Amt Inv. Excl. VAT and the Prepmt Amt to Deduct Excl. VAT are
updated with 500.00 LCY.
One invoice line is created for the total prepayment amount of both item lines on
the purchase order. The Compress Prepayment check box on the purchase order
is selected.
Susan, the Order Processor at CRONUS International Ltd. will first create the sales
order and the corresponding prepayment invoice. Later she will adjust the sales
order and the corresponding prepayment invoice.
Note: To successfully perform this lab, the previous lab “Set Up Prepayments
for Sales” must be completed.
Note: Make sure that the database is set up to handle the payment discount
excluding VAT. The payment discount is discussed in the “Receivables and Payables
Management - Payment Discount and Payment Tolerance” module in this course.
Customer 10000 The Cannon Group Ltd., establishes the following order with
CRONUS International Ltd.
Note: To successfully perform the following detailed steps, the profile and
corresponding role center for the order processor must be assigned to your user ID.
Task 1: Create the Prepayment Sales Order and Process and Review
the Prepayment Sales Invoice
Detailed Steps
1. Create the prepayment sales order according to the scenario.
a. On the Navigation Pane, click Home.
b. Click Sales Orders.
c. Click New to create the prepayment sales order.
d. Unfold the General FastTab.
e. Press ENTER to automatically insert a sales order number in the
No. field.
f. In the Sell-to Customer No. field enter 10000 and move to the
next field. The sales order header is automatically filled in with the
default settings that are from the customer card.
g. In the Document Date field, enter 01/24/14.
h. Expand the Shipping FastTab.
i. In the Shipping Advice field, enter Complete.
j. Click Yes.
k. Expand the Prepayment FastTab.
The Prepayment Due Date, Prepmt. Payment Discount % and Prepmt. Pmt.
Discount Date, are automatically filled in based on the Document Date and the
Prepmt. Payment Terms Code.
The Prepayment % field is automatically filled in with the default 20 percent that
is from the order header.
The Prepayment % field is automatically filled in with the default 20 percent that
is from the order header.
The Prepmt Amt Inv. Excl. VAT and the Prepmt Amt to Deduct Excl. VAT are
updated with 649.40 LCY.
The View - Posted Sales Invoices page is opened, with an automatic filter on the
sales order that the prepayment invoice is created from.
One invoice line is created for the total prepayment amount of both item lines on
the purchase order. The Compress Prepayment check box on the purchase order
is selected.
Notice that the VAT amount is calculated on the lowered base amount.
Customer 10000 The Cannon Group Ltd. changes the newly created order by
adding new items to the sale. Adjust the sales order with the following
information.
Note: To successfully perform the following detailed steps, the profile and
corresponding role center for the Order Processor must remain assigned to your
user ID.
Detailed Steps
1. Adjust the sales order according to the scenario.
a. On the Home tab, click Reopen.
b. Expand the General FastTab. The Status field is set to Open.
c. In the Document Date and Posting Date field, enter 01/27/14.
d. Expand the Lines FastTab.
e. Create a new sales order line.
f. In the Type field, enter Item.
g. In the No. field, enter 1924-W.
h. In the Quantity field, enter 5.
i. In the Unit Price Excl. VAT field, enter 136.40.
The Prepayment % field is automatically filled in with the default 20 percent that
is from the order header.
The Prepmt Amt Inv. Excl. VAT and the Prepmt Amt to Deduct Excl. VAT are
updated with 136.40 LCY.
The View - Posted Sales Invoices page is opened, with an automatic filter on the
sales order that the prepayment invoice is created from.
Notice that the VAT amount is calculated on the lowered base amount.
Note: To successfully perform the following detailed steps, the profile and the
corresponding role center for the accounts receivable administrator must remain
assigned to your user ID.
Detailed Steps
1. Process the first prepayment according to the scenario.
a. On the Navigation Pane, click Home.
b. Click Cash Receipt Journals.
c. Select the BANK cash receipt journal and then click Edit Journal
on the Home tab.
d. In the Posting Date field, enter 01/30/14.
e. In the Document Type field, enter Payment.
f. In the Account Type field, enter Customer.
g. In the Account No. field, enter 10000.
h. On the Home tab, click Apply Entries.
i. Select the open customer ledger entry for the first prepayment
invoice.
j. On the Home tab, click Set Applies-to ID.
k. Click OK to close the Apply Customer Entries page.
On 02/07/14 all the items are delivered to the customer and the final invoice is
created.
Note: To successfully perform the following detailed steps, the profile and
corresponding role center for the accounts receivable administrator must remain
assigned to your user ID.
Detailed Steps
1. Create the final invoice according to the scenario.
a. On the Navigation Pane, click Home.
b. Click Sales Orders.
c. Select the prepayment sales order for customer 10000 and then
click Edit.
d. Expand the General FastTab.
e. In the Document Date and Posting Date field, enter 02/07/14.
f. On the Home tab, click Post.
g. Select Ship and Invoice and then click OK.
Susan, the Order Processor at CRONUS International Ltd. will first create the sales
order and the corresponding prepayment invoice that the unrealized VAT will be
calculated for.
Arnie, the Accounts Receivables Administrator will create the final invoice, before
the prepayment is received.
Note: Before you start with the actual prepayment process, the first exercise
asks you to review the setup for unrealized prepayments. Make sure that you
complete this first!
Detailed Steps
1. Verify the General Ledger Setup.
a. In the Navigation Pane, click Departments.
b. Click Administration, and then click Application Setup.
c. On the Application Setup page, click Financial Management >
Finance > General Ledger Setup.
d. Expand the General FastTab.
e. Select the Unrealized VAT and Prepayment Unrealized VAT
check boxes.
f. Click OK to close the General Ledger Setup page.
Detailed Steps: This is not the correct VAT account, and a separate
unrealized VAT account should be created. However, for the demonstration you will
use the 5780 account.
Customer 10000 The Cannon Group Ltd., establishes the following order with
CRONUS International Ltd.
Task 1: Create the Prepayment Sales Order and Process and Review
the Prepayment Sales Invoice
The View - Posted Sales Invoices page is opened, with an automatic filter on the
sales order that the prepayment invoice is created from.
On 01/30/14, the order is shipped and invoiced to the customer. The prepayment
is not yet received. Review the postings for the unrealized VAT amount.
Detailed Steps
1. Create the final invoice according to the scenario.
a. On the Navigation Pane, click Home.
b. Click Sales Orders.
c. Select the prepayment sales order for customer 10000 and then
click Edit.
d. Expand the General FastTab.
e. In the Document Date and Posting Date field, enter 01/30/14.
f. On the Home tab, click Post.
g. Select Ship and Invoice and then click OK.
An invoice line is created for the full sales amount for each sales order line.
Again the unrealized VAT account is used for the negative prepayment invoice
line.
The posting of the unrealized to the realized VAT account will be processed at the
time of payment.
Correct Prepayments
After you post a prepayment invoice, you can process corrections or updates by
adding new lines to the order and by posting another prepayment invoice. Lines
cannot be deleted from an order when a prepayment is invoiced for the line.
1. On the order, on the Actions tab, click Prepayment, and then click
Post Prepayment Credit Memo.
2. If it is required, re-create the correct entries.
Note: When you create the prepayment credit memo, all prepayment invoices
will be credited. You cannot credit just one prepayment invoice.
To add new lines to an order after issuing a prepayment, follow these steps.
A new invoice is created for the difference between the prepayment amount
invoiced to this point and the new prepayment amount.
Module Review
Module Review and Takeaways
Prepayments are used in sales or purchases. You can use prepayments to charge
either a percentage of the total order or a specific amount before the items are
shipped to customers. Companies can also use prepayments to record
prepayments to vendors.
You can create several prepayment invoices for one order. You can also post
prepayment credit memos, for example when an order is cancelled.
1. What status is used when an order has one or more lines with a prepayment
amount, and a prepayment invoice has not been posted?
( ) Open
( ) Pending Prepayment
( ) Prepayment Awaiting
( ) Pending Approval
4. Microsoft Dynamics NAV 2013 searches items, customers, vendors, and price
groups for default prepayment percentages when an order is created. Which
of the following statements is incorrect?
1. What status is used when an order has one or more lines with a prepayment
amount, and a prepayment invoice has not been posted?
(√) Open
( ) Pending Prepayment
( ) Prepayment Awaiting
( ) Pending Approval
Module Overview
Completing the year-end closing process in Microsoft Dynamics NAV
2013 involves three steps.
1. Closing the fiscal year by using the Close Year function on the
Accounting Periods page.
2. Generating a year-end closing entry by using the Close Income
Statement batch job.
3. Posting the year-end closing entry together with the offsetting equity
account entries.
Objectives
1. In the Search box, enter Accounting Periods, and click the related
link.
2. On the Home tab, click Close Year. You will receive a message about
the year to be closed. This year is suggested based on the earliest
open year, and the corresponding check marks in the New Fiscal
Year field.
Note: To close a nonstandard year, add a check mark in the New Fiscal Year
check box of the last period to be included in the year to be closed.
• The Closed and Date Locked fields for all periods in that fiscal year
are selected and they cannot be cleared any longer.
• The Date Locked field for the first period of the next fiscal year is
selected and it cannot be cleared any longer.
• The period lengths for the closed periods cannot be changed.
Note: To prevent users from posting entries in a closed fiscal year, set a date
range in the Allow Posting From and Allow Posting To fields on the General
Ledger Setup page.
Scenario: After the 2013 fiscal year is closed, Phyllis, the Accounting Manager at
CRONUS International Ltd., realizes that she must post a December 2013 cleaning
expense for 80.00 local currency (LCY).
After Phyllis posts the expense, she reviews the entry to verify that the Prior-Year
Entry check box is selected to indicate that it is a prior-year entry.
Note: To complete this demonstration, make sure that the 2013 fiscal year is
closed. If a different year is closed, post into that year in step 6 of this
demonstration.
Demonstration Steps
1. Post the 2013 cleaning expense and review the posted entries.
a. In the Search box, enter General Journals, and click the related
link.
b. In the Batch Name field, click the drop-down list and then select
the DEFAULT journal batch.
c. Click OK.
d. Delete any existing journal lines in the batch.
e. In the Posting Date field, enter 12/31/13.
f. Make sure that the Account Type field is set to G/L Account.
g. In the Account No. field, enter 8110.
h. In the Amount field, enter 80.00.
i. Make sure that the Bal. Account Type field is set to G/L Account.
j. In the Bal. Account No. field, enter 2910.
k. On the Actions tab, click Post.
l. Click Yes to post the journal lines.
a. In the Search box, enter G/L Registers, and click the related link.
b. Press CTRL+END to move to the last entry and select this entry.
c. On the Navigate tab, click General Ledger to review the posted
entries.
d. Click the About This Page function.
e. Expand the Table Fields FastTab.
f. Locate the Prior-Year Entry field and verify that the value is set
to Yes. This means that this entry is considered a closing entry
and it will be included when the Close Income Statement batch
job is run.
You can use the Close Income Statement batch job multiple times to transfer the
income statement account balances. For example, you might have to do this when
the next entries are posted into a closed year.
To open the Close Income Statement batch job, follow these steps.
1. In the Search box, enter Close Income Statement, and click the
related link.
• Fiscal Year Ending Date – Automatically populated with the last date
in the latest closed fiscal year. This date is used to determine the
posting date for the journal.
• Gen. Journal Template – Identifies the name of the general journal
template that the entries are added in.
• Gen. Journal Batch – Identifies the name of the general journal
batch that the entries will be added in.
• Document No. – Automatically populated with the next available
number from the number series for the selected Gen. Journal Batch.
• Retained Earnings Acc. – Identifies the account that the retained
earnings entries are added in.
• Posting Description – Specifies the text to accompany the entries.
The default text is Close Income Statement.
• Close by – Provides the available accounting options in Microsoft
Dynamics NAV2013 to classify into multiple entries. The options are
as follows:
o Business Unit Code: If this field is selected, and the company is a
consolidated company, separate entries are created for each
business unit.
o Dimensions: For any dimensions selected, one entry is posted for
each dimension value combination used in a G/L account.
If neither option is used, a single entry is created for each
account.
• Inventory Period Close – Indicates that the inventory period(s) with
ending dates equal to or greater than the last date of the accounting
period is closed.
After you close a fiscal year, you can still post general ledger entries to the closed
year. When you post in a closed year, entries are marked as prior-year entries.
When the next entries are posted to a closed fiscal year, you must follow these
steps.
1. Run the Close Income Statement batch job to transfer the balances
to the retained earnings (equity) account.
2. Post the transferred entries.
Scenario: After the 2013 fiscal year is closed, Phyllis, the Account Manager, must
run the Close Income Statement batch job to transfer the income statement
accounts to account 3120, the retained earnings account, as part of the fiscal year
processing.
The default general journal is used and the posting description includes the fiscal
year number.
You must keep the Area, Business Group, and Customer Group dimension
information that is posted on the income account entries.
Demonstration Steps
If an account is not specified in the Retained Earnings Acc. field in the Close
Income Statement batch job, one or more lines must be inserted into the journal
with the retained earnings account, and the amount that will be posted to the
account.
When the journal is posted, one or more entries are posted to each income
statement account so that its balance becomes zero. Also, the retained earnings
account is updated for the gain or loss.
In this demonstration, a general ledger account that has 2013 entries is reviewed
before and after the journal is posted, to obtain a comparison. The steps for
reviewing these entries are not part of the closing process.
Scenario: To complete the year-end closing process, Phyllis posts the entries
transferred to the DEFAULT general journal batch.
Demonstration Steps
Notice that the Total Balance field at the bottom of the window
contains a zero balance. Therefore, the journal can be posted.
e. On the Actions tab, click Post.
f. Click Yes to post the journal.
g. Click OK.
h. Click OK to close the General Journal page.
a. In the Search box, enter Chart of Accounts, and click the related
link
b. Select account 9110.
Notice that an offsetting line appears for the amount noted when you
reviewed the account before posting the journal.
Notice that the amount for the Close Income Statement 2013 line
matches the amount for this account from the general journal.
In this lesson, the 2013 fiscal year is already closed and it uses the three step
process. It is now audit time and the auditors have found an additional vacation
compensation expense for 7,844.74 LCY that must be posted in 2009.
As the accounting manager, it is your responsibility to post the accrual. The debit
is to the Vacation Compensation expense (account 8740), and the credit is to the
Vacation Compensation Payable account (5840). Use 12/31/13 as the posting date
for the entry.
After the entry is made, transfer and post the expense to include it in the closing
process. Use the following criteria to complete the closing process.
Detailed Steps
1. Post the accrual according to the scenario.
a. On the Navigation Pane, click Departments.
b. Click Financial Management > General Ledger > General
Journals.
c. In the Batch Name field, click the drop-down list and select the
DEFAULT journal batch.
d. Click OK.
e. Delete any existing journal lines in the batch.
f. In the Posting Date field, enter 12/31/13.
g. Make sure that the Account Type field is set to G/L Account.
2. Run the Close Income Statement batch job according to the scenario.
a. On the Navigation Pane, click Departments.
b. Click Financial Management > Periodic Activities > Fiscal
Year > Close Income Statement.
c. Make sure that the Fiscal Year Ending Date is 12/31/13.
d. In the Gen. Journal Template field, click the drop-down list and
select GENERAL.
e. In the Gen. Journal Batch field, click the drop-down list and
select DEFAULT.
f. Click OK.
g. In the Retained Earnings Acc. field, enter 3120.
h. In the Posting Description field, add 2013 to the end of the text.
i. In the Dimensions field, click the AssistEdit (…) button.
j. Clear the Selected check box for the AREA, BUSINESS GROUP,
and CUSTOMER GROUP dimension codes.
k. Click OK to close the Dimension Selection page.
l. Click OK to run the Close Income Statement batch job.
m. Click OK to the message that the journal lines are now created.
Module Review
Module Review and Takeaways
The year-end closing processes in Microsoft Dynamics NAV 2013 are the final step
in the fiscal year. A company must close all the income and expense accounts to
obtain a final statement and balance for the year.
The year-end closing processes close all entries in Microsoft Dynamics NAV 2013
and the Close Income Statement batch job transfers all general ledger accounts
to the balance so that the company is ready for the next period.
Completing the year-end closing processes will make data segregation and
analysis easier, and will also simplify the review of the posted entries in the Chart
of Accounts, because the balances only reflect the current year activity.
1. What does not occur after the Close Year process is run?
( ) The next entries posted in the closed year are marked as prior-year
entries.
( ) The Closed and Date Locked check boxes in the Accounting Periods
window are selected.
2. What steps must be performed after an entry is posted into a closed fiscal
year?
( ) The Close Income Statement batch job must be run and then the
transferred entries must be posted.
( ) Accrued Earnings
( ) Retained Earnings
( ) Accrual Entries
( ) Retained Accruals
5. What occurs when you post a journal that contains the closing entries?
( ) The income statement accounts are updated for the gain or loss.
( ) Two journals are created when the Close Income Statement batch job
is run.
1. What does not occur after the Close Year process is run?
( ) The next entries posted in the closed year are marked as prior-year
entries.
( ) The Closed and Date Locked check boxes in the Accounting Periods
window are selected.
2. What steps must be performed after an entry is posted into a closed fiscal
year?
(√) The Close Income Statement batch job must be run and then the
transferred entries must be posted.
3. Which of the following statements is false for the Close Income Statement
batch job?
( ) Accrued Earnings
( ) Accrual Entries
( ) Retained Accruals
( ) The income statement accounts are updated for the gain or loss.
( ) Two journals are created when the Close Income Statement batch job
is run.
(√) The journal is automatically posted when the Close Income Statement
batch job is run.