 Posting
transactions
|
| Posting -- the final process to transaction entry in Down To Earth. This
action updates all the necessary files with the proper information needed for reporting, inquiries,
and history for your business. It is an important step and the register that prints is your audit
trail, part of your business' permanent records. |
| What should you do if your post Hangs, your Power goes out, you find Transactions remaining after your post, or you think
you need to Abort a post. |
|
|
|
|
My post seems to be hung up and taking too long, what do I
do?
All posting routines within Down To
Earth require exclusive use of the master records being updated by the
post. If the
posting is taking longer than normal it's most likely because there is another Operator in
an input screen locking a record or file that the post needs to
use.
Have the Operators end out of input screens or
displayed reports to an application menu. Be sure to check multiple "Phantom"
processes or sessions that might have their screen saver on, hiding the
display.
DO NOT kill the post process! Restarting a post can cause duplicate
records. (See the next FAQ.)
Back to top
|
|
|
The power went out during a
post. Can I restart the post from the menu?
Do NOT start the post over via
the Down To Earth menu without verifying the data first. You need to know what did and did not
get posted? Most DTE v7
posting processes can be restarted from the
menu for any application because each transaction carries "flags" that identify if it was
posted. Even so the data should be verified for accuracy after the post is
re-run.
With DTE
v3.5, you absolutely can not restart from the menu
for any application except General Ledger Journal transactions. (G/L journal transactions
may be started over at any time if a transaction post does not finish.) If you
restart from a menu, you may get duplicates in some but not all of your data
files.
There is a log that is generated for each
posting routine. This log tells what program was being run at the time of the power
failure. By adding a "restart" command to that file, you bypass the programs that were
completed successfully and "restart" where it left off.
For complete details, restart format, and the
log filenames for each application post, contact our Software
Support team.
Back to
top
|
|
|
My General Ledger transactions
look like they posted but they still print on the Proof list. Did they really post? And,
how can I get them off the Proof list?
General Ledger transaction posting is unique within Down To Earth for
v3.5 and standard in DTE v7. There are seven “tests” that each transaction must pass
to be posted and/or cleared from the transaction file. Tests such as verifying that the account
number is valid, the transaction date is within a defined fiscal year, and the debits and
credits balance are three examples.
This situation is usually caused by one or more
of the transactions failing a test. Even if some transactions did post,
all records
need to pass all tests to be cleared from the transaction file. If you look closely
at the posting register you should see an error message. If you don’t see it, try posting
again and watch the screen for any error messages that may display.
Once you have found the error and corrected the
problem, you can post again. At this point, only the transactions that did not post
before will post but all transactions in the transaction file will be cleared upon
completion.
Back to
top
|
|
|
Can I abort out of a
transaction posting once it has started?
No . Once a post process has displayed the Printer Option menu column for the
Posting Register, you cannot change your mind - you must proceed with the post. Prior to that,
such as when prompted for General Ledger Account numbers and confirmation, or a Posting date,
the “Exit window” shortcut is allowed and you can safely exit the process.
Back to
top
|
|
Additional assistance is also available from our Technical Support department.
|
