The Ledger : errors

Help for Error Headaches!

Jennifer Maroney — Tue, 21 Jul 2009 16:16:00 GMT

Are you getting an error and don't know what to do? I found this great post in The User's Edge blog that I wanted to share with you. Check out Sarah's Shortcuts: Lions, tigers, and errors, oh my!

Talk to you soon!

Posting Errors? Check Your Post Dates

Jennifer Maroney — Thu, 01 Jan 2009 12:28:00 GMT

If your fiscal year or period has ended, you may suddenly start receiving errors such as Period Closed or Period Not Found when posting to General Ledger. These errors happen when transactions post to a hard-closed, soft-closed, or an undefined fiscal year. To resolve the error:

Review the Batch Validation or Pre-post Report to find the transactions that failed validation. You can find the exceptions in bold under the problem transaction. If you are posting a journal entry batch, the cursor stops in the date field of the transaction causing the error message.
If the post date is incorrect, change the post date of the transaction to a valid, open fiscal year. In Accounts Payable, if the Post date field is grayed out on a paid invoice, refer to How to edit the post date on a paid but unposted invoice.
If the post date is correct:
1. Verify the fiscal year was created. If it hasn't been created, add the new fiscal year.
2. If the fiscal year exists and is soft closed, reopen the period.
3. If the fiscal year is hard closed, restore to a backup created before the fiscal year was closed or post to an open fiscal period.
  Note: If you restore to a backup, any data entered after the backup was created will be lost.

Happy posting. Talk to you soon!

Check Number in Use Errors?

Jennifer Maroney — Mon, 10 Nov 2008 12:49:00 GMT

You check printing day is going great. Everything balances so you click Create Now and then it happens... Error: Invalid starting check number. AARGGHHH! Even though the error states the starting check number is invalid you know the number is, so what now. When you go to print the checks, the system verifies all numbers in the range are available for use. If any check in the range has already been used you will receive the error message.

OK, so now you know why you get the error, let's find the problem check or checks. To do this, you can either create a query for the check numbers or filter the bank register for the range of checks to be used. These options will only display the numbers that are actually in use.

With the check number in hand, let's get rid of the error. There are a few different options:

If the check was printed incorrectly or out of order, void and purge the check.
If the check was printed incorrectly or out of order, renumber the check.
If the check was printed correctly or you cannot void the check, change the starting check number.

After voiding, renumbering, or changing the starting check number, go ahead and click Create Now. Your checks should print error free; just make sure the correct check stock is in the printer .

Talk to you soon!

The Ledger Lowdown: Avoid Errors When Adding New Accounts

Jennifer Maroney — Thu, 12 Jun 2008 10:45:00 GMT

Error: All segments must have valid values! I'm sure this is an error all of you have see at least once in your General Ledger lifetime. Instead of throwing up your hands when you get this error, follow these steps to fix it and prevent another error in the process.

Verify the account code has been created. If not, you can add it in Configuration or on the fly.
Verify the account code is active:
1. In Configuration, click Tables.
2. Highlight the segment table and open the table entry.
3. Unmark the Inactive checkbox and click OK.
Verify the account code combination is valid:
1. In Configuration, click Account Setup.
2. Highlight Invalid segment combinations.
3. Remove the invalid segment combination.
4. If the segment combination should be invalid, select a different combination when creating the account.

Enjoy adding accounts without errors. Talk to you soon!