Deliver Remainder and Invoice Remainder on a PO

Deliver Remainder is significant in Two way and Three way matching principles.

Invoice Remainder is significant only in Three way matching.

Example:

Two-way matching:

1. When the PO with one line and quantity 8 is CONFIRMED, then the Deliver Remainder = 8, Invoice Remainder = 0.
2. When it is INVOICED, then the Deliver Remainder = 0, Invoice Remainder = 0.

Three-way matching:

1. When the PO with one line and quantity 8 is CONFIRMED, then the Deliver Remainder = 8, Invoice Remainder = 0.
2. When it is RECEIPTED, then the Deliver Remainder = 0, Invoice Remainder = 8.
3. When it is INVOICED, then the Deliver Remainder = 0, Invoice Remainder = 0.

Partial Receipt and Invoicing example for Three way matching:

1. When the PO with one line and quantity 8 is CONFIRMED, then the Deliver Remainder = 8, Invoice Remainder = 0.
2. When it is RECEIPTED PARTIALLY for 5, then the Deliver Remainder = 3, Invoice Remainder = 5.
3. When it is INVOICED PARTIALLY, then the Deliver Remainder = 3, Invoice Remainder = 0.

To conclude:

Deliver Remainder = Quantity - Received
Invoice Remainder = Received - Invoiced



Above example is where the 'Received' quantity is different (more) than the 'Invoiced' quantity. In the example:

Quantity  - 25
Received - 24.40
Invoiced  - 22.86

To cancel the Deliver Remainder and Invoice Remainder in this case, following is to be done:

1. Use the 'Update remaining quantity' from Update line > Deliver remainder and click the 'Cancel quantity' button. This will cancel Deliver remainder of 0.60.
2. To cancel the 'Invoice remainder' of 1.54, use the 'Correct' feature. Post the receipt for 22.86. This will clear the 'Invoice remainder'.

Thanks

Sarang

Some facts / observations about Projects...

1. Sales Price and Cost Price setup for a (specific) project does cascade down to the sub-projects, unless separate prices are setup for the sub projects.

2. Project SO can be invoiced to the customer via project invoice proposal, even if the Sales Order is not confirmed. (Create a SO, do not confirm and then run the project invoice proposal [with 'Sales order line' checked and 'Update item quantity' = All] and verify that the sales order line gets picked up in the project invoice proposal, even if it is not 'CONFIRMED'.)

3. Project PO can be invoiced to the customer via project invoice proposal, ONLY if the Purchase Order is invoiced / partially invoiced. If the PO is partially invoiced, then the project invoice will be of the proportionate sales value. If the PO is fully invoiced, then the project invoice will be of the full sales value.

4. Line Property from the Project does get cascaded down to Purchase Order, but it is not cascaded down to the Sales order. This is now corrected in the AX 2012 R3 CU9. [[Some more details on this: Sales Order line has a Line Property field at the table level (not displayed on the front end), but it is not populated at the table level. This was the bug. Because the Line Property field was not populated in the Sales Order line, the back to back PO created on top of it was also not having the Line Property field populated. Ideally the Project Purchase Order should have a line property or else the system complains about the line property missing while confirming the PO. However because the PO was created back to back from the sale order, which did not have line property, the system did not complain. However now this issue is resolved. Even if the Project SO has nothing to do with Line Property, but because the back to back PO created from SO should have it (Line Property), the line property is now being populated at the table level in the Sales Order line table.]]

5. Project invoice proposal, if cancelled, will still be seen in the project invoice proposal list with a status of Cancelled. (However Pending supplier invoice will not be seen in the list if deleted. But will still be maintained in the back end table.)

6. Project adjustment functionality has two main aspects: a. to allow the users to select the new values for the attributes of the transactions to be adjusted. b. to allow the users to select the default values for the attributes of the transactions to be adjusted.

7. The screen that appears after clicking the 'Adjust' button, will give the option for the user to change to 'New' attributes for all the transactions selected for adjustment OR to pull the default values of the attributes from the setup for all the transactions selected for adjustment.

8. Once clicked OK, all the transactions selected for for adjustment will be affected / changed / edited, however they will be displayed individually in the lower pane of the adjustment form based on the transaction selected in the upper pane of the adjustment form.

9. If you click the 'Post' button now, the adjustment will be posted ONLY for the transaction seen in the lower pane of the adjustment form. So if there are three transactions in the adjustment form, you will have to click the post button thrice and not once, as anyone would think.

10. This means that the lower pane of the adjustment pane will always have one transaction in any case, unless it is splitted.

11. Once the transactions are pulled up on the adjustment form and if the user has not done / selected anything on the intermediate form which asks the user to 'Split' or change to new values or select the default values, AND if the user wishes to now change the value of the attribute on the transaction, he can still do so by changing it manually in the lower pane of the adjustment form. After changing all the values, if the user feels like pulling it back from the default values, then user can make use of the 'Update' drop down and select what he wishes to do. The option selected in the 'Update' drop down will pull the default values for the selected attribute for that transaction.

12. The moment the first estimate is posted for either completed contract or completed percentage type of a fixed price project, the project invoice cannot be selected for credit note. If you try to do do, then you get this message: No transactions exist that can be selected for credit note.

13. Purchase order created from Project will have a project id field populated in the Purchase Order line, only if it was selected in the Project Id field in 'General' tab of the 'Create Purchase Order' form. If the project ID is not selected manually there and the PO is created, then there is no way that PO can be linked to the Project.

14. Sales price field in the Project Purchase Order Line is ONLY EDITABLE for the stand alone Project PO. However if the project PO is created as a back to back PO from a Project SO, then the Sales Price field in the Project Purchase Order Line is NOT EDITABLE and ZERO.

15.  If the dimensions are defined on the Customer record, then they are inherited on the Project Contract record. If the Project is created for that Project Contract, then the dimensions on the Project record are taken from the Project Contract record. If the dimensions are NOT defined on the Customer record and are defined on the Project Contract record, then the dimensions on the Project record are still taken from the Project Contract record. 

16. Dimensions are not pulled across from the ‘Project contract’ into the ‘Copy project wizard’. However, when the project is created using a ‘Copy project wizard’ and the dimensions left blank in the wizard, the project record inherits the dimensions from the ‘Project contract’. But if anyone of the dimensions is altered/changed in the ‘Copy project wizard’, then only the changed dimension appears on the final project record.

17. The Line property has Accrue revenue (Checked) and in the project group Post Cost - Expense = P&L, with Accrue revenue (checked), then the postings to
Dr WIP -sale value
   Cr Accrued revenue - sale value
only occurs if the Sales price is mentioned in the expense journal. If it is not mentioned, then this posting mentioned above is not posted.

More to follow on this...

Thanks
Sarang