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