AqBanking

30.07.2022

22:58 Bug #262: SWIFT 940 parsing substitutes wrong entry date if the :61 field contains none.

Martin,
> I think the OFX importer is not very usefull to Gnucash because 1) you have your own OFX importer which ... jralls@ceridwen.us

22:45 Bug #262: SWIFT 940 parsing substitutes wrong entry date if the :61 field contains none.

John,
>But to the original point of this bug: SWIFT MT940 specifies that there must always be a value date while t... martin

20:00 Bug #262: SWIFT 940 parsing substitutes wrong entry date if the :61 field contains none.

Martin,
Martin,
> That's the whole purpose of AqBanking's import/export interface...
Good. I hoped so, thanks ... jralls@ceridwen.us

11:08 Bug #262: SWIFT 940 parsing substitutes wrong entry date if the :61 field contains none.

John,
>The question about various SWIFT profiles plus adding CAMT is from the AQBanking API side. Once the import ... martin

05:09 Bug #262: SWIFT 940 parsing substitutes wrong entry date if the :61 field contains none.

The question about various SWIFT profiles plus adding CAMT is from the AQBanking API side. Once the import is parsed ... jralls@ceridwen.us

02:43 Bug #262: SWIFT 940 parsing substitutes wrong entry date if the :61 field contains none.

>BTW, aside from matching the profiles with what Gwenhywfar knows about nearly all of the code that converts AQB in... martin

02:12 Bug #262: SWIFT 940 parsing substitutes wrong entry date if the :61 field contains none.

Martin,
Yes, that would work, though it would be applied to all MT940 users. The profiles are hardcoded into the ... jralls@ceridwen.us

01:45 Bug #262: SWIFT 940 parsing substitutes wrong entry date if the :61 field contains none.

John,
>Gave me hope that you'd fix it, because using the value date is not what the parser currently does.
The ... martin

01:37 Bug #262: SWIFT 940 parsing substitutes wrong entry date if the :61 field contains none.

Your English is fine. It's just that
> Right, and thats what the parser currently does.
Gave me hope that you'd... jralls@ceridwen.us

00:28 Bug #262: SWIFT 940 parsing substitutes wrong entry date if the :61 field contains none.

John,
>OK, but how about using the value date for the entry date?
That's what I tried to explain above (I'm afr... martin

29.07.2022

23:54 Bug #262: SWIFT 940 parsing substitutes wrong entry date if the :61 field contains none.

Martin,
OK, but how about using the value date for the entry date?
As for the supplemental data, heck if I know... jralls@ceridwen.us

23:13 Bug #262: SWIFT 940 parsing substitutes wrong entry date if the :61 field contains none.

John,
indeed, that was a bug I just fixed in Gwenhywfar (which handles date stuff). So passing invalid dates (e.g.... martin

22:31 Bug #262: SWIFT 940 parsing substitutes wrong entry date if the :61 field contains none.

Martin,
Well, if the value date matches the balance date then there's no harm in AB_Transaction_GetDate() returnin... jralls@ceridwen.us

22:18 Bug #262: SWIFT 940 parsing substitutes wrong entry date if the :61 field contains none.

John,
>Isn't it the case that in type 2 reports the value date and the balance date are the same if there's no ent... martin

21:49 Bug #262: SWIFT 940 parsing substitutes wrong entry date if the :61 field contains none.

Martin,
Isn't it the case that in type 2 reports the value date and the balance date are the same if there's no en... jralls@ceridwen.us

21:04 Bug #262 (Feedback): SWIFT 940 parsing substitutes wrong entry date if the :61 field contains none.

John,
SWIFT formats are extremely complicated to get right across all parts of the information flow from bank serv... martin

00:02 Bug #262 (In Progress): SWIFT 940 parsing substitutes wrong entry date if the :61 field contains none.

martin

28.07.2022

23:49 Bug #262 (Closed): SWIFT 940 parsing substitutes wrong entry date if the :61 field contains none.

The SWIFT 940 format's transaction field provides for two dates, a mandatory value date and an optional entry date. I... jralls@ceridwen.us