Re: Combinations & Permutations..... sort of

My experience is to match from newest back to oldest, with newest being defined newest in the last billing cycle (probably last month) first. The issue almost invariably is a disputed invoice that has been held out for the past 4 to 8 months, depending on your resolution process.

Partial payments are very unlikely in a business setting.



On 9/30/2014 1:16 PM, Roger Harman wrote:

It will post the first matching set looking at oldest first. Next week, unallocated and they have to deal with it manually.

Date: Tue, 30 Sep 2014 12:30:10 -0400
Subject: Re: Combinations & Permutations..... sort of
From: gallium.arsenide@xxxxxxxxx
To: rpg400-l@xxxxxxxxxxxx

On Tue, Sep 30, 2014 at 11:53 AM, Roger Harman <roger.harman@xxxxxxxxxxx> wrote:

If we can match the entire payment amount, wonderful. If not, it just posts as unallocated and they have to review it. Anything to offload the manual intervention is a plus. There is a lot of volume.

So, are you designing this to be just a "suggestion generator" for
manual review, or will it go ahead and update the database on its own?

What if you have invoices of $10, $15, $20, $30, and $45, and you have
a payment of $60? And what if your system picks ($15 + $45), but then
next week you get a payment of $45? (Meaning that you probably should
have picked $10 + $20 + $30 originally.)

John Y.
--
This is the RPG programming on the IBM i (AS/400 and iSeries) (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.