Fazeshift’s AR agents read the reference your customer actually used — whichever field they put it in — and match it to the right invoice before a dollar posts. They work across your ERP, your bank, and the portals your customers route payment through, with retainage tracked as retainage, not as a stale balance.
Back charge · Ridgeline Builders
$38,412.00 Invoice #21147
That mismatch shows up in three places, in three different shapes — and all three still get worked by hand.
One customer pays against a PO your ERP never linked. The next uses a document number instead of the invoice number. The next sends only a street address. One billing address can be sitting on eight near-identical open invoices, and you’re the one who sorts out which is which.
A meaningful share of what you’re owed routes through owner and GC portals, where the remittance sits until someone logs in to get it. Cash and card taken on-site never reach the bank feed at all. One AR manager told us more than five portals account for most of what gets paid.
A short pay that’s actually a GC back charge. A duplicate payment. An amount that’s just off. None of it is rare enough to call an exception anymore, and each one lands on someone’s desk to post as a manual offsetting entry.
Built for how construction actually gets paid
Your ERP stays the system of record — Trimble Viewpoint Vista, Sage Intacct, or whatever else runs the job — and the agent works across it, your bank, and the portals your customers use, posting back only what you’ve approved it to post.
Step 01
Open invoices and job-level detail read from wherever your ERP keeps them, payments and remittance pulled from your bank and lockbox, and the AP and owner portals your customers route payment through — without asking you to consolidate anything first.
Where it shows up in your week
The same platform, pointed at the parts of construction billing that take the most time.
Every AR workflow. One platform.
A construction company running Trimble Viewpoint Vista turned cash application over to the agent — and the share it resolves untouched keeps climbing as volume grows.
See customer storiesAuto-applied
From 89% to 97%
The share of payments resolved without anyone touching them, first full month vs. now — climbing on a growing volume, not a shrinking one.
Works with what already runs the job
The agent connects to your ERP, reads your open invoices, and posts cash application back to your books. Payments and remittance come from your bank and lockbox, and from the AP and owner portals your customers route payment through, in whatever format they arrive. Running something else? Tell us what, and we’ll confirm what connecting it looks like.
View integrations
The ones that come up first, almost every time.
The fastest way to see this is on your own paperwork. Bring a batch — the ones citing a PO you never linked, an address instead of an invoice number, a portal download nobody wanted to open — and we’ll show you how the agent reads and applies them.