Errors When Sending Invoices to HaloPSA

This screen is a popup window that appears automatically when sending billing lines to HaloPSA does not complete successfully. Its purpose is to show you, in a clear list, which invoices or lines failed and why, so you can identify the problem before attempting to send again.

When to use this screen

This window is not opened manually: it appears automatically right after you use the "Send to HaloPSA" option from the invoice detail, when the system detects that one or more lines could not be sent to HaloPSA successfully.

If the sending process completes without issues, this window never appears and you are instead taken to the list of processed invoices. A send that went through can still come back with a notice (for example, lines left out because they were no longer queued, or recurring invoices that may still hold lines of an earlier month); that notice is shown as a message before you are taken to the list, not in this window.

The send runs on the server, and the invoice detail screen waits for its result. This window opens when that result arrives, even if the connection dropped for a moment during the send.

What it shows

The window presents a table ("Error Log") with the details of each error that occurred during sending:

You can sort any column by clicking its header, and you can also filter the results by typing directly in the filter row that appears below the headers.

Available actions

• Select a row: clicking a row in the table highlights it. This is only for reviewing the error detail; it does not trigger any additional action.
• Close the window (close icon in the top corner): closes the error window. Closing it always automatically redirects you to the processed invoices screen in Halo ("haloprocessedinvoices"), regardless of whether you fixed the issue or not.

There are no buttons to retry the send or to edit the lines directly from this window; its purpose is purely informational.

Step-by-step flow

1. From the invoice detail, you select the lines to invoice and choose the "Send to HaloPSA" option from the actions menu.
2. The system attempts to send the lines to HaloPSA.
3. If one or more lines fail to send, this window opens automatically showing the list of errors.
4. You review the Message column for each row to understand what happened with each company/invoice.
5. You close the window using the close icon.
6. The system automatically takes you to the list of processed invoices in Halo, where you can check the current status and, if needed, correct the information and try sending again from there.

Common errors and how to resolve them

• "Cannot send to HaloPSA. There are N ambiguous line(s) that must be resolved first. Please use the 'Resolve Ambiguities' button to resolve them before sending." This message appears before reaching this window (it blocks the send). It means there are ambiguous billing lines that the system could not automatically match to a product or charge in Halo. You must use the "Resolve Ambiguities" button on the invoice detail screen to resolve them before attempting to send again.
• Messages in the Message column of the error table: each row in the table shows the specific reason a line or invoice could not be sent to HaloPSA (for example, communication issues with Halo, invalid data on the invoice, or inconsistencies in the company information). The exact text comes directly from Halo's response or from the sending process, so it may vary from case to case. If the message is not clear, contact support with the invoice number ("Number") and the company name ("Company") shown in the corresponding row.
• "HaloPSA stored this invoice (invoice N), but BillingBot could not record it, so its lines still show as pending. Check that invoice in HaloPSA before sending this package again." Halo accepted the invoice, but BillingBot could not save the result. Open the named invoice in HaloPSA to see what it holds. Sending the package again is safe: BillingBot recognises the lines Halo already holds and does not write them twice (and if the invoice was a new one-time invoice, the next send uses it instead of creating another one). Do not use Delete Queued Package or Change Target Invoice on those lines: they are refused while Halo holds lines of a failed send, because re-queuing or moving them would bill them twice.
• After a failed send, what next? Fix the cause and send the package again, or delete the package and queue the charges again, depending on where the problem was. See When only part of a package was sent and When a send failed on the Send Charges to HaloPSA page.

Related screens

• Invoice detail in HaloPSA
• Result of sending to Halo
• Resolve ambiguous charges
• Invoices ready to process