Question
I've approved timesheets in Forecast, but they are not appearing in Sage Intacct. Why?
Answer
Timesheets may not sync from Forecast to Intacct if timesheet settings are not configured in alignment with the integration's requirements in either Forecast and/or Sage Intacct.
Common errors that prevent timesheet sync
- Timesheets sync only if their associated project is synced. If a project is not synced, time entries reported against it will not sync.
- User is not assigned to the task they are registering time on in Forecast.
- Timesheet submission frequency is not set correctly in Intacct.
Troubleshooting
First, confirm the projects are synced across platforms. If a project is not synced, the time entries reported against it will not sync.
If projects are synced, next review your Time Management settings in Forecast. If you are not an Admin user, you will need to work with your Forecast Admin to access these settings.
- Check out Syncing Timesheets with Sage Intacct for details on the settings required in Forecast.
To confirm your Forecast settings
- Click Admin in the navigation ribbon.
- Select Time Management from the dropdown.
- Scroll to Time registration settings.
- Review your settings using the image below, ensuring you have all required settings enabled.
If projects are synced, and your Forecast Time Management settings are correct, review your Timesheet settings and Timesheet rules in Intacct.
- Check out Syncing Timesheets with Sage Intacct for details on the settings and rules required in Intacct.
To confirm your Intacct settings
- Log into Intacct.
- From the main menu, select Projects.
- Select Setup, then Configuration.
- Under Configure Projects, expand Timesheet settings.
- In Track time by select Project and task.
- In Timesheet duration, select Weekly.
Additionally, ensure the following timesheet rules setting is selected in Intacct.
- From Projects, select Configure Projects.
- Expand Timesheet rules.
- Scroll down to Enable duplicates.
- Check the box for Lines in a timesheet.
Comments
0 comments
Article is closed for comments.