Customers/Sales Ledger System

Rough bid needed for development of a customers/sales ledger. This should be a very familiar project for anyone who has built such a system before. Development tool must be Microsoft Visual Basic 6.0. Data access must be carried out through ADO. Database will be Microsoft Access 2000. Basic requirements... Record general customer information, including their credit details; Analyse customer's invoices, credits and payments over a period defined by the user; Display balances for customers over a specified time period; Enter batch invoices and credit notes; Apply credit charges to customers who do not pay on time; Print customer labels, letters, invoices, statements and reports; Option to export labels, letters, invoices, statements and reports to Excel; Set an account status for individual customer accounts; Select a department to be used for analysis, and a discount percentage to be used in raising invoices and credits; Use extended credit control facilities, e.g. hold credit review details, such as date account opened, last credit review date and application date, and a memorandum field for further credit information; Phone customers via a modem link from computer; Set up multiple delivery addresses for customers; Use customised price lists for each customer, and/or allow selection of an additional discount scheme for customers; Set up and maintain customised customer price lists; Keep a record of contacts with customers, and raise contact invoices using the information entered; E-mail invoices and statements to customers; Database schema will be provided to the winning bidder, as will more in-depth specification detailing data entry screens, reports, etc. ## Deliverables 1) Complete and fully-functional working program(s) in executable form as well as complete source code of all work done. 2) Installation package that will install the software (in ready-to-run condition) on Microsoft Windows platforms (Windows 95 or later). 3) Complete ownership and distribution copyrights to all work purchased. 4) Code must be self-documenting and easy to read, with comments and any variables, objects, modules, classes, etc. named with standard Microsoft notation (e.g. mstr - module level string, gstr global level string, etc). ## Platform Microsoft Windows 95 or later.