ISolved Keystone Integration - Revision history

Pmorey: /* Keystone System Options */

2025-01-23T21:31:44Z

Keystone System Options

← Older revision		Revision as of 21:31, 23 January 2025
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)~~		\|
	\|		\|
	\|-		\|-

Pmorey: /* Keystone System Options */

2025-01-23T21:31:31Z

Keystone System Options

← Older revision		Revision as of 21:31, 23 January 2025
Line 25:		Line 25:

	For most configurations only two options need to be specified:		For most configurations only two options need to be specified:
	*ISolved API Credentials (~~client_code~~)		*ISolved API Credentials
			::client_code (required)
			::legal_code (required only for multiple Keystone companies with separate payrolls)
	*ISolved Default JC TrxType		*ISolved Default JC TrxType

Line 39:		Line 41:
	\|-		\|-
	\| ISolved API Credentials		\| ISolved API Credentials
	\| client_code		\| client_code<BR>legal_code (see above)
	\| Memo		\| Memo
	\| base_url=<Base URL><BR>~~client_code~~=<Customer Client ~~Code~~><BR>~~client_id~~=<Customer Client Id><BR>~~client_secret~~=<Customer Client ~~Secret~~>		\| 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 ~~Base URL~~><BR>client_id=<GH ~~Client Id~~><BR>client_secret=<GH ~~Client Secret~~>		\| base_url=<GH Customer><BR>client_id=<GH Customer><BR>client_secret=<GH Customer>
	\| (see below)		\| (see below)
	\|		\|
Line 113:		Line 115:
	\|		\|
	\| List		\| List
	\| None,All,All except Check/DirDep,All except Check/DirDep/Earn,Only Impound/Inv/Other		\| None<BR>All<BR>All except Check/DirDep<BR>All except Check/DirDep/Earn<BR>Only Impound/Inv/Other
	\| All except Check/DirDep/Earn		\| All except Check/DirDep/Earn
	\| Controls consolidation of G/L transactions		\| Controls consolidation of G/L transactions

Pmorey: /* iSolved Information */

2025-01-23T21:23:50Z

iSolved Information

← Older revision		Revision as of 21:23, 23 January 2025
Line 10:		Line 10:
	*Client Code		*Client Code
	::There is a spreadsheet containing the client codes for Keystone customers located in Teams under <b>Support Team->General->Files->Payroll->Keystone iSolved Client IDs.xlsx</b>. If the customer is not on this list obtain their Client Code from iSolved and add it to the list.		::There is a spreadsheet containing the client codes for Keystone customers located in Teams under <b>Support Team->General->Files->Payroll->Keystone iSolved Client IDs.xlsx</b>. 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		*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 already on Keystone prior to signing up with iSolved, they will use the GivenHansco URL which is built into the integration.

Pmorey: /* Overview */

2025-01-23T21:22:35Z

Overview

← Older revision		Revision as of 21:22, 23 January 2025
Line 3:		Line 3:
	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.		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.

	<i>This integration requires Keystone 4.7.12 or higher.</i>		<i>This integration requires Keystone 4.7.13 or higher.</i>

	==Configuration==		==Configuration==

Pmorey at 00:56, 23 January 2025

2025-01-23T00:56:50Z

← Older revision		Revision as of 00:56, 23 January 2025
Line 9:		Line 9:
	The first step in configuring the integration is to obtain the following information from iSolved for the customer:		The first step in configuring the integration is to obtain the following information from iSolved for the customer:
	*Client Code		*Client Code
	::There is a spreadsheet containing the client codes for Keystone customers located ~~[https://givenhansco.sharepoint~~.~~com/:x:/s/supportteam~~/~~EQqgxEecLItKm0hwRFfIKroBlyOGxtsHWlnmE8FHfOP_HA?e=wZlJKP here~~.] If the customer is not on this list obtain their Client Code from iSolved and add it to the list.		::There is a spreadsheet containing the client codes for Keystone customers located in Teams under <b>Support Team->General->Files->Payroll->Keystone iSolved Client IDs.xlsx</b>. If the customer is not on this list obtain their Client Code from iSolved and add it to the list.
	*URL		*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 already on Keystone prior to signing up with iSolved, they will use the GivenHansco URL which is built into the integration.

Pmorey at 00:50, 23 January 2025

2025-01-23T00:50:34Z

← Older revision		Revision as of 00:50, 23 January 2025
Line 162:		Line 162:
	*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 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.		*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.

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

Pmorey at 00:45, 23 January 2025

2025-01-23T00:45:29Z

← Older revision		Revision as of 00:45, 23 January 2025
Line 156:		Line 156:
	\|		\|
	\|}		\|}

			===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.

Pmorey: /* Keystone System Options */

2025-01-23T00:38:06Z

Keystone System Options

← Older revision		Revision as of 00:38, 23 January 2025
Line 25:		Line 25:
	*ISolved API Credentials (client_code)		*ISolved API Credentials (client_code)
	*ISolved Default JC TrxType		*ISolved Default JC TrxType


	{\| border="3" cellspacing="0" cellpadding="3"		{\| border="3" cellspacing="0" cellpadding="3"

Pmorey: /* Keystone System Options */

2025-01-23T00:37:30Z

Keystone System Options

← Older revision		Revision as of 00:37, 23 January 2025
Line 23:		Line 23:

	For most configurations only two options need to be specified:		For most configurations only two options need to be specified:
	:ISolved API Credentials (client_code)		*ISolved API Credentials (client_code)
	:ISolved Default JC TrxType		*ISolved Default JC TrxType

	{\| border="3" cellspacing="0" cellpadding="3"		{\| border="3" cellspacing="0" cellpadding="3"

Pmorey: /* Keystone System Options */

2025-01-23T00:37:09Z

Keystone System Options

← Older revision		Revision as of 00:37, 23 January 2025
Line 21:		Line 21:
	===Keystone System Options===		===Keystone System Options===
	There are several system options that must be configured. These options are located under <b>General Ledger->Import Payroll Options</b>.		There are several system options that must be configured. These options are located under <b>General Ledger->Import Payroll Options</b>.

			For most configurations only two options need to be specified:
			:ISolved API Credentials (client_code)
			:ISolved Default JC TrxType

	{\| border="3" cellspacing="0" cellpadding="3"		{\| border="3" cellspacing="0" cellpadding="3"