Skip to main content
Skip table of contents

Posting Returned Core Invoices

Reference No: 24246

Details

In CR2, the Sales.csv file which gets generated when Accounts Receivable (AR) Batches are posted in either the Peachtree or QuickBooks format in the following set of scenarios, as explained below.

Scenario - 1

  1. Create a Parts Sale Order - Reservation (PSO) from Accounts module.

  2. Add a part to this PSO [PR#1].

  3. Enter a Unit Price for the added part.

  4. Click on the Return icon. The Return Items window opens.

  5. Enter the ID of a Part [PR#2] that is not added to this PSO and press Enter key. System prompts with the message "The scanned part was not sold on the order. Return anyway?".

  6. Click YES. Return Core window opens.

  7. Enter any amount in the Cost Price and Return Price fields.

  8. Click OK.

  9. A new part gets added to the PSO with status as Returned Core.

  10. Invoice the PSO.

  11. Post the Invoice in either the Peachtree or QuickBooks format from the Invoicing module.

The entries within the Sales.csv file which gets generated are as given in the table below.

Table 1.0

Column Number

Prior to version 02.00.08

From version 02.00.08 onwards

4

False

True

20

Negative Amount

Positive Amount

27

Negative Amount

Positive Amount

Scenario - 2

  1. Create a Parts Sale Order - Reservation (PSO) from Accounts module.

  2. Add a part to this PSO [PR#1].

  3. Enter a Unit Price for the added part.

  4. Click on the Dispatch icon and dispatch this part.

  5. Click on Return icon. The Return Items window opens.

  6. Enter the ID of a Part [PR#2] that is not added to this PSO and press Enter key. System prompts with the message "The scanned part was not sold on the order. Return anyway?".

  7. Click YES. Return Core window opens.

  8. Enter any amount in the Cost Price and Return Price fields.

  9. A new part gets added to the PSO with status as Returned Core.

  10. Change the Unit Price of the Part with status as Returned Core [PR#2] to any price higher than the Unit Price of the dispatched Part [PR#1]. System prompts the message "Changing Price will not change the cost of the Returned core."

  11. Click OK. The PSO Total becomes a negative amount.

  12. Invoice the PSO. An invoice with negative amount gets created.

  13. Post the Invoice in either the Peachtree or QuickBooks format from the Invoicing module.

The entries within the Sales.csv file which gets generated are as given in the table below.

Table 1.1

Column Number

Prior to version 02.00.08

From version 02.00.08 onwards

4

False

True

20

Negative Amount

Positive Amount

27

Negative Amount - for returned core/lines

Positive Amount - for returned core/lines

29

Positive - for sold line

Negative - for sold line

Scenario - 3

  1. Create a Parts Sale Order - Reservation (PSO) from Accounts module.

  2. Add a part to this PSO [PR#1].

  3. Enter a Unit Price for the added part.

  4. Click on Return icon. The Return Items window opens.

  5. Enter the ID of a Part [PR#2] that is not added to this PSO and press Enter key. System prompts with the message "The scanned part was not sold on the order. Return anyway?".

  6. Click YES. Return Core window opens.

  7. Enter any amount in the Cost Price and Return Price fields (for example, 100$).

  8. A new part gets added to the PSO with status as Returned Core.

  9. Add a Misc. Charge to the PSO with Unit Price less than that of the Part with status as Returned Core [PR#2]. (for example, Unit price of Misc Charge = 25$.)

  10. Invoice the PSO.

  11. Post the Invoice in either the Peachtree or QuickBooks format from the Invoicing module.

The entries within the Sales.csv file which gets generated are as given in the table below.

Table 1.3

Column Number

Prior to version 02.00.08

From version 02.00.08 onwards

4

False

True

20

Negative Amount

Positive Amount

27

Negative Amount - for returned core/parts

Positive Amount - for sold parts

Positive Amount - for returned core/parts

Negative Amount - for sold parts

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.