26.1 Winter Product Updates

PO Data Sync & Matching - No manual lookup required!  

Manually cross-referencing PO numbers between invoices and Yardi was tedious and error-prone. PredictAP syncs PO data directly from Yardi, automatically detects PO numbers on invoice images, matches them to the correct PO, and validates against the predicted vendor.

(req. Yardi InterfacesVendorInvoicingPI22 or above)

 Automatic PO details Coding - Ditch the hand-coded PO invoices.

Invoices linked to a PO must have the correct line item data otherwise Yardi will reject the submission. PredictAP eliminates this failure point by automatically overwriting invoice line items with PO data before submission, while also validating that the invoice total aligns with PO line item amounts.*

(req. Yardi InterfacesVendorInvoicingPI22 or above)

*If you’re using PI25.7+ see PO Burndown below

 PO Visibility, Controls, & Exceptions - Manage POs with Ease 

When PO issues arise, users previously had little context to diagnose or resolve them. PredictAP surfaces clear invoice statuses for PO-related exceptions, provides a manual PO dropdown for vendor-specific selection, and exposes PO numbers across the invoice grid, in the filter options, and on the Invoice Status Report. 

(req. Yardi InterfacesVendorInvoicingPI22 or above)

 PO Partial Consumption (aka “Burndown”)

Property managers using a single PO across multiple invoices—like a $10,000 maintenance PO drawn down by several $2,000 invoices—previously had to create 1:1 POs or manually adjust amounts. PredictAP now supports partial PO consumption, submitting predicted invoice amounts against open PO balances and tracking the remaining balance available for future invoices. 

(req. Yardi InterfacesVendorInvoicingPI25.7 or above)