Enhancements & Revisions
Adagio Receivables 6.5A
February 16, 2000
- Dates can now be
entered without the slash "/".
- Paired finder fields were giving an
error when tabbing to the second field (department) if the value was not
correct. This has been corrected.
- Now protects against copying or
moving to an open batch.
- Invoice, cash, and adjustments now send the correct
description info to Quik History.
- Reusing an existing check to relate
unmatched transactions no longer causes an integrity error.
- When re-editing a cash batch
entry where the cash entry has been previously posted, the payment amount is no
longer editable.
- Cash posting was intermittently rejecting balanced entries as being
out of balance and placing the entry in an error batch. This has been
corrected.
- Cash error posting journal report now correctly shows transactions
that have duplicate document numbers.
- Error posting journals can now be
printed even if there were no successfully posted transactions in the posting
sequence range selected.
- Batch status is now correctly set to printed when printing a
range of batches.
- Application of cash to a large number of invoices for open item
customers has been speeded up.
- Editing a cash batch entry with a
large number of details for a customer with a large number of transactions has
been speeded up.
- Distributions with tax included now show 3, 4, and 5 decimal tax rates
correctly when entering invoices.
- Import customers now accepts 2 digit
years in year 2000.
- Interest now ages to the correct bucket on statements in all
cases.
-
When entering a Miscellaneous Cash Receipt, you sometimes received and error
incorrectly indicating the amount had not been totally applied. This has been
corrected.
- When posting a Miscellaneous Cash Receipt with the option set to send
Customer Name to the G/L Description, the description is now
correct.
-
Zero balance statements were not printing in some cases. This has been
corrected.
- Statement page numbers were incorrect in some cases. This has been
corrected.
- Statement specifications with detail lines set to "without matching
details" now print correctly.
- Statements were not ignoring next
months transactions in some cases when printed using the "Aged as of" option.
This has been corrected.
- When a payment is applied during invoice entry, the Job
Costing batch is now correctly updated.
- When a job related invoice included
"Other Charges" and Billings, the Other Charges are now properly broken out
correctly in the JC billing batch.
- When a check paid multiple invoices
where not all invoices were job related, all payments were sent to Job Costing
instead of just the job related payments. This has been corrected.
- When a check paid
multiple job related invoices the payment amount was not distributed correctly.
This has been corrected.
- Retainage invoices with multiple details were causing an
unbalanced GL entry. This has been corrected.
- You can no longer turn off the
retainage option when there is outstanding retainage.
- When Retainage was turned on
you can now print an aged retainage report properly.
- If you used the discount field only
(payment amount is zero) in a manual check to write-off a Balance Forward
transaction, integrity errors are no longer caused.
- Transactions posted for Balance
Forward customers with a credit balance are now being correctly
applied.
-
Posting adjustment entries to a non-existent document for a Balance Forward
customer caused an integrity error. This has been corrected.
- Adjustments, cash and
credit notes are now being correctly applied to transactions with current
balances for Balance Forward customers.
- In normal mode in cash batch entry
for Balance Forward customers, the date fields displayed in the grid are no
longer blanked out as invoices are selected for payment.
- When a debit note is applied
to a series of open invoices for a Balance Forward customer, the invoice current
amounts are now correctly adjusted.
- The date on the Balance Forward line
on the Aged Trial Balance report is now correct in all cases.
- Corrected error
"Invalid argument to date encode" when entering terms using 'specific day of the
month'.
-
Due dates and discount dates for terms using specific day of next month now
support leap years correctly.
© Copyright Softrak Systems Inc. All rights reserved.
|