Skip to main content

Phase codes and cost codes not populating — troubleshooting guide

When phase codes, cost codes, GL accounts, or equipment codes don't appear or auto-populate on transactions, it's usually a configuration issue with your ERP connection, rules, or account setup.

How codes pull into Vergo

Codes — phase codes, cost codes, GL accounts, and equipment codes — come from your connected ERP. Vergo refreshes these lists from the ERP nightly (about every 24 hours), so your coding options match your accounting system. You can search your full ERP code list right in each coding field's dropdown. If something was just added in the ERP and you need it before the nightly refresh, contact support for a manual refresh.

Phase codes not appearing on a job

Phase codes are job-specific — tied to the individual job in your ERP, not the global chart of accounts. If they're not appearing when you select a job, it usually means:

  • The job doesn't have phase codes set up in the ERP

  • The phase codes exist in the ERP but haven't synced yet (they come over on the nightly refresh)

  • Phase codes aren't enabled on your Vergo account

  1. Confirm in your ERP that the job has phase codes assigned and applied.

  2. Wait for the nightly refresh (or contact support for a manual refresh) and check again.

  3. If they still don't appear, contact support — phase codes are enabled by Vergo (typically at account setup if your company uses them), and the team can confirm or enable it.

Cost codes or GL codes not pulling in

  1. Confirm the codes are active in your ERP (inactive codes generally aren't imported).

  2. Check whether they appear on other jobs/transactions — if so, the issue may be specific to that transaction.

  3. If they were just added in the ERP, wait for the nightly refresh or request a manual refresh from support.

Custom Rules not auto-coding

Vergo's Custom Rules can auto-code transactions based on vendor, amount, or other criteria. They're on by default for all accounts and are managed in Settings → Custom Rules. If a rule isn't firing:

  • The conditions aren't met — check the rule's criteria against the transaction's actual data (vendor, job, amount).

  • The vendor name doesn't match exactly — vendor matching must match the imported vendor name precisely.

  • Rule order — rules apply in the order they were created, and the first matching rule wins.

  • The rule references a job that no longer exists — if the job was removed or renamed in the ERP, the rule can stop matching.

Equipment codes not populating

Equipment codes are enabled by Vergo, usually at onboarding. If the equipment code field isn't available or codes aren't populating, contact support to have it enabled, then confirm the codes exist in your ERP so they sync in.

💡 Tip: if you enter the same codes repeatedly for the same vendor or card, set up a Custom Rule (Settings → Custom Rules) to apply default coding automatically.

Did this answer your question?