Alga PSA Time and Billing
Overview
Before a billing run, a service manager checks that time is submitted and approved, that
billable work is flagged billable, and that invoices are not sitting in draft or going
overdue. These are all reads; none is admin-gated in Conduit. Approving a time sheet,
requesting changes, finalising or sending an invoice is not possible through this
connector. List what needs doing and who should do it.
Key Concepts
| Concept |
Values |
Time sheet approval_status |
DRAFT, SUBMITTED, APPROVED, CHANGES_REQUESTED |
Time entry work_item_type |
ticket, project_task, non_billable_category, ad_hoc, interaction, co_managed |
Invoice status |
draft, sent, paid, overdue, cancelled, pending, prepayment, partially_applied |
Common Workflows
Time sheet approval backlog
alga_time_sheets_list with approval_status SUBMITTED, sorted by submitted_at
ascending: these wait on a manager.
{"approval_status": "SUBMITTED", "sort": "submitted_at", "order": "asc", "limit": 100, "page": 1}
- Repeat with DRAFT for sheets not yet submitted and CHANGES_REQUESTED for sheets sent
back. Narrow to one period with
period_id.
- Map
user_id to names with alga_users_list, and to managers with alga_teams_list
(each team has a manager) so each item has an owner.
- Report per technician: period, state, age. Flag anything submitted more than a few
days ago.
Hours by technician
alga_time_entries_list with user_id, date_from and date_to (YYYY-MM-DD).
Page to the end. If a page request fails, report the hours as incomplete rather than
presenting the technician totals as complete.
- Split by
is_billable and by work_item_type. A high share of ad_hoc or
non_billable_category time is worth a conversation.
- For a whole team, loop over its members from
alga_teams_list, at most 4 calls at a
time.
alga_time_entries_get for the detail on any single entry that looks wrong.
Billable work logged as non-billable
alga_time_entries_list with is_billable false and work_item_type ticket for the
period. Check each ticket's client and contract (see
client-review) and list entries that look billable. A
person changes the flag in Alga.
Invoice health
- Overdue:
alga_invoices_list with status overdue, sorted by due_date
ascending. Group by client.
- Stuck in draft:
status draft with invoice_date_to a week or more ago.
- Due soon:
status sent with due_date_from / due_date_to covering the next 14
days.
- Drill in with
alga_invoices_get and alga_invoices_items_list; map line items to
services with alga_services_list.
Who is booked when
alga_schedules_list with user_id and start_date / end_date shows scheduled work,
useful next to logged time when hours look low.
Gotchas
- Time entry
date_from / date_to and invoice date filters are YYYY-MM-DD; the
start_time_* / end_time_* filters are UTC timestamps.
- A key whose user can't read every time sheet sees only some entries. If totals look
low, check the role before drawing conclusions.
alga_time_entries_list has no client filter. Go through tickets or work items to
attribute time to a client.
- Confirm how your instance stores invoice amounts before adding them up.
- Invoices and time are sensitive. Share per-technician hours only with the people who
manage them.
Related Skills
1---2name: alga-psa-time-and-billing3description: >4 Alga PSA time and billing reads: time sheet approval states and the5 backlog waiting for a manager, time entries by technician, work item type,6 service and billable flag, technician schedules, invoice status (draft,7 sent, overdue, paid ...) with date-range filters, invoice line items, and8 the service catalog. Read-only: approvals and invoice actions stay in Alga.9when_to_use: >-10 When checking Alga PSA time sheets, technician hours, billable versus11 non-billable time, or invoice status before a billing run or month end.12 Use when: alga time sheets, alga approvals, alga timesheet backlog, alga13 billable hours, alga utilization, alga overdue invoices, alga draft14 invoices, alga month end.15metadata:16 source: https://skillmd.com/skills/wyre-ai/alga-psa-time-and-billing17---1819# Alga PSA Time and Billing2021## Overview2223Before a billing run, a service manager checks that time is submitted and approved, that24billable work is flagged billable, and that invoices are not sitting in draft or going25overdue. These are all reads; none is admin-gated in Conduit. Approving a time sheet,26requesting changes, finalising or sending an invoice is not possible through this27connector. List what needs doing and who should do it.2829## Key Concepts3031| Concept | Values |32|---|---|33| Time sheet `approval_status` | `DRAFT`, `SUBMITTED`, `APPROVED`, `CHANGES_REQUESTED` |34| Time entry `work_item_type` | ticket, project_task, non_billable_category, ad_hoc, interaction, co_managed |35| Invoice `status` | draft, sent, paid, overdue, cancelled, pending, prepayment, partially_applied |3637## Common Workflows3839### Time sheet approval backlog40411. `alga_time_sheets_list` with `approval_status` SUBMITTED, sorted by `submitted_at`42 ascending: these wait on a manager.43 `{"approval_status": "SUBMITTED", "sort": "submitted_at", "order": "asc", "limit": 100, "page": 1}`442. Repeat with DRAFT for sheets not yet submitted and CHANGES_REQUESTED for sheets sent45 back. Narrow to one period with `period_id`.463. Map `user_id` to names with `alga_users_list`, and to managers with `alga_teams_list`47 (each team has a manager) so each item has an owner.484. Report per technician: period, state, age. Flag anything submitted more than a few49 days ago.5051### Hours by technician52531. `alga_time_entries_list` with `user_id`, `date_from` and `date_to` (`YYYY-MM-DD`).54 Page to the end. If a page request fails, report the hours as incomplete rather than55 presenting the technician totals as complete.562. Split by `is_billable` and by `work_item_type`. A high share of `ad_hoc` or57 `non_billable_category` time is worth a conversation.583. For a whole team, loop over its members from `alga_teams_list`, at most 4 calls at a59 time.604. `alga_time_entries_get` for the detail on any single entry that looks wrong.6162### Billable work logged as non-billable6364`alga_time_entries_list` with `is_billable` false and `work_item_type` ticket for the65period. Check each ticket's client and contract (see66[client-review](../client-review/SKILL.md)) and list entries that look billable. A67person changes the flag in Alga.6869### Invoice health7071- **Overdue**: `alga_invoices_list` with `status` overdue, sorted by `due_date`72 ascending. Group by client.73- **Stuck in draft**: `status` draft with `invoice_date_to` a week or more ago.74- **Due soon**: `status` sent with `due_date_from` / `due_date_to` covering the next 1475 days.76- Drill in with `alga_invoices_get` and `alga_invoices_items_list`; map line items to77 services with `alga_services_list`.7879### Who is booked when8081`alga_schedules_list` with `user_id` and `start_date` / `end_date` shows scheduled work,82useful next to logged time when hours look low.8384## Gotchas8586- Time entry `date_from` / `date_to` and invoice date filters are `YYYY-MM-DD`; the87 `start_time_*` / `end_time_*` filters are UTC timestamps.88- A key whose user can't read every time sheet sees only some entries. If totals look89 low, check the role before drawing conclusions.90- `alga_time_entries_list` has no client filter. Go through tickets or work items to91 attribute time to a client.92- Confirm how your instance stores invoice amounts before adding them up.93- Invoices and time are sensitive. Share per-technician hours only with the people who94 manage them.9596## Related Skills9798- [api-patterns](../api-patterns/SKILL.md)99- [client-review](../client-review/SKILL.md)