NetSuite Troubleshooting Guide

Error Text

You do not have permissions to set a value for element is billable due to one of the following reasons: 1) The field is read-only; 2) An associated feature is disabled; 3) The field is available either when a record is created or updated, but not in both cases.

• Kantata Time > NetSuite
• Kantata Expenses > NetSuite

• The Billable time in Kantata OX is tracked to a task marked as Non-Billable in NetSuite. This is not permitted by NetSuite.
• The Billable time is being tracked to a NetSuite project that has no customer.
• When syncing expenses, the Expense category is not mapped in the mapping tables.

For resolution, you may need to complete one or all of the following processes based on circumstance:

1. In Netsuite, locate and select the desired [Project].
2. Manually Add a Customer to the project.
3. Re-emit the Time events.
4. In Kantata OX, Add the Customer Internal ID to the associated [Kantata Project] custom field.
   Tip: Consider changing the Customer Field to be a required field on NetSuite projects to limit this error in the future.

Mark the Task as Billable Instead of Non-Billable 

1. In Kantata OX, navigate to and select the currently Non-Billable [Task].
   Note: The Event Payload contains the workspace_id and the story_id.
2. Select the Billable checkbox.
3. Resync the Task scenario(s).
4. In NetSuite, confirm that the [Task] Billability is updated to Billable.
5. Re-emit the Time Entry event.

Mark the Time Entry as Billable Instead of Non-Billable

1. In the integration platform, use the field information list below to locate and select the desired [Time Entry]:
   • • user_id = User
     • workspace_id = Project
     • date_performed = Date
     • time_in_minutes = Amount of Time
2. Reject the timesheet.
3. Edit the Billability of the time entry to be Billable.
4. Resubmit and Re-approve the timesheet.
5. Resync the Time scenario.
   Note: If the Time Lock setting is active, then you will have to Unlock the time before you can Reject and Edit.

Invalid customer reference key [#######] for employee [#####].

• Kantata Time > NetSuite

For resolution, you may need to complete one or all of the items within the following process based on circumstance:

Ensure NetSuite has the Most Recent Assignments

1. In NetSuite, locate and select the desired [Project].
2. If the [Project] Status is Inactive, confirm if it should be Re-Activated in NetSuite.
   Tip: You may need to Re-Activate the project if necessary.
3. In the integration platform, Re-Run the Project scenario(s).
4. Re-Run the Task scenario(s) to ensure NetSuite has the most recent assignments.
5. Re-emit the event to bring the time entry over.

Invalid customer reference key [#######] for entity [#####].

• Kantata Time > NetSuite

The project that this time entry or expense is being synced to is not yet in NetSuite.

-or-

The project that this time entry or expense is being synced to has been made Inactive in NetSuite.

For resolution, you may need to complete one or all of the following processes based on circumstance:

Ensure NetSuite has the Most Recent Assignments

1. In the integration platform, Re-Run the Task scenario(s) to ensure NetSuite has the most recent assignments.
2. Re-emit the event to bring the time entry over.

Reactivate a Project and Sync to NetSuite:

1. In NetSuite, locate and select the desired [Project].
2. If the [Project] Status is Inactive, confirm if it should be Re-Activated. 
3. Re-Activate the project.

-or-

      If you can't Re-Active the project, confirm that the project should be syncing to NetSuite.

3. Once the project syncs to NetSuite, update the GL Project ID and GL Customer ID fields within Kantata to contain the correct Project and Customer Internal IDs from NetSuite.

Invalid customer reference key [#######] for subsidiary [#####].

• Kantata Project > NetSuite

For resolution, you may need to complete one or all of the following items within this process based on circumstance:

Confirm Information in Kantata Custom Fields

1. In Kantata, confirm that the custom fields containing the Customer ID and the Subsidiary have correct values. If not, Add the desired [Subsidiary].
2. In NetSuite, confirm that the customer has the correct [Subsidiary] assigned. If not, Add the desired [Subsidiary].
   Note:

   If you make a correction in NetSuite, you may need to Re-emit the event. 

   -or-

   If you make a correction in Kantata, you must Resync the Project scenario after updating the Kantata project.

Invalid jobresource reference key [#######].

• Kantata Projects > NetSuite

For resolution, complete the following process:

1. In NetSuite, locate and select the desired [Employee Record].
2. Select the Human Resources tab.
3. Check the Project Resource checkbox.
4. Save the record.
   Note: Ensure that the employee associated with the Employee Record does not have a <null> Labor Cost.

• Kantata Tasks > NetSuite

For resolution, you may need to complete one or all of the following processes based on circumstance:

1. In NetSuite, locate and select the desired [Employee Record].
2. Select the Human Resources tab.
3. Check the Project Resource checkbox.
4. Save the record.

Resync and Re-emit the Project Exceptions

1. Within NetSuite, locate and select the desired [Project].
2. Confirm that the correct Resource is on the project. If not, Edit and update it.
3. Resync the Project scenario or locate and Re-emit the Failed Project event.
   Note: You may need to locate the Failed Project event(s) and Resolve it before Resyncing or Re-emitting the Project events.

4. Under the Preferences subtab, confirm that the Display all resources for project task management is checked.
   Note: You can enable this setting if the box is unchecked:

   1. Edit the project.
   2. Check the Display all resources for project task management checkbox.
   3. Select Save.
   Note: If you use Project Allocations in NetSuite, you will need to check the Allow allocated resources to enter time to all tasks checkbox as well.

5. Re-emit the failed Task event.

• Kantata Tasks > NetSuite

The project in Kantata has the GL Project ID field filled out incorrectly. 

-or-

The NetSuite project was deleted or its status is Inactive.

This means that the Task scenario is trying to update a task that is on the deleted or inactivated project.

For resolution, you may need to complete one or all of the following processes based on circumstance:

1. In NetSuite, locate and select the desired [Project].
2. Confirm that the Project Status is Inactive and that this is the correct project to link with the Kantata project.
   Note: If it is not the correct project, it is recommended to Delete the incorrect project from NetSuite.
   Note: If a new project has already been created, ensure the custom field holding the Kantata Project ID in NetSuite has the correct Workspace ID.

Confirm Kantata Project Details

1. Within Kantata, locate and select the desired [Project].
2. Find the GL Project ID custom field and confirm that it matches the desired Project Internal ID from NetSuite.
3. Ensure the Customer Status in NetSuite is Active.
4. Ensure the customer in NetSuite has Subsidiary as an available selection on the project within Kantata.

• Kantata Tasks > NetSuite

For resolution, complete the following process:

Verify and Enter Labor Cost Fields Across Software

1. When this error appears, select the View option that appears next to the message. A list of Task events appears. 
2. Select [Event] located to the right of the Task events. The Event Payload window appears.
3. Locate the assignee_names and their corresponding Task Assignees at the bottom of the screen.
4. Corroborate these Employee Records with NetSuite by ensuring they all have a Labor Cost under the Human Resources tab.
   Note: If the Labor Cost is not used or not necessary in NetSuite, you can set the field to the amount of $1.00.

• Kantata Projects > NetSuite
• Kantata Time > NetSuite
• Kantata Tasks > NetSuite

For resolution, you may need to complete one or all of these processes:

If the Location Doesn't Need to be Mandatory

1. In NetSuite, locate and select the desired [Form].
2. Edit and update the form to Remove the Location Field Requirement.
3. In NetSuite go to Accounting Preferences.
4. Select Remove next to the Location Field Requirement to remove it system-wide.

If the Error is on a Timesheet or Expense Report

1. In NetSuite, locate and select any [Employee Record].
2. Find the Location field and ensure it is set and updated within the record. The Location field can be inherited from here.
3. Go to Setup > Company > Locations and ensure the expected Location is not Archived.
4. Re-emit the event.

If the error is on a NetSuite Invoice 

1. In NetSuite, locate and select the desired [Invoice].
2. Find the desired item and Add the desired Location. The Location field can be driven by this item.
3. Re-emit the event.

No users mapping for Kantata ID [#######]

-or-

Kantata users [#######] are not mapped to NetSuite users.

• Kantata Projects > NetSuite
• Kantata Tasks > NetSuite
• Kantata Time > NetSuite
• Kantata Expenses > NetSuite

Potential Cause

For resolution, complete the following process:

Update Valid User Mapping in Kantata

1. Enter the following link into your web browser to navigate to the desired [Kantata User]: https://app.mavenlink.com/profiles/######
   Note: Replace the "######" portion of the link with the ID numbers that are displayed within the integration platform error. This takes you to the profile of the member causing the error.
2. Edit and update the User Mapping Table to include the missing [User].
3. Ensure the missing [User] is mapped to an active [User] within NetSuite.
4. Re-emit the failed event.
   Note: If the user identified is not a member of your Kantata Account, the URL may take you to a Private Profile page.

• NetSuite Projects > Kantata
• NetSuite Employee Expenses > Kantata

A NetSuite Employee is not mapped to a Kantata user.

-and/or-

A client is using Generic Resources in NetSuite.

For resolution, you may need to complete one or all of the following processes based on circumstance:

Find and Update Valid User Mapping in NetSuite

1. In NetSuite, locate and select any [Employee Record].
   Note: Replace the numbers in the "id=?####" portion of the link with the ID Number(s) found in the error message. This will take you to the employee identified.
2. Edit and update the User Mapping table in the integrations platform.
   Note: If an employee doesn't exist under the ID Number, the record may have been deleted from NetSuite or considered a Generic Resource on the project.

Update the Generic Resources in NetSuite

1. Within NetSuite, go to Lists > Employees > Generic Resources > List.
2. Select any [Resource] and replace the ID [Number] in the URL with the [ID Number(s)] found in the error message.
   Note: If Generic Resources can be removed from the NetSuite project without issue, please do so.
   Note: If Generic Resources are no longer needed in NetSuite, consider disabling the feature.
   Note: You can Ignore or Dismiss this error because Generic Resources will not be synced by the integration.

• Kantata Invoice > NetSuite

For resolution, you may need to complete one or all of the following items based on circumstance:

• The Subsidiary Project Level custom field in Kantata may have been changed after project creation. Ensure it matches with NetSuite.
• Ensure that all Subsidiary fields match between Kantata and NetSuite projects.

• Kantata Projects > NetSuite
• Kantata Tasks > NetSuite
• Kantata Time > NetSuite
• Kantata Employee Expenses > NetSuite

For resolution, you may need to complete one or all of the following items based on circumstance:

If the NetSuite Employee Status is Active

1. In NetSuite, locate and select the desired [Employee ID] indicated by the [#] found in the NetSuite error.
2. Edit and update that Employee Record and Re-Activate it. 

If the NetSuite Employee Status is Inactive

1. In the integration platform, locate the User Mapping Table used by the scenario.
2. Edit and map the desired [Kantata User] to an active NetSuite employee.
   Note: It is recommended that Inactive employees remain on the User Mapping table to reduce these errors, as they remain on their previous projects and tasks in Kantata.

• Kantata Projects > NetSuite

The Subsidiary custom field on the project in Kantata is blank.

-or-

The Kantata Project Currency doesn't match the NetSuite Subsidiary Currency.

-or-

The project was synced with [X] currency to a customer that didn't have [X] currency assigned to them as an available currency.

For resolution, complete the following process:

Resync the Project to NetSuite

1. Within Kantata, locate and select the desired [Project].
2. Edit and correct the Subsidiary custom field.
3. Resync the Project scenario.
   Note: If the desired Subsidiary is missing from the custom field, you will have to Add it to the Subsidiary Mapping Table on the integration platform.
   Note: If the project doesn't sync to NetSuite, this Exception/Event can be dismissed.
   Tip: Consider using a Project Filter—like a Status or Custom Field—to avoid generating Exceptions for projects that are not intended to sync.

An employee in NetSuite doesn't have a valid Labor Cost on their Employee Record.

-or-

The status of the NetSuite Employee Record is Inactive.

For resolution, complete the following process:

Verify the Employee Record and Labor Cost Fields

1. In NetSuite, navigate to any [Employee].
2. Replace the numbers in the URL after “/employee.nl?id=” with the ID Number from the error in the integration platform. This loads the target [Employee Record].
3. Confirm the [Employee Record] Status is Active. With this status, you can now verify the Labor Cost field.
4. Within NetSuite, navigate to the Human Resources subtab.
5. Confirm that the amount in the Labor Cost field is correct. Edit and update if necessary.
6. Confirm that the Project Resource checkbox is checked. Edit and check the box if necessary.
7. Re-emit the failed event.

• Kantata Invoices > NetSuite

The GL Task Item ID custom field may be blank for one or more tasks on an invoice.

-or-

The Subsidiary custom field is blank on the workspace.

For resolution, complete the following process:

Update the Empty Fields within the Invoice

1. Navigate to the failed [Invoice], and note the tasks that are being invoiced.
   Note: The Invoice Number will be under the Event Payload.

2. Edit and update the tasks that do not have a valid GL Task Item ID selection on the custom field.
3. In Kantata, Edit and update the invoice with a minor change.
   Example: Edit the invoice and update it with a trivial change, such as adding a period to the end of the memo.

4. Save the invoice.
5. Resync the invoice.

{"errors"=>[{"type"=>"system", "message"=>"Not found"}]}

-or-

{"errors"=>[{"type"=>"system", "message"=>"Not found"}]}

-or-

Not Found.

• Error when creating a Local Record for an Existing Time Bill.

For resolution, complete the following process:

Update the Empty Fields within the Invoice

1. Find the Workspace_ID that is contained within the Event Payload.
2. Use the Workspace_ID to locate and select the desired [Workspace].
3. Sync the data.
4. If the Exception data syncs:

Unarchive the Workspace and Re-emit the event.

-or-

If the Exception data doesn't sync:

Dismiss this error.

For resolution, complete one of the following processes based on circumstance:

If the [Expense Category] selected in NetSuite is correct

1. Edit and update the Expense Category Mapping Table to map it to a [Kantata Expense Category].
2. Re-emit the event.

-or-

If the [Expense Category] in NetSuite is incorrect

1. Edit and update the [Expense Category] on the vendor bill or expense report.
2. Resync the scenario.

Potential Cause

For resolution, complete the following process:

1. Edit the Kantata [Project Title], and reduce the number of characters to be less than 83.
2. Resync the scenario.

The Kantata custom field designated to hold the NetSuite Project ID has the incorrect Project ID.

For resolution, complete the following process:

1. In Kantata, Edit and update the custom field with the correct NetSuite Project ID.
2. Resync the Scenario.

For resolution, complete one of the following processes based on circumstance:

If the Subsidiary Custom Field on the Kantata Project is correct:

1. In Kantata, Edit and update the Mapping Table to map the Subsidiary to an active NetSuite subsidiary.
2. Re-emit the scenario.

-or-

If the Subsidiary Custom Field on the Kantata Project is incorrect:

1. In Kantata, Edit and update the Subsidiary custom field to the correct choice.
2. Resync the scenario.

For resolution, complete one of the following processes based on circumstance:

If the Role within Kantata is correct

1. In Kantata, Edit and update the Sale Item Mapping Table to map the [Role] to an active NetSuite service item.

-or-

If the Role within Kantata is incorrect

1. Reject and then Edit the time entry to have the correct [Role]. 
2. Resubmit and Approve the scenario.
3. Resync the scenario.

For resolution, complete one of the following processes based on circumstance:

If the Category of the NetSuite Transaction Line Syncs to Kantata

1. Edit and update the [Category] chosen on the line level of the transaction to include a Category.
   Tip: Ensure that the Category is mapped on the Expense Category Mapping Table on the integration platform.

-or-

If the Category of the NetSuite Transaction Line Doesn't Sync to Kantata

1. Edit the Transaction line and Remove the project from the Customer: Job field.

-or-

1. Dismiss this event if the Transaction line has a project associated with it in NetSuite.

Please enter value(s) for: Client

-or-

Please enter value(s) for: Subsidiary

For resolution, complete one of the following processes based on circumstance:

If the Project Doesn't Sync to NetSuite

1. In Kantata, locate and select the desired [Workspace].
2. Edit and update the custom fields for Client ID and Subsidiary.
3. In NetSuite, ensure the Customer Status is Active.
4. Ensure that the associated NetSuite Subsidiary is mapped on the Subsidiary Mapping Table on the integration platform.

-or-

If the Project Syncs to NetSuite

1. Dismiss this event.
   Tip: Consider using a Project Filter—like a Status or Custom Field—to avoid generating events that are not intended to sync.

Please enter value(s) for: Department, Location.

-or-

Please enter value(s) for: Class.

For resolution, you may need to complete one or all of the following processes based on circumstance:

Verify Mapped Details on NetSuite Employee Record

1. In NetSuite, locate and select the mapped [Employee Record].
2. Ensure that the Location, Department, and Class field information is correct.
3. Ensure the chosen segment—Location, Department, or Class—is not Inactive. This means it appears as a valid choice for the Subsidiary of the project within Kantata.

Setting the Location and Department Segments as Not Required

For resolution, complete one of the following processes based on circumstance:

If the Time Entry Role is Correct

1. In the integration platform, Edit the Sale Item Mapping Table to map the Role to an active service item in NetSuite.

-or-

If the Time Entry Role is Incorrect

1. In the integration platform, use the field information list below to locate and select the desired [Time Entry]:
   
   • • user_id = User
     • workspace_id = Project
     • date_performed = Date
     • time_in_minutes = Amount of Time
2. Reject the timesheet.
3. Edit the Role to be a Mapped Role.
4. Resubmit and Re-approve the timesheet.
5. Resync the scenario.
   Note: If the Time Lock setting is Active, then you will have to Unlock the time before you can Reject and Edit.

For resolution, you may need to complete one or all of the following items based on circumstance:

• If the Total Transaction Amount in NetSuite is positive, consider combining the negative line with a positive line of greater value and then use the Net Amount for the Total Amount on that line.
• You can keep the positive and negative lines separated in NetSuite. However, you can then Edit the positive line that synced to Kantata to be the Net Total of the 2 lines.

Potential Cause

This NetSuite error occurs when the same employee in NetSuite is being added to the same project twice.

-and/or-

This error most often occurs when 2 different users in Kantata are mapped to the same employee in NetSuite on the User Mapping Table.

For resolution, complete the following process:

Review and Manage Users

1. In the integration platform, review the User Mapping Table and ensure that each Kantata Employee is mapped to only one NetSuite Employee.
2. In Kantata, locate and select the desired [Workspace].
3. Remove any duplicate users or users that do not belong within that workspace.

Billable time in Kantata is tracked to a task marked as Non-Billable in NetSuite.

-or-

Billable time is being tracked to a NetSuite project that has no Customer.

-or-

When syncing expenses if the expense category is not mapped in the mapping tables.

For resolution, you may need to complete one or all of the following processes based on circumstance:

If the NetSuite Project has no Customer

1. In NetSuite, locate and select the desired [Project].
2. Manually Add the desired [Customer] to the project.
3. Re-emit the Time events.
4. In Kantata, Add the Customer Internal ID to the project custom fields.
   Tip: Consider making the Customer Field a required field on the NetSuite project to limit this error in the future.

If the Task is Billable Instead of Non-Billable

1. In Kantata, locate and select the desired [Task].
   Note: The Event Payload contains the workspace_id and the story_id.
2. Edit the task and check the Billable checkbox to change the task's Billability.
3. Resync the Task scenario.
4. Once the task has been successfully updated in NetSuite, Re-emit the Time Entry event.

If the Time Entry is Non-Billable Instead of Billable

1. In the integration platform, use the field information list below to locate and select the desired [Time Entry]:
   • • • • user_id = User
         • workspace_id = Project
         • date_performed = Date
         • time_in_minutes = Amount of Time
2. Reject the timesheet.
3. Edit the time entry, and change the Billability to Billable.
4. Resubmit and Re-approve the timesheet.
5. Resync the Time scenario.
   Note: If the Time Lock setting is Active, then you will have to Unlock the time before you can Reject and Edit.

Time entries of a Kantata user are syncing to a project in NetSuite that is not the same subsidiary listed as the NetSuite employee.

For resolution, you may need to complete one or all of the following processes based on circumstance:

If the Employee Subsidiary Must Change in NetSuite

1. In NetSuite, locate and select the currently mapped [Employee]. The Employee Record appears.
2. Edit and set the Employee Record Status to Inactive.
   Warning: NetSuite Employee Subsidiaries can't change after their initial creation.
3. Create a new Employee Record with the correct subsidiary.
4. Add relevant or required information to the Employee Record.
5. Edit and update the User Mapping Table in use by the Time scenario to map the desired [Kantata User] to the new NetSuite Employee Record.
6. Re-emit the Time Entry event.

If the Project Subsidiary Must Change - Kantata Originating System

1. In NetSuite, locate and select the desired [Project].
2. Delete or set the [Project] Status to Inactive if Kantata is the originating system.
   Warning: NetSuite Project Subsidiaries can't change after their initial creation.
3. In Kantata, Clear the custom field for the NetSuite Project ID.
4. Edit and update the Subsidiary custom field to the correct subsidiary.
5. Resync the Project scenario.

-or-

If the Project Subsidiary Must Change - NetSuite Originating System

1. In Kantata, locate and select the desired [Project].
2. Delete or Archive the current Workspace of the project if NetSuite is the originating system.
3. In NetSuite, Delete or set the [Project] Status to Inactive.
4. Create a New Project with the correct subsidiary.
5. Resync the Project scenario.

For resolution, you may need to complete one or all of the following processes based on circumstance:

If the Task Status is Completed

1. In Kantata, locate and select the desired [Task].
2. Set the Task Status to Started or Not Started.
   Tip: When the Task scenario syncs again, it will re-open the task in NetSuite. This allows Time events, once Re-emitted, to Sync to NetSuite.
3. In the integration platform, Re-emit the Time event.
4. Resync the Task scenario.
5. In NetSuite, locate and select the desired [Task].
6. Edit and manually update the Task Status from Completed to Not Completed.
   Tip: The Task Status can be changed back to Completed if no more time is tracked to it.
7. Re-emit the Time event.
   Tip: Consider editing the task to no longer sync the Task Status to NetSuite. This allows tasks to be completed in Kantata and remain open in NetSuite for time syncing.

If the Employee is not Assigned to the Task in NetSuite

1. In the integration platform, ensure the Task scenario has run and that the event containing the task has not failed.
2. In NetSuite, ensure the employee has the Labor Cost field filled out.
3. In NetSuite, ensure the Task Status is not Inactive.

• Kantata Tasks > NetSuite

For resolution, you may need to complete one or all of the following processes based on circumstance:

Mark the Project as Active

If the task needs to be synced, the project must be marked as Active.

1. In NetSuite, locate and select the desired [Project].
2. Edit and update the [Project] Status to Active.
3. Re-emit the event.

-or-

Dismiss the Event

1. In NetSuite, locate and select the desired [Project].
2. Review the Project details. If the Project Status is Inactive and does not need to be updated, you can Dismiss the event.

• Kantata Invoices > NetSuite
• Kantata Projects > NetSuite

For resolution, complete the following process:

Verify and Update Information in NetSuite

1. In NetSuite, go to NetSuite Logs > Payload Request.
2. Verify that the GL Customer ID, NetSuite Project ID, GL Task Item ID, and other information fields are correct.
   Tip: If there are any inaccuracies within the Payload Request, you can Edit and update the information within the NetSuite Logs to be accurate.
   Tip: The Customer ID field specified on the Invoice scenario must be the Numeric Internal ID of the NetSuite Customer.
   Note: The creation of NetSuite Workflow is interfering with the NetSuite integration.

• NetSuite Projects > Kantata

For resolution, complete the following process:

Verify and Turn On the Multi-Currency Feature

1. In NetSuite, go to Setup > Company > Enable Features.
2. Check that the Multi-Currency Feature is turned on in Netsuite.
   Tip: Select the Multi-Currency Feature checkbox to enable this feature if it is not checked.

• Kantata Tasks > NetSuite

For resolution, complete the following process:

Disable the Planned Work Feature

1. In NetSuite, go to Setup > Company > Enable Features.
2. Within this page, go to the Company tab located under Projects. 
3. Locate the Planned Work checkbox. You can disable this feature by unchecking the checkbox.
   Warning: Review and consider disabling this option if it is checked and the feature is enabled. While this may resolve the Planned Work Error, it will also disable the feature on the client account.

• Kantata Time Entry > NetSuite
• Kantata Invoice > NetSuite

This is likely a problem with the item in the Sale Item Mapping Table. The item that the integration is trying to add to the time entry when it's creating the record is not allowed in the subsidiary that the project—or employee—is in.

-or-

The Time Entry line item needs to be mapped to a Service for Sale. NetSuite items that are labeled as Service for Purchase are unable to be used in this case.

For resolution, you may need to complete one or all of the following items based on circumstance:

• Have the Client locate and verify the details of the [Sale/Service Item] within NetSuite:
  • Ensure that the item is available for the project's subsidiary.
  • Ensure that the subsidiary associated with the NetSuite project and the Employee Contact Record matches.

• NetSuite Users > Kantata

Potential Cause

Resolution

For resolution, you may need to complete one or all of the following items based on circumstance:

If the User Needs to be Added to the Kantata Account

1. In Kantata, go to Settings > Members. The Members Page opens.
2. Locate and Invite the desired [User]. 

If the User was Removed from the Kantata Account

1. In Kantata, go to Settings > Members. The Members Page opens.
2. Locate and Re-Invite the desired [User]. 

-or-

1. In Kantata, go to the Admin Panel.
2. Locate and Consolidate the desired [User].

If the User Needs to be Verified in a Kantata Account History

1. In Kantata, go to the Admin Panel.
2. Locate and verify if the desired [User] exists within the system.
3. Select and Consolidate the desired [User] into the Kantata account.

• Kantata Invoices > NetSuite

Potential Cause

There is a paid invoice associated with the event within NetSuite, but no Kantata Invoice ID is associated with it. The event is created but it should not be.

For resolution, complete the following items:

• Ignore and Dismiss the Event.
• Note down the Kantata Invoice ID that is associated with the event for the next time this occurs.

• Kantata Vendor Expense > NetSuite Vendor Bills

Potential Cause

For resolution, complete the following items:

• Edit and update the Expense Category Mapping so that each Expense Category is mapped to a unique NetSuite Expense Category.

• Kantata Time Reports > NetSuite Timebills

Potential Cause

For resolution, complete the following process:

Edit the Time Entry Role for the Time Entry

1. In the integration platform, use the field information list below to locate and select the desired [Time Entry]:
   • user_id = User
   • workspace_id = Project
   • date_performed = Date
   • time_in_minutes = Amount of Time
2. Reject the timesheet.
3. Edit the Role to be a Mapped Role.
4. Resubmit and Re-approve the timesheet.
5. Resync the Time scenario.

• Kantata Projects > NetSuite

Potential Cause

For resolution, you may need to complete one or all of the following items based on circumstance:

If the Kantata Project Currency is Incorrect

1. In Kantata, locate and select the desired [Project].
2. Update and Revert the desired project’s Currency to match the current NetSuite project’s currency.

-or-

1. In NetSuite, locate and Delete the desired [Project]. 
2.  Resync the Kantata project to create the project with the correct currency.