Confirm account moves from payments

78 views
Skip to first unread message

Eduardo J de la Garza G

unread,
Jul 19, 2016, 11:25:06 AM7/19/16
to tryton
Hello,

With the modules account_payment and account_payment_clearing, tryton has the functionality to register the payments; when the user clics on the "success" button, it creates the payment account move and its reconciliation, this is fine but, the account move remains at state "draft".  Is there something I should do or is there another module to make the move become "posted"?

Or, which is the next step to confirm all the payment account moves without search and confirm each one individually?

I will appreciate your comments,

Eduardo J. de la Garza G.


Cédric Krier

unread,
Jul 19, 2016, 12:05:06 PM7/19/16
to tryton
For now, there are nothing to post it (except manually).
The difficulty is that for protocol like SEPA, we must allow to fail a
payment even if it was succeeded. So we need to delay the post of the
payment move.
So we are looking for a nice solution to this problem. Maybe a cron
task/wizard that post all moves old enough.

--
Cédric Krier - B2CK SPRL
Email/Jabber: cedric...@b2ck.com
Tel: +32 472 54 46 59
Website: http://www.b2ck.com/

Eduardo J de la Garza G

unread,
Jul 19, 2016, 1:05:06 PM7/19/16
to tryton
Ok, thanks for your response Cédric.
Regards,
Eduardo J. de la Garza González

Sergi Almacellas Abellana

unread,
Jul 20, 2016, 11:23:09 AM7/20/16
to try...@googlegroups.com
El 19/07/16 a les 18:03, Cédric Krier ha escrit:
> On 2016-07-19 06:48, Eduardo J de la Garza G wrote:
>> > Hello,
>> >
>> > With the modules account_payment and account_payment_clearing, tryton has
>> > the functionality to register the payments; when the user clics on the
>> > "success" button, it creates the payment account move and its
>> > reconciliation, this is fine but, the account move remains at state
>> > "draft". Is there something I should do or is there another module to make
>> > the move become "posted"?
>> >
>> > Or, which is the next step to confirm all the payment account moves without
>> > search and confirm each one individually?
>> >
>> > I will appreciate your comments,
> For now, there are nothing to post it (except manually).
> The difficulty is that for protocol like SEPA, we must allow to fail a
> payment even if it was succeeded. So we need to delay the post of the
> payment move.

Reading the code I see clearing move is canceled if it has been already
posted, so i don't see any problem about directly posting the move and
then creating a cancel move if the payment is failed.

--
Sergi Almacellas Abellana
www.koolpi.com
Twitter: @pokoli_srk

Cédric Krier

unread,
Jul 21, 2016, 5:00:04 AM7/21/16
to try...@googlegroups.com
The inconvenient is that it could lead to have many moves cancelled
generated. I'm still more in favor of a cron task that post them after a
delay because it matches better with the SEPA rules and also it allows
to still do manual posting.

Sergi Almacellas Abellana

unread,
Jul 22, 2016, 3:34:08 AM7/22/16
to try...@googlegroups.com
El 21/07/16 a les 10:57, Cédric Krier ha escrit:
As SEPA is not the only processing method: I'm wondering if we should
define on the journal if the move should be posted or not.

Cédric Krier

unread,
Jul 22, 2016, 3:45:03 AM7/22/16
to try...@googlegroups.com
On 2016-07-22 09:34, Sergi Almacellas Abellana wrote:
> As SEPA is not the only processing method: I'm wondering if we should define
> on the journal if the move should be posted or not.

If we have a cron task, I do not think it is needed. But probably the
delay for posting should be configured per payment journal.

Sergi Almacellas Abellana

unread,
Jul 29, 2016, 2:21:26 PM7/29/16
to try...@googlegroups.com


El 22/07/16 a les 09:42, Cédric Krier ha escrit:
> On 2016-07-22 09:34, Sergi Almacellas Abellana wrote:
>> >As SEPA is not the only processing method: I'm wondering if we should define
>> >on the journal if the move should be posted or not.
> If we have a cron task, I do not think it is needed. But probably the
> delay for posting should be configured per payment journal.
I have been thinking about it and I think It can be also confirmed when
the bank statement is imported.

It will be also a good moment to mark the processing payments as succeed
if not done already.

Cédric Krier

unread,
Jul 29, 2016, 2:50:03 PM7/29/16
to try...@googlegroups.com
On 2016-07-29 20:21, Sergi Almacellas Abellana wrote:
> El 22/07/16 a les 09:42, Cédric Krier ha escrit:
> >On 2016-07-22 09:34, Sergi Almacellas Abellana wrote:
> >>>As SEPA is not the only processing method: I'm wondering if we should define
> >>>on the journal if the move should be posted or not.
> >If we have a cron task, I do not think it is needed. But probably the
> >delay for posting should be configured per payment journal.
> I have been thinking about it and I think It can be also confirmed when the
> bank statement is imported.

I guess you mean posted (instead of confirmed), but still a cron task
will bring both behaviours.

> It will be also a good moment to mark the processing payments as succeed if
> not done already.

Agree.

Sergi Almacellas Abellana

unread,
Aug 8, 2016, 5:36:05 AM8/8/16
to try...@googlegroups.com
El 29/07/16 a les 20:48, Cédric Krier ha escrit:
>> > It will be also a good moment to mark the processing payments as succeed if
>> > not done already.
> Agree.
Just to followup. I created https://bugs.tryton.org/issue5765 to
implement this feature.
Reply all
Reply to author
Forward
0 new messages