This page contains technical details for troubleshooting our Acumatica integration, it's recommended that you read the Setup and Feature guides first.
Check the Job History first
If something does not synchronize as expected, open Job History from the Acumatica integration page. Job History gives you a high-level view of recent synchronization jobs. Click the Technical Details button to see more detailed information if an error occurs.
When testing a configuration change, use Run Now instead of waiting for the next scheduled synchronization. This makes it much easier to confirm whether the change resolved the issue.
If a timesheet does not synchronize
Check that:
- The ProjectManager project is linked to Acumatica.
- The task has synchronized to an Acumatica Project Task.
- The task is Active in Acumatica (this can be set automatically).
- The resource is linked to the correct Acumatica employee.
- The timesheet is approved.
- Send Approved Timesheets to Acumatica is enabled.
- The synchronization has run since the timesheet was approved.
If costs do not appear
Check that:
- The project is linked.
- Receive Actual Costs from Acumatica is enabled.
- The Acumatica costs are associated with a Project Task.
- The synchronization has run since the costs changed.
- Your Cost Calculation setting matches what you expect to see.
Remember that Actual Cost Only excludes open commitments, while Committed + Actual includes them.
Set up links before turning on your schedules
When first implementing the integration, link and verify your projects and resources before relying on scheduled synchronization.
A useful approach is to configure one project first, run each synchronization manually, verify the results in both ProjectManager and Acumatica, and then enable your preferred daily, weekly or monthly schedules.
Make changes in the system that owns the information
For the cleanest workflow:
- Manage operational schedules, progress and approved time in ProjectManager.
- Manage accounting transactions, commitments and actual financial costs in Acumatica.
The integration gives each team visibility into the information it needs without requiring both teams to maintain the same information manually in both systems.
Everything was working but now it's stopped
This usually indicates that your Connected Application has expired in Acumatica (by default Connected Applications expire after a certain number of days). We will try and detect this and automatically show a message on the Acumatica Settings screen inside ProjectManager, you'll also see a connection error inside the Job History.
You can also click Settings on the Acumatica screen in ProjectManager to change the Connected Application settings at any time, if a new secret has been created by your IT team for example.