Skip to main content
Introduction

BillingBot Documentation

Ready to Invoice is the heart of BillingBot: here you import charges from your cloud distributor (Pax8, Ingram CloudBlue, ITCloud, Twilio, or a CSV file), review and correct them, and send them to HaloPSA as invoice lines for your client...

Last updated 24 days ago

Ready to Invoice is the heart of BillingBot: here you import charges from your cloud distributor (Pax8, Ingram CloudBlue, ITCloud, Twilio, or a CSV file), review and correct them, and send them to HaloPSA as invoice lines for your clients. The goal is to turn your monthly licensing and cloud consumption billing from hours of manual work into a guided flow that takes minutes.

Ready to Invoice main screen
Ready to Invoice main screen with charges imported for the period.

New to BillingBot? Start with Getting Started: create your tenant β€” the full onboarding, with every configuration option explained.

The monthly flow in 5 steps

  1. Import β€” In Ready to Invoice, select the integration and the period, then load the charges. BillingBot first syncs the product catalog and then downloads the charges for the period.
  2. Map β€” Link each distributor company to its company in Halo, and each product to its Halo product. Lines with pending mapping are marked in red; tools like Products without SKU and Bulk Mapping of Recurring Invoices speed up this step. This work is heaviest in the first month; after that, BillingBot remembers the mappings.
  3. Review and correct β€” Adjust individual lines (Edit Invoice Line), exclude anything that shouldn't be billed, or reassign charges to another company when a client absorbs another client's charges.
  4. Send to HaloPSA β€” Queue the charges and confirm them from Send Charges to HaloPSA. If multiple lines compete for the same destination, BillingBot will ask you to resolve the ambiguities before sending.
  5. Verify β€” Check the sending result (invoices created or updated per client) and, if something failed, the details in Sending Errors.

Key concepts

ConceptWhat it means
IntegrationThe source of the charges: Pax8, Ingram CloudBlue, ITCloud, Twilio, or CSV. Configured once on the Integrations screen.
PeriodThe billing month whose charges are imported and processed.
Mapping (Mapped)The link between a distributor company/product and its equivalent in Halo. An unmapped line cannot be sent.
Recurring invoiceThe Halo invoice generated each month for a client; BillingBot adds the charge lines there.
TCO (Track Cost Only)A line that only records internal cost: it is not billed to the client but is kept for margin tracking. Set for one line and month, for a client, or for every client β€” see the levels.
ExcludedA product marked not to be billed. It is decided either for one client or for every client, and the decision is remembered from one month to the next β€” it is not a one-off change to this period's line. View excluded rows by checking the "Excluded" box.
Client recordOne distributor company linked to one PSA client, with its own invoice settings. A distributor company belongs to exactly one record; a PSA client can hold several, one per distributor company. See Client Management.

Dashboard

Ready to Invoice screens

AutoTask / Contracts

Integrations

Universal CSV

Ingram Micro

Invoice History

Client Management

Product Management

Charge Mappings

Settings

Pricing

Where do I find…?

I want to…Go to…
Import this month's chargesReady to Invoice β†’ select Integration and Period β†’ "Load Data"
Know why a line shows in redReady to Invoice β†’ "Mapped" column (company or product mapping is missing)
Bill a product's charges to another clientReassign Charges
Bill two distributor companies to the same PSA clientClients
Correct a price before sendingEdit Invoice Line
Send everything to HaloReady to Invoice β†’ Actions β†’ "Queue Charges for HaloPSA" β†’ Send Charges to HaloPSA
See which invoices were created in HaloSending Result or the "Processed Invoices" screen in the side menu

Sending actions to HaloPSA create or modify real invoices in your Halo instance. Always review the totals per company before using "Send to HaloPSA".