One of the photo studio management systems we are taking a look at is Táve Studio Management. Like many software in the marketplace, Táve offers an export capability that imports transactions directly into QuickBooks – that is, when it works.
Táve uses a QuickBooks functionality called IIF import. Actually, Intuit no longer encourages the use of IIF transfers for transaction entries and prefers the use of their SDK software to directly communicate with QuickBooks. The rub here is that many photographers prefer the use of MAC computers – and Intuit SDK does not work with QuickBooks for MAC. So software developers like Táve – who want to support both PC and MAC computers - have no choice but to use the IIF transfer function to import data into QuickBooks.
The truth of the matter is that if set up correctly the IIF transfer does in fact work. That said, however, there are a number of issues surrounding setting up the IIF transfer so that it does work properly. Unfortunately, the IIF functionality in QuickBooks provides very little feedback when something does go wrong. Either the import process simply crashes or the QuickBooks file itself gets corrupted with no explanations.
(NOTE – and I cannot emphasize this strongly enough – ALWAY, ALWAYS, ALWAYS make a backup copy of your active QuickBooks file before attempting any IIF import, whether from Táve or any other software. And always use a test copy of your QuickBooks file to determine if a new IIF import will actually work. NEVER, NEVER, NEVER perform an IIF import into your only working copy of your QuickBooks data file. Be warned that any IIF transfer can fail for a host of reasons – even previously working IIF imports – and you risk permanent corruption of your QuickBooks data file with each import. So, having a previously created backup copy available is an easy way to recover your otherwise lost data.)
One of the issues we found with the Táve IIF export is that the maximum size of the data fields in Táve can be longer than some of the QuickBooks maximum field lengths. What can happen, for example is that the Táve IIF output provides QuickBooks with a list of the Items that are being billed to customers in the current Táve export. QuickBooks reviews the list of Items and adds any that are missing from the QuickBooks Item List before processing the sales transactions.
A mis-match can occur because QuickBooks has a 31 character limit for the Item Name – Táve does not. So if your Item Name in Táve is, let’s say 40 characters long, QuickBooks will automatically truncate that Item Name to 31 characters when setting up a new Item in QuickBooks. Then later in the IIF transfer, Táve sends a sales transaction with the 40 character Item Name. QuickBooks cannot handle the data mis-match and simply crashes the import function.
There are a number of solutions to this, which I have suggested to Team Táve, but I have not heard back from them. In the meantime, the easiest solution for the current Táve users is to simply not exceed the QuickBooks data field character limits when setting up the corresponding fields in Táve. So, for example, if you limit the Item Name in Táve to 31 characters or less and the Customer Name to 41 characters or less, etc. then the Táve-to-QuickBooks IIF transfer has a better chance of working – unless, of course, that is there are other data mis-matches.
You can find the complete list of field character limitations in QuickBooks at http://support.quickbooks.intuit.com/Support/Articles/INF12402. If you keep these field limits in mind when setting up your Táve file, you are less likely to incur some of the IIF transfer problems.