One freelance buy windows 7 upgrade 50 newsletter designer who specializes in genealogy utilizes both software because the combination makes him complete his design tasks twice as fast. Users has (buy windows 7 family) nothing to do with MS SQL Logins however if you are on SQL version – users are translated to SQL as logins and given access to all Great Plains related database: DYNAMICS and companies• User Classes. Users has cheap windows 7 computers nothing to do with MS SQL Logins however if you are on SQL version – users are translated to SQL as logins and given access to all Great Plains related database: DYNAMICS and companies• User Classes.

Talk:Bookkeeping

From FreemedDeveloperWiki, the FreeMED developers' Wiki.

From a discussion with Irv:

  • Insurance payments, patient payments, copayments and deductibles need to be separately described.
  • A close, for us, means that no more data can be entered for this date. In a more general accounting system [1], closing transfers income accounts to equity accounts. We're not going to do this. The closing tool should display the total cash received for that period, including enough data to fill out a bank deposit slip. A user (presumably with special privileges) will sign off on the day's (week's? month's?) close, and no more entries can be added for that period.

Adam 00:19, 4 Aug 2005 (EDT)

[edit]

What the USER (book keeping) needs

  • Entering insurance forms
    • The insurance form is returned from a company
    • A check is attached (eg 500$)
      • The check will need to be split
      • Each patient entry SHOULD show up from the check
        • Can get it from pull down by MR/ pat name/ pat number
      • Each entry will have a charge, a write down (perhaps a combination of codes) and a date
      • Each entry MAY have a copay (if any)
    • Each entry is credited with an amount from the check
    • The total of the entries must balance to the check
Retrieved from "http://developer.freemedsoftware.org/wiki/index.php/Talk:Bookkeeping"
Navigation