Quickbooks IIF record import mistake – Solved

Quickbooks Payroll Support
Quickbooks Payroll Support

We as of late changed banks. Our.IIF record downloads worked fine from the old bank however we have been having issues with the downloads from the new bank. I have invested a considerable amount of energy attempting to recognize the issue and believe that I may have an idea now. 

  • While downloading the.IIF document we get messages like 
  • error  on line 6: Can’t record invalid exchange and 
  • Error on Line 73: You can’t change the sort of a name or include a copy name. 
  • Toward the finish of the transfer, we end up with ‘two’ new ledgers: 
  • Obscure 
  • 9_____835-Demand Deposit 

The two financial balances show similar aggregates yet one is a negative number and the other a positive. 

In view of my own audit, it appears that there are two issues: 

Two financial balances are being produced rather than one. 

In the. IIF document it would appear that any exchange that has a TRNSTYPE of “Installment” brings about an error  (Can’t record invalid exchange) 

(I feel that I can address the ‘You can’t change the kind of a name or include copy name’ error  message). 

We previously experienced this issue with an organization record that he was working with so chosen to attempt it with a QuickBooks test organization account and ran into a similar issue… so I don’t believe that it’s an issue with the product (QB Premier Ed. 2016). 

bringing IIF records into QuickBooks 2019 

import IIF record into QuickBooks work area 

QuickBooks we couldn’t import at the present time 

  • ; [error] it’s a rundown or exchange that isn’t bolstered by the IIF import process. 
  • incapable to import IIF records into quickbooks 
  • IIF record not bringing in 
  • quickbooks 2019 mistakes 
  • quickbooks 2019 IIF import mistake 

Suggest: if you are facing various QB errors then use Quickbooks file doctor to automatically resolve all kind of QB errors.

These are a portion of the new limitations and bugs, a large portion of which are maintained a strategic distance from when utilizing the suggested strategy above. 

When bringing in time records, QuickBooks may mistake and show that the related worker address is invalid – despite the fact that you are not bringing in changes to the representative. 

  • Import will fall flat if class field esteems on-time records are not dates – yet the class list isn’t a rundown of dates. 
  • The Send Later (email later) status for deal structures is disregarded. 
  • QuickBooks won’t import switch/credit lines on exchanges. For instance, you can’t import an arrival detail on a receipt, a line that diminishes the receipt completely. – this might be fixed. 
  • It won’t import 0.00 sum solicitations (and maybe different deals) regardless of whether the subtleties of the receipt are non-zero. 
  • Record numbers are erroneously restricted to 12 characters however a lot bigger qualities are really permitted in QB. 
  • Telephone numbers on name records are erroneously constrained long which will frequently make the expansion be discarded – while any longer qualities are really acknowledged in QB. 
  • In the event that you endeavor to incorporate a semi-colon (;) on a record in the IIF document, QB quits perusing the line at the semi-colon. In the event that there are required fields from that point forward, the import fizzles. On the off chance that discretionary fields, at that point they are not imported and you will lose information. 
  • On the off chance that you incorporate any characters with a PC ASCII esteem somewhat bigger than a Tilda (~) QB now imports it as a “?” character – while all other QB variants fill in true to form. 
  • Additionally better quality characters past this range. 
  • QB underpins these characters utilizing the old IIF import and the ordinary UI. 
  • This implies no names with European/global characters will work. For instance, René Cresté will import as “Ren? Peak?”. 
  • The accommodated status is overlooked during import. All exchanges are imported as uncleared, which totally vanquishes the utilization of the field. 
  • While the accommodated status is disregarded, QB still checks the qualities and will obstruct the whole import if there is a solitary accommodated status other than Y or N or void. Be that as it may, both IIF and QB bolster a third status, “recently cleared”, the “*” you can find in the register, which is spoken to in IIF utilizing a third character. 
  • Import falls flat in the event that you preclude the client on deals receipt exchanges. And yet QB doesn’t require a client on deals receipt exchanges. You can record them without a name, which is normally done when bringing in the day by day deals exchanges. 
  • When bringing in workers with impeccably designed locations – they are destroyed: the City, State, ZIP fields are copied and entered in the subsequent road address field. 
  • When bringing in a check with no check number (since it isn’t generally a check, for instance, yet a charge or comparable) QuickBooks relegates a check number in any case. – this might be fixed. 
  • Spending records won’t import – QuickBooks gives an error : “It’s a rundown or exchange that isn’t bolstered by the IIF import process.” Which is obviously off-base. 

So finally we have fixed this issue, and if you still getting QB error then you can contact Quickbooks support number. Their trend executives will resolve your errors in a few seconds and you will work smoothly with Quickbooks


Please enter your comment!
Please enter your name here