Sage 50 US - How to prevent syncing invoices into a Closed Period.

Modified on Thu, 14 Mar 2024 at 11:32 AM

If you followed the Sage 50 US Pre-installation & Connection Guide we asked you to create a specific user for the Sync Tool with either Administrator or Full Access to Sage 50 US.

A problem that this could create for you is that it's possible to sync invoices into a closed period in Sage 50, since the User created has privileges to do so.

You can prevent this from occurring by adjusting the access the User set up in the sync tool.

Log in to Sage 50 US as the Admin and go to Maintain -> Users -> Set Up Security

Select the user which is being used by the Sync Tool and select Edit User's Rights.

Change the selection to Selected Access and press Next.

In the following screen go to Company and scroll to the Task sectionHere change the setting Transactions in Prior Periods to View Only and Save.

This will prevent the user set up in the tool from posting transactions into a closed period in Sage 50 US. 

One very important note: When performing a sync you must be logged in Sage 50 as this user. If you're logged in as another user with different access, it's possible that the user's privileges will override the privileges of the user in the sync tool.
If you're logged into Sage 50 US as the Admin when you perform a sync, the Admin privileges supersede that of the user in our tool. Therefore the transaction could still post into the closed period.

If all is set up correctly you should see the following sync error when an invoice attempts to sync into a closed period. 

The invoice itself in SageAPA will Sync Error, you'll need to resetthe invoice and change the date & due date before you can export and sync again. 

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select atleast one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article