Key takeaways
- Spectrum already has an approval engine: Invoice Approval routing codes send an invoice through reviewers in sequence, with an approval limit per reviewer. The work that stays manual is coding each invoice line to job, phase and cost type.
- Trimble Construction One subscribers can use Spectrum's Automatic Invoicing, which enters invoice headers from uploaded PDFs as validated, unapproved invoices. The job cost distribution still has to be coded.
- For project cost management, the approver should be the person who owns the job budget, and the approved cost should reach Spectrum job cost the same day, not at month end.
- Vergo proposes the line-level coding from your own Spectrum history and posts through Spectrum's web services: Add Vendor Invoices, Add Job Cost Transactions, Add G/L Journal Entries and Add Vendor.
- Decide early which system holds the approval of record. Running two full approval chains on the same invoice doubles the work for project managers.
Where should you go next?
- See the Vergo + Viewpoint Spectrum integration
- Learn more about Vergo AP Invoice Automation
- See how Vergo approval workflows work
- Vergo for construction
What does Viewpoint Spectrum already do for invoice approval?
Spectrum has native digital invoice approval. An administrator turns it on under System Administration > Installation > Accounts Payable on the Invoice Approval tab, then builds routing codes under Accounts Payable > Maintenance > Invoice Approval Routing. Each routing code lists reviewers in the order they should see the invoice, can carry an approval limit per reviewer so small invoices skip senior approvers, and can send email notifications as the invoice moves. The routing code is applied to a vendor, and reviewers work their queue in Accounts Payable > Data Entry > Invoice Approval (Trimble Help).
Capture has also moved. Trimble Construction One subscribers can upload PDF invoices in batches to Automatic Invoicing, which extracts invoice headers and sends them to Spectrum as validated, unapproved vendor invoices that then enter Invoice Approval. Trimble notes that only vendors with a last invoice date in the past 12 months are recognized automatically.
That leaves two gaps that matter for project cost management. First, header capture does not produce the job cost distribution: someone still decides which job, phase and cost type each line belongs to. Second, routing is attached to the vendor, while the person who should approve a construction invoice is usually whoever owns the job it is charged to.
How do you automate invoice coding and approvals in Spectrum, step by step?
- Pick the approval of record. Either approve before the invoice reaches Spectrum and post it approved, or post it unapproved and let Spectrum Invoice Approval run. Pick one per invoice type so project managers approve once.
- Put every invoice through one intake. A single AP email address for suppliers, subcontractors and rental houses, so nothing arrives in a superintendent's truck and waits a week.
- Code each line to Spectrum's cost structure. Job, phase and cost type for job cost lines (most Spectrum companies use labor, material, subcontract, equipment and other), and a GL account for overhead lines. A supply-house invoice with conduit for one job and fixtures for another is two distributions, not one.
- Check the commitment. For subcontract and PO invoices, compare billed-to-date against the committed amount on the job before the invoice is approved, not after it is paid.
- Route by job and amount. Send each invoice to the project manager who owns the job, with a second approver above a dollar threshold. Keep the threshold table short enough that a PM can recite it.
- Post through the API, not a file. Spectrum authorizes outside systems with an Authorization ID created in the Data Exchange Installation screen, scoped to specific companies and web services. Once it exists, approved invoices post through Add Vendor Invoices with their job cost distribution, and nobody re-keys them.
- Reconcile weekly, not monthly. Compare the AP open list and job cost detail each week so the WIP schedule at month end holds no surprises.
How does digital invoice approval support project cost management?
On a construction job, cost that has been incurred but not yet approved does not show up in job cost, so the cost-to-complete is understated. The faster an invoice goes from received to approved and posted, the more accurate the job's actual cost is on any given day. That is why the approver should be the project manager, not an AP clerk working a vendor queue. The PM knows whether the 40 yards of concrete on the ticket were poured on this job, and whether the change order behind a subcontractor's extra line has been executed.
Digital approval also creates the record owners and sureties ask for: who approved which cost, on which job, on what date, against which commitment. Spectrum keeps the approval history for invoices that go through its Invoice Approval. When approval happens upstream, the approving system must keep the same history and attach it to the invoice it posts.
What makes construction invoice coding different from generic AP?
Generic AP tools code an invoice to one GL account. A construction invoice often spans several cost codes, and sometimes several jobs. A single subcontractor pay application can reference a schedule of values across phases, with retention held on each line. Equipment rentals and shared material deliveries are routinely split across jobs. If automation flattens these into one line, Spectrum's job cost reports and the WIP schedule built from them stop being reliable. Cost type matters as much as the job: material posted as subcontract distorts committed cost reports and makes projections look better than they are.
What does one invoice look like end to end?
An electrical supplier emails an invoice with nine lines to the AP inbox. Six lines are conduit, wire and boxes for job 24-117, a medical office building. Three are fixtures for job 24-122, a tenant improvement. Vergo reads the lines, not just the vendor name at the top, and proposes job 24-117 with the rough-in phase and the material cost type for the first six lines, and job 24-122 with the fixtures phase for the other three. Each proposal shows why it was chosen, so the AP reviewer confirms instead of looking codes up. Approval routes by project, the way the company has configured it. Once approved, it posts to Spectrum through Add Vendor Invoices with both job distributions, and the material cost appears on both jobs that day. Payment then runs in Spectrum on the company's normal payment cycle.
How does Vergo handle this?
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. Vergo reads the invoice itself, line by line, and predicts the job, the phase and cost code, and the cost type from what was actually bought, not just the vendor name on the header. Every coding shows why it was chosen, so a reviewer confirms in seconds instead of re-coding by hand. Approval workflows are optional and fit how you already control spend: route by GL account, by amount, or by project, or skip approval flows entirely and let policy flags catch only what breaks a rule.
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. Card spend, employee reimbursements and AP invoices run through one coding model, with one reconciliation. Vergo captures, codes, approves and syncs invoices; it does not pay them. Payment stays in Spectrum and on the rails you already use.
Related questions
- What construction AP automation add-ons work with Viewpoint Spectrum?
- Top-rated AP automation tools for Viewpoint Spectrum users in construction
- What approval thresholds should a construction company set for vendor invoices?
- How do I split a vendor invoice across multiple construction projects?
- What accounts payable software integrates with Viewpoint Spectrum?
Frequently Asked Questions
How do contractors use digital invoice approval for project cost management in Viewpoint Spectrum?
They route each invoice to the project manager who owns the job, with a second approver above a dollar threshold, and post the approved invoice to Spectrum job cost the same day. Approved cost then shows up in job cost reports and projections while the job is still running. Spectrum's own Invoice Approval routes by vendor routing code; tools like Vergo route by project or amount before the invoice posts.
Can Spectrum handle invoice approval workflows natively?
Yes. Spectrum's Invoice Approval uses routing codes that send an invoice through reviewers in sequence, with optional approval limits per reviewer and email notifications. Routing codes are assigned to vendors. Teams add an automation layer mainly for line-level job cost coding and for routing by job rather than by vendor.
Does Spectrum's Automatic Invoicing code job cost lines?
Trimble describes Automatic Invoicing as entering invoice headers from uploaded PDFs, producing validated, unapproved vendor invoices. It is available to Trimble Construction One subscribers. The job, phase and cost type distribution on each line is still coded by a person or by a coding tool such as Vergo.
Which Spectrum web services does AP automation use to post invoices?
Spectrum's list of web services includes Add Vendor Invoices, Add Job Cost Transactions, Add G/L Journal Entries and Add Vendor, plus Get Vendors for reading the vendor list. Vergo uses those five. Access is granted with an Authorization ID created in Spectrum's Data Exchange Installation screen.
Should approvals happen in Spectrum or before invoices reach Spectrum?
Either works, but pick one per invoice type. Approving upstream lets you route by job and see the line coding at approval time. Approving in Spectrum keeps the history inside the ERP. Running both on the same invoice means a project manager approves the same cost twice.
How should multi-job invoices be handled in an automated workflow?
Split them at the line level before posting. Each line carries its own job, phase and cost type, and the invoice posts with a distribution per job. Equipment rentals, shared deliveries and blanket subcontracts are the usual cases.
How do approval thresholds work for construction invoice routing?
Thresholds are usually set by invoice amount, cost type or job. For example, a company might send invoices under $2,500 to the project manager only, add the controller between $2,500 and $25,000, and add an executive above that. Subcontract invoices that exceed the committed amount should escalate whatever their size.
Does Vergo integrate directly with Viewpoint Spectrum for AP posting?
Yes. Vergo posts approved invoices through Spectrum's Add Vendor Invoices web service with the job cost distribution, creates new vendors with Add Vendor, and posts job cost and GL entries with Add Job Cost Transactions and Add G/L Journal Entries. It reads vendors with Get Vendors. Vergo does not pay invoices; payment stays in Spectrum.
How is retention handled in automated invoice processing for Spectrum?
Capture retention at the line level based on the subcontract terms, so the retainage payable and the net payable are both correct on each line. Posting retention as one lump sum at the end of the invoice breaks retainage reporting by phase.
