[ 01 // billingbot ]
Distributor invoices,
billed in HaloPSA.
BillingBot reads the invoices your distributors actually send, prorates, arrears and credits included, and turns them into HaloPSA or Autotask billing. On Halo, the lines arrive coded for QuickBooks Online or Xero.
[ 02 // the problem ]
Halo knows your seat counts. Your distributor bills something else.
Real distributor invoices carry prorates, arrears, credits, mid-cycle changes and multi-month adjustments. HaloPSA can’t reconcile those by itself, so someone re-keys them every month, and the misses become revenue you never bill.
Bills the real invoice
BillingBot imports the actual invoice lines from each distributor, not a subscription count, so what you bill matches what you were charged.
Handles the awkward lines
Prorates, arrears, credits and mid-cycle changes land on the right client invoice. It was built around Pax8’s bill-forward and bill-in-arrears model.
Stops the leak
One documented case found $150,000 a year in revenue leakage. Against 10 to 15 hours of manual invoice work a month, BillingBot is $99.
[ 03 // how it works ]
Invoices in. Billing out. Books in step.
01
Connect HaloPSA
Give BillingBot an API-only Halo agent (it uses no Halo license) and an API application. Test Credentials pulls in your products, tax codes and income and expense accounts.
02
Connect your sources
Add Pax8, Ingram Micro, D&H, ITCloud.ca, Twilio or a CSV file, in any order. Match each distributor’s company names to your Halo clients once.
03
Review and send
Charges land by client on Ready To Invoice. Exclude, move or adjust them, then send one client or all of them to HaloPSA.
[ 04 // what it handles ]
The rules your billing already follows, written down once.
Set each rule globally, then override it per distributor or per client when a contract says otherwise.
Three invoice behaviors
Create a new invoice (one per Ingram hardware order, say), attach to the client’s latest invoice, or add to and update their recurring invoice.
Invoice modifiers
Drop $0 lines, drop favorable prorates, collapse Azure consumption into one line per client or leave it off, or exclude a client completely.
Cross-client mapping
Bill one company’s charges, or single lines, to a different client. BillingBot remembers the mapping every cycle after.
Product lifecycle
A SKU you’ve never sold is created in Halo under a BillingBot item group with your income and cost accounts, mapped to a default item, or left for you to map.
Coded for your books
Every line carries the income, COGS and tax codes from Halo’s QuickBooks Online or Xero integration, so Halo’s own sync takes it the rest of the way.
Hands-off Pax8
New Pax8 invoices are detected as they arrive and can be billed for mapped clients without anyone opening the screen.
Also included: bulk or per-client sending, universal search and Excel-style filters on Ready To Invoice, renamable item group headers on Halo invoices, and unlimited users per instance.
[ 05 // connections ]
Masters of middleware.
Every source BillingBot reads, and everywhere it writes.
Sources
Distributors and usage
Anything without an integration comes in through the CSV import.
Billing
HaloPSA
Everything BillingBot does lands in Halo, where you already bill.
Accounting
Your books, through Halo
BillingBot doesn’t connect to your accounting system directly. It codes each line for Halo’s own sync.
On the public roadmap: TD Synnex, Egnyte, DNSFilter and Sherweb. Vote or add a request at ideas.billingbot.app.
[ 06 // origin ]
Built for our own desk first.
BillingBot started as an internal tool at TechPulse, an MSP that needed it before anyone else did.
Jun 2021
The Invoice Bootstrapper
A PowerShell GUI we built to push our own Pax8 invoices into HaloPSA.
Dec 2021
Rebuilt from scratch
Rewritten as a web application so other MSPs could use it.
2024
Public launch
BillingBot opens to MSPs on HaloPSA, launched in a joint webinar with Halo.
Oct 2024
Stellar Guardian
Pax8 OAuth sign-in, automatic Pax8 invoice detection and multi-user workspaces.
Jul 2025
Aurora Aegis
Universal search, Excel-style filters and a redesigned Ready To Invoice.
[ 07 // inside billingbot ]
See it before you sign up.
The console your billing team works in: distributor connections, per-source rules, and every charge waiting to go to your PSA.
[ 08 // pricing ]
One plan. One price.
No per-seat math. Every feature and every integration is included, and everyone on your team gets a login.
BillingBot
One plan
$99/mo
Or $999 a year.
Every plan includes
- Distributor invoices processed over API
- Pax8, D&H, Ingram Micro Cloud Marketplace (CloudBlue), Ingram Micro hardware, Twilio and ITCloud.ca
- Any other vendor by CSV import
- Azure and CSP consumption imported from providers like Pax8
- Azure collapsed to one line per client, or left off
- Invoice backup and history with one-click restore
- New SKUs created as products in HaloPSA or Autotask
- Charges or whole clients billed to another account
- One-to-many and many-to-one charge mapping
- Charges attached to recurring or existing invoices
- Billing rules, reconciliation and automated actions
- SKUs excluded globally or per client
- Margins, costs and price overrides
- Charge grouping for cleaner invoices
- Unlimited users
- Every feature and integration, no à la carte pricing
- Covered by our Ethical Software Guarantee
Which distributors does BillingBot support?
Pax8, Ingram Micro (Cloud Marketplace and hardware), D&H, ITCloud.ca and Twilio usage, plus a Universal CSV import for any other vendor. TD Synnex is on the roadmap, not live yet. Ingram software invoices need your Ingram cloud billing on Xvantage.
Does it connect to QuickBooks Online or Xero?
Not directly, and it doesn’t need to. BillingBot reads the income, cost and tax codes from Halo’s own QuickBooks Online or Xero integration and puts them on every line it posts, so Halo’s sync carries the invoices into your books. US customers on Xero can use Xero’s built-in Avalara Auto Look Up for tax.
What access does it need in HaloPSA?
An API-only agent with the Administrator role (Halo’s API requires it) and an API application using Client ID and secret with the All:Standard scope. API-only agents don’t use a Halo license.
How long does setup take?
Most MSPs are live within hours: connect Halo, authenticate your distributors, map your clients and set your billing rules. The first invoice run tells you if anything needs another rule.
How does it deal with Azure consumption?
Pax8 and other CSP invoices can carry thousands of Azure lines. BillingBot collapses them into one line per client using the cost and price from the distributor, or leaves them off entirely if you absorb the cost. You can choose per client.
Where do I get support?
Email support@techpulsecloud.com or use the Feedback button in the app. The documentation is at docs.techpulsecloud.com, and the public roadmap is at ideas.billingbot.app.
Which distributors does BillingBot support?
Pax8, D&H, Ingram Micro Cloud Marketplace (CloudBlue), Ingram Micro hardware, Twilio and ITCloud.ca, over their APIs, plus any other vendor by CSV import. TD Synnex and Egnyte are in development.
What happens to the products and SKUs already in our PSA?
You choose: BillingBot creates new products as they appear on invoices, maps charges to the products you already have, or leaves products to you. New products can carry your accounting codes, so your catalog doesn’t need rebuilding.
Can it handle multi-company or white-label billing?
Yes. Map charges between companies one-to-many or many-to-one, bill a client through a parent or master account, and split charges across entities. The mapping rules stay in place every month.
How does it handle tax codes and accounting?
On HaloPSA, BillingBot respects the tax codes, income accounts and expense accounts from QuickBooks Online or Xero, including Xero’s Avalara integration for US tax.
What’s on the roadmap?
OrderBot, our procurement tool for HaloPSA, is next: real-time pricing, availability and electronic ordering inside your PSA. More distributors are in development. See and vote on the roadmap at ideas.billingbot.app.
[ 10 // start ]
Stop re-keying distributor invoices.
Seven days free. Most MSPs are live within hours.