Overview
In any business solution implementation, it is crucial for consultants to first gather and fully understand customer requirements in order to comply with any statutory and regulatory requirement like accounting standards. Next would be how to translate these requirements using Microsoft Dynamics NAV. One interesting topic I have encountered during business process reviews is on employee-related transactions, specifically cash advances that are subject for liquidation.
A consultant can always come up with different proposed business solutions and ideas on how to use Microsoft Dynamics NAV to record this type of transaction from setup to settlement. Some might propose employees should be recorded as customers or as vendors or both. Then use payment journals to setup receivable or payable and then use other journals to record liquidation and reverse receivable or payables. Needless to say, there are all sorts of processes.
What most non-accounting consultants tend to overlook is the fact that with any business solution, the focus should not only be on the boundaries of the system but more importantly, it’s capability in complying with regulatory and statutory requirements such as accounting standards.
As an Accountant , NAV user and consultant, I always look into a combination of applying the accounting standards first, then executing my solution using the different NAV functionalities and lastly, coming up with a workaround in case of a gap.
In this post, I am sharing with my fellow consultants a proposed solution I implemented to one of my clients who is in fact satisfied with the guaranteed accounting and process outputs in terms of employee’s cash advances subject for liquidation.
Definition
In the normal course of business, cash advances are given to employees as a temporary fund support to a specific operational requirement for which issuance of a purchase order would be impractical. As a general rule of thumb for accounting, cash advances are recorded as part of receivables and which they have to be liquidated or settled subsequently through submission of receipts as proof of incurring the expense, collecting excess cash or reimbursing the employee for the excess expense incurred on top of the cash advance received.
Nav Functionalities And System Setup
Transactions that involve setup of receivable for cash advance issued and its liquidation will use functionalities of NAV like Purchase Order, Purchase Invoice, Payment Journal, Cash Receipts Journal and Purchase Prepayment.
To ensure correct accounting entries are made when posting transactions in NAV, the following setups are required:
- Chart of Accounts. Apart from the usual chart of accounts for both balance sheet and income statement, the G/L accounts below should also be created:
No. |
Name |
Income/Balance |
Account Type |
Direct Posting |
Reconciliation Account |
Gen. Posting Type |
Gen. Bus. Posting Group |
Gen. Prod. Posting Group |
VAT Prod. Posting Group |
---|---|---|---|---|---|---|---|---|---|
1110 |
Cash on hand |
Balance Sheet |
Posting |
Yes |
Yes |
|
|
|
|
1600 |
Rec’ble from employees |
Balance Sheet |
Posting |
No |
Yes |
Purchase |
EMPLOYEE |
GL |
|
3196 |
Payable to employees |
Balance Sheet |
Posting |
No |
Yes |
Purchase |
EMPLOYEE |
GL |
|
7361 |
Any expense account |
Income Statement |
Posting |
Yes |
Yes |
Purchase |
DOMESTIC |
GL |
VAT12 |
Note:
a. Cash on hand account will be used to record excess cash from cash advance.
b. Rec’ble from employees account will be used in general posting setup as Purchase Prepayments Account.
c. Payable to employees account will be used as vendor posting group for employees which will be created as vendors.
- General Posting Setup. The following general posting setup assumes that purchase lines associated with employee’s cash advances will only have G/L account types.