How to Register
 |
 |
 |
 |
|
CashWorks™ Frequently Asked QuestionsQ. Is it possible to use optional fields in CashWorks?
A. Starting from version 5.3D, CashWorks supports Sage 300 optional fields functionality (support for the Mandatory option is added in version 5.5E). Besides, Field Extender (another add–on from SYSTRONICS) can be used to capture any number of optional fields (including attachments) anywhere in CashWorks and in other modules of Sage 300.
Q. Can CashWorks be installed in Sage 300 with Oracle database? What if the server is Linux based?
A. CashWorks supports all databases supported by Sage 300. We have not specifically tested CashWorks with a Linux server, but we don't expect any problems with it. However, it may not run on Linux workstations.
Q. Does CashWorks support import/export functionality?
A. Import/export is supported throughout CashWorks, just like with any other module of Sage 300.
Q. How can payments to customers be handled? How about receipts from vendors?
A. CashWorks includes a Customer Payment transaction that can be used to handle customer refunds. Vendor Receipts are currently not supported due to lower demand for this transaction.
Q. Is there a way by which we can reset the document numbers in CashWorks?
A. The Year End feature allows resetting transaction numbers in older versions of CashWorks. Starting from CashWorks 5.5E, the Prefix, Length and Next Number for all transactions can be changed at any time.
Q. I added a new bank in Sage 300 Bank Services, but it does not appear in CashWorks. What should I do?
A. Once a bank is added in Sage 300 Bank Services, you need to define it in CashWorks as well. Go to CashWorks –> C/W Bank Services –> Banks. Use the finder on the Banks form to select the new bank, or enter the bank code manually (using navigation buttons will not show the new bank initially). Enter all the details and add the bank code. Once you do that, you will be able to use the new bank in CashWorks as well.
Q. Does CashWorks support different transaction numbering for each bank?
A. CashWorks has only one numbering system. Unfortunately, auto–generated numbers are not bank specific, so the sequence is common for all banks.
Q. Does CashWorks integrate with Project and Job Costing module?
A. Yes, CashWorks allows entering Customer Receipts and Vendor Payments for job related documents.
Q. Does CashWorks integrate with US Payroll?
A. Yes. U/P checks appear in CashWorks Bank Reconciliation screen allowing reconciling them the same way as other transactions entered through CashWorks. U/P checks also update C/W bank balances automatically during their posting.
Q. With what Sage 300 modules does CashWorks integrate? Which are the required ones?
A. CashWorks integrates with System Manager, Transaction Analysis and Optional Field Creator, General Ledger, Accounts Receivable, Accounts Payable, Project and Job Costing, and US Payroll. The required ones are System Manager and General Ledger. If you want to enter Customer Receipts and Vendor Payments then Accounts Receivable and Accounts Payable modules are also required.
Q. Does CashWorks have year–end procedures allowing deleting obsolete data?
A. Yes, CashWorks has Periodic Processing which includes Clear History and Year End. C/W Clear History allows deleting posted/deleted batches, posting errors, and the cleared reconciliation journal. Year End allows resetting batch and transaction numbers for all C/W transactions.
Q. When transactions are posted from CashWorks to A/R, A/P or G/L, are optional fields sent there too?
A. Optional fields in CashWorks are implemented in style similar to Sage 300. So if the same optional fields are defined in corresponding Sage 300 modules then optional field values pass on to those modules.
Q. Is it possible to print vouchers for Bank Transfers?
A. Yes, you can print them from the Bank Transfer or Transfer Voucher screens.
Q. Is there any reference fields available in A/P & A/R for transactions originated from C/W? The requirement is to reconcile transactions flowing from CashWorks to A/P, A/R & G/L.
A. This information is not available in AR/AP/GL, but you can extract it from C/W tables. In CWHDR table, fields AASCNTBTCH, and AASCNTENTR store the Sage 300 batch and entry numbers for realized entries.
Q. CashWorks substitutes the functionalities of A/R & A/P. This being the case, why don't we have a single posting of batches from C/W, which would update AR/AP respectively and create the final batch in G/L?
A. To post batches in A/R and A/P automatically, you have to select the Automatically Post Batches in Subledgers checkbox in C/W Options.
Q. Is it possible to have multiple checks in one entry?
A. No, you should create a separate entry for each check having its own transaction number, check number, check date, etc.
Q. Is it possible to drill down from Sage 300 modules to CashWorks?
A. Older version of CashWorks supports drill–down from G/L only. CashWorks 5.5E and newer support also drill–down from A/R and A/P to CashWorks.
Q. Is it possible to do a bank transfer from C/S Bank to C/W Bank. Or maybe there is another method of updating C/W bank from C/S bank? (In case when company uses C/S bank for normal transactions but for petty cash transactions uses C/W bank; fund has to transfer from main C/S bank to C/W petty cash Bank).
A. Unfortunately, it is not possible to mix C/S banks and C/W banks. If you do, bank reconciliation will not come right, neither in CashWorks nor in Common Services. So if a company is posting transactions to certain banks through CashWorks, they should ONLY post transactions to those banks through CashWorks, not from Common Services. Also, they should reconcile such banks only in CashWorks. And if some banks are used without CashWorks, then transactions to those banks must be posted ONLY from AR/AP, not from C/W.
Q. Does CashWorks integrate with Inter Company Transactions (ICT) fully like the standard Bank Services?
A. CashWorks sends batches to AR/AP/GL and sends reverse check and return check transactions to Bank Services within the same company database. It does not "know" anything about ICT.
Q. Can we have "Cash" payment type for G/L related transactions also?
A. In CashWorks versions up to 5.5D, cash type of transactions are only supported in customer receipts. CashWorks 5.5E adds support for cash type of transactions in customer payments, vendor payments, and G/L related transactions.
Q. Is it possible to post batches by range in CashWorks?
A. Starting from version 2017F PU1, CashWorks supports this functionality.
Q. Is CashWorks Compatible with Windows Vista?
A. Yes.
Q. Reversing a check from CCMC results in the following error: "Cannot reverse this check. It has been partially or fully paid by other check(s). You must reverse other check(s) that paid this check before reversing itself."
A. The error message comes from Sage 300 Bank Services. The check was used in the Apply To details of another payment transaction. In such cases, the other check must be reversed first, before the check in question can be reversed.
Q. I could not find an option to re–activate the application which shows "CashWorks Expired."
A. This behavior may be caused by a change in the systems date. If CashWorks detects that the system date has been changed backwards during evaluation period, it blocks the activation. As a solution we recommend to uninstall CashWorks, manually delete the C/W 55D.LIC file and install the application again. Once you do that, you should be able to enter the activation code.
Q. How does CashWorks determine this field CWHDR.ORIGPDC? When will this field change the value O and 1?
A. The value of the field CWHDR.ORIGPDC is set to 0 or 1 at the time of entering the respective transaction, and never changes. This field shows whether the check (if the payment type was 'Check') originally has been entered as PDC (CWHDR.ORIGPDC value is 1) or not (CWHDR.ORIGPDC value is 0).
Q. While realizing a vendor payment in the Management Console, the following error comes up: "Check number must be blank for non check transactions."
A. In Sage 300 A/P, each vendor can be assigned a default payment code. A/P supports payment codes of four types (Cash, Check, Credit Card and Other). Older versions of CashWorks (up to 5.4D/5.5D) only support the Check type of Payment Codes. CashWorks 5.5E onwards supports all types of payment codes.
The above mentioned error arises when you realize a transaction in CashWorks version D, and the default payment code assigned to the vendor is not of Check type. To resolve the issue, simply assign a check type payment code to the vendor. In CashWorks 5.5E onwards, the error does not appear as that version supports all payment types.
The above mentioned error arises when you realize a transaction in CashWorks version D, and the default payment code assigned to the vendor is not of Check type. To resolve the issue, simply assign a check type payment code to the vendor. In CashWorks 5.5E onwards, the error does not appear as that version supports all payment types.
Q. If CashWorks Customer Receipts and Vendor Payments are replacing A/R Receipts and A/P Payments, can we remove Receipt (Payment) Entry Rights from the Users in A/R (A/P) so that they will not enter transaction by mistake?
A. These transaction rights are required so that the users can enter Apply Document transactions in A/R and A/P. Besides, C/W requires those rights for realizing transactions. As a workaround you can define Apply Document as the default Transaction Type in AR/AP options, and then remove the Transaction Type field from the Entry Screen through UI Customization.