sql-ledger-users

Re: [SL] unique ID's

[<arc...@mt...>]

> 
> From: "C. Duncan Hudson" <Du...@Du...>
> Date: 2007/02/07 Wed AM 11:23:06 CST
> To: sql...@li...
> Subject: Re: [SL] unique ID's
> 
> Our accountants just about stroked out when they discovered duplicate
> invoice numbers in SQL-Ledger.  The official response on this list was
> "don't let your users make duplicaes".  Which, I think was a little
> poor.  Our users weren't doing it on purpose, but the Post As New
> buttons duplicate invoices, quotes, POs, etc verbatim - including the
> ID.  I can't imagine why anyone who wasn't cooking their books would
> want duplicate invoice numbers, so I added logic to force a new invoice,
> quote and PO number assignment if a duplicate existed.
> 
> Dunc

The only reason I've had to use duplicate invoice numbers, was in cases where a vendor's software would not match SL Ledger due to differences on if the tax was calculated on the subtotal or each line item.

I would:
1) create an AP transaction (with just the tax difference) using the same number as the vendor invoice in SL.
2) Put a comment in the notes field, about why the transaction existed.

By using the same invoice number, a report would group them together.


Since then, a kind list member, George Osvald gave me a alternative.
http://sourceforge.net/mailarchive/message.php?msg_id=9106581
(ignore my misguided reply in the archive.. i misunderstood what he meant)


I wish that:

1) Administrator users could override the tax on vendor invoices
2) That SL allowed you to force unique invoice numbers. A toggle like that of enforce transaction reversal would be good.

Cheers
Roy

Re: [SL] unique ID's

[C. D. H. <Du...@Du...>]

arc...@mt... wrote:
>> From: "C. Duncan Hudson" <Du...@Du...>
>> Date: 2007/02/07 Wed AM 11:23:06 CST
>> To: sql...@li...
>> Subject: Re: [SL] unique ID's
>>
>> Our accountants just about stroked out when they discovered duplicate
>> invoice numbers in SQL-Ledger.  The official response on this list was
>> "don't let your users make duplicaes".  Which, I think was a little
>> poor.  Our users weren't doing it on purpose, but the Post As New
>> buttons duplicate invoices, quotes, POs, etc verbatim - including the
>> ID.  I can't imagine why anyone who wasn't cooking their books would
>> want duplicate invoice numbers, so I added logic to force a new invoice,
>> quote and PO number assignment if a duplicate existed.
>>
>> Dunc
>>     
>
> The only reason I've had to use duplicate invoice numbers, was in cases where a vendor's software would not match SL Ledger due to differences on if the tax was calculated on the subtotal or each line item.
>
> I would:
> 1) create an AP transaction (with just the tax difference) using the same number as the vendor invoice in SL.
> 2) Put a comment in the notes field, about why the transaction existed.
>
> By using the same invoice number, a report would group them together.
>
>
> Since then, a kind list member, George Osvald gave me a alternative.
> http://sourceforge.net/mailarchive/message.php?msg_id=9106581
> (ignore my misguided reply in the archive.. i misunderstood what he meant)
>
>
> I wish that:
>
> 1) Administrator users could override the tax on vendor invoices
> 2) That SL allowed you to force unique invoice numbers. A toggle like that of enforce transaction reversal would be good.
>   
I have no logic to prevent duplicate vendor invoices - with hundreds of 
vendors I have to allow for the fact that there will be dups on that 
side of the house. But with my company's documents there can be no 
duplicates - I believe that is basic GAAP. As for tax... Ugh - I wish 
you could override tax throughout the entire application. SQL-Ledger's 
tax logic is the biggest thorn in my side.

Dunc

Re: [SL] unique ID's

[Dieter S. <dsi...@sq...>]

You have the sourcecode, change it, submit a patch and I'll incorporate it 
in the code.

-- 
Dieter Simader       http://www.sql-ledger.com   Tel: (780) 472-8161
DWS Systems Inc.        Accounting Software      Fax: (780) 478-5281
============== On a clear disk you can seek forever ================

On Wed, 7 Feb 2007, C. Duncan Hudson wrote:

> arc...@mt... wrote:
>>> From: "C. Duncan Hudson" <Du...@Du...>
>>> Date: 2007/02/07 Wed AM 11:23:06 CST
>>> To: sql...@li...
>>> Subject: Re: [SL] unique ID's
>>>
>>> Our accountants just about stroked out when they discovered duplicate
>>> invoice numbers in SQL-Ledger.  The official response on this list was
>>> "don't let your users make duplicaes".  Which, I think was a little
>>> poor.  Our users weren't doing it on purpose, but the Post As New
>>> buttons duplicate invoices, quotes, POs, etc verbatim - including the
>>> ID.  I can't imagine why anyone who wasn't cooking their books would
>>> want duplicate invoice numbers, so I added logic to force a new invoice,
>>> quote and PO number assignment if a duplicate existed.
>>>
>>> Dunc
>>>
>>
>> The only reason I've had to use duplicate invoice numbers, was in cases where a vendor's software would not match SL Ledger due to differences on if the tax was calculated on the subtotal or each line item.
>>
>> I would:
>> 1) create an AP transaction (with just the tax difference) using the same number as the vendor invoice in SL.
>> 2) Put a comment in the notes field, about why the transaction existed.
>>
>> By using the same invoice number, a report would group them together.
>>
>>
>> Since then, a kind list member, George Osvald gave me a alternative.
>> http://sourceforge.net/mailarchive/message.php?msg_id=9106581
>> (ignore my misguided reply in the archive.. i misunderstood what he meant)
>>
>>
>> I wish that:
>>
>> 1) Administrator users could override the tax on vendor invoices
>> 2) That SL allowed you to force unique invoice numbers. A toggle like that of enforce transaction reversal would be good.
>>
> I have no logic to prevent duplicate vendor invoices - with hundreds of
> vendors I have to allow for the fact that there will be dups on that
> side of the house. But with my company's documents there can be no
> duplicates - I believe that is basic GAAP. As for tax... Ugh - I wish
> you could override tax throughout the entire application. SQL-Ledger's
> tax logic is the biggest thorn in my side.
>
> Dunc
> -------------------------------------------------------------------------
> Using Tomcat but need to do more? Need to support web services, security?
> Get stuff done quickly with pre-integrated technology to make your job easier.
> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
> _______________________________________________
> sql-ledger-users mailing list
> sql...@li...
> https://lists.sourceforge.net/lists/listinfo/sql-ledger-users
>

Re: [SL] unique ID's

[Roy P <or...@sh...>]

On Wednesday 07 February 2007 14:11, C. Duncan Hudson wrote:

> > I wish that:
> >
> > 1) Administrator users could override the tax on vendor invoices
> > 2) That SL allowed you to force unique invoice numbers. A toggle like
> > that of enforce transaction reversal would be good.
>
> I have no logic to prevent duplicate vendor invoices - with hundreds of
> vendors I have to allow for the fact that there will be dups on that
> side of the house. 

Agreed I should have been more specific by saying i wish AR invoice numbers 
were forced to be unique.

FWIW many of the frustrations I've run into with SL could be prevented if 
there was more built in prevention of user errors.

Cheers,
Roy