Dynamics NAV

The DATABASICS Time & Expense Reporting system integrates to Dynamics NAV to support time and expense accounting.

Each NAV entry module specific outbound specification from DATABASICS is outlined in separate sub-sections, as follows:

• Timesheet - labor accounting details

• Purchase Invoice - expense accounting, vendor payables

• Accounts Payable - reimbursable expense accounting, vendor payables

• General Ledger - labor and expense accounting details

NAV Extensions

There are industry specific Extension of Dynamics NAV. Using extensions like Serenic Navigator may add value for integration purposes and DATABASICS works with all of them allow enhanced functionality in support of our customers' requirements. The integrations will be similar to what is outlined here, but with adjustments made to facilitate for the customer’s and the specific extension’s requirements, including enhanced process functionality and format variations (like xml).

Inbound Data to DATABASICS

In a bi-directional integration Demographic (Organization) and Project (WBS) data typically originates in NAV and is imported to DATABASICS to support valid data in the outbound flows.

Organization Structure

In a NAV integration the DATABASICS Organization structure typically consists of one or more of the following:

• Company

• Vendor - supporting reimbursement through Accounts Payable if included

• Cost Rates - supporting project cost accounting solution if included

• Employee

The Employee typically has one or more of the following properties:

• Employee ID

• Vendor ID

• Employee First and Last Name

• Home Company

• Employee Type - supporting entry validation (e.g. OT) if included

• Email address

• Manager ID - supporting approval requirements if included

• Hire Date

• Termination Date

Work Breakdown Structure

In a NAV integration the DATABASICS Work Break Down Structure typically consists of one or more of the following:

• Project

• Project Type

• Task

• Bill Rate - supporting billing if included

The Project and Task typically has one or more of the following properties, supporting customer’s specific requirements:

• Contract Type

• Owning Company

• Resource Assignment

• Manager ID - supporting approval requirements if included

• Start Date

• End Date

Inbound Integration methods

Data flow inbound to DATABASICS is managed using the DATABASICS Import / Export utility.

In a NAV integration data can be read directly from views created by the customer or the customer can provide flat files with data, according to agreed specifications.

The loads will validate to make sure all the required fields are provided in order for the employee to be active in DATABASICS.

Direct Data Pull from Views

We can use the DATABASICS import / export utility to read data directly from views created by the customer. Using the direct pull solution provides the organization and project data, and refreshes the data in DATABASICS for new records and existing records without the need for an intermediary step.

This approach includes installing the import utility inside the customer firewall and linking the utility back to DATBASICS for delivery of the specified data.

An agreed specification will outline what data to import from where. Example employee profile specification:

The utility allows the customer to specify the frequency of each scheduled load and also gives the ability to refresh data manually.

Data Push to DATABASICS

Flat files can be imported into DATABASICS from a dedicated SFTP site: more information here

Files must be provided according to agreed specifications, loads can be scheduled according to requirement (e.g. weekly, daily, hourly), or manually triggered on an as needed basis.