After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 128769 - HBCI: Exchange rate silently set to 1
HBCI: Exchange rate silently set to 1
Status: RESOLVED OBSOLETE
Product: GnuCash
Classification: Other
Component: Import - AqBanking
2.3.x
Other All
: Normal major
: ---
Assigned To: gnucash-import-maint
gnucash-import-maint
Depends on:
Blocks:
 
 
Reported: 2003-12-08 01:19 UTC by Ben Bucksch
Modified: 2018-06-29 20:39 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Ben Bucksch 2003-12-08 01:19:07 UTC
Reproduction:
1. Default currency for new accounts is EUR
2. Currency for bank account "dollar" is US-$
3. Set up HBCI for that account
4. Get transactions
5. Select EUR-based income account (e.g. "salary") as far/source account

Actual result:
The income account will have the $-value in EUR. E.g. I received $1000, but
the salary account records 1000 eur. I can fix that by selecting "Edit
exchange rate" for the transaction on the "dollar" account side, but that's
non-obivous and error-prone.

Expected result:
Solution 1:
If the account currency != default currency, add a column "Exchange rate"
(or similar) and "Value [EUR]" (or similar) to the import dialog, so that I
can directly enter the exchange rate. Maybe also add a button to open the
"Edit exchange rate" dialog, if I prefer that.
Solution 2: (worse)
If the HBCI account currency != the currency of the source/far account, pop
up the "Edit exchange rate" dialog somehow.

Severity:
The current way silently leads to wrong account values, without being
obivous that this is the case. Costed me a few hours plus a litte #gnucash
chat to figure out what's wrong and how things should work. Thus, although
edge-case, severity major.
Comment 1 Ben Bucksch 2003-12-08 02:16:35 UTC
-> supposed HBCI maintainer
Comment 2 Christian Stimming 2003-12-09 08:54:32 UTC
In principle, the HBCI import already knows about the exchange rate.
However, this feature is not yet implemented in OpenHBCI. But in the
upcoming openhbci-tng version which is likely to be used in Jan/Feb
next year it will probably be implemented. Then the easiest solution
is to actually use this exchange rate information directly. But it
depends on changes in openhbci.

Solution 1 would require a major GUI overhaul of the importer dialog.
I don't know how this could possibly fit into the window.

For solution 2 it is not quite clear to me at what time this dialog
should pop up. 

And in any case I totally agree that this should at least be clearly
marked somewhere and in some documentation. However, currently no
documentation for the HBCI features exist anyway. I don't have the
time to write it, so somebody else has to, and so far nobody did.

By the way, which (HBCI) bank is this? Some bank outside Germany? This
would be interesting to know.
Comment 3 Ben Bucksch 2003-12-09 09:04:31 UTC
Christian, thanks for replying.

> the easiest solution is to actually use this exchange rate
> information [from the bank] directly.

I don't think there is any. I get a US-$ transfer to a US-$ account.
The currency conversion only happens within the GnuCash accounts, for
internal bookkeeping.

> solution 2

Note that this solution would be very annoying - usually one dialog
per transaction.

> documentation

FWIW, I don't think that documenting it in some help file or tutorial
would make this less severe.

> which (HBCI) bank is this?

Deutsche Bank Privatkunden.
Comment 4 Christian Stimming 2006-08-04 09:17:28 UTC
Issue still exists in 2.0.x and current SVN.
Comment 5 Mark 2012-08-31 22:12:55 UTC
Had this happen today to me as well (2.4.11 under Windows).
Bank account is EUR, expense counter account is USD.
Price for the transaction date in the price editor is 0.7something, but GnuCash used 1.0
Comment 6 John Ralls 2018-06-29 20:39:24 UTC
GnuCash bug tracking has moved to a new Bugzilla host. The new URL for this bug is https://bugs.gnucash.org/show_bug.cgi?id=128769. Please continue processing the bug there and please update any external references or bookmarks.