Re: Duplicate AP invoices (per vendor)

Subject: Re: Duplicate AP invoices (per vendor)

From: David G <..hidden..>

Date: Mon, 14 Mar 2016 18:52:10 +0800

Hi Chris

On 14/03/16 14:27, Chris Travers wrote:

On Mon, Mar 14, 2016 at 12:34 AM, Erik Huelsmann <..hidden..> wrote:

In the past we prevented multiple invoices from the same vendor with identical numbers.

If I remember correctly, some people complained and we have relaxed this limitation.

I'm now thinking that we may want to have duplicates disabled by default, but we might want to offer an administrator access button in setup.pl to enable it. That way, the default operation will better fit expectations of accountants/ bookkeeper, with the ability to support countries where rules and/or execution are less strict, without the need to have mails on the users list explaining how to get into the database and drop specific constraints.

Having an explicit (expert) setting like this also makes the situation more noticeable/explicit: a dropped constraint can go unnoticed for years.

What do you say?

A unique constraint works well and scales well. Something like this would have to be thought out very carefully.

I think one option would be an option at database creation time and a way to disable. Disabling would effectively be one-way. With a unique constraint, once you disable, you don't have a good way to re-enable.

I almost agree, I think by default (not a choice at creation) the constraint should be enabled.
If an administrator chooses to they should be able to disable it, after acknowledging that the process will almost always be irreversible (ie: if anything is created that would violate the constraint)

In the future if an administrator chooses they can attempt to re-enable the constraint, at which time a check should be done, if nothing would violate the constraint, simply re-enable it.
If any violations would occur list the relevant Invoices in a printable/exportable form.
This would allow manual fixes to be applied if there are violations and it makes sense to do so, while allowing the constraint to be re-applied if the database would remain consistent, which prevents issues where someone enables it out of curiosity.

--
Bye,

Erik.

http ://efficito.com -- Hosted accounting and ERP.
Robust and Flexible. No vendor lock-in.

--

Best Wishes,
Chris Travers

Efficito: Hosted Accounting and ERP. Robust and Flexible. No vendor lock-in.

http://www.efficito.com/learn_more
------------------------------------------------------------------------------
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785231&iu=/4140
_______________________________________________
Ledger-smb-devel mailing list
..hidden..
https://lists.sourceforge.net/lists/listinfo/ledger-smb-devel

------------------------------------------------------------------------------ Transform Data into Opportunity. Accelerate data analysis in your applications with Intel Data Analytics Acceleration Library. Click to learn more. http://pubads.g.doubleclick.net/gampad/clk?id=278785231&iu=/4140