/
NetSuite Troubleshooting & FAQ

NetSuite Troubleshooting & FAQ

Error during Posting transactions to NetSuite Expense or Timesheet Invalid Employee or Project/Job?

This issue whenever the employee or Project/Job is no longer active in NetSuite or it got deleted from NetSuite or it got added manually in DATABASICS.

To fix this issue, please check the following:

  1. Check if the record exists in NetSuite and active and matches the same record in DATABASICS.

  2. Check if the start date or end date of the Job or Employee is outside of the period that a timesheet or expense could be recorded.

 


Error “Please enter value(s) for Cost Category, Department or Class “ when we insert into NetSuite Time Bill, Expense report or Account Payables (Specific related to Vendors) or Journal Entry?

Please check if you have any fields in the Classification section in the expense report if they are required. By default NetSuite uses classifications from the employee record to default the values whenever a report gets created. If the Classification gets customized to require additional fields to be entered for example Cost Category or Class, DATABASICS cannot post transaction that section, the only transactions DATABASICS could post to is the header and detail transactions record but not the Classification that is handled by NetSuite internal calls.

To fix this issue, there should no required fields on the Classification form in Expense Reports, AP and Journal Entry.

Error “Invalid login attempt”?

“Invalid login attempt” is a generic error thrown by NetSuite when there’s something misconfigured in the authentication headers. The best way to troubleshoot this is to use the “Login Audit Trail” search. From there, you should be able to troubleshoot what went wrong with your parameters. It could be that you entered an extra character or blank space to one of your tokens (which is pretty common) or you’re not generating new timestamp or nonce.

To do this, follow these steps from the Help Guide:

  1. Go to Setup > Users/Roles > User Management > View Login Audit Trail.

  2. Check the Use Advanced Search box.

  3. Click the Results subtab.

  4. Add the following fields: Detail, Token-based Access Token Name, and Token-based Application Name.

  5. Click Submit.

    The Detail column displays error messages for any token-based authentication logins with a status of Failure.

Error messages related to Authorization in NetSuite

Please check the articles below, and I believe you have access to them: 


Invalid search query. Detailed unprocessed description follows. Your current role does not have permission to perform this action.

Make sure you have access the List to query in the role and also make sure you have SuiteAnalytics added to Reports in Role. This is especially important for custom fields created by the client.

Manage Roles > Edit > Permissions > Reports:

  • SuiteAnalytics Workbook

Check the following you will need at least these two permissions:

Manage Roles > Edit > Permissions > Setup:

  • Log in using Access Tokens

  • REST Web Services

Manage Roles > Edit > Permissions > Reports:

  • SuiteAnalytics Workbook


For NetSuite, common errors when posting timesheets and expenses to General Ledger (GL) and Accounts Payable (AP) typically result from incorrect configurations, missing data, or permission issues. Below are the most frequent errors and their solutions.

Common GL Posting Errors in NetSuite

Common AP Posting Errors in NetSuite

Common Timesheet Posting Errors in NetSuite

Common GL Posting Errors in NetSuite

Common AP Posting Errors in NetSuite

Common Timesheet Posting Errors in NetSuite

1. "Invalid Account"

  • Cause: The GL account used in the transaction does not exist or is inactive.

  • Fix:

    • Verify that the account exists in the Chart of Accounts.

    • Ensure the account is active and assigned to the correct subsidiary (if using OneWorld).

2. "Period is Closed or Locked"

  • Cause: The accounting period for the transaction is closed or locked.

  • Fix:

    • Either reopen the period (if permitted).

    • Adjust the transaction date to an open accounting period.

3. "Out of Balance Transaction"

  • Cause: Debits and credits do not match.

  • Fix:

    • Ensure that total debits equal total credits.

    • Check for missing account allocations.

4. "Subsidiary Mismatch"

  • Cause: The subsidiary selected in the transaction does not match the subsidiary assigned to the entity.

  • Fix: Ensure that all entities (customer, vendor, employee) are assigned to the correct subsidiary.

5. "Currency Mismatch"

  • Cause: The currency of the transaction does not match the currency of the GL account.

  • Fix

    • Ensure that the correct currency is used.

    • Check multi-currency settings.

6. "Department, Class, or Location Required"

  • Cause: Some GL accounts require additional classifications (Department, Class, Location), but they were not provided.

  • Fix: Ensure required classifications are selected in the transaction.

7. "Vendor Not Found"

  • Cause: The vendor referenced in the expense transaction does not exist.

  • Fix: Confirm that the vendor exists and is active in NetSuite.

8. "Duplicate Vendor Bill"

  • Cause: An invoice with the same number already exists for the vendor.

  • Fix:

    • Change the invoice number or check if the transaction was already posted.

9. "Approval Required"

  • Cause: The invoice or expense requires approval before posting.

  • Fix:

    • Check approval workflow settings and ensure the necessary approvals are completed.

10. "Account Not Set for AP"

  • Cause: The AP account is missing from the vendor record or transaction.

  • Fix: Assign the correct AP account to the vendor record.

11. "Tax Code Missing or Incorrect"

  • Cause: The tax code required for the transaction is missing or incorrect.

  • Fix: Ensure that tax codes are correctly configured.

12. "Exchange Rate Not Found"

  • Cause: The exchange rate for a foreign currency transaction is missing.

  • Fix: Set up the exchange rate or allow NetSuite to auto-calculate it.

13. "Employee Not Found"

  • Cause: The employee submitting the timesheet does not exist in NetSuite.

  • Fix: Ensure the employee is active in Employee Records.

14. "Timesheet Period is Closed"

  • Cause: The payroll or time period is closed.

  • Fix:

    • Adjust the timesheet to an open period.

15. "Invalid Project or Customer"

  • Cause: The project or customer assigned to the timesheet is inactive.

  • Fix: Ensure that the project or customer is active.

16. "Employee Not Assigned to Project"

  • Cause: The employee is not assigned to the project linked to the timesheet.

  • Fix: Assign the employee to the project in NetSuite.

17. "Billing Rate Not Defined"

  • Cause: The rate for the timesheet entry does not match the employee or project billing rate.

  • Fix: Ensure the correct rate is applied in Billing Rate Cards.


Related content

2025 DATABASICS, Inc