When transactions are approved in Vergo, they're exported to your ERP (Foundation, Viewpoint Vista, or Viewpoint Spectrum). A sync error means one or more transactions failed to transfer — most often because of coding the ERP won't accept.

The ERP rejects a transaction when a coding value doesn't exist or isn't valid there. A frequent example is a phase code that isn't enabled or applied on the job, or a Job/Cost Code/GL value that doesn't match the ERP.

A successful sync always moves the transaction to the Reported tab — that's your confirmation it went through.

After a sync runs, Vergo shows a results screen marking each transaction success or failed. Hover over the failed icon to see the specific error — it usually points straight at the field the ERP rejected. If the message isn't clear, contact support with the transaction URL.

Jobs, cost/phase codes, and GL accounts come from your ERP and refresh in Vergo nightly. If a value you need was just created in the ERP and isn't available yet, wait for the nightly refresh or contact support for a manual refresh, then correct the coding and retrigger the sync.

If the problem is the ERP connection itself rather than coding, that's tied to your ERP setup — see your ERP setup guide (Foundation, Vista, or Spectrum) for connection details, and contact support if the connection needs to be re-established. For a dropped card connection (a bank/Plaid reconnection), see Reconnecting a card connection.

If the ERP rejects a transaction because it already exists there, check the ERP before syncing again. If it was entered manually in the ERP, you may need to remove that manual entry to keep a clean audit trail. (To stop an approved transaction from syncing at all, an Admin can Mark it as Reported — see the duplicates article.)

If you've corrected the coding and it still won't sync, contact support with the transaction URL, the error shown on the results screen, and your ERP type.