ISolved Keystone Integration: Difference between revisions

From KeystoneIntranet
Jump to navigation Jump to search
 
Line 45: Line 45:
| base_url=<API Base URL><BR>client_id=<Customer API Client Id><BR>client_secret=<Customer API Client Secret><BR>client_code=<Customer Client Code><BR>legal_code=<Customer Legal Code>
| base_url=<API Base URL><BR>client_id=<Customer API Client Id><BR>client_secret=<Customer API Client Secret><BR>client_code=<Customer Client Code><BR>legal_code=<Customer Legal Code>
| base_url=<GH Customer><BR>client_id=<GH Customer><BR>client_secret=<GH Customer>
| base_url=<GH Customer><BR>client_id=<GH Customer><BR>client_secret=<GH Customer>
| (see below)
|  
|  
|  
|-
|-

Latest revision as of 21:31, 23 January 2025

Overview

GivenHansco has developed an integration between iSolved Payroll and Keystone financials (G/L, C/M and J/C.) This integration makes use of the iSolved API to allow transfer of payroll data directly from iSolved into Keystone transaction batches. Once transferred these batches can be reviewed and/or posted.

This integration requires Keystone 4.7.13 or higher.

Configuration

iSolved Information

The first step in configuring the integration is to obtain the following information from iSolved for the customer:

  • Client Code
There is a spreadsheet containing the client codes for Keystone customers located in Teams under Support Team->General->Files->Payroll->Keystone iSolved Client IDs.xlsx. If the customer is not on this list obtain their Client Code from iSolved and add it to the list.
  • Legal Code
For customers who have multiple Keystone companies with separate payrolls, this field must also be specified.
  • URL
For customers who were already on Keystone prior to signing up with iSolved, they will use the GivenHansco URL which is built into the integration.
For customers who were signed up with iSolved prior to becoming a Keystone customer, they will use a different URL which must be provided by iSolved.
  • Client Credentials (Client Id/Client Secret)
For customers who were already on Keystone prior to signing up with iSolved, they will use the GivenHansco client credentials which are built into the integration.
For customers who were signed up with iSolved prior to becoming a Keystone customer, they will use a unique set of credentials which must be provided by iSolved.
  • Other
(TBD)

Keystone System Options

There are several system options that must be configured. These options are located under General Ledger->Import Payroll Options.

For most configurations only two options need to be specified:

  • ISolved API Credentials
client_code (required)
legal_code (required only for multiple Keystone companies with separate payrolls)
  • ISolved Default JC TrxType


Option Name Required Type Allowed Values Default Comment Keystone Version
ISolved API Credentials client_code
legal_code (see above)
Memo base_url=<API Base URL>
client_id=<Customer API Client Id>
client_secret=<Customer API Client Secret>
client_code=<Customer Client Code>
legal_code=<Customer Legal Code>
base_url=<GH Customer>
client_id=<GH Customer>
client_secret=<GH Customer>
ISolved Default JC TrxType Yes Lookup (J/C Trx Types) (none) Default J/C Trx Type for J/C transactions
ISolved JC Hours U/M Lookup (A/R Units of Measure) HR J/C Unit of Measure
ISolved GL Category (Check) String Check Item Category representing check G/L items
ISolved GL Category (DirDep) String DirDep Item Category representing direct deposit G/L items
ISolved GL Category (Earn) String Earn Item Category representing earning G/L items
ISolved GL Category (Impound) String Impound Item Category representing impound G/L items
ISolved GL Category (Invoice) String Inv Item Category representing invoice G/L items
ISolved GL Category (Other) String Other Item Category representing other G/L items
ISolved GL Consolidation by Item Category List None
All
All except Check/DirDep
All except Check/DirDep/Earn
Only Impound/Inv/Other
All except Check/DirDep/Earn Controls consolidation of G/L transactions
ISolved Labor Code String EARN Labor Code to process when importing J/C transactions
ISolved Labor Title (Asset) String Job Asset Labor Title containing J/C Asset Id
ISolved Labor Title (BudCat) String Job Budget Category Labor Title containing J/C Budget Category
ISolved Labor Title (Job) String Job Labor Title containing J/C Job Id
ISolved Labor Title (TrxType) String Job Trx Type Labor Title containing J/C Trx Type

Keystone Security Options

Users must have certain security options enabled to be able to import transactions to the three modules (G/L, C/M and J/C):

  • To import G/L transactions, the General Ledger Active and General Ledger Installed system options must be True.
  • To import C/M transactions, the Cash Management Active and Cash Management Installed system options must be True. Additionally, the user must have security permission for the Cash Management menu.
  • To import J/C transactions, the Job Cost Installed system option must be True. Additionally, the user must have security permission for the Job Cost menu.

Initial Checkout

Once the configuration has been completed on the customer's system, it is important to perform an initial checkout to verify that the configuration has been done correctly.

  1. Start the Import Payroll Transactions option on the General Ledger menu.
  2. A message will indicate that the system is "Loading Payroll Runs."
  3. After this completes, verify that the correct customer's name appears at the top of the screen.
  4. If an error message appears indicating "No Payroll Runs available to import" this means that there are no available payroll runs to import.