Hello Vantage Wise Ones:
We are using Vantage 8.030.407A
Our last payroll run actually posted UnBalanced Transactions to the
Ledger.
Help! Have you ever heard of this? Do you know if any other modules can
do this?
Below is the detail on how the imbalance occurred (yes, we goofed in the
set-up). We fixed it but I want to know:
+ Have you heard of this before?
+ Can other modules post unbalanced accounts to the ledger
+ The check box for "Allow Unbalanced Manual General Journal Entries"
does not stop unbalanced postings from modules. Is there something else
to set which will stop this?
Thanks for comments
Babette Welch
MIS Systems Analyst
1110 Wright Street
Marquette, MI 49855
Phone: 906-226-9747 ext. 229
Fax: 906-226-9779
www.argonics.com
www.kryptane.com
Detail on how Unbalanced posting happened:
Payroll Posting error documentation
1. First indication of problem was when the G/L recap information
did not print on the payroll register.
2. Information Techs were notified and investigated it before
payroll was posted. Tests were run on the test database and it worked
correctly on there, so we just assumed it was a onetime issue and
payroll was posted.
3. The Payroll G/L journal listing was run for that payroll to
obtain the missing G/L account recap info from the payroll register.
The first entry listed had no G/L account no. and the description stated
INVALID ACCOUNT MASTER.
4. Accounting investigated and found that the error was due to a
pay type (Overtime) missing having a Labor expense code set up for a
department/payroll class (Engineering) with an employee who had Overtime
pay. To prevent this from happening in the future, Labor expense codes
were entered for Overtime for all missing departments.
5. Accounting investigated what G/L account the missing overtime
was posted to in order to correct it to the proper account, and found
that Vantage had not posted it at all and our G/L was out of balance by
that amount.
6. To correct this, accounting checked the box in the G/L control
accounts to allow unbalanced entries. A one sided entry was made to the
correct G/L account to correct the G/L. The box was then unchecked
again to not allow unbalanced entries.
The concern/bug is that Human Resources should have been notified when
they originally posted the problem payroll group that there was a
posting error and shouldn't have allowed them to post the payroll until
that Labor expense code was added to correct the problem.
Also, NEVER is posting allowed for UN-Balanced entries.
It is disturbing that Vantage has no error trap for catching UN-balanced
entries.
We are concerned that other modules could have this same issue.
[Non-text portions of this message have been removed]
We are using Vantage 8.030.407A
Our last payroll run actually posted UnBalanced Transactions to the
Ledger.
Help! Have you ever heard of this? Do you know if any other modules can
do this?
Below is the detail on how the imbalance occurred (yes, we goofed in the
set-up). We fixed it but I want to know:
+ Have you heard of this before?
+ Can other modules post unbalanced accounts to the ledger
+ The check box for "Allow Unbalanced Manual General Journal Entries"
does not stop unbalanced postings from modules. Is there something else
to set which will stop this?
Thanks for comments
Babette Welch
MIS Systems Analyst
1110 Wright Street
Marquette, MI 49855
Phone: 906-226-9747 ext. 229
Fax: 906-226-9779
www.argonics.com
www.kryptane.com
Detail on how Unbalanced posting happened:
Payroll Posting error documentation
1. First indication of problem was when the G/L recap information
did not print on the payroll register.
2. Information Techs were notified and investigated it before
payroll was posted. Tests were run on the test database and it worked
correctly on there, so we just assumed it was a onetime issue and
payroll was posted.
3. The Payroll G/L journal listing was run for that payroll to
obtain the missing G/L account recap info from the payroll register.
The first entry listed had no G/L account no. and the description stated
INVALID ACCOUNT MASTER.
4. Accounting investigated and found that the error was due to a
pay type (Overtime) missing having a Labor expense code set up for a
department/payroll class (Engineering) with an employee who had Overtime
pay. To prevent this from happening in the future, Labor expense codes
were entered for Overtime for all missing departments.
5. Accounting investigated what G/L account the missing overtime
was posted to in order to correct it to the proper account, and found
that Vantage had not posted it at all and our G/L was out of balance by
that amount.
6. To correct this, accounting checked the box in the G/L control
accounts to allow unbalanced entries. A one sided entry was made to the
correct G/L account to correct the G/L. The box was then unchecked
again to not allow unbalanced entries.
The concern/bug is that Human Resources should have been notified when
they originally posted the problem payroll group that there was a
posting error and shouldn't have allowed them to post the payroll until
that Labor expense code was added to correct the problem.
Also, NEVER is posting allowed for UN-Balanced entries.
It is disturbing that Vantage has no error trap for catching UN-balanced
entries.
We are concerned that other modules could have this same issue.
[Non-text portions of this message have been removed]