# Importing a camt.054 SEPA message
**URL:** https://discuss.tryton.org/t/importing-a-camt-054-sepa-message/329
**Category:** User
**Created:** [March 21, 2017, 1:18am UTC](https://discuss.tryton.org/t/importing-a-camt-054-sepa-message/329 "2017-03-21T01:18:04Z")
**Posts on this page:** 5
**Page:** 1
### Author:  [@Jani-Matti](https://discuss.tryton.org/u/Jani-Matti)
#### Post date: [March 21, 2017, 1:18am UTC](https://discuss.tryton.org/t/importing-a-camt-054-sepa-message/329/1 "2017-03-21T01:18:05Z")
Hi all,
Sorry if this seems like a retarded question, but how would I go about importing a camt.054 SEPA message into Tryton?
What we are trying to do is to use the camt.054 messages to automatically track incoming customer invoice payments.
---
### Author:  [@ced](https://discuss.tryton.org/u/ced)
#### Post date: [March 21, 2017, 9:39am UTC](https://discuss.tryton.org/t/importing-a-camt-054-sepa-message/329/2 "2017-03-21T09:39:47Z")
> [@Jani-Matti](#):
>
> how would I go about importing a camt.054 SEPA message into Tryton?
You have to create an “IN” sepa message with the XML in the message field. Then you have to process the workflow: → “wait” → “do”.
> [@Jani-Matti](#):
>
> What we are trying to do is to use the camt.054 messages to automatically track incoming customer invoice payments.
Be careful that camt.054 is payment notification not statement. So normally you should only receive information about your payments.
---
### Author:  [@Jani-Matti](https://discuss.tryton.org/u/Jani-Matti)
#### Post date: [March 21, 2017, 2:19pm UTC](https://discuss.tryton.org/t/importing-a-camt-054-sepa-message/329/3 "2017-03-21T14:19:43Z")
> [@ced](#):
>
> You have to create an “IN” sepa message with the XML in the message field. Then you have to process the workflow: → “wait” → “do”.
What would be the best way to automate this on the server? We get a daily camt.054 statement so a cron job probably?
> [@ced](#):
>
> Be careful that camt.054 is payment notification not statement. So normally you should only receive information about your payments.
The way Finnish banks implement it is that it only includes received payments with a reference number plus possible reversals.
---
### Author:  [@ced](https://discuss.tryton.org/u/ced)
#### Post date: [March 21, 2017, 3:06pm UTC](https://discuss.tryton.org/t/importing-a-camt-054-sepa-message/329/4 "2017-03-21T15:06:43Z")
> [@Jani-Matti](#):
>
> What would be the best way to automate this on the server? We get a daily camt.054 statement so a cron job probably?
It really depends on how you receive the file. But of course you can script it using proteus.
> [@Jani-Matti](#):
>
> The way Finnish banks implement it is that it only includes received payments with a reference number plus possible reversals.
Tryton module manages CAMT.054 as notification only so it will do nothing about payments that do not exist in the database.
Indeed it seems you are looking for the statement message CAMT.053 which is actually a bank statement. An prototype was developed in [issue4658](https://bugs.tryton.org/issue4658) but it should probably be redesigned for [issue5882](https://bugs.tryton.org/issue5882).
---
### Author:  [@Jani-Matti](https://discuss.tryton.org/u/Jani-Matti)
#### Post date: [April 11, 2017, 8:58am UTC](https://discuss.tryton.org/t/importing-a-camt-054-sepa-message/329/5 "2017-04-11T08:58:48Z")
> [@ced](#):
>
> Tryton module manages CAMT.054 as notification only so it will do nothing about payments that do not exist in the database.
So wait. There’s currently no way to use any kind of CAMT report to match posted customer invoices to incoming payments?
In Finland a traditional business account bank statement doesn’t include separate lines for payments made with a reference number. All incoming and outgoing transactions with a reference number are grouped into daily totals (total incoming, total outgoing). The CAMT.054 report is the one that lists those transactions, and those transactions alone. The logic being that transactions with an associated reference number shouldn’t ever need to be handled by people.