Short answer: An AI agent can help a general contractor find overdue invoices, draft a reminder, or prepare a draw invoice. It should not receive open-ended authority to transfer funds, change payees, approve a disputed change order, or mark money received without a human checking the underlying record. “Can the agent do it?” is a different question from “Who approves it, and what stops a mistake?”

Opsite publishes this guide and sells contractor software. The checklist below is meant to help you test Opsite and any other vendor against the same job, not to claim that every example action is available on every plan.

First, separate reading from acting

“Move money” can mean several different things. Ask the vendor to identify exactly which of these actions its agent can perform today:

  • Read: find an invoice, draw, payment status, or subcontractor document.
  • Draft: prepare an invoice or reminder for someone to review.
  • Send: deliver a client-facing invoice or payment reminder.
  • Change a record: mark an invoice sent or paid, update a draw, or change an amount.
  • Transfer funds: initiate an actual payment through a bank or payment provider.

These have different consequences. A draft with the wrong amount is easy to catch. A reminder sent to the wrong client can damage trust. A changed payment record can mislead the office even if no bank transfer occurred. A transfer or payee change calls for the strongest approval and reconciliation process. Do not accept a single “AI can handle billing” answer for all five.

A demo test for a real GC workflow

Bring a sample job with one unpaid draw invoice, one paid invoice, and one disputed charge. Use sample contact details rather than live client data until you understand the vendor's controls.

  1. Ask the agent what is overdue. It should identify the invoice and job, show the due date and status, and point to the source record. If it cannot show where the answer came from, stop the test.
  2. Ask for a reminder draft. Check recipient, amount, due date, tone, attachments, and whether the disputed charge is excluded. Ask which person reviews the draft before it goes out.
  3. Try a duplicate request. Repeat the same instruction or refresh the page. Ask the vendor to demonstrate how it prevents two reminders, two invoices, or two financial updates from one request.
  4. Try a forbidden action. Use a read-only or field-role account to request a financial change. The system should deny the action outside the agent's allowed permissions, not rely on the agent politely declining.
  5. Check the record afterward. Find the activity history, the resulting invoice state, and the way to pause or revoke access. Then mark the sample invoice paid and confirm that the next reminder would be suppressed.

This is a test plan, not a claim that a particular vendor passes every step. If a vendor cannot show the controls in its current product and plan, treat that workflow as unverified.

Controls to ask for before enabling any financial write

  • Narrow permissions: give the agent only the jobs and actions it needs. Start with read-only access. A field user should not inherit owner-level financial rights through an agent.
  • Human approval for high-impact actions: require a named person to review amounts, recipients, and the source record before client-facing or financial actions that could cause harm.
  • Server-side enforcement: the application receiving the request must check the user's permissions. A prompt telling the model “do not pay” is not an access control.
  • Replay protection: ask how duplicate requests and retries are handled, especially for invoices, reminders, and status changes.
  • Visible history and a stop switch: you should be able to see what was requested, approved, attempted, and completed, and pause or revoke the agent when something looks wrong.

These questions follow the risk-management approach in NIST's AI Risk Management Framework and OWASP's guidance on excessive agency: define human oversight, limit tools and permissions, and approve high-impact actions. They are useful buying criteria, not a certification of any product.

Where Opsite fits in this test

Opsite's Collections Agent walkthrough shows the settings screen for reminder intervals, send time, custom messages, and pause controls. The screen is evidence of configuration options. It does not prove that a reminder was delivered, a payment was collected, or every approval step above is implemented. Ask us to run the sample-invoice test and show the resulting records.

Current pricing lists Lino, the in-app assistant, on Professional and AI Agents on Enterprise. Ask which billing actions and approval controls are live on the plan you are considering before making a purchase decision.

Questions contractors ask

Can AI send a payment reminder without me?

Some products can automate reminders, but the important detail is your rule set: which invoices qualify, when messages go out, who receives them, how disputes are excluded, and how you pause or review a send. Test those controls with a sample invoice.

Is marking an invoice paid the same as moving money?

No. Marking a record paid changes your system's view of the account; a bank or payment provider handles the actual transfer. Both can cause problems if wrong. Reconcile the record with the payment source before treating the invoice as settled.

What should stay human?

Keep decisions about payees, transfers, disputed charges, contract changes, and unusual client communication with an accountable person. Let software prepare context and drafts, then verify the consequential action against the job record.

Want to test this with your own billing workflow? Request a workflow fit review. Bring one representative invoice and a question you want the agent to answer.

Reviewed September 28, 2026. Product capabilities and plan details can change; verify them in a current demo.