Customer ID and Billing

Welcome to QB-Flow. This page walks you through getting your Customer ID, running your first update, verifying it worked, and understanding how monthly billing is calculated.

What Happens After You Subscribe

1. You'll receive a subscription confirmation email from FlowDevs within a few minutes.
2. Shortly after, a separate welcome email arrives with your unique Customer ID.
3. You use that Customer ID with the QB-Flow executable (or with one of our RMM deployment scripts) to update QuickBooks Desktop on your endpoints.
4. At the end of each month, you receive an invoice based on the number of endpoints QB-Flow ran against.

Step 1: Get Your Customer ID

Your Customer ID is emailed to you within a few minutes of subscribing. It looks like this:

cus_XXXXXXXXXXXXXXXX

You'll pass this ID to qb-flow.exe when you run it, either directly from PowerShell or as a variable inside an RMM deployment script. Example command:

qb-flow.exe /customerid cus_XXXXXXXXXXXXXXXX

Keep this Customer ID somewhere safe. You'll need it for every QB-Flow run and every deployment script. If you can't find the welcome email, check spam, then email clientsupport@flowdevs.io and we'll resend it.

Step 2: Run Your First Update

How you deploy QB-Flow depends on the tooling you already use. Pick the guide that matches your environment:

• Nerdio Setup — for Nerdio Manager for MSP (NMM) and Azure Virtual Desktop pools
• Datto RMM Setup — for Datto RMM PowerShell components
• ConnectWise RMM Setup — for ConnectWise RMM PowerShell actions
• NinjaOne Setup — for NinjaOne (formerly NinjaRMM) automations

If you're running QB-Flow standalone (no RMM), the executable lives at https://flowdevsblob.blob.core.windows.net/qbflow/QB-flow.exe. Run it from an elevated PowerShell session on each host, passing your Customer ID with /customerid.

We recommend starting with 1 to 3 test endpoints before deploying across your whole fleet.

Step 3: Verify the Run Succeeded

QB-Flow doesn't pop a "success" dialog. There are two reliable signals you can check on the endpoint:

1. The log file exists. QB-Flow writes a log to C:\Windows\Temp\qbflow_<yyyyMMdd_HHmmss>.log on every run. If a recent log is there, it ran.
2. The QuickBooks installer folder is empty (or no longer contains the latest .msi / .cab files). This is intentional. The QuickBooks updater uses the presence of those files as its trigger to apply an update. QB-Flow removes them after applying the release so Intuit can't re-trigger the same update outside your scheduled window.

Do not open the QuickBooks Update window to verify a run

The QuickBooks Update window inside QuickBooks Desktop is not a passive status screen. Simply opening it can re-enable Intuit's automatic update service in the background, even if you never click "Update Now." That is the exact behavior QB-Flow is built to prevent.

If you want to confirm QB-Flow ran, check the log file. That is the source of truth, not the in-app Update window.

If the log is missing

If no recent qbflow_*.log exists on the endpoint, the script never executed. Usually it's one of these:

• Antivirus blocked the signed QB-Flow executable. Whitelist the FlowDevs signing certificate.
• The firewall blocked the download URL. Whitelist https://flowdevsblob.blob.core.windows.net/qbflow/QB-flow.exe.
• The Customer ID was missing or mistyped in the script.

If you've checked all three and it still isn't running, send us the deployment script and we'll help you diagnose it.

Billing Process

Billing runs on a monthly cycle and is based on the number of unique endpoints QB-Flow executed on during the month.

• What counts as an endpoint: any unique Windows device where QB-Flow ran at least once during the billing month. Running it multiple times on the same device in the same month still counts as one endpoint.
• Invoice timing: invoices are sent at the end of each month based on the count of unique endpoints from that month.
• Volume tier: the per-endpoint rate is determined by your total endpoint count for the month, using the pricing table above.
• No long-term commitment: you only pay for the endpoints QB-Flow actually ran against. If you don't run it in a given month, you aren't billed for that month.

Questions About Your Customer ID or Billing?

Email clientsupport@flowdevs.io for anything ID, billing, or invoice related.

If you'd like hands-on help with deployment, you can grab time with us on our bookings page.