Complete PHP/MySQL project

This project is to complete an ongoing php/MySQL database project. The current project is 50% completed. Successful bidder must be well educated and experienced with PHP4 and MySQL 5 and be able to create a maintainable CSS. The operating system on this server based program will be RedHat Linux AS 3.0 or Fedora 4.0. ## Deliverables Create PHP form to add users to users table. There will currently be 5 classes/groups of users. Each user group must have specific rights granted to specific tables defined in the [login to view URL] page. Users table to record all user info as well as group assignment. Group names follow: Data Entry CSR Adjuster Reviewer Billing Rights to specific tables/fields will follow after acceptance of bid. Each user will be assigned to only one group. The group is login specific via username and password. Session tracking and auditing must be enabled via cookie sent to the user machine and IP addy must be tracked per each session in the audit log located within the MySQL database. Audit log to be searchable by username, date, IPaddy and must have Boolean search capabilities. Uploadable files. File will be uploaded via web upload. Each file must be tagged to a specific item in the main transaction table. Files will be in .pdf format and will have several large photo files embedded in each file. Automated e-mail for uploaded files will be sent to reviewer and CSR notifying each of an upload of specific file number. The uploaded file must be named/renamed to the corresponding file number. Reviewed files. Files processed by reviewers must be viewable via link to the .pdf file for each item in the transaction table. The reviewer will either accept or reject the file as correct or incorrect. If the file is correct, an email will be sent to CSR, adjuster and to billing notifying of the acceptance of the file AS-IS. If the file is rejected, an email will be sent to the CSR and adjuster notifying them of the rejected status of the file (by file number) and the reviewer must be able to make notes on the email as to why the file was rejected and these notes must also be recorded in the customer notes table. Billing System. No work has been completed on the billing system. Requirements for the billing system is as follows. 1. Each vendor has a particular rate schedule they pay for work done. Each vendor has specific parameters for each type of work done. The bill must integrate, from a vendor pay table, the information billable to each vendor as per their parameters. These parameters change from month to month and must be updatable through a php form. The invoice to be produced will be provided upon successful bid acceptance. The invoice total will be written to a current receivables table. Each type of work (line item detail) for each invoice is to be written to a current transaction table. When complete payment is made by the vendor for the entire invoice amount, the invoice total is to be moved from the current receivables table to a history receivables table and the transactional data is to be moved from the current transaction table to a history transaction table. Partial payments of invoices can be accepted but current status does not change until the balance due for the invoice reaches $0.00. 2. Adjusters get paid a percentage of each billing type. Some of the billing types are paid at 100%, others are paid at a negotiated percentage. This information is kept in a table for adjuster rates. Calculations for payroll must be made based on these percentages upon receipt of payment from vendor. Payroll data is auto entered into the payroll table upon receipt of vendor payment for a file. In the event of partial vendor payment, the amount due the adjuster will be calculated by the following formula: $ amount of partial payment/$ Total of invoice = adjuster pay. Payroll must be flexible enough for end user to choose payroll periods (ex. Weekly, bi-weekly, semi-monthly, monthly). Payroll for each adjuster is accumulated until the end of the pay period and a printable report must be generated by payroll clerk. Once the report for the period is done and payroll checks are printed, clerk will go back into the payroll file and update each adjuster’s line items with a check number and date. Once updated, the payroll file is updated with this information, all paid line items are moved to a history payroll table. When final payment is made by vendor, adjuster can be paid remainder due. Query by form functions. Database must have flexible “query by form?? functionality. End user must be able to query the database to determine which files are assigned to which CSR or adjuster or reviewer. End user must be able to query the status of each file. Status types are listed below: Unassigned Assigned Adjusted Reviewed Reviewer Approval/Rejection Billed to Vendor Paid by Vendor Adjuster paid. End user must be able to query “open?? files by adjuster and reviewer. End user must be able to query open receivables by vendor. End user must be able to query payroll table in the middle of a pay period in order to determine what is currently owed any or all adjusters. End user must be able to query YTD payments to adjusters for 1099 information. All queries must have date range function integrated All queries must be written in a manner that produces printable reports. A list of all required reports will be sent to the successful bidder along with examples. Design. The design must be aesthetically pleasing. Links to forms, reports, queries are to be done via ‘pop-up’ windows in order to allow employees to work in different modules of the program without closing other modules. The end user package must be wrapped in a bin file with algorithmic key code to unlock the program for use. Future plans are to utilize the serial number to unlock additional features of the program. Deliverables. The entire source code to be delivered in gzipped format. All code remains the copyrighted property of the buyer. A non-disclosure is required of the bidders before additional information is specified. The algorithmic program must be provided in a separate file. Buyer must be able to generate key codes for the end user. Any unused code, php pages, graphics, or files must be cleaned from the final product. All code MUST be professionally commented. Pages must be viewable in the following web clients: Netscape 5 or above Internet Explorer 5 or above Mozilla Firefox 1.5 or above OSX Safari 2.0 or above All deliverables will be considered "work made for hire" under U.S. Copyright law. Buyer will receive exclusive and complete copyrights to all work purchased. (No GPL, GNU, 3rd party components, etc. unless all copyright ramifications are explained AND AGREED TO by the buyer on the site per the coder's Seller Legal Agreement). ## Platform Linux AS 3.0 / Fedora 4.0 PHP 4 MySQL 5