PowerOps runs the service operation and connects to the systems around it. This page lists what ships today, described exactly. Nothing here is a roadmap item.
Accounting sync, included in your PowerOps plan.
Push customers, push invoices after the Create Invoice gate, pull payments back and apply them to the right invoices. Human-triggered, never silent.
How the QuickBooks sync worksPay links on invoices and portal payment.
Customers pay online; payment receipt fires the one automatic transition in the workflow, Invoiced to Paid. Everything else stays human-gated.
Invoicing moduleCummins, Kohler, and Generac event receivers.
Remote-monitoring events land as alerts on the equipment record, qualified through a live pilot with your fleet. A person decides the response.
Monitoring moduleGovernment bid import, included in your PowerOps plan.
After SAM.gov API setup, a daily job pulls federal opportunities under a fixed set of generator-related NAICS codes into the bid board, with Go/No-Go decisions tracked per pursuit.
Gov Bid TrackingText and email rails built into the platform.
Dispatch notifications and transactional email are built in, with unsubscribe handling. Campaigns in Marketing Engine and sequences in Sales are included in your PowerOps plan. Outbound sends fire only on a human approval click.
Automation boundariesThe way your existing data gets in.
Customers and contacts import from CSV or Excel with column mapping, validation, and a preview; the equipment page imports the generator fleet by CSV, one structured record per unit.
PowerOps is built on one rule: data flows, decisions gate. Integrations follow it. An invoice reaches QuickBooks only after a named person passed the Create Invoice gate. A monitoring alarm becomes a work order only when a dispatcher makes it one. A campaign sends only on an approval click. The integrations move data so nobody retypes it; they never move your business to a state a person didn't choose.
QuickBooks Online integration is included in your PowerOps plan; availability and connection setup must be confirmed during onboarding. Once configured and connected, customers can push to QBO, approved invoices can push with a QuickBooks item reference on every line, and QBO payments can pull back to the matching PowerOps invoices at their applied amounts. A person runs each sync and reviews what it pushed, pulled, and skipped. The full behavior is on the QuickBooks integration page.
Your PowerOps plan includes connection setup for Sage Intacct, Acumatica, and NetSuite. Live data sync for these systems is not available. QuickBooks Online has a sync workflow that requires configuration and a verified connection. Xero is not supported. If your books live on one of these systems, discuss your requirements in a demo.
Yes. Invoices carry pay links, and the customer portal supports online payment. Payment receipt is the one automatic workflow transition in PowerOps: Invoiced to Paid fires on payment, and every other stage change requires a named person.
PowerOps ships webhook receivers for Cummins, Kohler, and Generac remote-monitoring events, qualified through a live pilot with your fleet. Monitoring events land as alerts tied to the equipment record; a person decides what to do with them. Details are on the monitoring module page.
Two paths. The customer wizard takes CSV and Excel files for customers and contacts, with column mapping, validation before anything commits, and a preview of exactly what will be created. The equipment page imports units by CSV, each row carrying make, model, serial, category, kW rating, and fuel type, matched to existing customer sites by name. Create the site records before importing equipment that belongs to them.
Import your customer list in the trial and run a work order through to an invoice, with every stage attributed to a named person.