pydosh
A tool to view and check your bank statements.
About
A simple PyQt UI to manage bank statement records. Records are imported from files in CSV format and stored in a PostgreSQL database.
The main purpose is to rationalise receipts or direct debits against statement records, and each record row has a “checked” column to indicate if the record has been validated. There are numerous filters to use:
checked/unchecked status
account type
money in or out
date filter (last import, date range, particular month)
description field
amount (which also accepts numeric operators, eg “>” “<=”
Accounts
Each bank has a different format for their CSV files. There are 5 pre-insalled formats (ones that I know):
Natwest current account
Natwest mastercard
paypal (use the “Completed Balance” option when downloading)
First Direct
Credit Agricole
To add a new account, select Settings from the toolbar and hit the + button. All you have to do is give it a name and enter the CSV column number that relates to:
date
description
credit amount
debit amount
currency sign, to indicate how debit values are represented (1 if amount is positive, -1 if negative)
date format, which can be built up using the following characters:
d - the day as number (1 to 31)
dd - the day as number (01 to 31)
ddd - day name (‘Mon’ to ‘Sun’)
M - the month as number (1-12)
MM - the month as number (01-12)
MMM - month name (‘Jan’ to ‘Dec’)
MMMM - month name (‘January’ to ‘December’)
yy - the year as two digit number (00-99)
yyyy - the year as four digit number
For example, if a CSV record looks like this:
17/10/2008,C/L,"'BARCLAYS BNK 17OCT",-100.00,1234.20,"'Mr Me","'100001-12345678",
date is 0
description is 2
credit is 3
debit is 3
currency sign is -1
date format is dd/MM/yyyy
Getting Started
You will need a new PostgreSQL database, eg: sudo -u postgres createdb pydosh sudo -u postgres createuser will
Tip: If you need password-less access, you will need to change pg_hba.conf and change the interface authentication from md5 to trust
createdb --host localhost --username bob pydosh
When you first open pydosh, login with a valid postgres account. If pydosh detects an empty database it will initialise all tables for you.
Metadata
Release files for pydosh 2.1
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 |
|---|---|---|---|---|
| pydosh-2.1.tar.gz | 99.9 kB | Without provenance | Details for pydosh-2.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| pydosh-2.1.linux-x86_64.tar.gz | Details for pydosh-2.1.linux-x86_64.tar.gz |
Total release size: 334.7 kB
Release files / pydosh-2.1.tar.gz
| Download URL | pydosh-2.1.tar.gz |
|---|---|
| Size | 99.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a65a20c8bafd9bef1989ecc826af38b7c5afb0bb8a49e3b062e2a0f1ad06d0c3
|
|
BLAKE2b-256 checksum How to use checksums |
755e3996a148c06b2b8429936dc09ec04b52388b34b0ba0e733d7b10d0c9c349
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / pydosh-2.1.linux-x86_64.tar.gz
| Download URL | pydosh-2.1.linux-x86_64.tar.gz |
|---|---|
| Size | 234.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ff54ca8bf2768357fad261cd84aeae3b8be99b133a8700cf9e2f3081dcc495da
|
|
BLAKE2b-256 checksum How to use checksums |
1e99a93c6702138a1a0b1197c7f2a7a0b2ad174537113f8832172d8aec998d5c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for pydosh 2.1
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.