WHAT'S HAPPENING
April 6, 2010
REDWOOD CITY, Calif. & PENNINGTON, N.J. -- (BUSINESS WIRE) -- Ingres Corporation, the leading open source database management company and pioneer of the New Economics of IT, announced today that it has entered into a strategic partnership agreement with Contemporary Software Concepts of New Jersey, Inc. (CSC of NJ). more>>
CSC is very proud to announce that 2009 represents our 30th year in business. As one of our goals for this year, we have rolled out our new web site. This site contains links to our products and service offerings, user forum, documentation for our ERP application, and access to emergency support.
Over the past 30 years, CSC has been providing world-class services to clients throughout the United States. Included in our many service offerings are web development, SQL Server database management and application support by Microsoft certified professionals, Linux, Windows, Solaris, Unix, and network support, application help desk support, and report and query development. Our network support encompasses all aspects of server maintenance and backup, router and firewall configuration, peripherals, hardware support, and desktop integration. Support is available for both in-house servers and offsite hosted environments.
Our programming staff has extensive coding experience with MS SQL Server 2000/2005, MS Access, C#, VB.Net, ASP.Net, JavaScript, and PHP. In addition to customization of standard software packages, we also design and code custom applications for unique business requirements and integrate custom applications with several third party packages. We support integration with forms design software, bar code applications, data mapping applications, HTML and AS400 screen capturing software, and data search utilities.
Contemporary Software Concepts' mission is to maximize the value of business software investment by providing our clients with the highest quality service, knowledge, and software products. We are committed to maintaining an environment of open communication and teamwork which supports continuing personal and career development. Our dedication to professionally meeting these challenges with integrity has made us a company of quality for our customers and ourselves.
Please keep us in mind for any projects you're considering.
Best regards.
Sandra Gromball
Vice President
THE TOOLS TO MANAGE YOUR BUSINESS
The TelesisMFG Bank Reconciliation function operates within the GL Chart of Accounts and receives about half its input through the General Ledger Interface. The Bank Reconciliation function collects the banking transactions from the Accounts Payable and Accounts Receivable modules and matches them with the details from the bank statement. Any number of banks may be reconciled, and each bank can have a number of discrete transaction types. You establish the rules for reconciling the transaction types, and the methods for matching the transactions from TelesisMFG and the bank.
Three categories of GL Accounts are required to control Bank Reconciliation:
Each bank account in TelesisMFG is tied to a GL number, and each GL number is tied to a self-balancing entity. Any number of banks could operate in the three categories. As an alternative, a separate set of three GL categories could be set-up for individual banks, if that is more appropriate to your requirements. The expected bank balance, after taking into account any unprocessed checks and deposits, is the sum of the three account balances. The Bank Inquiry feature in Bank Reconciliation is specifically designed to give you the current expected bank balance.
There are two major transaction types which run in the Bank Reconciliation module:
The only transaction that needs entered in the Bank Reconciliation function is the bank statement. Each bank statement is processed as a batch. System controls exist to ensure that the statement opening balance agrees with the current account balance, and that the closing balance agrees with the opening balance plus and minus the transactions shown on the bank statement. The Bank Reconciliation function focuses on transactions that TelesisMFG expects to find on the bank statement, and transactions that actually appear on the bank statement.
Each bank statement transaction entered in TelesisMFG has two reference number fields. The first field is used for the check number, deposit slip number, or any other number that the bank may show against a given transaction. The second field carries the bank's transaction code for each line. While you use only one TelesisMFG transaction code to enter the whole batch of transactions, each line on the bank statement has its own individual transaction code by which you can identify the type of line you are dealing with.
Data entry into Bank Reconciliation may be done either manually or loaded directly from a bank transaction tape. Instead of manually entering your bank statements, TelesisMFG can take the same information from a standard serial file held on disk. If your organization has a large volume of banking transactions this upload facility can be a great time saver.
You have the capability of operating multi company activities within TelesisMFG. Each organization can be run in a separate database, or you can run a number of organizations within the one database. Or you could use a mixture of both.
TelesisMFG fiscal years can start and end on any date; the date of each transaction determines which year and period it is posted to. The Bank Reconciliation function uses the same period and year as the General Ledger.
Inquiries
TelesisMFG has several quick reference inquiry features to make the reconciliation process more convenient. The Bank Inquiry feature displays the current state of any bank account in the GL. Information displayed is related to the following areas: unmatched bank statement transactions; unmatched TelesisMFG transactions; and the balance according to the last bank statement, plus or minus any unpresented checks, etc. These transactions also appear in normal GL transaction inquiries against the relevant banking categories in the General Ledger.
A Batch Browse feature allows you to inquire about the status of a number of batches or to locate a particular batch and examine the entries of selected bank statements. The Bank Reconciliation Inquiry gives you an on-line look at the transactions relevant to the reconciliation of a given bank code.
The Presentation Inquiry deals with TelesisMFG transactions and displays the customer or vendor name and the presentation date. The main purpose is to determine the presentation date of any particular check or deposit. The presentation date is blank if the transaction is an unpresented check or deposit.
Reports
All reports produced by Bank Reconciliation as part of the Reconciliation Run are fixed formats except for the Batch Edit report which you control as far as the specifics of layout, sequencing and content are concerned.
The Batch Edit report gives you a listing of the bank statement transactions in one batch or multiple batches, before those batches are closed. The listing can be used to check for keying mistakes, or for a batch imbalance. The purpose of the Batch Edit Report is multiple batches, before those batches are closed. The listing can be used to check for keying mistakes, or for a batch imbalance. The purpose of the Batch Edit Report is threefold:
The Detailed Bank Reconciliation Matching Report is produced as the system is matching the TelesisMFG and bank transactions. It is available in either full format showing one line per bank or TelesisMFG transaction, or summary style, which does not list the unmatched TelesisMFG transactions.
The Journal Worksheet Report makes the error correction task easier by suggesting the type of GL journal entry that should be entered to correct a given mismatch. You may select whether to receive a full report, a summary report showing unmatched bank transactions only or no report at all.
A Bank Reconciliation Statement is produced for each bank code in the run. The report final total shows the funds available in the bank, after accounting for unpresented checks and deposits.
System Security
TelesisMFG has taken significant precautions to assure the safety and integrity of your data. System security starts at the operator sign-on where each individual is verified to be a valid user and is then allowed access to only those functions you have approved for them. Setting up operator records, and the options that go with them, is done at implementation. Individual operators can be banned from accessing entire modules or only certain functions in the TelesisMFG main menu. They can be given full access to some functions, restricted access to others, and no access to yet others.
SEE WHAT WE CAN DO FOR YOU