You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ofbiz.apache.org by Jacopo Cappellato <ja...@hotwaxmedia.com> on 2009/06/30 01:16:57 UTC
Best way to define different GL accounts for unreconciled/reconciled transactions
I would like to define a general way to define a mapping for an
accounting transaction with different accounts for the unreconciled
and reconciled entry.
For example, a customer payment could generate a debit transaction in
a 'temporary' account; once reconciled, the 'temporary' account is
credited for the same amount and the amount is then debited to a final
account (i.e. the transaction is moved from the temporary to the final
account).
How to model this?
I can think about two options:
1) adding a new entity "ReconciledGLAccountMap" to map a glAccountId
for the unreconciled entries to the one to be used for the reconciled
ones;
2) simply adding reconciledGlAccountId to all the (relevant) GL
account mapping entities we have in ofbiz
What do you think?
Jacopo
Re: Best way to define different GL accounts for unreconciled/reconciled transactions
Posted by Jacopo Cappellato <ja...@hotwaxmedia.com>.
I would like to keep separated all the 'temporary' accounts.
For example, a cash payment could go into an 'cash in transit account'
and after reconciliation be moved into the 'bank account'.
Jacopo
On Jun 29, 2009, at 5:31 PM, Adrian Crum wrote:
> Why not use the suspense account?
>
> -Adrian
>
> Jacopo Cappellato wrote:
>> I would like to define a general way to define a mapping for an
>> accounting transaction with different accounts for the unreconciled
>> and reconciled entry.
>> For example, a customer payment could generate a debit transaction
>> in a 'temporary' account; once reconciled, the 'temporary' account
>> is credited for the same amount and the amount is then debited to a
>> final account (i.e. the transaction is moved from the temporary to
>> the final account).
>> How to model this?
>> I can think about two options:
>> 1) adding a new entity "ReconciledGLAccountMap" to map a
>> glAccountId for the unreconciled entries to the one to be used for
>> the reconciled ones;
>> 2) simply adding reconciledGlAccountId to all the (relevant) GL
>> account mapping entities we have in ofbiz
>> What do you think?
>> Jacopo
Re: Best way to define different GL accounts for unreconciled/reconciled
transactions
Posted by Adrian Crum <ad...@hlmksw.com>.
Why not use the suspense account?
-Adrian
Jacopo Cappellato wrote:
> I would like to define a general way to define a mapping for an
> accounting transaction with different accounts for the unreconciled and
> reconciled entry.
>
> For example, a customer payment could generate a debit transaction in a
> 'temporary' account; once reconciled, the 'temporary' account is
> credited for the same amount and the amount is then debited to a final
> account (i.e. the transaction is moved from the temporary to the final
> account).
>
> How to model this?
>
> I can think about two options:
>
> 1) adding a new entity "ReconciledGLAccountMap" to map a glAccountId for
> the unreconciled entries to the one to be used for the reconciled ones;
> 2) simply adding reconciledGlAccountId to all the (relevant) GL account
> mapping entities we have in ofbiz
>
> What do you think?
>
> Jacopo
>
>