See what’s new in Agave

The sync errors list can be filtered by project manager name and email as well as sorted by them. If you work errors by who owns the job, you can narrow the list to your own.

Dashboard agents can search reference material for Viewpoint Vista, Viewpoint Spectrum, CMiC, Foundation, Sage 100 Contractor and Deltek ComputerEase while building a report: what each table holds, how that system names things, and which figures mean what. Fewer reports get built on a plausible-looking but wrong column.

Vendor statement reconciliation handles statements it cannot place. One with no vendor match gets a No Vendor Found status and a warning rather than failing quietly, and its amount and date can be edited when they arrived empty. Matching also loosened in two ways: an invoice date within a day of the statement counts as a match, and where a statement includes retention and the invoice does not, Agave subtracts the contract retention and compares again. Amount mismatches now appear in the email sent to the vendor.

Overhead invoice lines going to QuickBooks Desktop can carry a cost type, which was previously disabled whenever no project was set. Cost types are a company-level list in QuickBooks Desktop, so they apply with or without a job. Line quantity can also be taken from the matched contract line.

When an invoice comes back with a rejection comment, whoever fixes it can mark that comment resolved. The record then shows what was raised and that it was dealt with, so a reviewer picking the invoice up later can read the history instead of guessing.

A reviewer looking at something filed as an expense that should have been an invoice, or the other way round, can convert it in place instead of sending it back to the submitter to delete and refile.

Two additions to Credit Card Reconciliation. You can notify reviewers from the statement page rather than chasing them separately, and filter the transaction list to narrow a long statement to the rows you are working through. Statement transactions also match against transaction records directly, which widens what links automatically.

The field app asks for a department when someone uploads a receipt or creates an expense without one. Coding the department at capture means fewer expenses going back to the submitter for a field they could have filled in on site.