Assign Products Without SKU

This screen shows the list of billing lines coming from Pax8 that don't yet have an associated HaloPSA product. From here you can create a new product in HaloPSA based on the line, or link it to an existing Halo product, so the line can continue on its way to the invoice.

When to use this screen

It opens automatically from the main "Ready to Invoice" screen when you click the option to update SKUs, but only if there are lines still pending mapping. If all lines already have a Halo product assigned, the system will let you know there's nothing to do and the screen won't open.

You should use it whenever new Pax8 products appear (for example, a new subscription or a new add-on) that your BillingBot account doesn't yet know how to match to a Halo product.

What it shows

The screen displays a table ("Products Without SKU") with one row per billing line that doesn't have a Halo product assigned. You can search by text and filter each column with the filter bar below its header.

Available actions

• "Create Halo Product" ("+" icon): creates a new product directly in HaloPSA using the name and source SKU from Pax8, and automatically links it to this line (and to any other pending line with the same source product). The new product is created with your integration's default accounting settings (asset group, tax code, ledger accounts, etc.). If the creation was successful, you'll see the message "Product created succesfull". Warning: This action creates a new record in HaloPSA; don't use it if the product already exists there, as it would create a duplicate. In that case, use "Assign Halo Product".
• "Assign Halo Product" (circle with "+" icon): opens a secondary window ("Map Product to HaloPSA") with the catalog of recurring products already existing in Halo, so you can manually choose which one corresponds to the Pax8 line. The first time you use this option in the session, the system loads the Halo catalog showing the message "Loading Tables from Halo...". Inside that window:
  • You can search for the product by name, description, SKU, or ID.
  • Clicking "Assign" on a Halo product links the Pax8 line to that product and the window closes automatically.
  • If the selected Halo product doesn't have an "Accounts ID" (Halo SKU) configured, the system does not allow the assignment and explains that you must first fill in that field in HaloPSA, since it is required in order to send the charge to invoicing.
  • If the selected Halo product is already assigned to a different source product, the system shows a warning but still allows you to continue with the assignment (this may create ambiguous charges that will later need to be resolved manually).

Both actions immediately update the Id Halo, Name Halo columns and the Mapped icon for all pending lines that share the same source product, and save the change so you won't have to repeat it the next time that same product appears.

Step-by-step flow

1. From the Ready to Invoice screen, trigger the SKU update. If there are lines without a Halo product, this screen opens with the "Products Without SKU" list.
2. Review each line: check the Product column to identify which Pax8 product it is, and Mapped to confirm which ones are still pending (red icon).
3. Decide the action based on the case:
   • If the product doesn't exist yet in HaloPSA, click "Create Halo Product". Wait for the confirmation message "Product created succesfull".
   • If the product already exists in HaloPSA, click "Assign Halo Product". Wait for the catalog to load (if it's the first time) and then search for the matching product.
4. In the assignment window, locate the correct product using the search box and click "Assign".
5. Verify that the Mapped icon for the line (and for any other line with the same source product) has changed to a green check.
6. Repeat the process with the remaining pending lines until there are no unassigned products left.
7. Close the window; the changes have already been saved and the lines are ready to continue in the invoicing process.

Common errors and how to resolve them

• "There was a problem creating the Halo product. Please try again.": the product creation in Halo did not complete. Try the "Create Halo Product" action again; if the problem persists, check your Halo integration configuration.
• "This Halo product (ID: ..., Name: ...) cannot be assigned because it does not have an Accounts ID (Halo SKU)...": the Halo product you're trying to assign doesn't have the "Accounts ID" configured. You need to go into HaloPSA, fill in that field on the product, and then try the assignment again from here.
• "Warning: This Halo product (ID: ..., Name: ...) is already assigned to product '...'. Multiple products can map to the same Halo product, but this may create ambiguous lines that require manual resolution when sending to Halo.": this is a warning, not a block. It indicates that the selected Halo product is already linked to a different source product. You can continue, but keep in mind that this situation may create ambiguous charges that you'll need to resolve later before sending them to Halo.
• "There was a problem with your Halo API credentials. You will be taken to the Integrations configuration screen when clicking OK. Please click the Edit pencil next to your Halo API integration and update your credentials.": the Halo product catalog could not be loaded due to a credentials issue. Go to the integrations configuration, edit your Halo integration credentials, and try again.
• "!Error. All products have an assigned SKU.": this message appears on the originating screen (Ready to Invoice) and indicates that there are no lines pending mapping, so this screen will not open.

Related screens

• Ready to Invoice
• Resolve Ambiguous Charges
• Assign Product in HaloPSA