The Error Messages Table lists the possible error messages that you may get when attempting to import transactions along with an explanation and/or suggested remedy.
|"<CODE>" is not a creditor
|The transaction is a Creditor Invoice, but the NameCode supplied does not correspond to a creditor. It may correspond to a debtor, in which case you will need to open the debtor in the Debtors/Creditors list and click in the Creditor check box.
|"<CODE>" is not a debtor
|The transaction is a Debtor Invoice, but the NameCode supplied does not correspond to a debtor. It may correspond to a creditor, in which case you will need to open the creditor in the Debtors/Creditors list and click in the Debtor check box.
|"<TYPE>" is not a valid transaction type
|Transaction type must be one of CR, CP, DI, CI., JN, SO, PO or QU
|Account Code not specified
|The Detail.Account field is blank.
|Bad field type (<Field Text>)
|You may get this error if MoneyWorks was expecting a number or a date, and the text was not a valid number or date. You should check the field ordering because you may be importing information into the wrong fields.
|Contra account "<CODE>" does not exist
|The value supplied for the Contra field is not a valid account code.
|Contra account "<CODE>" is not a bank account
|For cash transactions, the Contra field must contain a bank account code.
|Contra account "<CODE>" is not an accounts payable account
|For Creditor Invoices, the Contra field must contain an Accounts Payable account.
|Contra account "<CODE>" is not an accounts receivable account
|For Debtor Invoices, the Contra field must contain an Accounts Receivable account.
|Could not determine transaction type.
|There was not enough information for the Work It Out heuristic to determine the transaction type. Typically this is because there were no detail lines for the transaction.
|Couldn't adjust for rounding error. Transaction not written
|If there is serious sunspot activity and Venus is in Sagittarius it may happen that MoneyWorks cannot adjust the GST values in the detail lines to make the sum of the detail line grosses match the transaction gross. This "cannot happen", but if it does this error will occur during the import phase (not the check phase). The transaction will need to be corrected in the source application.
|Debtor/creditor code missing
|When importing invoices, you must supply a debtor or creditor code.
|Detail line does not balance
|Detail.Net + Detail.GST does not equal Detail.Gross
|Details don't match gross
|The supplied transaction gross value does not match the sum of the detail line gross values (actually, the difference is larger than the specified rounding tolerance). The gross value supplied may not include all of the detail lines that you are importing or you may be importing the wrong gross values (are you importing net values into the Detail.Gross field for example?)
|Field dependency too complex
|MoneyWorks could not determine a value for one of the Work it Out fields. You may have a circular dependency. This will happen if, for example, you specify Work It Out for all of the Net, GST and Gross fields of a detail line. MoneyWorks does not have enough information to work out sensible values.
|Field too long (<Field Text>)
|The text is too long to fit into the field. Text fields in MoneyWorks are limited in length. You must shorten the text in the source file.
|You have included a space or an @ sign in the debtor or creditor code.
|Invalid record format
|The data in the text file does not correspond to the format that was specified.
|Invalid transaction date
|The transaction date is not a valid date. Make sure that the dates in the import file match the local date formatting
|The Name "XXX" is not of the correct type
|You are attempting to import a sales invoice to a name that is not a debtor, or a purchase invoice to a name that is not a creditor. You need to change the settings in the original name record.
|Not enough fields
|There are less fields in the import file than were specified to be imported. The source application may not be exporting records in a consistent format.
|Record too long
|The record is larger than MoneyWorks' import buffer. The only solution to this problem, should you encounter it, is to reduce the amount of information in the record.
|Run out of disk space!
|There is no room on the disk to make more transactions. You need to quit from MoneyWorks and make more space available on your hard disk. If this happens, you will get this error during the import phase (not the check phase). The import will stop.
|Specified period not open
|MoneyWorks determines the transaction period from the transaction date. The transaction date may be beyond the end date of the most recent period. You will need to open a new period before you can perform the import.
|Stock journals cannot be imported
|MoneyWorks does not allow you to import stock journal transactions. General journals are OK, using JN for the transaction type. and a negative detail.net for a credit. Tax must be zero.
|System account not allowed
|You cannot include "system" accounts in imported transactions. System accounts include bank accounts, accounts payable/receivable, profit and loss, and GST control accounts. MoneyWorks automatically inserts an "invisible" detail line for the contra account, which is always a system account (either BK, AR or AP). You can see this detail line when you print transactions with the Print Full Details option.
|Tax cannot be applied to a * account transaction
|The Detail.GST field is non-zero and the tax code for the detail line is *. The * tax code must not have tax applied to it.
|The account "<CODE>" does not exist
|The account code in one of the detail lines is not a valid account code.
|The Debtor/Creditor field must be empty for cash transactions
|You have imported a value into the NameCode field (or used a constant value) and the transaction type is not CI or DI. The NameCode field must be blank for cash transactions. You cannot import receipts or payments that correspond to invoices using transactions--see Importing Payments/Receipts on Invoices
|The debtor/creditor "<CODE>" does not exist
|The debtor or creditor code supplied in the NameCode field does not correspond to an existing debtor or creditor. To have MoneyWorks create new creditors when an unknown creditor code is encountered, click the Create Names check box in the Options dialog box when setting up the import.
|The invoice number: <NUMBER> is already used
|If the Check Invoice N°s option is being used, you will get this error if the invoice number (OurRef field) being imported is the same as the invoice number of an existing invoice. If you are using the Work It Out option for OurRef, you may need to set the next Invoice Number correctly in the Preferences (see Sequence Nos).
|The Tax Code "<CODE>" does not exist
|The tax code is not present in the tax table. This is most likely a fault in the source file, but you can also correct this problem by adding the code to the tax table using the Tax Codes command.
|Too many fields
|There are more fields in the import file than were specified to be imported. The source application may not be exporting records in a consistent format.
|Transaction is dated after current period
|The transaction date is after the end of the current period. You need to open the new period(s) before you can import the transactions.
|Warning - Tax code missing
|The Detail.Tax Code field was empty. You will get away with this warning only if the Detail.GST field is zero. You should really ensure that the tax code is supplied. This can be done easily by using the Work It Out option.