Closed GoogleCodeExporter closed 9 years ago
Original comment by kris...@nimbustecnologia.com.br
on 6 Nov 2014 at 8:57
As a first iteration on it we added support to import OFX file manually. For
that you should attach an .ofx file on the web and click record.
Original comment by kris...@nimbustecnologia.com.br
on 8 Nov 2014 at 12:08
If the account number or full institution name can be found on account
description, than this account will be used on the import. Otherwise no
account will be defined. For both cases the discovery method runs.
Original comment by kris...@nimbustecnologia.com.br
on 11 Nov 2014 at 3:10
We just released Inbox feature. Now you can bind a Google Drive folder to your
ledger. OFX files saved to this folder will be imported into the ledger. Learn
more:
http://about.bkper.com/guide_inbox.html
Original comment by krishnacaldas
on 1 Dec 2014 at 10:22
Mint and most of other financial control systems actually don't connect
straight to OFX services. They usually uses aggregators API's like Yodlee or
Intuit's services.
The security issues around those kind of services are controversial. They
usually uses non standard techniques such screen scrapping, accessing the
user's online bank account on behalf of user, parsing html, and providing bank
feeds.
We only use secure and standard methods of accessing user's data, such OAuth,
so, we decided NOT to use this kind of strategy to get users data.
To minimize the effort to insert bank data into bkper ledgers, we are investing
in a ways that users can quickly save OFX files to a folder and get them
imported into the ledgers. For first iterations, we provided connection to a
Drive folder and email, putting all connections together in a feature we called
"Ledger Inbox" (http://about.bkper.com/guide_inbox.html). Depending on how
things go, we can also consider connect to a Drop Box folder.
As soon as we go, we will add more processors to other kind of files, based on
users needs.
We will also continue to research standard and secure ways for the user to
insert data, and, if we any financial institution provides connections under,
for example, OAuth2 protocol, we will consider it, otherwise, any techniques
that can expose the user to a minimal risk will be avoided.
I will close this issue now and other needs, like reconciliation, duplications,
file processors and so on, should be filled in each specific issue.
Original comment by m...@nimbustecnologia.com.br
on 2 Dec 2014 at 2:42
I would highly recommend going against the policies that institutions like Mint
hold. Intuit has a poor reputation for handling user data and it reflects on
their products. Unfortunately the financial community is still reluctant to
provide many gateways for third-parties which makes these types of tasks
difficult.
The OFX idea is a step in the right direction. From here I think the direction
should be focused on making it easier for a user to aggregate financial data
without violating their security. A good example would be streamlining the
mobile interface for inputting transactions easily.
Original comment by jmgil...@google.com
on 2 Dec 2014 at 3:22
The financial data aggregation is one of our main goal. We will continue to
invest hard on make the data input easier for user, aways complying with
highest security standards.
One good tip is to connect a drive folder and take advantage of Google Drive
scanning shortcut on Android:
https://support.google.com/drive/answer/3145835?hl=en
By keeping a drive scanning shortcut tied to the folder bound to your ledger
you can scan a image and get it recorded to the Ledger in 3 touchs.
The OCR is not running for pdf's right now, but we are working on it, so we can
start extracting data from images, like amount, and also predict some hashtags.
Original comment by m...@nimbustecnologia.com.br
on 2 Dec 2014 at 3:40
By the way,
We will continue to invest in streamlining transactions entry through our
already running mobile apps (Android, iOS and Windows Phone)
:-)
Original comment by m...@nimbustecnologia.com.br
on 2 Dec 2014 at 3:50
Original issue reported on code.google.com by
jmgil...@google.com
on 8 Oct 2014 at 2:39