This is critical to have in LEAP. There are often instances where we need to pay for an item that was not ordered. If a supplier ships the wrong format or wrong book, we reach out to them and request a no-cost replacement for the one we wanted and were invoiced for. If we do not have an order for the item that was shipped in error, we very often request an invoice for it. The invoice they send does not load as an EDI, so we then create a manual (regular) invoice. We can do this and link the line(s) to a bib, but we cannot receive the line, cannot pay the invoice, and cannot create the item record.
The Client has this functionality, so that item can be linked to an invoice and supplier.

Here is the documented functionality in the client: https://documentation.iii.com/polaris/8.0/Default.htm#PolarisStaffHelp/Acquisitions/PAreceive/Receive_line_items_from_an_invoice.htm

In Leap, staff are having to add POLIs to copy to the invoice in order to receive them, which is a lot of extra work.

This is critical for us to get out of the staff client and into Leap for cataloging. Staff are being forced into staff client to fix invoices where the wrong fund was selected and they need to update quantity and price.

This is an issue we continually face, too. It is pretty necessary for us to have, as we often have some items in an order not submitted through EDI.

After trying this out on the test server, I can see why this is needed.