when using the sepa statement module, I regularly encounter some “non-matches” from my regex, usually they result from mistakes in my database (misspellings of party names, missing parties or such).
Till now, I copied columns from “origins” and “positions” and compared them with meld; that works, but seems not to be the most handy solution possible.
Is there something like a regex log - or another approach - which makes it more straightforward to find these non-matches?
For recurring misspellings, the Statement Rule module also remembers previous assignments. A rule can capture a named value such as:
Party: *(?P<party>.*)
Tryton stores the captured value in the origin’s keywords. It first tries to find a party whose name matches that value. If it cannot find exactly one party, it searches previous validated or posted statements for the same captured value and reuses the party selected there.
Thank you Adria, always interesting to learn, which sophisticated features are hidden deep inside Tryton. Actually, I never managed to actually use SEPA statement properly. It sort of works for me with faulty MT940 import, I’m here abusing party data in the reference line. But I could never make it work with CAMT52/53.
For that reason, I started my own approach, still very much in “proof-of-concept”-phase, just as a proteus script, which is working surprisingly well. If anybody is interested, you can find it HERE.. As I never achieved to learn programming (shame on me), it’s AI entirely; sorry for that. But indeed, I can already use it productively in my little company.