PredictAP fields stay up to date in two ways. Bi-Hourly syncs with a secure API connection to Yardi, and nightly syncs with Posted IR data.
Bi-Hourly Syncs
These fields are refreshed on a two-hour cycle through a secure API connection between Yardi and PredictAP. During each sync, PredictAP retrieves the latest data directly from Yardi to ensure the information displayed in our system is current and consistent with your Yardi environment.
Header
Vendor
Remittance Vendor
- New vendor additions and deletions (e.g., deleting a vendor from your Yardi database) will be picked up everyone 2 hours.
- Customers who have full vendor syncs with more than 20k active vendors may experience a greater than 2-hour delay after updating a vendor's status from active -> inactive or inactive -> active.
- Vendor status changes will be picked up every 2 hours for customers who do partial vendor syncs.
- If a vendor is deleted in Yardi database (for particle syncs) instead of being marked at inactive, PredictAP will not see this change and therefore not mark the vendor as inactive.
- PredictAP's Yardi interface user must have access to the vendor in order for PredictAP to access the vendor during syncs.
Purchase Orders
- If the purchase order is associated with a vendor that does not exist in PredictAP, we will not sync the PO until the vendor is added or populates in the vendor sync.
- If an open PO line item is associated with a GL account or property that does not exist in PredictAP, we will not sync the PO line item.
- VAT Rate and Tran Type fields will be visible (if applicable) and should be blank. Upon import to Yardi, if the PO has VAT Rate and Tran Type, those fields will auto-populate.
Detail
Entity
GL Account
Job Category
Expense Types
- PredictAP's Yard interface user must have access to the property/entity in order for PredictAP to access the property during syncs.
Nightly Syncs
When a PredictAP user updates an invoice record, those changes are saved when the invoice is submitted to Yardi. However, they are not added to the feedback loop at that stage.
Additional edits may also occur in Yardi during invoice review and approval. PredictAP waits until the invoice is paid and posted before using the final version to improve coding predictions for future invoices.
Every change made by users is saved, but only the values reflected in the posted invoice are used for training PredictAP. Once a value is posted, it will also appear as an option in the UI drop-down fields listed below.
The fields below are updated through a secure API connection from Yardi to PredictAP. This sync occurs once per night at 2:15 AM UTC (10:15 PM ET), ensuring the latest values are reflected in PredictAP:
Header
Funding Entity
UserPayableDefined2
Expense Type
Currency
Payment Method
Display Type
Detail
Job
Job Category
Job Contract
Segments
VAT Rate
Tran Type