Resolve ambiguous lines before sending to Halo
This popup appears when BillingBot detects that several processed lines point to the same Halo product within the same invoice and cannot decide on its own which Halo recurring invoice line corresponds to each Pax8 (or other integration)...
Last updated 24 days ago
This popup appears when BillingBot detects that several processed lines point to the same Halo product within the same invoice and cannot decide on its own which Halo recurring invoice line corresponds to each Pax8 (or other integration) charge. You must manually indicate the correct relationship before continuing with sending the invoice.
When to use this screen
This dialog opens automatically; it is not accessed from a menu. It appears when, on the Halo invoice detail screen, the system detects lines marked as ambiguous (for example, when clicking "Send to Halo" or the option that reviews lines before sending). While unresolved ambiguous lines exist, the system does not allow you to continue with the normal invoice sending process.
What it shows
At the top, a prominent amber-colored notice explains the situation:
Ambiguous Lines Detected — Multiple lines share the same Halo product. Please select which Halo invoice line corresponds to each processed line.
(Translation: ambiguous lines were detected because several lines share the same Halo product; you must select which Halo invoice line corresponds to each processed line.)
Below, the content is organized into cards by group. Each group brings together the lines that share the same Halo product within the same invoice and company. Each card shows:
- Group header: the Halo product name and its ID, plus the Halo invoice, the company/client name, and how many ambiguous lines that group contains.
- A grid with the lines to resolve, with these columns:
In the Halo Line dropdown menu, in addition to the actual lines of the recurring Halo invoice (with their description, quantity, and price), two special options always appear at the top of the list:
- "Create New Line (skip matching)": does not link the charge to any existing line; a new line will be created in Halo for this charge.
- "Exclude from Invoice (do not send)": the charge will not be sent to Halo at all. The charge itself is marked Not Invoiced / Excluded in Ready to Invoice (it does not stay "In Queue").
If the system managed to automatically suggest a match (by tracing the product number or matching the name), the menu may already appear preselected; you can still change it.
Available actions
Step-by-step flow
- From the Halo invoice detail screen, you attempt to send the invoice or review its lines.
- If there are lines that share the same Halo product and the system cannot automatically distinguish them, this dialog opens showing one group per ambiguous product.
- For each line listed in each group, review the data (source product, SKU, quantity, price) and, in the Halo Line menu, choose the Halo invoice line it corresponds to.
- If the charge does not yet exist as a line in Halo, choose "Create New Line (skip matching)".
- If the charge should not be billed, choose "Exclude from Invoice (do not send)".
- Repeat step 3 until all lines in all groups have a selection. The Resolve and Continue button is only enabled once this is satisfied.
- Click Resolve and Continue. While processing, the button shows a loading indicator ("Resolving...").
- If the save is successful, the dialog closes and the invoice detail screen updates showing the lines already resolved (without the ambiguity indicator).
- If you need to discard the process, click Cancel at any time; the lines will remain pending resolution.
Common errors and how to resolve them
- "Please select a Halo line for each ambiguous line.": you tried to click Resolve and Continue without having chosen an option in the Halo Line menu for one of the lines. Review all groups and make sure each row has a selection (you can use "Create New Line" or "Exclude from Invoice" if no existing line applies).
- "Error saving mappings: ...": a problem occurred while saving the assignments on the server (for example, a communication or validation error). The dialog remains open with your selections intact; you can try clicking Resolve and Continue again. If the error persists, contact support providing the full message shown.
Related screens
Was this helpful?
More in Ready to Invoice
Ready to InvoiceSend Charges to HaloPSAAssign Halo InvoiceAssign Products Without SKUStill need help? Ask the team