Details of 2 problems discovered with QIW. My client made an error on one of her invoices and went in and changed certain amounts in a line item that does not print on the invoice. As she is from the old school she still does a manual sales book, and noticed that her QIW batch total and her Sales Book Batch total did not match. They were exactly out by the changes she had made previously. After trying numerous things to get the QIW Batch total to match, she decided to Delete/Cancel the offending invoice and enter it again. Still did not balance. If I reactivate this invoice, delete all line items, Totals show nil, but on the main screen still shows a total of the amount our batch is out. (Does this make sense ... it does to me). Hence, I decided to export the batch, and re-import into another batch. This created PROBLEM 2, which I only discovered later. Very interesting. Invoices in the batch dated 23/8/2000 get pulled into Excel as 2/10/2001. This went unnoticed and obviously caused a bit of havoc in AR. I have simulated the problem in my office and it does the same thing. Invoices dated early August go through to Excel fine, but only those on or around 23 August 2000 come through with funny dates.

QIW ver6.5 (990215). Mine was on a standalone notebook, the clients was on a Peer to Peer Windows 98 network.

Any help will be appreciated.

PS : This month similar problem. Made a R300 change. Showed a R300 difference on batch total even though the invoice was cancelled. Reactivate the invoice, change the amount by R10, Cancel the invoice, and the batch total is now R290 out of balance. How can a cancelled invoice effect the batch total ? If you print the batch listing the total is correct .. different from the Batch Total on Batch Summary Screen.

Wayne

Hi Wayne,

We have had a few reports of something similar to this; however it is very rare and in each case the problem could not be duplicated easily. It often has to do with the deleting and re-entering of an item on an invoice. If you have a list of specific steps that can create the error from a brand new invoice batch, please post it here.

If the difference is related to a tax amount, you can edit a specific invoice for the customer tax status to something else, then change it back. When this field is edited, the tax for the invoice is recalculated correctly.

You may also be able to fix this by running the Data Integrity Check, and if the incorrect batch total is found, running the Rebuild function will correct it. If you choose to do this, make sure you back up the data prior to running these functions.

The date problems may be due to your date settings in Windows, or to the original batch total problem. Make sure that the date format for your Windows regional settings uses the YYYY year format.

The date format in Windows is dd/MM/yyyy. I have tried numerous date formats (yyyy/MM/dd; MM/dd/yyyy etc) with each change giving me different dates when I open my exported file in Excel 2000. I tried to export csv format and then reimport into QIW but that too gave me a date format error. To see what info is going into Excel I opened the CSV export file in Word and saw the date field as "000823". (23 Aug 2000 invoice). Is the date format QIW is sending Excel not being interpreted properly ? Any help would be appreciated.

With regards to problem 1 - I will post the steps if I can simulate the problem. Will also try integrity check when I go to the client again.

Hi Wayne,

I'm afraid I can't duplicate this using Adagio Invoices and Excel 2000, exporting an invoice with date 8/23/00 as an xls format file. Are you exporting as an Excel file or a Comma seperated file?

I can only suggest trying with a new invoice batch, as the problems with the batch totals may also be influencing the date issue (ie a corrupted batch).

You may also want to look into getting an upgrade for Quik Invoice for Windows, to either the lastest version or to Adagio Invoices.

Ok, just solved problem #2. My date format is set as dd/MM/yyyy and QIW obviously assumes MM/dd/yyyy. When I changed my date to MM/dd/yyyy and then do the export it comes through fine.

Now lets see if I can find out more on my first problem.

Thanks for the help thus far.