1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
|
# req-016
As a user, I want, of my purchase of this beer by card in a bank account I have
not set up to sync with Schist, to export it from my bank account in a digital
format and import it into Schist, so that my purchase of this beer is recorded
as a beer transaction.
Source: req-010
Satisfied by: ass-000, ass-014, req-052, ass-025, req-118, req-048, req-123,
req-125
Related to: req-080
## Use case
Trigger: the user buys a beer.
1. Wait until the user next regularly opens Schist on their desktop computer.
2. The user gets their bank transactions and stores them in a CSV file.
3. The user imports the CSV file into Schist.
### Extensions
#### The import misses a transaction
If the import misses out a transaction, this will be obvious the next time the
user reconciles their accounts. Then the user can look again in their bank's
records to track down the error and insert the missing transaction.
#### The import duplicates a transaction
If the import duplicates a transaction, this will be obvious the next time the
user reconciles their accounts. Then the user can look again in their bank's
records to track down the error and delete the duplicate transaction.
#### The import gets the columns wrong
If the import mis-matches the columns, for example, inserting the counterparty
into the description column, then the user can decide whether the error is
critical. If they judge it not to be critical, they can leave it as it is. If
they judge it to be critical, they can instead undo the import. Also, they can
update or delete the erroneous transactions.
|
