![]() ![]() If it has already been used, you must skip ahead one number.Ĭommon Posting Errors & Fixes in General Ledger (GL Error Batch) Normally when the system makes a "New" document, it is using the next sequential number. It's possible that someone had entered a manual document number in the past. Go to Options and change the Next Number for the document that you are getting the error to the next sequential number. If so, and you still get this error, there is a problem with the ARCUS table that needs to be checked by your partner.Įveryone must exit the module that you are getting the error for. Customer number is inactiveĮnsure that the Customer is set to Active. Instead the tax is calculated using the selling price which is incorrect.Ĭannot process document. When the invoice is sent to A/R from O/E, the tax calculation is off for the base price. ![]() The error occurs when a tax authority is set to use standard cost and an item is set to a unit price of $0 in an order. Total Amount of Details Does Not Equal Total Amount of Invoice Error Is Received These are some of the most common errors and fixes for Sage 300 accounts receivable. Review the entry, taxes, and totals to find the discrepancy.Ĭommon Posting Errors & Fixes in Accounts Receivable Net invoice amount is not equal to the net distributed amount for batch xxxx, entry xxx If not, you can add a letter/number at the end of the invoice which will still help you to identify the payment to that invoice. Review whether you are duplicating the entry. You have already used that Invoice number for that vendor. ![]() If so, you will need to go to Common Services, Fiscal Calendar to unlock/activate the year. Review entry to confirm that you are posting to the correct year. These are some of the most common errors and fixes for Sage 300 accounts payable. The Posting Errors report can be found where the Transaction Reports are located for accounts payable, accounts receivable, and general ledger (for G/L it is simply called the Posting Journals Report located within G/L Reports).Ĭommon Posting Errors & Fixes in Accounts Payable This should be your 1st check for any batches that don’t post due to an error. The best way to troubleshoot and find out is to print a Posting Errors Report. Perhaps you’re trying to post a transaction to a locked period or entering an invoice that has already been entered. Here’s a breakdown of some common Sage 300 posting errors and how to fix them. GL Error Batch), accounts receivable, or accounts payable. If you’ve been using Sage 300 (formerly “Accpac”) for a while, at some point you’ve probably experienced a posting error message, whether it be posting to the general ledger (ex. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |