It occurs to me the best thing to do regarding altering things that
may need to be in the reconciliation report is to gather best
practices before engaging in documentation. I suspect (but will have
to double check) that even GL items with the same source number and
date will be aggregated into th
I understand the concern about reconciliation. There are current ways
to adjust payments/receipts in the UI, but it involves separate
transactions. Now that we see the concern, it may be something that
can be fixed through documentation.
In general, if you issue an payment or overpayment or suc
On Tue, Apr 10, 2012 at 7:29 PM, Michael Richardson wrote:
>
> > "John" == John Locke writes:
>John> As mentioned on another thread, one change I would like to be
>John> able to make to a few posted invoices: change the contact
>John> within a customer -- e.g. to a new ECA.
>
> In
> "John" == John Locke writes:
John> As mentioned on another thread, one change I would like to be
John> able to make to a few posted invoices: change the contact
John> within a customer -- e.g. to a new ECA.
In other words, you write an invoice, send it, and then discover that
t
> "Chris" == Chris Travers writes:
Chris> On Mon, Apr 9, 2012 at 5:10 PM, Michael Richardson
Chris> wrote:
>> If reposted means that I can modify a PO before it is reconciled,
>> and then repost it (leaving an audit trail), then I'm okay.
Chris> I am not quite sure what
On Mon, Apr 9, 2012 at 6:40 PM, David wrote:
>
>
> On 10/04/12 10:59, John Locke wrote:
>> As mentioned on another thread, one change I would like to be able to
>> make to a few posted invoices: change the contact within a customer --
>> e.g. to a new ECA.
>>
>> If we can add notes and change the
On 10/04/12 10:59, John Locke wrote:
> As mentioned on another thread, one change I would like to be able to
> make to a few posted invoices: change the contact within a customer --
> e.g. to a new ECA.
>
> If we can add notes and change the contact, that would be really helpful.
>
+1
As far as
As mentioned on another thread, one change I would like to be able to
make to a few posted invoices: change the contact within a customer --
e.g. to a new ECA.
If we can add notes and change the contact, that would be really helpful.
On 04/09/2012 05:46 PM, Chris Travers wrote:
> On Mon, Apr 9,
On Mon, Apr 9, 2012 at 5:10 PM, Michael Richardson wrote:
>
> If reposted means that I can modify a PO before it is reconciled, and
> then repost it (leaving an audit trail), then I'm okay.
I am not quite sure what you mean by reconciling PO's, but reposting
doesn't apply to PO's. PO's and SO's
If reposted means that I can modify a PO before it is reconciled, and
then repost it (leaving an audit trail), then I'm okay.
I otherwise make too many errors in a session to have to reverse things.
I'm okay with reversing transactions I made in a previous session, but
what's a session in the alw
I second Erik's suggestion.
The voiding process seems incomplete to me if it requires me posting a
dummy payment in order to have it marked as closed
Andrew
On Mon, Apr 9, 2012 at 4:19 PM, Erik Huelsmann wrote:
> Replying to myself: I think that if we can create reports which exclude
> reversed
Replying to myself: I think that if we can create reports which exclude
reversed and reversal transactions, that serves both the accounting audit
trail purpose and the optical "I've deleted the transaction" purpose for
good overview.
Bye,
Erik.
On Mon, Apr 9, 2012 at 8:44 AM, Erik Huelsmann wro
On Mon, Apr 9, 2012 at 4:38 AM, Chris Travers wrote:
> Hi;
>
> I would like to propose that we stop allowing transactions to be
> reposted or deleted in 1.4, and instead always require transaction
> reversal.
>
> Is there any objection to this?
>
>
Here's my strong support for the proposal.
Bye,
On Sun, Apr 8, 2012 at 7:46 PM, Jigme Datse Rasku
wrote:
> Reposted, as the same transaction? I'm all for that.
Yes, as the same transaction.
Best Wishes,
Chris Travers
--
For Developers, A Lot Can Happen In A Second.
Reposted, as the same transaction? I'm all for that.
On Sun, Apr 8, 2012 at 7:38 PM, Chris Travers wrote:
> Hi;
>
> I would like to propose that we stop allowing transactions to be
> reposted or deleted in 1.4, and instead always require transaction
> reversal.
>
> Is there any objection to this
Hi;
I would like to propose that we stop allowing transactions to be
reposted or deleted in 1.4, and instead always require transaction
reversal.
Is there any objection to this?
Best Wishes,
Chris Travers
--
For Develop
16 matches
Mail list logo