Construction AP automation add-ons for Viewpoint Spectrum

Construction AP add-ons for Viewpoint Spectrum sit in front of the ERP: they capture invoices, code each line to job, phase and cost type, route approval by project or amount, and post to Spectrum through its web services. Vergo is one such add-on; it posts with Add Vendor Invoices and Add Job Cost Transactions, codes card spend and reimbursements the same way, and leaves payment in Spectrum.

October 28, 2026
See it with your ERP
Book Demo

Key takeaways

  • An AP add-on for Viewpoint Spectrum sits in front of the ERP: it captures invoices, codes them to job, phase and cost type, routes approval, and posts to Spectrum. Job cost, payroll, payments and reporting stay in Spectrum.
  • Check what Spectrum already covers before buying: Invoice Approval routing codes and, for Trimble Construction One subscribers, Automatic Invoicing of invoice headers.
  • The questions that separate add-ons are which Spectrum web services they post through, whether they code every line or only the header, and whether they also pay vendors.
  • Vergo codes each line by inference from your Spectrum history, posts with Add Vendor Invoices and Add Job Cost Transactions, and runs card spend and reimbursements through the same coding. It does not pay invoices.

Where should you go next?

What does Spectrum cover natively, and where do add-ons fit?

Spectrum covers vendor records, invoice entry, job cost, AP payment processing and a native digital approval process. Invoice Approval routes invoices through reviewers in the order set on a routing code, with approval limits per reviewer, and the routing code is assigned to a vendor. Trimble Construction One subscribers can also upload PDF invoices in batches to Automatic Invoicing, which extracts invoice headers and sends them to Spectrum as validated, unapproved invoices (Trimble Help).

Add-ons earn their place where volume meets job cost detail. A general contractor with dozens of active jobs receives supplier invoices with many lines across phases, subcontractor pay applications with retention, and rental invoices split across jobs. Someone still has to code the distribution line by line, and the right approver is the project manager on the job, not the reviewer attached to the vendor. Field purchases on company cards and employee reimbursements need the same job cost coding, and they usually arrive by a separate route.

What should you check in a Spectrum AP add-on?

  1. Which web services it posts through. Spectrum publishes a list of web services. For AP, the relevant ones are Add Vendor Invoices, Add Job Cost Transactions, Add G/L Journal Entries and Add Vendor. Ask which the add-on uses, and whether anything reaches Spectrum as a file import instead.
  2. How access is granted. Spectrum authorizes integrations with an Authorization ID created in the Data Exchange Installation screen, scoped to companies and web services. Your Spectrum administrator should know exactly what the add-on can write to.
  3. Line-level coding. Every line should carry job, phase and cost type, or a GL account for overhead. Header-only capture moves data entry around rather than removing it.
  4. Where approval lives. Upstream in the add-on, in Spectrum Invoice Approval, or both. Both means duplicate work for project managers.
  5. Commitments and compliance. How subcontract billings are compared with committed amounts, and how lien waivers and insurance certificates are checked before payment. Some add-ons do this themselves; others leave it to Spectrum and your payment process.
  6. Payments. Some add-ons also pay vendors, which means changing how money leaves the company. Others, including Vergo, leave payment in Spectrum.
  7. Card spend and reimbursements. Whether field purchases and employee out-of-pocket costs get the same job cost coding and land in the same reconciliation, or need a second tool.

What does a field purchase look like with an add-on?

A superintendent buys lumber and fasteners on a company card at a supply house. Without automation, the receipt photo goes to the AP clerk by text, and days later the clerk keys vendor, amount, job, phase and cost code into Spectrum after checking with the superintendent. With Vergo, the superintendent gets a text asking for the receipt and replies with a photo. Vergo reads the receipt line by line and proposes the job, phase and cost type from what was bought. Once the charge clears, the coded entry syncs to Spectrum without re-keying. The same coding applies to supplier invoices and employee reimbursements.

Does the AI read the receipt, or just the header?

This is where AI-native coding separates from OCR. OCR lifts the vendor, the date and the total off the top of the receipt, then hands the coding back to a person. Vergo reads the receipt itself, line by line, and predicts the coding from what was actually bought: the job, the phase and cost code, and the cost type, not just the vendor name on the header. One run to a supply house can be three cost codes across its lines, and header-level capture cannot see that. Every coding shows why it was chosen, so review means confirming in seconds rather than re-coding by hand.

How does Vergo handle this?

Vergo is an AI-native, card-agnostic spend platform for card spend, employee reimbursements and AP invoices. Vergo proposes the coding by inference from your own accounting structure and history: no rule library to build, no keyword lists to maintain, and new vendors are coded on first sight. Employees handle everything by text message, with no app to download and no portal login, and Vergo chases missing receipts itself. Approval workflows are optional: route by GL account, by amount, or by project, or skip approval flows and let policy flags catch only what breaks a rule. Transactions are ready to code the moment they happen, and once they clear, they sync into Spectrum.

Vergo connects through Spectrum's own API web services: approved invoices post with Add Vendor Invoices, job-cost entries with Add Job Cost Transactions, GL-only entries with Add G/L Journal Entries, and a vendor seen for the first time is created with Add Vendor; the vendor list is read with Get Vendors. Connecting your existing cards involves no card applications, no re-issuing and no banking change. Vergo does not pay invoices; payment stays in Spectrum.

Related questions

Frequently Asked Questions

Does Viewpoint Spectrum have built-in AP automation?

Partly. Spectrum includes vendor records, invoice entry, payment processing and native Invoice Approval routing. Trimble Construction One subscribers also get Automatic Invoicing, which enters invoice headers from uploaded PDFs. Add-ons are used for line-level job cost coding, routing by job, and bringing card spend and reimbursements into the same process.

What is the difference between an AP add-on and replacing Spectrum?

An add-on extends Spectrum without replacing it. Spectrum keeps job costing, payroll, payments and reporting. The add-on handles capture, coding and approval, then writes the finished entry into Spectrum through its web services.

Which Spectrum web services should an AP add-on use?

For AP, the relevant entries in Spectrum's web services list are Add Vendor Invoices, Add Job Cost Transactions, Add G/L Journal Entries, Add Vendor and Get Vendors. Ask any vendor which of these it calls and whether anything is imported by file instead.

Which Spectrum AP add-ons also pay vendors?

Payment-led platforms such as AvidXchange describe processing invoices and making electronic payments for Spectrum users. Vergo does not pay: it captures, codes, approves and syncs, and payment stays in Spectrum. Decide first whether you want to change how you pay vendors.

How should subcontractor lien waivers be managed in a Spectrum AP workflow?

Make receipt of the conditional waiver a condition for approving the current pay application, and the unconditional waiver for the prior period a condition for processing the next one. Keep the check inside the approval step, so the Spectrum payables list only contains invoices that are ready to pay.

How does Vergo integrate with Viewpoint Spectrum?

Through Spectrum's API web services, authorized with an Authorization ID from the Data Exchange Installation screen. Vergo posts approved invoices with Add Vendor Invoices, job cost entries with Add Job Cost Transactions, GL entries with Add G/L Journal Entries, new vendors with Add Vendor, and reads vendors with Get Vendors.

Can field staff submit invoices and receipts without Spectrum access?

Yes. With Vergo, field staff reply to a text message with a photo of the receipt or invoice. There is no app to download and no portal login, and they never need Spectrum credentials.

Does Vergo work for contractors running Spectrum alongside another ERP?

Vergo integrates with ERPs and accounting software, so a subsidiary on Viewpoint Vista or Foundation can run the same process. See the Viewpoint Vista and Sage 300 CRE integration pages for what posts to each.

CTA Succes Clicker
Get Started

Expense & invoice automation for your ERP

Book Demo
Book Demo