Simple plugin for ofxstatement
This is an ofxstatement plugin for Simple JSON statements downloaded from the site. ofxstatement converts the JSON into a series of “check” transactions in an OFX file.
ofxstatement is a tool for converting proprietary bank statements into the OFX format, suitable for importing into GnuCash, Moneydance, and other compatible applications. The plugin for ofxstatement parses a particular proprietary bank statement format and produces a common data structure that is then formatted into an OFX file.
Requirements
As with ofxstatement, this plugin requires Python 3. You will need to have ofxstatement installed; the package will be brought in as a dependency if you install the plugin via pip.
Installation
You can install the plugin via most of the normal Python methods (be sure to install using your environment’s python3 installation). Remove the –user option if you wish to install the package globally.
pip
pip3 install --user ofxstatement-simple
setup.py
python3 setup.py install --user
Configuration
Note that you can specify ‘bank’ and ‘account’ in ofxstatement’s configuration file (accessible using the ofxstatement edit-config command or directly at ~/.local/share/ofxstatement/config.ini (on Linux, at least). Setting these values makes it easier for your personal finance application to recognize which account the file’s data belongs to.
Also note that transactions for zero amounts are filtered by default. If you wish to include zero-amount transactions, set ‘zero_filter’ to ‘false’ in your settings. Here is an example of a settings block for the simple plugin:
[simple] account = 8675309 plugin = simple zero_filter = false
Usage
Export your Simple transactions into a JSON file (it’s currently <date>-exported_transactions.json). Then run:
$ ofxstatement convert -t simple <date>-exported_transactions.json simple.ofx
You can then import simple.ofx into the personal finance application of your choice.
History
0.1.0 (2015-10-11)
Uploaded to pypi
Added to github
Metadata
Release files for ofxstatement-simple 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| ofxstatement-simple-0.1.0.tar.gz | 22.5 kB | Without provenance | Details for ofxstatement-simple-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| ofxstatement_simple-0.1.0-py2.py3-none-any.whl | Python 2, Python 3 | none | any | Details for ofxstatement_simple-0.1.0-py2.py3-none-any.whl |
Total release size: 30.4 kB
Release files / ofxstatement-simple-0.1.0.tar.gz
| Download URL | ofxstatement-simple-0.1.0.tar.gz |
|---|---|
| Size | 22.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d50772c2288ba6530e11fbd49803a24d4871516e1d60272cf2795bdefbcc2177
|
|
BLAKE2b-256 checksum How to use checksums |
645fce707780762ca2038488118cab2488f42ae816d1c5ada116ec8aafccf04d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / ofxstatement_simple-0.1.0-py2.py3-none-any.whl
| Download URL | ofxstatement_simple-0.1.0-py2.py3-none-any.whl |
|---|---|
| Size | 7.9 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
0123c826353387bdf9a9e838da6bda84fadb3de4a1cf3685ef48154575ae661a
|
|
BLAKE2b-256 checksum How to use checksums |
8fc8cbdb6a5f4f21b41b70fa5147d8749244ad32331644bf60640d52bc2ae3b9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for ofxstatement-simple 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.