Aging Report - 2 questions
Posted: Wed Apr 01, 2009 2:20 pm
1) Is it possible to back date the aging date? I have the "Calculate Aging Monthly Instead of Daily" box in the Setup->Modules checked. I use the last date of the previous month for my aging date when I run month-end reports. However this month the date was updated to the first of the month by mistake. I tried to use the "Tools->Calculate Aging" to back date the aging as of March 31st, but it didn't work. When I went to each affected account individually the balance updated properly, but the tool didn't do it automatically. Is this by design or a bug?
2) I have a patient showing up on the Aging report rather than the guarantor. This patient was previously their own guarantor, but now someone else in the family is the guarantor. Are the aging amounts supposed stay with the original guarantor on the account even if it changes, or is this a bug? I tried running the database maintenance tool but nothing changed. This is also affecting my custom aging query, which has a column for writeoffs by procedure date. Since the insurance writeoffs are linked to the new guarantor on the account, but the balance is linked to the old guarantor the writeoffs are being excluded from the report because they don't match up. If this is by design then I'll need to figure out how to fix my query, but I thought I'd check first.
Thanks!
2) I have a patient showing up on the Aging report rather than the guarantor. This patient was previously their own guarantor, but now someone else in the family is the guarantor. Are the aging amounts supposed stay with the original guarantor on the account even if it changes, or is this a bug? I tried running the database maintenance tool but nothing changed. This is also affecting my custom aging query, which has a column for writeoffs by procedure date. Since the insurance writeoffs are linked to the new guarantor on the account, but the balance is linked to the old guarantor the writeoffs are being excluded from the report because they don't match up. If this is by design then I'll need to figure out how to fix my query, but I thought I'd check first.
Thanks!