Questions On a Payment Ledger

[Joe Cilinceon]

I'm looking for some suggestions how the best way to layout these tables or
if what I have below is effective.

First thing is each payment will tie to the account by a unique LedgerID and
will have a unique Transaction number (auto number).
This is what I have to have in these tables.
Date of Payment
Payment methods (can be multiple payment methods such as check, cash, credit
card)
What it payment pays such as Rent, Late Fee, Overpayment (credit).
What the Rent span pays for such as 1/1/05 thru 1/31/05.
Also need a method to reverse a payment due to a bad check or credit card
reversal.

What I have now is 3 tables for all this.
Ledger (main table) 1 record per transaction
Transaction
LedgerID
RentRate (amount owed for months rent for this payment)
PaymentDate
PaidFrom
PaidThru
-- From here on what it pays with a field for each. (Here is where I'm
thinking of adding another table to this design).
Rent
AdmFee
Lock
LateFee.......etc

Payment - 1 or more records with same transaction number depending on a
single payment method or several.
Transaction
Amount
Method (1 for cash, 2 for check etc)
Tracking (check number or credit card approval code)

NSFChecks - 1 record per transaction (I'm thinking of possibly adding this
data to the Ledger table listed above with perhaps a Reversal flag for
reversed payments. This flag would be necessary to stop it from adding the
amounts as collected.
Transaction
Amount
Tracking
Rev Date (date reversed payment)
Paid (Yes/No check box)


I was thinking of having a table that would have
Transaction - again can be only 1 or several depending on if it pays a
single item or many.
PaymentID (code such as 1 for rent, 2 for late fee and on)

Any help would be appreciated