When you code a Bill, you attach the matching purchase order by searching the PO number in the PO field. If a PO you recently created in your ERP doesn't appear — the field shows "no options" or the PO won't populate — it's almost always because the PO hasn't synced into Vergo yet.
Why this happens
POs, jobs, and cost/phase codes are created and maintained in your ERP (Foundation, Vista, or Spectrum) and synced into Vergo on a nightly schedule. A PO you entered in the ERP today generally won't be selectable in Vergo until the next sync runs — even when you can confirm the PO exists in the ERP.
What to do
Confirm the PO exists and is fully saved in your ERP.
If it's brand new, wait for the nightly sync to bring it into Vergo, then search the PO number again.
Need it sooner? Contact support and ask for a manual refresh — the team can re-pull your PO and coding data on demand. Once it's pulled in, the PO populates in the field and you can attach it to the Bill.
Include the specific PO number(s) and an example Bill URL when you reach out, so the team can confirm.
Related: jobs and cost codes
The same timing applies to jobs and cost/phase codes — they come from your ERP and refresh nightly. If a Bill needs a job or code that was just created in the ERP, it may not be available in Vergo until the next sync (or a manual refresh from support).