-
Notifications
You must be signed in to change notification settings - Fork 62
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add ISO20022 write support #59
Comments
I have implemented proof-of-concept ISO20022 writer, see my iso20022 branch. There are no changes to the UI, so the only way to test it at the moment is to replace OfxWriter with it. |
@andrewshadura, this looks iteresting. I think ofxstatement can support this output format, but I'm not sure the internal model ( What is your actual use case for this? |
My use case is converting non-standard legacy statement files my bank
provides into a standard interchange format. ISO20022 has been accepted as
a format to be used within SEPA zone, so I expect its usage to grow. In
particular, my accountant said, not sure how true that is, my bank is the
only bank in the country which doesn't support ISO20022 yet. And most
accounting software supports it too.
…--
Cheers,
Andrew
On 2 Jun 2017 20:35, "Andrey Lebedev" ***@***.***> wrote:
@andrewshadura <https://github.com/andrewshadura>, this looks iteresting.
I think ofxstatement can support this output format, but I'm not sure the
internal model (Statement and friends) are sufficient to generate a valid
ISO-20022 markup (it was never intended for that).
What is your actual use case for this?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#59 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAS4BZtTnC_cka1vYryeYJXWWMQakqVsks5sAFXYgaJpZM4NtBV6>
.
|
ISO20022, being a standard, is often the only format accepted by accounting software. Being able to generate ISO20022 would be a huge benefit, making it possible to use ofxstatement to convert from legacy formats.
The text was updated successfully, but these errors were encountered: