Skip to main content

HaloPSA: set a recurring invoice's schedule start date

Feature Request

HaloPSA ignores startdate on the recurring-invoice header: POST /RecurringInvoice and halo_create_recurring_invoice echo the new date back and persist nothing. Halo stores the schedule as a separate template record. A new tool, halo_update_recurring_invoice_schedule, writes that record (start date, with end date, period and days-ahead as optional fields), refuses a missing schedule id so it can never mint an orphan row, and reads the record back to confirm the write. The halo_create_recurring_invoice description gains a note that the header start date is ignored.

Status: Closed1 comment

Log in to comment and vote

Comments1

  • Christopher Scaminaci

    Team•

    Sep 20

    Shipped. halo_update_recurring_invoice_schedule is live: it writes the schedule record (start date, with end date, period and days-ahead as optional fields), refuses a missing schedule id so it can't create a stray row, and reads the record back to confirm the write.