Detailed Listing Report
Question: When I post from the AP module to the Ledger, the reference used in AP "disappears". Is there a way to get more than just the description to import into Ledger so that I can get it to show on the Detailed Listing Report?
For example, when entering invoices into AP, we use the reference box for the PO# and the description for what the item is. Is there a way to get both to import into Ledger?
Answer: To make the fields formatted with a properly 'scannable' bar code font, recent versions of the Adagio Specification Editor, such as for OE or PO, have a setting in the Options / Properties area to select the Bar Code font that you have downloaded and installed on your own. Any fields in a specification that are formatted using this same bar code font will not only have the font display, but also have the appropriate starting and ending characters added to the field value so that scanning it works.Yes, you can send whatever information you want (pretty much) from a subledger to the General Ledger by changing the integration options under Edit | Company Profile. You can find out details in the F1 - Help, or by watching this video, "Adagio Common Features - Send To GL Batches":
https://youtu.be/RTxSFkdO338
Incorrectly Dated Invoices
Question: An invoice (years ago) was posted to the year 2031 incorrectly. An adjustment was made immediately, but the adjustment was dated the current date. When the Open Payables report is run in the current date, the adjustment shows up but not the invoice, so the balance is off. Is there any way to remove these transactions so they don't show up on the report (aside from post-dating the report past 2031)?
Answer: Yes, this can be fixed using GridView Read/Write. However, we don't recommend you do this yourself. Please call us for help instead. GridView Read/Write can compromise your accounting database if it is used incorrectly.
Next time someone mis-dates an invoice, tell them to use a date in the past, not the future. Future mis-dates are really hard to fix.
You can actually prevent this from happening in future at all. Set the Company Profile warning so that the operator is alerted when future dates are accidentally entered. You can find this setting in the Company Profile on the Integration Tab under "Closed periods". Dates for fiscal years not yet opened are considered postings to closed periods and will generate a message.
.range In Financial Statements
Question: I've setup a range in my financial statement and the description I put in was a group description: "Other employee benefits". When the statement is expanded I get multiple lines saying other employee benefits, instead of pension, health etc.. I'd prefer to see the account description for each one when expanded. How can I do that? I know how to get the account description if it wasn't in a range, but how do I do it when I want the range to be called something that isn't part of an account description?
Answer: That's a good question because it shows you understand the benefit of using ranges. In the cell where you currently have the description, enter the following:
=GLDESC("Other employee benefits",3,$Bxx)
Where:
- The 2nd parameter (in this case 3) is the number of spaces that you want to indent the description
- The 3rd parameter points to the cell containing the range of GL accounts - replace xx with the row number (for instance $B12 on row 12)
When you expand the sheet, the individual account descriptions will appear.
Blank Check Stock Numbers
Question: When using blank check stock we have to manually confirm that the cheque numbers have not previously been used and posted in another check run. Is there a setting in Adagio that will have Adagio audit check numbers before printing to blank stock?
Answer: No, there is no such feature.
Instead, I strongly recommend using a different number of digits for your blank stock check numbers. For example 123 instead of 12345. Not only will it avoid duplicates, but when the checks clear the bank it will be obvious which ones were hand-written.
.
You can find more tips like this in the Softrak Technical Support Forum at www.softrak.com, by signing into the Client Portal.
|
New Adagio 9.3 modules have several standard built in features that will be sure to please regular Adagio users. Payables 9.3A, Ledger 9.3A and Purchase Orders 9.3A all shipped this past summer. These are the first modules to adopt new 9.3 features, the best of which are highlighted below.
