Interested


Sign up for a software demonstration.


CoreconLink for Microsoft Office Accounting - Integration Points


The CoreconLink for Microsoft Office Accounting is used to transfer information from Corecon 2007 to Microsoft Office Accounting. This utility can be downloaded from within Corecon 2007 and is typically installed only in the accounting department. Whether project financial information is entered by project managers or the accounting department, these financial transactions can be sent to Microsoft Office Accounting, eliminating duplicate data entry. The points of integration between Corecon and Microsoft Office Accounting are listed below.

Corecon
Feature
Transfer
Method
Microsoft SBA
Feature
Comments
Startup Phase
Companies <---> Customers
Vendors
Typically, an organization will implement Corecon after they have been working with Microsoft Office Accounting for a while. Given this scenario, the CoreconLink application would be used immediately to copy customers and vendors from the accounting system to Corecon.
Employees <---> Employees Like Customers and Vendors, Employees are typically copied from the accounting system to Corecon.
Payroll Items Linked Service Items Like Job Cost Codes, Corecon Payroll Items should be linked to Service Items in Microsoft Office Accounting. This is only required if Timecards are going to be transferred.
Tax Codes <---- Tax Codes Accounts payable and accounts receivable transactions below can reference a Tax Code. In the US, Tax Codes are setup to handle the markups for sales tax. With tax codes being linked in both systems, this will alleviate the accounting administrator of having to specify the correct code when sending transactions over to Microsoft Office Accounting.

Note: If Tax Codes are already setup in Microsoft Office Accounting, one can copy these codes to Corecon.
Project Setup Phase
Projects ----> Jobs A Corecon Project gets transferred to Microsoft Office Accounting only if it has been awarded. Immediately following this activity, job cost codes would then be linked to chart of accounts and service items (see step below).
Job Cost Codes Linked Items
Chart of Accounts
Classes
All financial transactions (Bills, Checks, Credit Card, Invoices, Timecards) in Microsoft Office Accounting require either a Service Item or Chart of Account when entering the item details. Classes can also be referenced depending on the company. In Corecon, all financial transactions require a Job Cost Code which are project specific.

Since project financial transactions will be entered in Corecon and then transferred to Microsoft Office Accounting, the CoreconLink has a feature to create relationships between Corecon Job Cost Codes and Service Items, Chart of Accounts, and Classes in Microsoft Office Accounting. This will alleviate the accounting administrator of having to specify the correct item or account when sending transactions over from Corecon.
Project Transactions: Accounts Payable
Bills * ----> Bills
Credit Card
Check
Bills are entered in Corecon and sent to Microsoft Office Accounting.
Sub Invoices * ----> Bills
Credit Card
Check
Sub Invoices are entered in Corecon and sent to Microsoft Office Accounting. Sub Invoices are processed based on the contract type: fixed lump sum, cost plus, or unit price. In addition, Sub Invoices can have retention.
Project Transactions: Accounts Receivable
Prime Invoices * ----> Invoices Prime Invoices are entered in Corecon and sent to Microsoft Office Accounting. Like Sub Invoices, the billing method is based on the contract type and the invoice can have retention.
Project Transactions: Labor Timecards
Labor Timecards ----> Time Trackings One of the benefits of Corecon in an organization is the ability of estimators and project team members to enter their own timecards. Thus, the accounting department can completely restrict access to Microsoft Office Accounting since timecards can be sent from Corecon to that system.

* - If the transaction has a negative total, it will then appear as a credit in Microsoft SBA.

Integration Nomenclature:
<---> Bidirectional Integration
----> Corecon exports to Microsoft SBA
<---- Microsoft SBA exports to Corecon