------_=_NextPart_000_01BDE083.6F5910CC
Content-Type: text/plain
Your message
To: Glen Harvy
Cc: emerald@iea-software.com
Subject: Re: Accounting periods
Sent: Tue, 15 Sep 1998 07:50:42 +0200
did not reach the following recipient(s):
Emerald-list@mail.extent.com on Tue, 15 Sep 1998 10:32:53 +0200
The recipient name is not recognized
MSEXCH:IMS:NMT:nmt:MAIN 0 (000C05A6) Unknown Recipient
------_=_NextPart_000_01BDE083.6F5910CC
Content-Type: message/rfc822
Content-Location: ATT-0-9D867D206F4CD211887400A0C9729CE3
Message-ID: <35FE0032.41FBC28F@iea-software.com>
From: "Dale E. Reed Jr." <daler@iea-software.com>
To: Glen Harvy <glen@aquarius.com.au>
Cc: emerald@iea-software.com
Subject: Re: Accounting periods
Date: Tue, 15 Sep 1998 07:50:42 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2232.9)
X-MS-Embedded-Report:
Content-Type: text/plain;
charset="windows-1252"
Glen Harvy wrote:
>
> I charge my customers as at the 15th monthly. That is, for the period
> starting at 0000 on the 15th and until 2359 on the 14th of the month.
>
> I have my accounts set to expire on 09/15/98 on the Billing cycle in the
MBR.
>
> I ran Call Consolidation on the 15th expecting the call data from 08/15/98
> to 09/14/98 to be consolidated and placed in the History table. The
> previous time I ran Call Consolidation was on 15th August.
>
> To explain my problem and as an example, on 09/14/98, one of our customers
> record showed TIME ON from 08/15/98 to 09/15/98 as 53 hours. After Call
> Consolidation on 09/15/98, TIME ON was calculated by Emerald for the same
> period as 27 hours.
>
> What APPEARS to have happened is the data from the period prior to
08/31/98
> has been consolidated. The data from 09/01/98 remains in the Time On
section.
>
> When I ran call consolidation I entered 09/15/98 as the Invoice Date.
>
> Examining the Call History for the above example customer, the Start Date
> shows 08/15/98 and the time is 45 hours.
Things sounds like the old behavior of Emerald 2.1. It consolidated
incorrectly based on month boundaries, rather than on the actually
billing
cycle. Emerald 2.2 corrects this problem and correctly consolidated on
the bondaries like you expect. One note, you may need to consolidate
on the next day (the 16th) rather than on the 15th, since the billing
cycle doesn't complete until after the 15th.
Dale E. Reed Jr. (daler@iea-software.com)
_________________________________________________________________
IEA Software, Inc. | RadiusNT, Emerald, and NT FAQs
Internet Solutions for Today | http://www.iea-software.com
------_=_NextPart_000_01BDE083.6F5910CC--