[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: voucher
- Subject: Re: voucher
- From: ario <..hidden..>
- Date: Sun, 19 May 2013 05:12:51 +0000
On Sat, 2013-05-18 at 11:13 +0200, Erik Huelsmann wrote:
>If you have any more questions, don't hesitate to ask!
I'd be glad to :)
About 'reversal' of the advanced payments.
Is it ok to use the overpayment account in the Payment section of the AP
Transaction when said person actually has done (and billed) the work he
has been paid for in advance?
If not, what would be the procedure?
I've been looking in the 'Cash|Vouchers|Reverse Payment' screen, but
don't know how to relate that to the AP that I'd have to book when the
work will be done.
Or is it that simple that booking the payment in the AP on the date the
voucher has been issued, followed by 'undoing' the voucher through
'reverse payment' is what the developers have intended?
Thanks again,
Ario
> Hi ario,
>
>
> On Sat, May 18, 2013 at 10:18 AM, ario <..hidden..>
> wrote:
> I tried to enter a prepayment done to somebody for future
> work, but get
> a 'no overpayment account specified' error in 'Cash|Payment'.
>
> Ok, INAA, but I take it an account in the CoA is required with
> the
> 'Overpayment' flag set.
>
>
> Exactly.
>
> Should this be a newly created assett account for this purpose
> (prepayments) only, to check later for zero balance?
>
>
> Well, prepayments for services to be delivered (by you) are debts to
> the customer, so should be recorded in Liability accounts. However, if
> you pay someone for services they will deliver to you some day, that's
> an asset.
>
>
> This leads to the conclusion that an AR prepayment account should be
> configured as a liability and an AP prepayment account should be
> configured as an asset.
>
> Then, in this specific case, should the 'Overpayment' flag be
> set on the
> 'Payables', or on the 'Receivables' line in the 'Edit Account'
> screen?
>
>
> Well, that depends. If I understand correctly, you paid someone to
> deliver work to you on a future date. Then, that's an overpayment in
> the payables side, so you would configure an asset account with the
> "Overpayment" flag on the Payables line.
>
> I think a separate account per person or group would be
> appropriate, no?
>
>
> There's no need for that: the system will track separate balances per
> counterparty -- using the single account you'll configure.
>
> Thanks for your time
>
>
>
> No problem. If you have any more questions, don't hesitate to ask!
>
>
>
>
> Bye,
>
>
>
>
> Erik.
>
>
> ------------------------------------------------------------------------------
> AlienVault Unified Security Management (USM) platform delivers complete
> security visibility with the essential security capabilities. Easily and
> efficiently configure, manage, and operate all of your security controls
> from a single console and one unified framework. Download a free trial.
> http://p.sf.net/sfu/alienvault_d2d
> _______________________________________________ Ledger-smb-users mailing list ..hidden.. https://lists.sourceforge.net/lists/listinfo/ledger-smb-users
------------------------------------------------------------------------------
AlienVault Unified Security Management (USM) platform delivers complete
security visibility with the essential security capabilities. Easily and
efficiently configure, manage, and operate all of your security controls
from a single console and one unified framework. Download a free trial.
http://p.sf.net/sfu/alienvault_d2d
_______________________________________________
Ledger-smb-users mailing list
..hidden..
https://lists.sourceforge.net/lists/listinfo/ledger-smb-users