import iif file

My company is using QuickBooks Pro 2013
Our IT guy is testing to see the vendor payable transaction processed from another software will be imported to the QB and found a couple of unwanted results.  Is there a way to fix these problems?

1. When the vendor name in the import file is slightly different from what it was registered under Vendor Center, it creates a new vendor name in Vendor Center.  We rather have an error message saying "the name is not found in Vendor Center"  or so than registering a new name.  Is there such a function available?

2. When a part of the transactions is not compatible and unable to import, an error message shows up like "line 17 is an invalid transaction" with the pop-up to choose OK or Cancel.  If you choose OK by accident, the rest of the data except for the invalid transaction will be imported.  We want to turn off this function.  Is there any way?
  • Thank you so much for the useful information.  Another question about the iif file is what is the name of the header (ex. DATE, ACCNT, NAME, CLASS, AMOUNT, MEMO) to use in the file if we want to import the reference number to Enter Bill.  If the current template does not have the header for the reference number, is it possible to create one?  If so, how??
Cancel
If you want this sort of functionality you can use a third party tool that uses the QuickBooks SDK.  We have a product that will let you enable an option not to create new vendors plus there is strong validation of your data before you even start the import.  You can request a free trial of our Transaction Pro Importer software and find out more at http://marketplace.intuit.com/AppID-2681-Overview.aspx
    Cancel
    Contribute an answer

    People come to Small Business Community for help and answers—we want to let them know that we're here to listen and share our knowledge. We do that with the style and format of our responses. Here are five guidelines:

    1. Keep it conversational. When answering questions, write like you speak. Imagine you're explaining something to a trusted friend, using simple, everyday language. Avoid jargon and technical terms when possible. When no other word will do, explain technical terms in plain English.
    2. Be clear and state the answer right up front. Ask yourself what specific information the person really needs and then provide it. Stick to the topic and avoid unnecessary details. Break information down into a numbered or bulleted list and highlight the most important details in bold.
    3. Be concise. Aim for no more than two short sentences in a paragraph, and try to keep paragraphs to two lines. A wall of text can look intimidating and many won't read it, so break it up. It's okay to link to other resources for more details, but avoid giving answers that contain little more than a link.
    4. Be a good listener. When people post very general questions, take a second to try to understand what they're really looking for. Then, provide a response that guides them to the best possible outcome.
    5. Be encouraging and positive. Look for ways to eliminate uncertainty by anticipating people's concerns. Make it apparent that we really like helping them achieve positive outcomes.
    Cancel