Skip to main content

Weighsoft Error: "Token Expired" or "Token Invalid" When Posting to Financials

This article details the steps required to resolve a posting issue where the token has expired

Noel Collings avatar
Written by Noel Collings
Updated over 3 months ago

Overview

The integration between Weighsoft and Financials relies on an API token generated in Evo. This token is essential for account synchronization and posting transactions between the two systems


Key Points

Token Generation and Validity

  • The API token is generated in Evo.

  • Each token is valid for a maximum of 180 days.

Token Expiry and Impact

  • When the token expires, Weighsoft will log an error in Admin > Logs with the message: "Token Expired"

  • Once expired, both account synchronization from Financials and posting to Financials will stop working.


Generate a New Token

Pre-requisites:

  • The user must have the "Administrator" role in Evo for Financials

  • The user must have the "Administrator" role set against the ERP Application Register application in Evo
    ​

  • They must have the "ERP Token Generator" app installed in their Evo Dashboard

Process:

  1. Go to the Token Generator app

  2. Select the token for the Financials product

  3. Click on Regenerate Token

  4. When the token appears onscreen click on the Copy button

    1. Note: do not manually copy it as this will not grab the entire token string

  5. Paste the token string somewhere easy to find (a notepad window for example)

Apply the Token to Weighsoft

  1. Hover on Administration

  2. Click on Lookups

  3. Click on Companies

  4. Go to the company in question

  5. Select the Credit Control tab

  6. Click Clear against Local Path 5

  7. Copy the Token string received from the customer/Evo and past it into Local Path 5

  8. Click Update

Once the above steps are completed posting runs and account syncs will start working again.

If the option to generate the ERP Token or add the Token Generator app is not showing you can try removing and re-adding the "ERP Application Register" role against the user in Evo

Did this answer your question?