Due Dates

OVERVIEW:

DELPHI32 automatically ages client accounts based on the due date of each session.  This allows you to track the 'age' of each session into the generally accepted categories of current, 30+, 60+, and 90+ days overdue.   A 'due date' is a date assigned by DELPHI32 to each session specifying the point in time at which that session becomes overdue.

Throughout DELPHI32, there are many factors associated with how and when due dates are set and tracked.  This section covers these factors.

  First, you need to assign the default number of days before a bill becomes overdue.  This is a system-wide setting and is set in the Accounting screen under the Setup menu.  In most cases, the default number of days will be 30.  Once you modify this setting, DELPHI32 uses this number of days as the default setting for overdue bills when adding new clients.

  Second, if needed, you can override the default number of days before a bill is past due on a client-by-client basis.  This is done in the Accounting tab on the Client Information screen and can be useful if you have a client that you would like to give more time before their bills become overdue.  This is not common but it is available.

  Third, DELPHI32 provides two different methods on when a due date for a session is defined.  This is done in the Accounting screen under the Setup menu, at the item labeled 'Due dates calculated 30 days from session date'.  The due date can be set '30' days from the date of the session, or '30' days from the date you actually sent the client a statement for that session.  Detailed instructions on this setting can be found in the Accounting screen under the Setup menu.  

  Fourth, DELPHI32 will automatically assign the correct due date based on the above settings.  However, if you would like to edit a due date that has already been assigned, you can do so on a session-by-session basis. This is explained in the section labeled Editing Co-payments for Past Sessions.  Both the editing of due dates and the editing of the expected co-payment for each session are done in the same manner.

  Lastly, DELPHI32 automatically assigns an overdue 'dunning' message to the most overdue balance on a client account and prints these messages on Client Statements.  The dunning messages can be assigned and/or modified in the Accounting screen under the Setup menu.