![]() |
BillMax Billing Solutions 877.245.5629 sales@billmax.com |
Table of Contents
A migration technique in which an Account"s non-zero beginning balance is entered into BillMax rather than migrating historical financial data. A much simpler migration technique than migrating historical financial data, but historical reporting and aging information is not available from BillMax.
Restrictions of the Beginning Balance Method
Deposit Charges may not be included in a Beginning Balance record. This is due to the fact Deposit Charges is are mapped one-to-one to Deposit Refunds.
Deposit Refunds or Refunds may not be included in a Beginning Balance record.
More than one type of Financial Transaction may not be represented in a Beginning Balance record. In other words, a Beginning Balance record may look like a Payment record or an Sale record, but not both.
An Account may not have more than one Beginning Balance record. If an Account requires more than one of the following:
Unallocated Payments.
Unallocated Sales.
Unallocated Store Credits.
historical data will need to be imported.
Beginning Balances do not show up on Sales, Payments, Credits, or Deferred Revenue reports. They also do not show up as "Tax Billed" on the Sales Tax report. However, subsequent payments will show up as "Tax Paid" on the Sales Tax report.
The payhist.startdate and payhist.enddate for Beginning Balances are for all intents and purposes are ignored. No monthlysale table records are created and they are not considered with computing tax exemption amounts.
Manual Allocations may be made to Beginning Balance records. However, Manual Allocations "from" Beginning Balance records are not allowed. In other words, when receiving a Payment, the Payment may be made to a Beginning Balance record that represents money owed. However, the Beginning Balance record is not available in the Charges/Deposits list to Allocate it to the Payment.
The Beginning Balance record must be the earliest in Account history. In other words, when doing a MySQL select from the payhist table and ordering by payhist.entdate, payhist.enttime and payhist.number, the Beginning Balance record must be first.
The payhist.entdate of the Beginning Balance record must be greater than or equal to the account.startdate.
The Beginning Balance Method consists of creating payhist table records with a type of 9. The following fields must be populated:
Table 2.1. Beginning Balance Representing Sales
| Required Fields |
|---|
account.number - The Account number. |
account.entdate - See restrictions 7 and 8 |
payhist.purchases - a positive value |
payhist.taxable, payhist.ntaxable, payhist.taxable - negative values where the sum of these is equal to the negative of payhist.purchases |
payhist.summary - the value set to "1" |
payhist.type - the value set to "9" |
| Optional Fields |
|---|
Table 2.2. Beginning Balance Representing Store Credits
| Required Fields |
|---|
account.number - The Account number. |
account.entdate - See restrictions 7 and 8 |
payhist.ucredit - a negative value |
payhist.taxable, payhist.ntaxable, payhist.taxable - positive values where the sum of these is equal to the negative of payhist.purchases |
payhist.summary - the value set to "1" |
payhist.type - the value set to "9" |
| Optional Fields |
|---|
Table 2.3. Beginning Balance Representing Payments
| Required Fields |
|---|
account.number - The Account number. |
account.entdate - See restrictions 7 and 8 |
payhist.bankacct - a positive value |
payhist.ucash - a negative value equal to the negative of payhist.bankacct |
payhist.summary - the value set to "1" |
payhist.type - the value set to "9" |
| Optional Fields |
|---|
After entering the Beginning Balance records, run /usr/local/billmax/bin/create_applies to update the Account balances.