jaraco.financial implements tools for financial management, particularly around Open Financial Exchange and Microsoft Money. These scripts help facilitate the continued use of Money using the free, sunset release, by enabling mechanical downloads of OFX data from institutions that support OFX.
Getting Started
The primary use of this package is the ofx command. After installing, run ofx –help for usage. Before using the project, you will want to supply institution and account information. See below for details on defining these input files.
This project is still a work in progress, but if you think you might find it useful, don’t hesitate to contact the author for help.
Planned Changes
The author plans to add some of the following features:
Integrate some of the most common institutions.
Accounts File
The “ofx download-all” command of jaraco.financial will retrieve the OFX transactions in a batch for a group of accounts defined in a YAML file. Currently, that file must be located in ~/Documents/Financial/accounts.yaml. The file should be a list of objects, each with institution and account attributes. It should also have a type property of “checking”, “savings”, “creditline”, or other appropriate OFX type. The institution must match exactly an institution as defined below. Here is an example accounts.yaml:
- institution: Bank of America account: "12345679" type: savings - institution: Wells Fargo account: "872634126" type: moneymrkt - institution: Chase (credit card) account: "4000111122223333" username: myusername
The username attribute must be included if the username of the local user (running the ofx command) differs from the account name on the account.
Institutions Definition
Institution definitions can be provided in a YAML format in the file ~/Documents/Financial/institutions.yaml. The following is an example definition for a credit card:
Chase (credit card): caps: - SIGNON - CCSTMT fid: "10898" fiorg: B1 url: https://ofx.chase.com
To check that your institutions are being loaded correctly, use the ofx list-institutions command.
Metadata
Release files for jaraco.financial 2.2.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 |
|---|---|---|---|---|
| jaraco.financial-2.2.0.tar.gz | 23.1 kB | Without provenance | Details for jaraco.financial-2.2.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| jaraco.financial-2.2.0-py3-none-any.whl | Python 3 | none | any | Details for jaraco.financial-2.2.0-py3-none-any.whl |
Total release size: 41.8 kB
Release files / jaraco.financial-2.2.0.tar.gz
| Download URL | jaraco.financial-2.2.0.tar.gz |
|---|---|
| Size | 23.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
202a81c8ccb8a800c5a0eb7dff45b439e6b3e3d5365cdb7370635fb415dfef99
|
|
BLAKE2b-256 checksum How to use checksums |
129c3630cc927bb0dba9d7cb902779d63537525a7ab237aacffb27ebdbcd63f8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.12.1
|
Release files / jaraco.financial-2.2.0-py3-none-any.whl
| Download URL | jaraco.financial-2.2.0-py3-none-any.whl |
|---|---|
| Size | 18.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a184cb60b0dd1647fd178136586437b9dd12ec63f4434004b2afbc60cb5ab141
|
|
BLAKE2b-256 checksum How to use checksums |
7cbe62fcd8a7b6a7c01d9ebb7ff2a4cda6c0343e0a88572abca60a0be612eea0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.12.1
|
Security for jaraco.financial 2.2.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.