Improve regExp to support zE= or XE= to retrieve clientID because obfuscation is freqently changed...

Gilles Dartiguelongue authored 2 months ago and Romain Bignon committed 1 week ago

While there is no requirement to use it as it does not apply to
the same class, it is probably better to keep a sense of how CapBank
is trying to achieve transaction listing. The Transaction objects
creation condition are refactored to account for the new parameters and
the previously set coming attribute.

Le module bred permet désormais de lister / récupérer les relevés de comptes associés
aux personnes morales (sociétés).

(Il est certainement possible d'ajouter la même fonctionnalité pour des comptes de
personnes physiques - mais je n'en ai pas à disposition.)

Gilles Dartiguelongue authored 3 months ago and Romain Bignon committed 1 week ago

Some bank modules such as societegenerale provide basic information
about loan payments. Use it to map to the proper OFX aggregate.

This aggregate was introduced in OFX 2.2.

Gilles Dartiguelongue authored 3 months ago and Romain Bignon committed 1 week ago

Refactor OFX export to implement OFX 2.2 support.

Main changes are OFX 2.2 requires valid XML format. Use lxml to ease
manipulation of the document.

Jump straight to 2.2 as it supports:

- A mechanism for pending transactions.
- A defined approach for account obfuscation (masking).
- Multiple new tags related to loans.

Gilles Dartiguelongue authored 3 months ago and Romain Bignon committed 1 week ago

Modules that implement `Transaction._transfer_account` now benefit
proper mapping in OFX export.

Gilles Dartiguelongue authored 3 months ago and Romain Bignon committed 1 week ago

Some banks such as Société Générale allow access to this information.
If the module extracts it, use it.

Gilles Dartiguelongue authored 3 months ago and Romain Bignon committed 1 week ago

Category is extracted from transaction wording. It reflects the nature
of the transaction and not really the extra information that the OFX
specification imply this should be used for. See 3.2.6 Memo <MEMO> and
the example provided in 11.4.4.1 <STMTTRN>.

If the module sets a more detailled `_memo`, use it.

Gilles Dartiguelongue authored 3 months ago and Romain Bignon committed 1 week ago

FITID is the transaction ID issued by financial institution.
It seems more appropriate to use `Transaction.id` when available.
At least for modules such as societegenerale, either this or the raw
value of `idOpe` appear to match FITID definition.

Gilles Dartiguelongue authored 3 months ago and Romain Bignon committed 1 week ago

Thanks to schwifty, it is easy to fill this information now.
BRANCHID and ACCTKEY are optional per specification so they only appear
in the output document if necessary.

Gilles Dartiguelongue authored 3 months ago and Romain Bignon committed 1 week ago

According to OFX specifications, these fields are not necessary nor
optional in a CCACCTFROM definition.

See 11.3.2 Credit Card Account <CCACCTFROM> and <CCACCTTO>.

Ludovic LANGE authored 10 months ago and Romain Bignon committed 1 week ago

By calling a detail page for each transaction, we can gather more details about
the transaction, in particular the whole `raw` label of the transaction.

Cf #684

Ludovic LANGE authored 1 week ago and Romain Bignon committed 1 week ago

Today I had the opportunity to fix error detection as the "Impots" website was under maintenance.