Every day at 6:00am we run the batch process that ages all our customer debt into current, 30-60, 60-90 and 90+ range buckets. There looks to be three tables in Dynamics Finance that this appears to process:
1) CustTrans contains a complete history of customer financial flows across a large number of transaction types
2) CustTransOpen contains mostly the same fields as CustTrans, but only contains transaction flows classified as still being in an "Open" state
3) CustAging contains one record per customer account, where the customer debt is sorted into age buckets
CustAging is the only place where the age buckets appear. However, if there is a still-open cash payment made by the customer that's not yet been allocated against an invoice, that amount is deducted from the oldest debt bucket wherever a value is present.
My assumption is that "CustAging" is created by the batch process, so the values in it are only true at the time it's run. However, i'm being asked if I can make this keep up to date as the day progresses. Building an always-up-to-date version based on CustTransOpen looks complex, partticularly because unmatched payments get applied against one or more non-zero values in debt buckets, starting with the oldest and cascading down until the payment value is exhausted. My questions are:
1) Is CustAging really created in batch, or is it updated all the time?
2) If CustAging is not updated throughout the day, is there any description of how CustAging is built from CustTransOpen?
Any help/guidance or pointers would be really appreciated.
Ian W.
