Daily Close 2 Error Log

Back Office Menu -> Daily Close Menu -> Daily Close Errors -> Daily Close 2 Error Log

When Daily Close 2 is run the program checks for any errors that would result in posting problems or problems with the audit trails that will be generated in Daily Close 3.
 If an error is identified, that invoice remains in Batch status and does not post to History.
 It does not pass the Daily Close 2 level and is prevented from moving on to Daily Close 3 with the other invoices. The invoice in error will NOT post through Daily Close 2 until the errors for it, as identified on the Error Log, are resolved.

If errors are found, the Error Log is the last report printed automatically at the end of Daily Close 2 processing.
 Click the REPORT button at the bottom of this inquiry to re-print the Error Log report if required as outlined in Print Daily Close 2 Error Log.

The Error Log shows the Invoice # with the problem, the reference or type of error, and an error message stating the problem. The Sequence # indicates the number of problems, i.e. the first, second, third problem with that invoice.

Once the errors are solved, re-run Daily Close 2 to pick up and re-check the corrected invoices. On this second run of Daily Close 2, only the invoices that had errors will be left to be processed, so it should go quickly.

Note: If any product numbers have been changed, in Change/Merge Product Numbers, for any products in error on Invoices in Batch, re-run Daily Close 2 to also correct the product numbers on the error log.

Errors are sorted by the following reference types:
 HEADER - the problem has been identified in the invoice header
 D0000# - the error is in the Details and the detail sequence # is listed
 S0000# - the error is in the Services and the service sequence # is listed
 TAXES - the problem is related to the tax fields
 PMTS - the problem is related to the Payment method
 WARR - the problem is related to the product Warranty information

The following is a list of possible errors, and the steps needed to solve them.
 HEADER errors:

•CURRENCY CODE G/L ACCOUNTS MISSING

 Reference  Error Message
 ---------  -------------
 HEADER     DEFAULT ACCOUNTS RECORD FOR CURRENCY X
 

This error appears if an invoice has been generated for a currency (e.g. X) with missing or invalid G/L accounts.

The reference HEADER indicates that the problem was discovered when the software checked the invoice header.
 To solve:

1.Add the G/L posting accounts back into Default Accounts.

2.After solving all errors on the Error Log, re-run Daily Close 2 so that the invoices which caused the errors will post.

•CURRENCY CODE MISSING

 Reference  Error Message
 ---------  -------------
 HEADER     CURRENCY CODE X FOR CUSTOMER 2069
 

This error appears if an invoice has been generated for a Customer (e.g. 2069) with a missing or invalid Currency code (e.g. X).

The reference HEADER indicates that the problem of the missing Currency Code was discovered when the software checked the invoice header.
 To solve:

1.Add the currency code back in Currency Codes.

2.After solving all errors on the Error Log, re-run Daily Close 2 so that the invoices which caused the errors will post.

•CURRENCY EXCHANGE G/L ACCOUNT MISSING

 Reference  Error Message
 ---------  -------------
 HEADER     CURRENCY EXCHANGE ACCT#  FOR DEFAULT ACCOUNT X
 

This error is generated if there is no G/L account number assigned for the Currency Exchange amount, for the currency of the Invoice. (e.g. X ) The currency code on the invoice is assigned from the Customer record in Customer Information.
 To solve:

1.Enter a valid liability G/L account to be used for Currency Exchange postings, in Default Accounts for this currency code.

2.After solving all errors on the Error Log, re-run Daily Close 2 so that the invoices which caused the errors will post.

•CUSTOMER NUMBER INVALID

 Reference  Error Message
 ---------  -------------
 HEADER     CUSTOMER NUMBER 1408
 

This error is generated if the customer number (e.g. 1408) on the invoice has been deleted, merged, or is invalid.
 There are 3 options available to solve this problem:

1.If the customer number is wrong:

▪Print a copy of the Invoice.

▪Delete the Invoice from Batch in Delete A Single Invoice .

▪Re-enter the invoice for the correct customer number in Miscellaneous Invoices to be posted in the next DBR.

2.If the customer number is wrong:

▪Reset the invoice status to Current using the utility Move Invoice From Batch To Current.

▪Correct the customer number in Miscellaneous Invoices in Change mode, and post in the next DBR.

3.If the customer number is correct but has been deleted:

▪Add the deleted customer number back in Customer Information.

▪Re-run Daily Close 2.

•DAMAGE WAIVER G/L ACCOUNT INVALID OR MISSING

 Reference  Error Message
 ---------  -------------
 HEADER     DAMAGE WAIVER ACCT# YYYY FOR DEFAULT ACCOUNT C
 

This error is generated if the G/L account number assigned for the Waiver posting (e.g. YYYY ) is invalid or has been deleted for the waiver code on the Invoice.
 To solve:

1.Enter a valid G/L revenue account to be used for Waiver Revenue postings, in Waiver Codes for the default or for the currency in the window on the G/L by Curr field.

2.After solving all errors on the Error Log, re-run Daily Close 2 so that the invoices which caused the errors will post.

•DEPOSITS HELD G/L ACCOUNT INVALID OR MISSING

 Reference  Error Message
 ---------  -------------
 HEADER     CUSTOMER DEPOSITS HELD ACCT# 2999 FOR G/L DEFAULT X
 

This error is generated if there is a missing or invalid G/L account number (e.g. 2999) assigned for Customer Deposits Held, for the currency of the Invoice. (e.g. X ) The currency code on the invoice is assigned from the Customer record in Customer Information.
 To solve:

1.Enter a valid liability G/L account to be used for Customer Deposits Held postings, in Default Accounts for this currency code.

2.After solving all errors on the Error Log, re-run Daily Close 2 so that the invoices which caused the errors will post.

•DIVISION INVALID

 Reference  Error Message
 ---------  -------------
 HEADER     DIVISION CODE 006
 

This error is generated if the division (e.g. 006) assigned to the invoice has been deleted, or is invalid as a G/L type division.
 There are several options available to solve this problem:

1.If the division is wrong:

▪Print a copy of the Invoice.

▪Delete the Invoice from Batch in Delete A Single Invoice.

▪Re-enter the invoice with the correct division in Miscellaneous Invoices to be posted in the next DBR.

2.If the division is wrong:

▪Reset the invoice status to Current using the utility Move Invoice From Batch To Current.

▪Correct the division code in Miscellaneous Invoices in Change mode, and post in the next DBR.

3.If the division is correct, but has been deleted:

▪Add the missing division code back into Divisions.

▪Re-run Daily Close 2.

4.If the division is correct, but has been changed from a G/L Division Type:

▪Change the division type in Divisions to 'G/L' or to 'Both'.

▪Re-run Daily Close 2.

•HEADER AMOUNT DOES NOT MATCH DETAILS TOTAL

 Reference  Error Message
 ---------  -------------
 HEADER     INVOICE 4819 TOTAL NOT EQUAL TO DETAILS
 

This error is generated if the invoice details including the products, services, taxes, damage waiver, deposit taken, etc, have been adjusted but the invoice header has been not recalculated to allow for this change.
 To solve:

1.Print a copy of the Invoice.

2.Delete the Invoice from Batch in Delete A Single Invoice.

3.Re-enter the invoice in Miscellaneous Invoices to be posted in the next DBR.

Alternate solution:

1.Using Move Invoice From Batch To Current, reset the invoice to a Current status.

2.In Miscellaneous Invoices in Change mode, move the cursor through the invoice details and totals screens to recalculate the invoice amounts, to be posted in the next DBR.

•INVOICE NUMBER ALREADY USED FOR THIS CUSTOMER

 Reference  Error Message
 ---------  -------------
 HEADER     INVOICE 1090  CUST# 520 IN POSTED A/R INVOICES
 

This error appears if an invoice has been generated using the same invoice # (e.g. 1090) as an existing posted invoice for the same customer (e.g. 520).

The reference HEADER indicates that the problem was discovered when the software checked the invoice header.
 To solve:
 Print the 2 invoices, one from Batch and one from History from Print Invoices, and compare them to determine if this is a duplicate of the same invoice, by checking the invoice details, dates, and dollar amount.

oIf this is not the same invoice, and does need to be posted, delete the new invoice from Batch in Delete A Single Invoice and re-enter it in Miscellaneous Invoices with a different invoice number (e.g. 1090A), to be posted in the next DBR.

oIf this is a duplicate invoice and should not be re-posted, delete the second invoice from Batch in Delete A Single Invoice.

•INVOICE NUMBER ASSIGNED TO ANOTHER INVOICE

 Reference  Error Message
 ---------  -------------
 HEADER     INVOICE 1694 IN UNPOSTED A/R INVOICES
 

This error appears if a new invoice has been created using the same invoice # (e.g. 1694) as an existing unposted invoice.

The reference HEADER indicates that the problem was discovered when the software checked the invoice header.
 To solve:
 The postings for the existing unposted invoice can be reviewed in A/R Invoices. From these postings determine if this is a duplicate invoice, or print the 2 invoices, one from Batch and one from History, from Print Invoices. Compare them to determine if this is a duplicate of the same invoice, by checking the customer information, dates, invoice details, and dollar amounts.

oIf this is not the same invoice, and does need to be posted, delete the new invoice from Batch in Delete A Single Invoice and re-enter it in Miscellaneous Invoices with a different invoice number (e.g. 1694A), to be posted in the next DBR.

oIf this is a duplicate invoice and should not be re-posted, delete the second invoice from Batch in Delete A Single Invoice.

•METHOD OF PAYMENT CODE MISSING

 Reference  Error Message
 ---------  -------------
 HEADER     METHOD OF PAYMENT CODE #1   AMEX
 HEADER     METHOD OF PAYMENT CODE #2   DC
 

This error is generated if an operator deleted the Method of Payment Code indicated (i.e. AMEX or DC) from Method Of Payment Codes after the Method had been selected on an unposted Invoice.

The reference HEADER indicates that the problem of the missing Method of Payment was discovered when the software checked the invoice header.
 To solve:

1.Select Method Of Payment Codes and re-add the Method of Payment indicated as the source of the trouble.

2.After solving all errors on the Error Log, re-run Daily Close 2 so that the invoices which caused the errors will post.

•METHOD OF PAYMENT G/L ACCOUNT MISSING

 Reference  Error Message
 ---------  -------------
 HEADER     G/L ACCT# 1100 FOR METHOD OF PAYMENT CODE #1   CASH
 HEADER     G/L ACCT# 1105 FOR METHOD OF PAYMENT CODE #2   CHECK
 

This error is generated if there is a missing or invalid G/L account number (e.g. 1100 or 1105) assigned to the Method of Payment Code (e.g. CASH OR CHECK) in Method Of Payment Codes.

The reference HEADER indicates that the problem of the missing G/L accounts was discovered when the software checked the invoice header.
 There are 2 options to solve this error:

1.If the G/L accounts are incorrect:

▪In the Method Of Payment Codes correct the G/L accounts for the Method of Payments indicated as the source of the trouble.

▪After solving all errors on the Error Log, re-run Daily Close 2 so that the invoices which caused the errors will post.

2.If the G/L accounts are correct, but are missing from the Chart of Accounts:

▪Add the invalid G/L accounts back into Chart Of Accounts.

▪After solving all errors on the Error Log, re-run Daily Close 2 so that the invoices which caused the errors will post.

•METHOD OF PAYMENT NOT SPECIFIED

 Reference  Error Message
 ---------  -------------
 HEADER     ON ACCOUNT YES/NO NOT SET
 

This error appears if an invoice has not been designated as On Account, nor as paid by cash, Visa, or a valid Method of Payment.
 To solve:

1.Print a copy of the Invoice.

2.Delete the Invoice from Batch in Delete A Single Invoice.

3.Re-enter the invoice in Miscellaneous Invoices to be posted in the next DBR.

•TERMS CODE FOR A CUSTOMER MISSING

 Reference  Error Message
 ---------  -------------
 HEADER      TERMS CODE FOR CUST #  AAAAA , POSTED DUE DATE = INV DATE.
 

This error appears if an invoice has been generated for a customer (e.g. AAAAA) with a missing or invalid Terms Code in the "Codes" window of Customer Information.

The reference HEADER indicates that the problem was discovered when the software checked the invoice header.
 To solve:

1.Add the corresponding Terms code back into Terms Codes.

2.After solving all errors on the Error Log, re-run Daily Close 2 so that the invoices which caused the errors will post.

DETAIL errors:

•ACCUMULATED DEPRECIATION G/L ACCT# ON DEPRECIATION CLASS MISSING

 Reference  Error Message
 ---------  -------------
 D00003     ACCUM. DEPN ACCT# FOR DEPN CLASS XX  ON TAG#  ZZZZ
 

This error is caused by missing or invalid G/L posting account numbers in the Depreciation Class. A posting was generated to the Accumulated Depreciation account for the depreciated portion per the Fixed Asset Tag, on the sale of a Non-bulk rental product.

The "D" in the Reference D00003 indicates that the error is in an Invoice Detail. The number which follows the "D" indicates which detail line caused the error, i.e. 00003 indicates the third product on the invoice.
 To solve:

1.Enter valid G/L accounts in the window on the "Depreciation Accounts" field in Depreciation Classes.

2.After solving all errors on the Error Log, re-run Daily Close 2 so that the invoices which caused the errors will post.

•DEPRECIATION CLASS MISSING

 Reference  Error Message
 ---------  -------------
 D00004     DEPN CLASS ON TAG#  16660 FOR PRODUCT#    1000-0095
 

This error is caused by a missing or invalid Depreciation Class on the Fixed Asset Tag (e.g. 16660) for a Rental Product (e.g. 1000-0095).

The "D" in the Reference D00004 indicates that the error is in an Invoice Detail. The number which follows the "D" indicates which detail line caused the error, i.e. 00004 indicates the fourth product on the invoice.
 To solve:

1.Review the Fixed Asset Tag for the product in Rental Inventory, to identify the problem Depreciation Class.

▪If the Depreciation Class is incorrect, enter a valid class on the Fixed Asset Tag.

▪If the Depreciation Class is correct but invalid, enter the class back into in Depreciation Classes.

2.After solving all errors on the Error Log, re-run Daily Close 2 so that the invoices which caused the errors will post.

•DETAIL DIVISION INVALID

 Reference  Error Message
 ---------  -------------
 D00001     DETAIL DIVISION CODE 006
 

This error is generated if the division (e.g. 006) assigned to the invoice detail for the product revenue posting, has been deleted, or is invalid as a G/L type division.
 There are several options available to solve this problem:

1.If the division is wrong:

▪Print a copy of the Invoice.

▪Delete the Invoice from Batch in Delete A Single Invoice.

▪Re-enter the invoice with the correct division in Miscellaneous Invoices to be posted in the next DBR.

2.If the division is wrong:

▪Reset the invoice status to Current using the utility Move Invoice From Batch To Current .

▪Correct the division code in the expanded product detail in Miscellaneous Invoices in Change mode, and post in the next DBR.

3.If the division is correct, but has been deleted:

▪Add the missing division code back into Divisions.

▪Re-run Daily Close 2.

4.If the division is correct, but has been changed from a G/L Division Type:

▪Change the division type in Divisions to 'G/L' or to 'Both'.

▪Re-run Daily Close 2.

•EXCEEDED THE MAXIMUM ALLOWABLE NUMBER OF DETAILS

 Reference  Error Message
 ---------  -------------
 D00901     MORE THAN 900 DETAIL LINES
 

This error is triggered when an invoice had a total number of detail lines greater than 900.
 To solve, the invoice must be split into two or more invoices:

1.Reset the invoice status to Current using the utility Move Invoice From Batch To Current.

2.Print a copy of the invoice from Print Invoices.

3.Access the invoice details in Miscellaneous Invoices in Change mode, and delete the details from sequence 901 on.

4.Create a second invoice for the same customer and same date with the overflow detail records. This second invoice can be given the same invoice number with an 'A' to help identify it has a continuation of the original invoice. (e.g. 3912 & 3912A)

5.Both invoices will post in the next DBR.

•FIXED ASSET TAG MISSING

 Reference  Error Message
 ---------  -------------
 D00014     FIXED ASSET TAG# 16275   FOR PRODUCT# 32164-02
 

This error is caused by a missing Fixed Asset Tag (e.g. 16275) for a Rental Product (e.g. 32164-02).

The "D" in the Reference D00014 indicates that the error is in an Invoice Detail. The number which follows the "D" indicates which detail line caused the error, i.e. 00014 indicates the fourteenth product on the invoice.
 To solve:

1.Re-enter the same Fixed Asset Tag number for the product in Rental Inventory.

2.After solving all errors on the Error Log, re-run Daily Close 2 so that the invoices which caused the errors will post.

•MAINTENANCE PROVISION G/L ACCOUNT MISSING

 Reference  Error Message
 ---------  -------------
 D00001     MAINTENANCE ACCT#'S NOT SET UP FOR PRODUCT CLASS  XX
 

This error is generated if there are missing G/L account numbers for either of the two Maintenance Provision accounts in Rental Product Classes . (e.g. class XX ) The Product Class corresponds to the rental product that carries a maintenance provision hourly rate on the invoice.
 To solve:

1.Enter a valid liability G/L account to be used for Maintenance Provision postings, in Rental Product Classes for this class. The two accounts are:

▪MAINTENANCE EXPENSE - (expense account)

▪MAINTENANCE PROVISION - (liability account)

2.After solving all errors on the Error Log, re-run Daily Close 2 so that the invoices which caused the errors will post.

•MISC SALES ITEMS

 Reference  Error Message
 ---------  -------------
 D00006     PRODUCT # 4553  IS A MISC ITEM, COST MUST BE ENTERED
 

A Miscellaneous Product is often used for sales items that are "one time sales". The cost for these Miscellaneous items changes on every sale. In Sales Inventory, if the cost is zero and the product is flagged to Prompt for cost, the Daily Close #2 will stop any invoice which is selling this product from posting and print the error message that a cost must be entered.
 To solve, follow Steps 1 & 2 for ZERO COSTS FOR SALES ITEMS below.

•PRODUCT CLASS DELETED

 Reference  Error Message
 ---------  -------------
 D00012     PRODUCT CLASS P4552 FOR PRODUCT # 4221
 

This error is caused if the Product (#4221) was assigned to a Product Class (P4552) that no longer exists. An operator has deleted the Product Class. The Product Class assigned determines which General Ledger accounts should be used for posting the revenue and costs.

The "D" in the Reference D00012 indicates that the error is in an Invoice Detail. The number which follows the "D" indicates which detail line caused the error, i.e. 00012 indicates the twelfth product on the invoice.
 To solve:

1.The Product Class is missing.

▪If the Product Class is not supposed to exist any longer, change the Product Class on the item to a valid Class in Rental Inventory. In both Sale & Rental product programs, just Down Arrow to reach the Product Class prompt, and type in the new class.

▪If the Product Class is supposed to exist, re-add the missing Product Class using Rental Classes or Sales Classes.

2.After solving all errors on the Error Log, re-run Daily Close 2 so that the invoices which caused the errors will post.

•PRODUCT CLASS G/L ACCOUNTS MISSING

 Reference  Error Message
 ---------  -------------
 D00009     COGS ACCT#  5010 FOR PRODUCT CLASS S03
 D00009     REVENUE ACCT#  5010 FOR PRODUCT CLASS S03
 D00009     INVENTORY ACCT#  5010 FOR PRODUCT CLASS S03
 D00009     WARRANTY REVENUE ACCT#  5010 FOR PRODUCT CLASS S03
 D00009     SALE OF RENTAL ACCT# 5010 FOR PRODUCT CLASS S03
 D00009     CROSS STORE CHECK-IN ACCT# 5010 FOR PRODUCT CLASS S03
 

These errors are caused by missing or invalid G/L posting account numbers in the Product Class (e.g. SO3) for Cost of Goods Sold, for Revenue, for Inventory, for Warranty Revenue, for Sale of Rental, and for Cross Store Check-In accounts.

The "D" in the Reference D00009 indicates that the error is in an Invoice Detail. The number which follows the "D" indicates which detail line caused the error, i.e. 00009 indicates the ninth product on the invoice.
 To solve:

1.Enter valid G/L accounts in Sales Product Classes or Rental Product Classes.

2.After solving all errors on the Error Log, re-run Daily Close 2 so that the invoices which caused the errors will post.

•PRODUCT CLASS G/L DISCOUNT ACCOUNTS MISSING

 Reference  Error Message
 ---------  -------------
 D00005     INVALID DISCOUNT ACCT#'S FOR PRODUCT CLASS 90
 

This error only appears if the feature to Post Document Discounts to G/L is activated in the Company Posting Parameters and there is a missing or invalid G/L posting account number in the Product Class (e.g. 90) for Price Discounts, or for Circular Discounts.

The "D" in the Reference D00005 indicates that the error is in an Invoice Detail. The number which follows the "D" indicates which detail line caused the error, i.e. 00005 indicates the fifth product on the invoice.
 To solve:

1.Enter valid G/L accounts in Sales Product Classes or Rental Product Classes.

2.After solving all errors on the Error Log, re-run Daily Close 2 so that the invoices which caused the errors will post.

•PRODUCT DELETED

 Reference  Error Message
 ---------  -------------
 D00022     PRODUCT # 48982-01
 

This error is caused if the Product (#48982-01) no longer exists.

The "D" in the Reference D00022 indicates that the error is in an Invoice Detail. The number which follows the "D" indicates which detail line caused the error, i.e. 00022 indicates the twenty-second product on the invoice.
 To solve:

1.Print a copy of the Invoice.

2.Delete the Invoice from Batch in Delete A Single Invoice.

3.Re-enter the invoice correctly in Miscellaneous Invoices to be posted in the next DBR.

•PRODUCT POSTING ID CODE MISSING

 Reference  Error Message
 ---------  -------------
 D00017     INVALID POSTING IDENTIFICATION XX
 

This error is generated if there is an invalid Posting ID code (XX) on the invoice detail line for a non-bulk rental product. The Posting ID can be used to control the revenue and expense G/L posting accounts.
 This only applies if the Posting by Inventory by Customer Type processing has been activated in the Support Application Parameters.
 The "D" in the Reference D00017 indicates that the error is in an Invoice Detail. The number which follows the "D" indicates which detail line caused the error, i.e. 00017 indicates the seventeenth product on the invoice.
 To solve:

1.Review the Posting ID code for the product detail on the invoice in Posting Identification By Invoice. The invoice has a Batch status.

▪If the Posting ID code is incorrect, enter a valid code for the product detail on the invoice.

▪If the Posting ID code is correct but has been deleted, it can be re-entered in Posting Identifications.

2.After solving all errors on the Error Log, re-run Daily Close 2 so that the invoices which caused the errors will post.

•PRODUCT POSTING ID CODE G/L ACCOUNTS MISSING

 Reference  Error Message
 ---------  -------------
 D00019     REVENUE ACCOUNT XXXX FOR POSTING ID XX
 D00019     EXPENSE ACCOUNT XXXX FOR POSTING ID XX
 

These errors are caused by missing or invalid G/L posting Revenue and/or Expense account numbers in the Posting ID code (XX) assigned to the invoice detail line. These errors could also be caused if the Posting ID code itself, was missing or invalid, as explained in the previous error example.
 This only applies if the Posting by Inventory by Customer Type processing has been activated in the Support Application Parameters.
 The "D" in the Reference D00019 indicates that the error is in an Invoice Detail. The number which follows the "D" indicates which detail line caused the error, i.e. 00019 indicates the nineteenth product on the invoice.
 To solve:

1.Enter valid G/L accounts in Posting by Primary Customer Type, or update the Posting ID code in Posting Identification By Invoice for the invoice detail line for the product.

2.After solving all errors on the Error Log, re-run Daily Close 2 so that the invoices which caused the errors will post.

•REWARDS PROGRAM POSTING G/L ACCOUNTS MISSING

 Reference  Error Message
 ---------  -------------
 D00001     REWARDS REVENUE DEFERRED #
 D00001     REWARDS EXPENSE ACCOUNT #
 

These errors are caused by missing or invalid G/L posting Revenue and/or Expense account numbers in the Default Accounts for the currency of the invoice.
 This only applies if the Rewards Program processing is activated in Custom Processing.
 This error could be triggered by and Invoice Detail or Service.
 The number which follows the "D" indicates which detail line caused the error, i.e. 00001 indicates the first product or service on the invoice.
 To solve:

1.Enter valid G/L accounts in the Rewards Processing window of the Default Accounts.

2.After solving all errors on the Error Log, re-run Daily Close 2 so that the invoices which caused the errors will post.

•ZERO COSTS FOR SALES ITEMS

 Reference  Error Message
 ---------  -------------
 D00001     COST OF 0 FOR PRODUCT #  1553-345A   NOT ALLOWED
 

At the time of creating the invoice, the cost (average cost) of sales items is stored on the invoice. If the cost is zero, the Daily Close #2 will stop any invoice which is selling this product from posting and print the error message that a zero cost is not allowed.
 Items which have Cost Type + (Zero Cost) and Cost Type % (Auto Calculate cost as a percentage of selling price) will NOT cause this error. Disposals of Rental equipment for zero cost will NOT cause this error.

The "D" in the Reference D00001 indicates that the error is in an Invoice Detail. The number which follows the "D" indicates which detail line caused the error, i.e. 00003 indicates the third product on the invoice.
 To solve:

1.Select Correct Daily Close Cost Errors . The prompts are:

INVOICE #

From the Error Log Report, read the Invoice # and enter it here. The items which caused the errors will display, including the Product # and the Product Description.

COST

Press Right Arrow once to reach the cost field. Enter the cost EACH for this product.

COST DISCREPANCY

If the product quantity is also zero, a window opens stating that the cost of the sales part is currently zero in product file, and providing the opportunity to update the product average cost in Sales Inventory.
 Type N (NO) to leave the product average cost at zero in the product file. No over-shipped Cost Adjustment amount will be calculated in Post A/P Invoices, when the new quantity of this sale part is received and invoiced. If the new cost does differ, the over-shipped report will still print, but any adjustment must now be entered manually.
 Type Y (YES) to update the product average cost in the product file. Then later when the sale part is received and invoiced, if the new purchase price of the sales part is different, over-shipped Cost Adjustment transactions will still be generated in Post A/P Invoices.

Complete all other zero costs for items on this invoice.

Finished?

Press ACCEPT Key to return to the Invoice # prompt. Begin the next invoice, or press ESCAPE to exit.

2.After solving all errors on the Error Log, re-run Daily Close 2 so that the invoices which caused the errors will post.

3.If required, change the average cost in Sales Inventory to prevent future errors.

SERVICE errors:

•SERVICE CODE DELETED

 Reference  Error Message
 ---------  -------------
 S00001     SERVICE CODE  4
 

This error appears if an operator deleted the Service Code indicated (i.e. 4) from Service Codes after the Service had been selected on an unposted Invoice.

The "S" in the Reference S00001 indicates that the error is a Service. The number which follows the "S" indicates which Service detail line caused the error, i.e. 00001 indicates the first service on the invoice.
 To solve:

1.Re-add the missing Service using Service Codes.

2.After solving all errors on the Error Log, re-run Daily Close 2 so that the invoices which caused the errors will post.

•SERVICE CODE DIVISION INVALID

 Reference  Error Message
 ---------  -------------
 S00001     SERVICE DIVISION CODE 006
 

This error is generated if the division (e.g. 006) assigned to the service detail for the revenue posting, has been deleted, or is invalid as a G/L type division.
 There are several options available to solve this problem:

1.If the division is wrong:

▪Print a copy of the Invoice.

▪Delete the Invoice from Batch in Delete A Single Invoice.

▪Re-enter the invoice with the correct division in Miscellaneous Invoices to be posted in the next DBR.

2.If the division is wrong:

▪Reset the invoice status to Current using the utility Move Invoice From Batch To Current.

▪Correct the division code in the expanded service detail in Miscellaneous Invoices in Change mode, and post in the next DBR.

3.If the division is correct, but has been deleted:

▪Add the missing division code back into Divisions .

▪Re-run Daily Close 2 .

4.If the division is correct, but has been changed from a G/L Division Type:

▪Change the division type in Divisions to 'G/L' or to 'Both'.

▪Re-run Daily Close 2.

•SERVICE CODE G/L POSTING ACCOUNT INVALID OR MISSING

 Reference  Error Message
 ---------  -------------
 S00004     G/L ACCT# YYYY FOR SERVICE CODE ZZZ
 

This error appears if there is a missing or invalid G/L account number (e.g. YYYY) for the Service Code indicated (e.g. ZZZ).

The "S" in the Reference S00004 indicates that the error is a Service. The number which follows the "S" indicates which Service detail line caused the error, i.e. 00004 indicates the fourth service on the invoice.
 To solve:

1.Enter a valid G/L account in Service Codes, to be used for revenue postings for this service.

2.After solving all errors on the Error Log, re-run Daily Close 2 so that the invoices which caused the errors will post.

•SERVICE CODE WARRANTY G/L ACCOUNT INVALID OR MISSING

 Reference  Error Message
 ---------  -------------
 S00002     G/L ACCT# YYYY FOR SERVICE CODE WARRANTY XXX
 

This error appears if there is a missing or invalid G/L account number (e.g. YYYY) for the Warranty postings on the Service Code indicated. (e.g. XXX)

The "S" in the Reference S00002 indicates that the error is a Service. The number which follows the "S" indicates which Service detail line caused the error, i.e. 00002 indicates the second service on the invoice.
 To solve:

1.Enter a valid G/L account in Service Codes to be used for Warranty revenue postings for this service.

2.After solving all errors on the Error Log, re-run Daily Close 2 so that the invoices which caused the errors will post.

•REWARDS PROGRAM POSTING G/L ACCOUNTS MISSING

 Reference  Error Message
 ---------  -------------
 D00001     REWARDS REVENUE DEFERRED #
 D00001     REWARDS EXPENSE ACCOUNT #
 

These errors are caused by missing or invalid G/L posting Revenue and/or Expense account numbers in the Default Accounts for the currency of the invoice.
 This only applies if the Rewards Program processing is activated in Custom Processing.
 This error could be triggered by and Invoice Detail or Service.
 The number which follows the "D" indicates which detail line caused the error, i.e. 00001 indicates the first product or service on the invoice.
 To solve:

1.Enter valid G/L accounts in the Rewards Processing window of the Default Accounts.

2.After solving all errors on the Error Log, re-run Daily Close 2 so that the invoices which caused the errors will post.

TAX errors:

•TAX CODE DELETED

 Reference   Error Message
 ---------   -------------
 TAXES       TAX CODE  STX
 

This error appears if an operator deleted the Tax Code indicated (i.e. STX) from Tax Codes after the Tax Code had been selected on an unposted Invoice.

The Reference "TAXES" indicates that the software found the error when checking the Taxes on the invoice.
 To solve:

1.Re-add the missing Tax Code using Tax Codes.

2.After solving all errors on the Error Log, re-run Daily Close 2 so that the invoices which caused the errors will post.

•TAX CODE MISSING

 Reference   Error Message
 ---------   -------------
 TAXES       TAX CODE
 

This error appears if a Tax Code is missing on a product detail or service of an unposted invoice.

The Reference "TAXES" indicates that the software found the error when checking the Taxes on the invoice.
 To solve:

1.Reset the invoice status to Current using the utility Move Invoice From Batch To Current.

2.In Miscellaneous Invoices in Change mode, access the product details screen and press <F9> to Expand the product detail. Check the two tax codes in each record.

3.Also check the Expanded service details on the invoice to confirm that there are two valid tax codes on each record.

4.Post the invoice in the next DBR.

•TAX CODE G/L ACCOUNT NUMBER MISSING

 Reference   Error Message
 ---------   -------------
 TAXES       G/L ACCT# FOR TAX CODE  XXX
 

This error appears if there is a missing or invalid G/L posting account for the valid Tax Code "XXX".

The Reference "TAXES" indicates that the software found the error when checking the Taxes on the invoice.
 To solve:

1.Enter a valid G/L account in Tax Codes.

2.After solving all errors on the Error Log, re-run Daily Close 2 so that the invoices which caused the errors will post.

•TAX PROCESSING NOT COMPATIBLE

 Reference   Error Message
 ---------   -------------
 TAXES       TAX ON COST PROCESSING CANNOT BE USED WITH TAX SOFTWARE
 

This error appears if an item on the invoice utilizes a tax based on the product cost as set in Tax Codes, rather than based on the product price, and a third-party tax software such as Vertex is employed that does not respect tax on cost.

The Reference "TAXES" indicates that the software found the error when checking the Taxes on the invoice.
 To solve:

1.Change the 'On Cost' flag for the Tax Code in Tax Codes.

2.After solving all errors on the Error Log, re-run Daily Close 2 so that the invoices which caused the errors will post.

•TAX SETUP INCOMPLETE

 Reference   Error Message
 ---------   -------------
 TAXES       VERTEX: Tax Library is Not Configured.
 

This error appears if a software package such as Vertex is employed, but the setup is not complete in the Company Taxing Parameters.

The Reference "TAXES" indicates that the software found the error when checking the Taxes on the invoice.
 To solve:

1.Review the Vertex setup in the Company Taxing Parameters, checking the Web URL link and the Username and Password.

2.After solving all errors on the Error Log, re-run Daily Close 2 so that the invoices which caused the errors will post.

•TAX AREA UNDEFINED

 Reference   Error Message
 ---------   -------------
 TAXES       Error Determining Tax - Check Address
 

This error appears if Vertex software is employed, as setup in the Company Taxing Parameters, and the address on the invoice information is insufficient, or the information is too general, to determine the tax region.

The Reference "TAXES" indicates that the software found the error when checking the Taxes on the invoice.
 To solve:

1.Review the invoice and correct the tax address.

2.After solving all errors on the Error Log, re-run Daily Close 2 so that the invoices which caused the errors will post.

•TAX CALCULATION OUT OF BALANCE WITH VERTEX CALCULATION

 Reference   Error Message
 ---------   -------------
 TAXES       INV TAX (#.##) != VERTEX(#.##)
 

This error appears if Vertex software is employed as setup in the Company Taxing Parameters, and the taxes calculated on the invoice in SRM do not match the taxes that Vertex has calculated.

The Reference "TAXES" indicates that the software found the error when checking the Taxes on the invoice.
 To solve:

1.This error is really more of a warning.
 The invoice is not held in Batch. Instead it is processed through Daily Close 2 where it is moved to History and the invoice posting transactions are written to A/R Invoices.
 If the tax transactions lines on the invoice in SRM need to adjusted they can be corrected in A/R Invoices before the invoice is posted through Daily Close 3: Post Invoices

2.A comment is automatically added to the invoice to identify this condition. The comment is flagged not to print on the invoice.

PAYMENT errors:

•METHOD OF PAYMENT CODE MISSING

 Reference  Error Message
 ---------  -------------
 PMTS       METHOD OF PAYMENT CODE VISA
 

This error is generated if an operator deleted the Method of Payment Code indicated (e.g. VISA) from Method Of Payment Codes after the Method had been selected on an unposted Invoice.

The reference PMTS indicates that the problem is related to the Payment portion of the invoice.
 To solve:

1.Select Method Of Payment Codes and re-add the Method of Payment indicated as the source of the trouble.

2.After solving all errors on the Error Log, re-run Daily Close 2 so that the invoices which caused the errors will post.

•METHOD OF PAYMENT G/L ACCOUNT MISSING

 Reference  Error Message
 ---------  -------------
 PMTS       G/L ACCT# 1100 FOR METHOD OF PAYMENT CODE MC
 

This error is generated if there is a missing or invalid G/L account number (e.g. 1100 ) assigned to the Method of Payment Code (e.g. MC) in Method Of Payment Codes.

The reference PMTS indicates that the problem is related to the Payment portion of the invoice.

 There are 2 options to solve this error:

1.If the G/L accounts are incorrect:

▪In the Method Of Payment Codes correct the G/L accounts for the Method of Payments indicated as the source of the trouble.

▪After solving all errors on the Error Log, re-run Daily Close 2 so that the invoices which caused the errors will post.

2.If the G/L accounts are correct, but are missing from the Chart of Accounts:

▪Add the invalid G/L accounts back into Chart Of Accounts.

▪After solving all errors on the Error Log, re-run Daily Close 2 so that the invoices which caused the errors will post.

PRODUCT WARRANTY errors:

•VENDOR WARRANTY ACCOUNT NUMBER MISSING

 Reference   Error Message
 ---------   -------------
 WARR        G/L ACCT# YYYY FOR WARRANTY VENDOR ZZZ
 

This error appears if there is a missing or invalid G/L posting account (e.g. YYYY) for the warranty vendor (e.g. ZZZ) assigned on a W.O. invoice with warranty posting.

The Reference "WARR" indicates that the software found the error when checking the Warranty information required to post a Work Order invoice.
 To solve:

1.Enter a valid G/L warranty posting account in Vendor Information, for the vendor identified in the error message.

2.After solving all errors on the Error Log, re-run Daily Close 2 so that the invoices which caused the errors will post.

•WARRANTY TAX CODE INVALID OR MISSING

 Reference   Error Message
 ---------   -------------
 WARR        WARRANTY TAX1 CODE  GST
 WARR        WARRANTY TAX2 CODE  PST
 

These errors appear if the Vendor Tax Codes 1 or 2 (e.g. GST or PST) have been deleted from the Tax file. The warranty tax codes used on W.O. invoice are taken from Vendor Information.

The Reference "WARR" indicates that the software found the error when checking the Warranty information required to post a Work Order invoice.
 To solve:

1.Re-add the missing Tax Codes using Tax Codes.

2.After solving all errors on the Error Log, re-run Daily Close 2 so that the invoices which caused the errors will post.

•WARRANTY TAX G/L ACCOUNT NUMBER MISSING

 Reference   Error Message
 ---------   -------------
 WARR        G/L ACCT# YYYY FOR TAX CODE  XXX
 

This error appears if there is a missing or invalid G/L posting account (e.g. YYYY) for the valid Tax Code "XXX" to be used for warranty posting.

The Reference "WARR" indicates that the software found the error when checking the Warranty information required to post a Work Order invoice.
 To solve:

1.Enter a valid G/L account in Tax Codes.

2.After solving all errors on the Error Log, re-run Daily Close 2 so that the invoices which caused the errors will post.

ACTIONS:
 Additional actions provided by buttons on the Daily Close Error screen include:

•Print Copy of the Error List:
 Click the REPORT button at the bottom of this inquiry to re-print the Error Log report if required as outlined in Print Daily Close 2 Error Log.

Topic Keyword: RSEF01