Open topic with navigation

Bank Lockbox Posting

Last Revised: April 13, 2021

 

Table of Contents

When to use:  As needed to post payments from a lockbox file from a bank.  There are three major steps for this process:  moving the lockbox file from the ACT FTP server to your local hard drive; moving the file to the ACT 7 server, and posting the payments to the ACT 7 Tax Collection System.   For some tax offices, check and coupon images will also be loaded so they can be seen in the Deposit Status screen.

Each tax office's lockbox file will have a unique format.  Contact ACT for information on how to understand these files.

The normal client preferences for tolerance payments are observed.  For half payments and quarter payments, the Split Payment Flag code is updated with an H or Q, respectively (Brazoria County only). Technical note: In the P records in the file the two digits following the account number determine the payment type: 00 - partial or full payment, 10 - half payment, 01 - quarter payment).

For accounts whose monies you want to put in escrow for further research, enter the desired escrow jurisdiction number in the Lockbox Jurisdiction field in the Account Detail screen.

Funds for accounts that are blocked for payment are placed in refund for the accounts. Funds for inactive accounts (those with an Account Status beginning with 'X' or 'I')are placed in the Lockbox-Clear account.

If more than one account is paid on a single coupon, and an overpayment is generated, the refund amount will be applied to the final account. When multiple coupons exist with one check in a lockbox file, the under/over pay is put on the last coupon.

Harris County's lockbox recognizes payments for accounts having 33.11 tax units by looking for '50' as the last two digits of the year field on the coupon. The first two digits of the year indicate the specific year (0850 - 2008, 0750 - 2007).  For these accounts, if the payment fully pays just the 33.11 units, the program will distribute the money accordingly. However, if a partial payment is on the lockbox file, the program will pay the 33.11 units in full if possible, then allocate the money across the remaining units. If multiple coupons are involved, the lockbox will not recognize these as 33.11 payments. Other tax offices allocate 33.11 fees across all jurisdictions, not just those charging 33.11 penalties.

Harris County's lockbox can also be used for posting Internet payments if the Deposit Type parameter is set to CC. The same remit sequence is used for all accounts in a lockbox file or an Internet payment file.

Bexar County's and Galveston County's lockboxes post payments received for prior year split quarter pay receivables to a specific escrow unit. Payments received for fully paid quarter pay accounts are put in the overpay tax unit (8001).

For Bexar County, duplicate payments for the same account and year are summed together and shown as one payment.

For Fort Bend County, the lockbox ignores inactive or deleted accounts. The account number on the OCR line may be the scan line number on the Account Detail screen. For the Jaguar lockbox file, money for deleted accounts is put in the overpay escrow unit for the account instead of the lockbox-clear account.

For Philadelphia, fees will be paid first on payments having receipt dates from 05/01/2011 forward, then the oldest year is paid next. Fees on payments having earlier receipt dates will be paid last and the oldest year is paid first. For Philadelphia accounts only, the maximum penalty is 7% and is assessed at 1% per month for due dates between 2/1 of tax year+1 and 8/31 of tax year+1. If the due date is after 8/31, no penalty is assessed. If the As of Date on the Account Status screen is before the due date, no penalty is assessed. The lockbox will not be posted if any coupon or check is missing in the file. The process will stop if multiple checks or coupons per transaction are found.

Dallas County, the process below can be used for cash drawer remittances and eCommerce posting.

El Paso's city liens are paid after all other taxes and fees are paid. The oldest lien is then paid first, the lien release fee (unit 9111) is paid last.

ClosedUser Entitlements

The following user entitlements must be set for each user who needs access to the Batch Menu and Batch Request screens. They are part of the Run Batch Processes task.  See Tasks, Entitlements, and Jobs for more information. The user entitlement for each batch menu no. mentioned below must be set to Y for each authorized user. Batch menu nos. default to N when they are added.

BATCH_MENU - access to the Batch Menu to generate the reports.

BATCH_REQUEST - access to the Batch Request screen to see the reports.

 

Closed Client Preferences:  

LOCKBOX_CLEARACCT: Set to Y to allow monies for invalid accounts to be stored in a LOCKBOX-CLEAR account; set to N to not allow this (which will cause the lockbox to stop processing). ACT recommends that tax offices that have lockboxes set this to Y.

LOCKBOX_CLEARTU: (OBSOLETE) Enter the tax unit to store LOCKBOX-CLEAR funds.

LOCKBOX_POST_ORDER: Enter the number (for ex., 1) that indicates the lockbox posting order for your tax office. This preference takes precedence over the Special Rule parameter if that parameter is set to 00.  A number 1 (the default) permits posting to the coupon year first (if available in the file), then from the current year, then the oldest year, the next oldest year, etc. Number 2 allows posting to the coupon year first (if available in the lockbox file), then from the oldest year first, the next oldest year, etc.  A 3 will post in order from the current year to the oldest year. In the Oracle version of the lockbox, only numbers 1-3 are permitted in the preference.

OVERPAY_STATUS: If this is set to OH, all overpayment refunds generated by the lockbox will be put on hold.

MIX_AGROLLBACK_ONLINE: If this preference  is set to N, rollback payments made through the lockbox will be put in escrow.

BANKRUPTCY_TO_ESCROW: Enter Y to send bankruptcy lockbox payments to the escrow unit defined by BANKRUPTCY_ESCROW_TU. Enter N to post these payments normally.

BANKRUPTCY_ESCROW_TU: Enter the escrow tax unit used to store bankruptcy lockbox payments if BANKRUPTCY_TO_ESCROW is set to Y. The default is 8999.

LOCKBOX_QUARTER_PAY: (OBSOLETE) Set to Y to have the lockbox pay the next available unpaid quarter on divided quarter pay accounts. Once the earliest quarter receivable has been paid, the next quarter will be paid, and so forth.  Any remaining funds will be put into refund for the current year.  Tolerances are applied to the last quarter paid. Set this preference to N to put the entire payment amount into refund for all accounts having divided receivables.

(Bexar County only) Payments received for prior year split quarter pay receivables are posted to unit 8026. Payments received for the current year are applied to the appropriate quarter.

STMT_SITE_CODE: Some tax offices enter a number here that then appears in the OCR line of their statements.

For rollback elections: If this number corresponds to the stmt_id field in the taxunit_suppress table, the lockbox program is coded to avoid paying the tax units associated with that stmt_id.  Once the election is over and receivables have been calculated for the rollback units, the program is also coded to pay only those units.  The OCR line contains the statement IDs, which the lockbox then reads to determine which units to pay.

PAYMENT_BLOCK_ENFORCE: Enter ACCOUNT to block payment for an entire account; enter YEAR to block payment only for specific years of an account. The Block Account for Payment flag must be set for each year if the preference is set for YEAR.

BLOCK_ACCOUNT_TU: Enter the escrow unit to put money that is directed toward blocked payments. Remember that if PAYMENT_BLOCK_ENFORCE is set to YEAR and years other than the year that is blocked are still due, the lockbox program will pay those other years before putting money in this escrow unit.  The default unit is 8001.  If you want a different unit, you will need to change this preference.

SPECIAL_CASHIER_OVERAGE_TU: (Harris County Tax Office only) overpayments for special cashier 9000 through 9200. The default is 8020.

SPECIAL_CASH8000_OVERAGE_TU: (Harris County Tax Office only) overpayments for special cashier 8000 through 8800. The default is 8025. For special cashier number 7000-7999, overpayments are put in unit 8001. For special cashier nos. 7000-7099, 7200-7299, 8000-8199 and 8600-8799, only units associated with the Linebarger law firm are paid.

LOCKBOX_PAYAGREE_RPT: Set to Y to let the lockbox program create a report on accounts with active payment agreements; set to N to not create this report. The default is N.

SHORT_PAY_ALLOCATION: By default, tolerance underpayments are taken out of penalty in the tax unit set in the PRIM_JURIS client preference.  If you wish to change where the under variance is taken from, set SHORT_PAY_ALLOCATION to one of the following: ATTORNEY, PENALTY, INTEREST, or DISCOUNT.  SHORT_PAY_ALLOCATION is ignored if SHORT_PAY_GO_NEGATIVE is set to N.  For examples of this, click here.

SHORT_PAY_GO_NEGATIVE: If you want the system to allow amounts applied to 'under tolerance'  to be taken from individual tax units (not 8003), set this client preference to Y.  To have amounts applied to 'under tolerance'  taken from the escrow column of 8003 (or the unit you set in UPAY_TOLER_TU), set it to N.

SHORT_PAY_NEG_ADJ_DISCOUNT: If the preference SHORT_PAY_ALLOCATION is set (is not expired) and the preference SHORT_PAY_GO_NEGATIVE is set to N, then this client preference, SHORT_PAY_NEG_ADJ_DISCOUNT, can be invoked for tax offices having discount units. Set SHORT_PAY_NEG_ADJ_DISCOUNT to Y to maintain the current behavior of increasing the discount amount if a discount unit is underpaid within tolerance. (For ex., if a unit's discount amount is.10 and the unit is underpaid by.01, the discount will show as.11.) Set SHORT_PAY_NEG_ADJ_DISCOUNT to N to leave the discount amount alone and instead put the underpay amount in the escrow column of unit 8003 as a negative amount (for ex., the discount amount in the previous example remains .10 and a -.01 is put in the unit 8003's escrow column.

OPAY_TOLER and OPAY_TOLER_TU: Set to the amount and unit, respectively, to use for overpayments within tolerance.

UPAY_TOLER and UPAY_TOLER_TU: Set to the amount and unit, respectively, to use for underpayments within tolerance.  

OVERPAY: Refunds will be placed in the tax unit specified in this client preference if CREATE_ADJUSTMENT_RECORD is set to Y

OVERPAY_STATUS: Set this to OH to have refunds created by overpayments placed on hold automatically.

FEES_PAY: If this is set to FIRST, then all fees (including Returned Check Fees) will be paid first, before any levies or penalties and interest. This happens even if the payment year specified in the lockbox file is different from the year for which fees are due. To disallow this, set to LAST or change the expiration date on the preference to a prior date.

IMAGE_URL, IMAGE_URL2: Set to the URL where the check and coupon images (if any) are stored. Contact ACT for assistance. At Bexar County, IMAGE_URL is used for the Frost Bank lockbox and IMAGE_URL2 is used for its RP Solutions image processing. If the IMAGE_URL preference is expired, the lockbox process will not add the directory path entered in that path as part of the database entry that holds the URL for the check and coupon images.

MIXED_HALF_PAY_UNITS: Set to Y to accept payments on accounts where some units allow half pays and others do not. If all half pay units are paid in full, any remaining money is used to pay the remaining units. Set to N to take payments only if all units accept half pay or no units allow half pays.

Note: On the Tax Rates tab of the Tax Unit Maintenance screens, the Half Pay Split Flag box must either be set to Y or left blank for each jurisdiction that will allow extended delinquency dates for half payments for the current tax year. The default setting for this flag is Y. If this preference is missing or set to something other than N, the payment program assumes each unit accepts half pays.

MIXED_HALF_PAY_END_DATE: Enter the date on which to end the messaging about mixed half pay units in advanced payments (for ex. 12/01/yyyy). You may not want this date to occur on a weekend. The preference MIXED_HALF_PAY_UNITS must be set to Y. If the lockbox is posted after this date but before 2/1/(tax year = 1) and the account has a split payment flag of H (for half pay), the non-half pay units will be paid first.

ATTY_SPCL_STMTS (Dallas County only): Set to Y to process attorney jurisdictions on coupon, otherwise enter N (the default).

ALLOW_LB_SHORT_PAY (Dallas County only):Set to Y to allow Dallas lockboxes to accept short payments, otherwise enter N (the default).

LB_RULE_1 (OBSOLETE, Dallas County only):Set to Y to post lock boxes by maximum year and maximum tax unit number first, or set to N to post by maximum year and lowest unit number first.

LB_RULE_2 (Dallas County only): Set to Y to collect attorney fees on units 1-7999, or set to N (the default) to collect from attorney fees on units 1-999 only.

OVERPAY_DALLAS_LOCK: (Dallas County only) Set to Y to put overpayments in Dallas County lockboxes on hold. Set to N to not put these on hold.

UNDER_PAY_ALLOCATION : Determines which column a short pay within tolerance will come from.

OVER_PAY_ALLOCATION: Determines whether to put an overpay within tolerance within interest or penalty.

FORCE_DEP_DATE_CURRENT_MONTH: If set to Y, a deposit date within the current month must be entered. If any other date is used, the process will abort and the LB10E report will display the reason for the error. When set to N (the default), this requirement is not enforced.

ESCROW_REFUND_TU: Enter the tax unit used to accept advance payments made on the next year's taxes.

WEEKEND_LOGIC_FOR_PANDI: If set to N, penalty and interest will always increase on the first day of the month. If this is set to Y, penalty and interest will not increase until the second business day of the new month if the last day of the month is on a Saturday or Sunday. This applies to current and prior year delinquent amounts. When taking a payment, the receipt date of the deposit will observe this rule also; if, for example, February 28 is on a Sunday and this preference is set to Y, additional penalty and interest will not be added to accounts until March 2, a Tuesday. Payments with a receipt date of March 1 will be charged penalty and interest as if it were still February. The default setting is N.

Move the lockbox file from the FTP server to your local hard drive:

  1. Using My Computer on your PC's desktop, go to Tools and select Map Network Drive.
  2. In the Folder field, enter \\[IP no. for ACT server\FTP_[tax office name]_Mortgage.
  3. Click Finish.  A window will appear that lists all the files in the FTP directory.
  4. Highlight the lockbox file.

Note:  The file must be in a text format and the name must not have any spaces in it.  Be sure to save the file with a.txt extension

  1. Copy and paste the file to your local hard drive.

Move the payment file to the ACT 7 server:

  1. From the Main Menu, click on Products, then Batch Products.  The ACT Batch Menu will appear.  
  2. Upload the file to the ACT 7 server. This copies the file, it does not remove the file from your system.

Post the lockbox payments:

  1. Return to the Batch Menu.
  2. Click in the batch menu item that corresponds to your lockbox. For example, Prosperity Bank Lockbox Process with Images.or for Nueces County, TDS check swiping, no. 123).  The item number should appear in the Selection field at the bottom of the screen.
  3. Press Enter.  The parameter screen will appear. There may be several fields that are not visible when entering this screen.  Use the down arrow key from the last visible field to scroll to them, or use the scroll bar on the right side of the screen.

Note: Not all lockbox parameter screens have all of the fields described below, or the names of the fields may vary slightly from what is noted below. Please skip the instructions for fields that are not on your particular parameter screen.

  1. Enter the file name of the uploaded file in the File Name field.

Note: This has to be exact and is case sensitive. Include the file extension of.txt in lower case.

  1. In the Deposit No. field, enter up to 12 characters. For some tax offices, the system will use the first 8 and assign the rest beginning with '0001'. Other tax offices can use all 12 characters and/or digits to create their own deposit number.  A separate remit sequence no. is created for each transaction.
  2. (Oracle version only) In the Deposit Type field, enter LB (lockbox), CC (credit card), EC (e-check), MC (mortgage company), or BP (bill pay).
  3. Enter the desired Deposit Date for the deposit being created.
  4. Enter the desired Receipt Date for the deposit being created. (For Harris County Internet payments only, the payment transaction date on the file will be used instead of this receipt date).
  5. (Cobol version only) In the Report Option field, leave the default of D.
  6. In the Posting Option field, enter E to edit or P to post. (In the Oracle version, this is called Process Option.)

Note: Edit mode shows how the payments will post and does not actually change the account records. It is recommended that you run this first to prevent duplicate payments; if duplicate payments have been made, the amounts on this file will appear as refunds. Post actually applies the payment to the account.

  1. (Cobol version only) Enter a four-character operator ID in the Operator field. Example: LKBX for lock box.  
  2. (Cobol version only) Leave the Deposit Override field set to the default of N to use the deposit date entered above.  To use the system date (today's date), enterY.
  3. In the Postmark Override field, enter Y to use the receipt date you entered above.  Leave the default of N to use the receipt date on the lockbox file itself.
  4. Set the Funds Source and Payee Code (Payee Code is in the Cobol version only) fields to the default of 0 if you have no fiduciary or if you are using the fiduciary given in each record of the file.

Note:  If you want to override the fiduciary code listed in the file, change Funds Source to 1 and enter the desired fiduciary number in the Payee Code field.  This number can be up to eight digits. You can also set Funds Source to 2 if you want to use the fiduciary number given in the header record of the file (call ACT for assistance). If there is no header record and you do not want to enter a fiduciary number, leave the default of 0.

For Bexar County, to use the fiduciary given in each record, set Funds Source to 1 and Payee Code to 0. Set Funds Sources to 3 to read the fiduciary in the header record for each transaction if it is greater than 0, but to read the fiduciary in the data record if it is less than or equal to 0. If a specific payment year is given in the file, the payment is posted to that year with overpayments being put the current year overpayment tax unit.

Payments are not posted to any years more recent that what is set in the CURR_YEAR client preference. For ex., if the preference is set to 2006 but 2007 data has been loaded into the production database, payments will not be posted to 2007.

If the Special Rule is set to 00 and there are multiple coupons associated with one or more checks, the first account is paid off in full first, then the second, and so on.  For Fort Bend County, the current year will be paid first on all accounts for that check.  Any remaining money will then be applied to the unpaid prior years, starting with the oldest year. Refunds are put on the last account associated with the check.

  1. (Cobol version only) In the Deposit Type field, enter MC for mortgage, LB for lockbox, CC for Internet payments or BP for Cadence bill pay).
  2. (Cobol version only) In the Do Not Use field, leave the default of N.
  3. In the Request Sequence No. field, leave the default of 1000.
  4. (Cobol version only) Leave the Portfolio Login Name field blank.
  5. (optional) Set the Escrow Override Unit field to an escrow unit number only if you want to use a different overpayment unit than what is in the OPAY_TOLER_TU client preference.
  6. (optional) Set the Escrow Override Status field to OH if you want all of the overpayment amounts to be put on hold. Leave this field blank to not put the overpayment refunds on hold.
  7. (Cobol version only) Leave the Portfolio Lock ID set to 0.
  8. (Cobol version only), RT Lawrence and Jaguar lockboxes only) In the Image URL Client Pref field, leave the default of URL2 to use the preference IMAGE_URL2 or enter URL to use IMAGE_URL.
  9. Leave the Office Location Code field blank if you do not use these codes (which are set in the Office Locations screen) or enter a specific office location code to assign to the deposit being created.
  10. (Cobol version only, OPECS Scanner lockbox only) Leave the Attorney ID field blank to post funds to all jurisdictions, or enter a specific attorney ID to post only to units associated with that attorney. Any remaining funds are put in the overpay tax unit.
  11. Click Submit Job.
  12. Click OK on the "OK to Submit Job" pop-up screen.

Note: If any errors occur during the lockbox posting, the program stops and 'rolls back' any payments already posted. See the LB010 report for information on the error.  For Philadelphia only, transactions are still posted up to the transaction that created the first error. One such error would occur is two or more checks were in a row on the file without corresponding coupons. An LBPRINT report is generated for Philadelphia that shows the accounts that caused the error.

After the process has completed (an End Time for this job appears after pressing F7, then F8), you can look at the deposit(s) in the Deposit Status screen, or you can run a Deposit Status Report to verify that the deposit(s) were posted correctly.

  1. To preview and print your reports, see Previewing and Printing Reports.

If the first line in the lower portion of the Batch Request screen says **FATAL ERRORS**, this mean that some account numbers are invalid, the total amount of the coupons does not match the total amount of the checks, or there is a duplicate deposit name (the program looks only at the first four letters/numbers of the deposit name).  You have several options. 1) You can edit the lockbox file and remove the invalid account numbers, in which case you will have to post those manually through the Advanced Payment screen in order to balance to the bank deposit amount for the file,  2) you can locate the coupon(s) with the invalid account number(s) and edit the coupon amount to match the check amount, or  3) you can post the file without any editing.  In this latter case, the lockbox program creates a LOCKBOX-CLEAR account that contains the funds for the invalid accounts.  Once you have determined how to correct the amounts, you will need to transfer money from the LOCKBOX-CLEAR account to the correct accounts.

(Montgomery County 2012 lockbox only) For accounts whose scan line numbers are longer than 7 digits and those having scan line numbers whose first 7 digits (actually digits 2-7 only) match the same digits in the longer scan line numbers, the lockbox will put these payments in the LOCKBOX-CLEAR account for tax office research and posting. The accounts will be listed on the LB010E report. The amounts put in LOCKBOX-CLEAR are also on the LB060 report. These accounts have also been put into a trigger table that has a request seq. no. of 1. The trigger table is used to compare scan line numbers to the accounts in the lockbox files.

This process creates several reports that show how the file will be processed and posted to the accounts. These reports are created both for Edit and Post modes. They can be seen by clicking on the appropriate line in the bottom half of the Batch Request screen, after you have clicked on the correct batch request seq. line for the Edit or Post process you just ran.

The reports are:

LBBC01P.nnnnn, LBBC01R, LB001, and similar front-end processors for each tax office: This lists the accounts and amounts for which the coupon and check data do not match. If this report has '** ERROR** in it,the 'debug' report, LB010 and LB040 reports will provide information on the errors.

Debug report: This lists each 'job' run by the lockbox. A return code of anything other than '0' indicates a failure.  The lockbox will stop processing and rollback any changes or posted payments already made.

LB010: This is the main lockbox processing program. It reads the lockbox file and determines the correct distribution, remittance, and posting rules. If no errors are found during the initial processing, you will not see this job listed in the batch request jobs. If there are errors, a report is generated that lists the account number, year, tax unit and an error message.  There will also a second LB010 line that produces no report, but that contains these words: "FATAL ERROR. ABORT." See above for more information on this message. You should also look at the LB040 for additional error messages.

LB012A:  This is the Batch Payment Processing Detail Transaction Listing, which creates the initial data report from the lb010 data. It lists individual transactions by type (which defaults to coupon), account number, amount to post to each account, post date (month and year only), tax year (defaults to 0), tax unit (defaults to 0) and payee (fiduciary number).  The information is sorted by deposit number (i.e., also by fiduciary), then by account number. The remit IDs (check numbers) are given for each deposit.

LB012E:  This is the Batch Payment Processing Special Transactions and Exceptions listing. It reads the posting rules, then  displays the transactions by deposit, then by account number, amount to post, post date (yyyymm only, displayed as the last 6 digits of the amount to post figure), tax year (defaults to 0), tax unit (defaults to 0), deposit date (yyyymmdd) and payee (fiduciary).

NJB020r – This  behind the scenes process sorts distribution records according to client preference settings.

NJB025r – This behind the scenes process totals the amount due for each validation number, account and year

NJB030r – This behind the scenes process allocates the posting rule amount to each distribution records

LB035A:  This is the Batch Payment Processing Overpayment Detail Register that allocates the remittance to the distribution records.  The report is sorted by fiduciary number, then by account number. It also lists, for each account, the deposit number, tax year, tax unit, overpay amount and (for most tax offices) the payee (fiduciary) for each check used to pay this account. If an account is listed more than once, that indicates that it is being paid with more than one check.   The total amount of overpayment given on the report is also provided. If an account is blocked for payment and sent to an escrow unit as a result, this report will have a message to that effect.

This report can be used to check to be sure that the file you are processing has not already been posted.  This will show you the refunds that will be set up in the case of duplicate processing.

NJB036r – This behind the scenes process removes duplicate distribution records

NJB037r,NJB038r – These behind the scenes processes detect and correct levy overpayments on coupon collisions. They take duplicate payments (those for the same account and year that could result in an overpayment of that year when other years remain due) and applies the overpayment portion to, first, the current year, and then to either the oldest or most recent year.

LB037E: This is another Special Transactions and Exceptions report that lists partial payments and duplicate payments.  Discount payments are not considered to be partial payments. Included on the report for each account, the deposit number, tax year of the payment, amount, indications of half, quarter, and disaster pay, and the condition (for ex., partial payment applied).

LB037CE: This is the same as LB037E, but shows partial payments applied only to the current year.

LB38E: This report shows Coupon Collision Repairs. A coupon collision occurs when more than one coupon exists for the same account in the same batch on the file.  Coupon collisions result in a temporary overpay or refund before the money is allocated to other years.  AVAILABLE indicates a coupon collision resulting in money available to be allocated.  REMAINING shows what was left after the money was allocated to other years where money was owed.  If all money was allocated, REMAINING would be 0.00. NOT ALLOCATED indicates that the funds were not moved to other years.

LB040: Database Process Update Log. A behind the scenes process actually posts the payments to the database. If the report states Normal EOJ, you have posted the payments successfully.  If it states Edit Mode - No Database Updates, this is confirmation that you have run this in edit mode, not posting mode.  This also lists any tolerance overpayments. If the lockbox program fails, error messages are given here.

LBPPRPT: (optional) The Payment Agreement report lists accounts having payment agreement statuses of active, D1 (late 1 month), or D2 (late 2 months). For each account, the owner name, year he agreement was created, status, agreement number, begin and end dates of the agreement, monthly payment amount and the year of any active bankruptcy or lawsuits are given.

LB045 - TC298A:  This Lockbox Distribution report is sorted by deposit and gives the receipt date, and the totals per deposit for levy paid, discount given (if any), penalty & interest, attorney fees, other fees, refund amount and payment amount (a gross total for each deposit) .  Totals are given for the entire file.

LB045 - TC298B:   ThisLockbox Distributionreport is sorted by jurisdiction, then by tax year and roll code (all, real, personal, and other).  It lists totals for each year and roll code for levy paid, discount given (if any), penalty & interest, attorney fees, other fees, refund amount and payment amount (a gross total for each roll code per year).  Totals are given for each jurisdiction.

LB045 - TC298C:   ThisLockbox Distributionreport is a summary of LB045B.  sorted by year (whether delinquent or all), then by jurisdiction.  It lists totals per year and jurisdiction, and roll code for levy paid, discount given (if any), penalty & interest, attorney fees, other fees, refund amount and payment amount (a gross total for each roll code per jurisdiction).  Totals are given at the end of each year (delinquent and all).

LB050 - TC298D: This Lockbox Distribution report is sorted by jurisdiction and shows disbursement amounts separated by M&O, I&S, and total of M&O and I&S. Tax rates are shown, as are totals by year and fund for   levy paid, discount given (if any), penalty & interest, TIF amount, disbursal total (sum of levy, p&i, and TIF), attorney fees, other fees, refund amount and payment amount (a gross total for each fund per year).  Totals for each column are given for each jurisdiction.  Grand totals for all years are provided on the last page.

LB050 - TC298E:  This Lockbox Distribution report is a summary of LB050D.  It is sorted by jurisdiction and then by fund (M&O, I&S). For each unit and fund it displays levy paid, discount given (if any), penalty & interest, TIF amount, disbursal total (sum of levy, p&i, and TIF), attorney fees, other fees, refund amount and payment amount (a gross total for each fund per unit).

Out.log: This log file lists each of the lockbox's 'jobs' and reports whether it ran successfully or not.

LB060:  This is the Batch Payment Processing Transactions With Allocations report showing all of the remittance and distribution information for the lockbox being posted. It is sorted by deposit. The check amount (remit amount) and check numbers (remit ID) are given for each deposit. For each account, the year, units being paid, check number (associated with a numerical sequence 1, 2, 3, etc.), receipt date (YYYYMMDD), amount to post, total amount to post, and payee (fiduciary) are given.  If an account is being paid with two checks, it is listed twice, with the amount to post being the amount taken from each check.Totals are provided for each line and for each column of data for a remit sequence (a payment)

LB060R: (Harris County only) This Batch Payment Processing Transactions With Remit Sequence report is similar to the LB060 but adds the remit sequence number for each transaction.

LBSALERP - (Harris County only) This is a listing of accounts in the lockbox that have a legal status of 'SO' (sold).  The years that have this status are listed for each account.

LB101-PARTPAY - This lists partial payments. For each account, the unit paid, year paid, taxes due, and payment amount are given.

LBPRINT (Philadelphia) - This lists instances where multiple coupons or checks appear in the file. Only a single coupon/check relationship is permitted for this lockbox.

(Philadelphia only, for owner occupied payment agreements) The following posting rules are followed and displayed in the same reports as above, but each is appended with 'O', for ex. LB060AO. Also, the lockbox will have both regular accounts and accounts belonging to owner occupied payment agreements. Two deposits will be created, one for the regular accounts and one for owner occupied payment agreements that is the same deposit number + 'O', for ex., 20140720O:

First pay all fees (9000) for all tax years, beginning with oldest tax year.

Then find oldest tax year with amount due.

If principal (5200) is due, move any calculated interest to unit 5301 (booked interest) of that tax year.

Move any calculated penalty to unit 5302 ( booked penalty) of that tax year.

Update due date of receivable of tax unit 5200 to first day of next month of receipt date entered.

Pay principal (unit 5200) with attorney fees for that tax year.

Pay booked interest (unit 5301) with calculated 18% attorney fees for that tax year.

Pay booked penalty (unit 5302) with calculated 18% attorney fees for that tax year.

Pay lien (unit 5303) with attorney fees for that tax year, and then any other unit (5304, 5305, etc.).

Repeat for the next oldest year with amount due.