OCA
/
bank-statement-import
5
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
281 Commits
10 Branches
0 Tags
2.7 MiB
Tree: 607a5b976b
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '607a5b976b'
${ noResults }
bank-statement-import/account_bank_statement_impo.../test_files/golden-camt053.pydata

34 lines
1.8 KiB
Raw Normal View History

[10.0] Better parse camt groupped transactions (#131) * 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
6 years ago
​
​
​
​
​
Remove dead fields from unittests
6 years ago
[10.0] Better parse camt groupped transactions (#131) * 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
6 years ago
​
[10.0][FIX] account_bank_statement_import_camt: switch name and note
6 years ago
​
[10.0] Better parse camt groupped transactions (#131) * 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
6 years ago
Remove dead fields from unittests
6 years ago
​
[10.0][FIX] account_bank_statement_import_camt: payment amounts (#166)
6 years ago
[10.0] Better parse camt groupped transactions (#131) * 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
6 years ago
[10.0][FIX] account_bank_statement_import_camt: switch name and note
6 years ago
​
[10.0] Better parse camt groupped transactions (#131) * 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
6 years ago
Remove dead fields from unittests
6 years ago
[10.0][FIX] account_bank_statement_import_camt: payment amounts (#166)
6 years ago
​
​
[10.0][FIX] account_bank_statement_import_camt: switch name and note
6 years ago
​
[10.0][FIX] account_bank_statement_import_camt: payment amounts (#166)
6 years ago
​
Remove dead fields from unittests
6 years ago
[10.0] Better parse camt groupped transactions (#131) * 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
6 years ago
​
[10.0][FIX] account_bank_statement_import_camt: switch name and note
6 years ago
​
[10.0] Better parse camt groupped transactions (#131) * 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
6 years ago
Remove dead fields from unittests
6 years ago
  1. (None,
  2. 'NL77ABNA0574908765',
  3. [{'balance_end_real': 15121.12,
  4. 'balance_start': 15568.27,
  5. 'date': '2014-01-05',
  6. 'name': '1234Test/1',
  7. 'transactions': [{'account_number': 'NL46ABNA0499998748',
  8. 'amount': -754.25,
  9. 'date': '2014-01-05',
  10. 'name': 'Insurance policy 857239PERIOD 01.01.2014 - 31.12.2014',
  11. 'note': 'MKB Insurance 859239PERIOD 01.01.2014 - 31.12.2014',
  12. 'partner_name': 'INSURANCE COMPANY TESTX',
  13. 'ref': '435005714488-ABNO33052620'},
  14. {'account_number': 'NL46ABNA0499998748',
  15. 'amount': -564.05,
  16. 'date': '2014-01-05',
  17. 'name': 'Direct Debit S14 0410',
  18. 'note': 'Direct debit S14 0410 AC07 Rek.nummer blokkade TESTBANK/NL/20141229/01206408',
  19. 'partner_name': 'Test Customer',
  20. 'ref': 'TESTBANK/NL/20141229/01206408'},
  21. {'account_number': 'NL46ABNA0499998748',
  22. 'amount': -100.0,
  23. 'date': '2014-01-05',
  24. 'name': 'Direct Debit S14 0410',
  25. 'note': 'Direct debit S14 0410 AC07 Rek.nummer blokkade TESTBANK/NL/20141229/01206408',
  26. 'partner_name': 'Test Customer',
  27. 'ref': 'TESTBANK/NL/20141229/01206407'},
  28. {'account_number': 'NL69ABNA0522123643',
  29. 'amount': 1405.31,
  30. 'date': '2014-01-05',
  31. 'name': 'INNDNL2U20140105000217200000708',
  32. 'note': '#RD PARTY MEDIA CUSNO 90782 4210773',
  33. 'partner_name': '3rd party Media',
  34. 'ref': '115'}]}])