[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: workflow broken in 1.3
- Subject: Re: workflow broken in 1.3
- From: Chris Travers <..hidden..>
- Date: Tue, 10 Apr 2012 04:36:09 -0700
On Tue, Apr 10, 2012 at 1:56 AM, Håvard Sørli <..hidden..> wrote:
> On 09. april 2012 22:53, John Locke wrote:
>>> I understand where that's coming from. I need to think about a good
>>> solution that would suit both you and an auditor to propose to you.
>>> Let me sleep on it a bit.
>>> Isn't the true problem here though that you can't enter the
>>> transaction in a non-local currency? Surely you should be able to
>>> reconcile a USD amount against a USD amount. My expectation would be
>>> that the USD amount is the same each time the bill comes in.
> (Just reading, have not done tests on this.)
> I think the correct accounting with this is to post the Invoice with the
> "translated" currency to the books (with the date of the invoice - and
> "translated" currency on that date.
> When you pay, you post the payment (on the date of payment, in your
> currency, and the difference to an Agio/ Disagio account.
> Could the reconciliation post the diff to an Agio account?
Currently the way we handle things is that the invoice is posted in
the "official books" currency with a marker which says which currency
it is. Then we convert back for reconciliation. There was a problem
in 1.3 for a while but that has been fixed. Note that payment posts
again in the translated currency plus it posts gains and losses.
Regarding editable invoices, I think we need to think of two things:
1) What information in the invoice should be editable after posting
My thinking is that quantities, amounts, etc should *not* be editable
after posting. Invoices can be edited when they are unapproved but
not when they are approved. I think we should eventually have a
workflow that allows you to switch between ECA's for a single entity
but not between entities. Also eventually it should be possible to
add but not delete notes to invoices. Notes would be marked either
customer visible or not. That's a ways away though.
Better than sec? Nothing is better than sec when it comes to
monitoring Big Data applications. Try Boundary one-second
resolution app monitoring today. Free.
Ledger-smb-users mailing list