(That could have been just keeping up with new features, or a minor tweak to fix a bug - or could have been to slow down defectors and stick it to Quicken to keep up.) Somewhere along the way, the folks at iBank/Banktivity made some change to the structure of their QIF export. While I understand Quicken has no control over what Banktivity does, I feel that if they have a feature to import from Banktivity, then they should look into reports that something changed and that it's not working - or they should remove the claim that they can import from Banktivity if they have consciously decided not to pursue Here's my guess: Quicken wrote a converter for iBank years ago, and it worked. Unfortunately, some support reps may not go that extra mile, and may fall back on the reply from Quicken Anja that Quicken has no control over the QIF export and does not guarantee the results. It should be possible for them to document this and escalate the case to the produce development team. (2) Contact Quicken Support by phone, and ask a support representative to screen share with you to walk through creating a new file from the Banktivity exported QIF to see that the data is not importing correctly. Unfortunately, if the person at Quicken validating the submissions cannot reproduce the problem - which they clearly can't without a current Banktivity data file - they may not investigate it further. You generally will not hear any response to such a bug report, except in rare cases whether they want to reach out for more information. (1) Use the Help > Report a Problem to explain carefully that the import from Banktivity appears to be broken Include in your note that you'd be willing to provide a copy of your Banktivity file to help them with testing. I think you have two possible paths forward: Or if they are, they have decided not to invest resources into keeping up with such updates because their stats show relatively few people are using it. On the Quicken end, my guess is they aren't constantly re-testing this import process, so if something has broken, they're likely not aware of it. Kindly note, for any requests received between 8:00 AM and 6.59 pm on weekdays – (except Sundays & Bank holidays) will be processed on the same day.Here's my guess: Quicken wrote a converter for iBank years ago, and it worked. Once verified, the funds will be transferred in the respective RTGS cycle to the beneficiary Log onto internet banking/ mobile banking appĨ. To transfer funds through our RTGS channels, kindly follow these simple steps:ġ. The time taken to credit the Beneficiary's account will be dependent on the time taken by the Beneficiary's bank to process the payment. All requests received after 7.00 pm above INR 10 lacs, customer account will be debited and request will be processed beginning of next Business day.All Requests received after 7.00 pm below INR 10 lacs will be processed on the same day.Requests received between 8:00 AM and 6:59 PM on weekdays (except Sundays & Bank holidays) will be processed on the same day.Kindly note, you will only be able to make payments through internet banking, if you have a single or unconditional signing authority on your account. Once verified, the funds will be transferred to the beneficiary Click ‘Submit’ and enter in the OTP sent to your registered mobile numberĨ. Select a beneficiary or use our ‘One Time Beneficiary’ option to transfer funds without registering a beneficiaryħ. Enter the amount you want to transfer (must be between ₹1 and ₹20,00,000 only)ĥ. Log onto internet banking/mobile banking appĤ. To complete online money transfers through our NEFT channels, kindly follow these simple steps:ġ.