[Emerald] Strange Billing Quirk

Drew Halevy ( (no email) )
Tue, 11 Apr 2000 15:23:45 -0500

This is a multi-part message in MIME format.

------=_NextPart_000_0000_01BFA3C9.EDD3D4E0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

Hello, I am having a strange problem that happens every so often. I am using
version 2.5.329 and every so often when I go to batch>print it will pick up
an old invoice-for example, today I created a new user, invoiced next term
and then went to batch and chose print, so that it would mark the invoice as
sent. It picked up an invoice from 3/9/00 with a due date of 3/26/00. We run
a batch every thursday, plus 3 or 4 other times during the week, so why
would this one suddenly be picked up. The only clue that I have is that
3/26/00 + our standard 14 day extend brings it up to 4/9/00, and today was
the first day I have run batch since then-any ideas? thanks in advance-Drew

------=_NextPart_000_0000_01BFA3C9.EDD3D4E0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">

Hello,=20I am having a strange problem that happens every so often. I am using =version=202.5.329 and every so often when I go to batch>print it will pick up =an old=20invoice-for example, today I created a new user, invoiced next term and =then=20went to batch and chose print, so that it would mark the invoice as =sent. It=20picked up an invoice from 3/9/00 with a due date of 3/26/00. We run a =batch=20every thursday, plus 3 or 4 other times during the week, so why would =this one=20suddenly be picked up. The only clue that I have is that 3/26/00 + our =standard=2014 day extend brings it up to 4/9/00, and today was the first day I have =run=20batch since then-any ideas? thanks in=20advance-Drew
------=_NextPart_000_0000_01BFA3C9.EDD3D4E0--