Accounting
The controller reviews exceptions instead of keying invoices.
Walter owns the repetitive ledger-side work: three-way invoice matching, payroll and equipment cost coding, job-cost integrity, and month-end support. Deterministic math lives in fat code; the agent classifies, matches, and explains — and never posts.
The problem
What this costs you today — and what Walter does instead.
The pain
Invoices are keyed and matched by hand, and duplicates slip through for trusted vendors.
With Walter
Walter matches invoice to commitment to received evidence, runs a fuzzy duplicate screen on every invoice, and queues clean matches for one-click approval.
The pain
Cost-on-the-ground appears with no budget — the change-order smell — and goes unnoticed.
With Walter
Job-cost integrity checks flag actuals without budget and route them to change orders.
The pain
Month-end accruals and cost-to-complete are a scramble.
With Walter
Walter drafts accruals for work-performed-not-invoiced and pre-fills the cost-to-complete questionnaire from graph state.
The workflow
How Walter runs it.
- 01
Invoice matching
Three-way match invoice, commitment, and received evidence; verify balance, codes, retainage, and duplicates with cited exceptions.
- 02
Sub invoice vs. SOV
Reconcile sub billings against commitment SOV and field percent-complete, flagging overbilling before the pay cycle.
- 03
Payroll coding
Propose cost codes for timecards from daily-log activity and route certified-payroll jobs to contract compliance.
- 04
Equipment allocation
Allocate owned-equipment hours to cost codes from field logs and flag idle equipment on rent.
- 05
Job cost integrity
Track budget vs. committed vs. actual vs. forecast; move budgets on approved COs and flag unbudgeted cost.
- 06
Month-end
Draft accruals, pre-fill cost-to-complete, and support the WIP schedule with flagged over/under-billings.
Human in the loop
What stays your call.
- Walter never posts to the GL, approves an invoice, or releases a payment — a hard ceiling that never graduates.
- Every match and exception cites its evidence; arithmetic is fat-coded, not model-generated.
- Payroll is coding only — salary, rate, and bonus data never enter any project agent's context.
What you get
Outputs.
- Match and exception queue
- Coding proposals
- Job cost reports with cited variances
- Month-end package
- Overbilling flags
Hands off to
It doesn't work alone.
Walter's workflows share one construction brain, so a signal in one becomes action in the next — automatically.