* correctly parse entries with multiple transactions
Our bank does it. Care has been taken not to break cases where
Ntry/NtryDtls/TxDtls isn't used: if any piece of information isn't found
on these nodes, the matching information from the Ntry is used. Most
often the entry has a sum or a summary and the transaction details are
more precise and specific, so it makes sense to use their contents
rather than its.
* more complete unit tests for camt parser
This checks the whole output data of the parser against its expected
output.
* add a test case that checks TxDtls decoding
* special case for Ntrys without TxDtls
* CO-12 - Date Import BVR
* FIX tests
* CO-1232 Fixed issues with CAMT parser tests
Message was not taken from AddtlNtryInf element, if not part of details.
Not sure wether it actually can be part of details (NtryDtls element), but this change least intrusive.
Alexis de Lattre
eLBati
ecino
Emanuel Cino
david wulliamoz
Louis Bettens
Holger Brunn
Ronald Portier (Therp BV)
Stéphane Bidoul