HaloPSA

Reads billable time entries from HaloPSA and turns them into proof-of-service records per customer, agent and charge type. Services are a separate invoice document: they never appear on the weclapp license invoice of the invoice run but go individually into the weclapp booking report. In the app, HaloPSA is therefore a separate menu item directly above weclapp — not an integration like the license portals.

Credentials (gear icon)

HaloPSA API access (URL of the instance, client ID/secret of the API application with read permissions on tickets/times/customers/agents).

Metrics

• One metric per HaloPSA billing article, value = the customer's hours in the period.
• Agent names are resolved via the agent list; times without a time-zone specification are interpreted as local device time.
• The worked duration comes from the time window (start to end time of the entry), not from the reported hour value. HaloPSA sometimes delivers this hour value incorrectly (with a swallowed decimal place: 0.75 → 75, 3.5 → 35); the span between start and end is the reliable source. Only when an entry has no end time does the reported hour value apply.
• Implausible individual values are discarded: entries above 744 hours (a complete month nonstop) cannot be real time tracking and go into neither snapshots nor monthly totals nor the live list.
• The hours remain visible as snapshot data in the dashboard, trends and export (proof of service) — nothing is invoiced from them.

View

Three tabs:

1. Time entries (live) — the individual entries, for review and for booking into the booking report.
2. Monthly totals — aggregated per customer and charge type; the last snapshot of a month carries the monthly total as the proof of service.
3. Article mapping — which weclapp article is used per charge type when booking into the booking report (see below).

Whether an entry counts as billable is determined by the billable flag in HaloPSA itself — it is maintained there. The former billable toggle in Multiverse (including the sync back to HaloPSA) has been removed.

Individual times into the weclapp booking report

Individual time entries are booked into the weclapp booking report — for the traceability of which agent did which activity, and as the basis of the separate service invoice document in weclapp. Each booking creates a task in weclapp (customer from the customer mapping, article from the article mapping of this view, assignee via the HaloPSA agent's e-mail) plus a time entry with duration, billable flag and the description "TicketID: … [Ersteller: …] - Notiz".

• Manual only: per row via the weclapp icon, or collectively via checkboxes + "Book selected to weclapp" (with a confirmation dialog). Nothing books automatically.
• Idempotent: booked entries carry a green "booked" chip and are locked against double booking; on partial failures the half-finished booking is cleaned up automatically.
• Undoing: the delete button on booked entries removes time entry + task in weclapp — the entry can then be booked again.
• Conventions: e-mail actions appear as "E-mail Korrespondenz", "Quick Time" collective tickets as "Client Support Office Hours"; the ticket creator comes from the HaloPSA custom field "Ticket Ersteller" (the collective account "General User" is omitted).
• Prerequisites: the customer is mapped to a weclapp customer, the charge type to a weclapp article (tab "Article mapping"), and the agent e-mail exists as a weclapp user — if anything is missing, the entry is skipped with an understandable message.

Article mapping

In the Article mapping tab, the weclapp article used for booking individual times into the booking report is stored per charge type. The list shows all known charge types (from the snapshots) plus already mapped products. This mapping used to live in the weclapp article mapping — existing mappings were migrated automatically. Since the separation, HaloPSA times no longer appear in the weclapp product catalog or in the customer line items.

Specifics

• Client IDs are stable → automatic rename detection.
• The weclapp license invoice contains no HaloPSA line items anymore — services run exclusively through the booking report as their own invoice document.