video1.0<iframe src="https://www.loom.com/embed/a1552601d752439a9fb65d76c61096dd" frameborder="0" width="1920" height="1440" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>14401920Loomhttps://www.loom.com14401920https://cdn.loom.com/sessions/thumbnails/a1552601d752439a9fb65d76c61096dd-4aa5afbd2470b646.gif151.83Until recently, PredictAP had no purchase order support for Nexus customers. With our PO Recognition release, I can detect PO numbers from invoice documents and submit them to Nexus automatically, but not every invoice includes a PO number. Now with PO Recommendation, when an invoice arrives without a PO, PredictAP checks for open POs that match on Vendor, Property, and Amount, then holds the invoice in a Review PO Recommendation exception stack and surfaces the best match for you to review. The suggested PO appears in the Purchase Order Number field, with a banner on top. I ask you to click Review Recommendation, confirm the suggested PO, or remove it to clear the PO number.