Post reply

lease data model

  • June 28, 2012 at 3:21 pm

    #98722

    Hi I have been a SQL developer for many years but have somehow managed to avoid doing any finance related applications. However my current project is a custom lease management system. I boned up on modeling double entry accounting and I feel pretty good about that.

    But I am not sure the best way to handle 10 years of fixed and scheduled lease payments. Should I keep a separate table to record all future payments and run a daily job to post due payments to the posting table? or should I just making posting entries that are future dated?

    Or something else? Any ideas or links to related material appreciated

    Dave

    Trainmark.com IT Training B2B Marketplace
    (Jobs for IT Instructors)

  • June 28, 2012 at 9:25 pm

    #1506930

    chisholmd (6/28/2012)

    Should I keep a separate table to record all future payments and run a daily job to post due payments to the posting table?

    That would be my plan. Makes it real easy to tell when someone is behind especially if each of the two tables has a running balance. Add a special column for late fees.

    --Jeff Moden

    RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
    First step towards the paradigm shift of writing Set Based code:
    ________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.
    "Change is inevitable... change for the better is not".
    Helpful Links:
    How to post code problems
    How to Post Performance Problems
    Create a Tally Function (fnTally)
    Intro to Tally Tables and Functions

Viewing 2 posts - 1 through 1 (of 1 total)

You must be logged in to reply to this topic. Login to reply