Invoice
A legacy invoice header: the description, date and hourly rate a project was billed at before sales invoices replaced it.
- Summary view
- InvoiceList, 11 fields. What a list returns by default.
- Detail view
- Invoice, 11 fields. The default for a single read and for every write.
- Read with
- api:
read: andinvoices::invoices read - Write with
- api:
write: andinvoices::invoices create
It can be listed, read and created, but never edited or deleted through the API: both are always refused. Its rows are not exposed in any form, so there is no line-item total here.
Used by
Fields
- Detail only
- Only in the detail view.
- Only with include
- Only when you ask for it with include.
- Server-assigned
- Set by plnnrly, never by a request.
The project this invoice was raised for.
Employee the invoice is attributed to. Assigned from the authenticated user on create and never writable; null once that user is deleted.
The employee this invoice is attributed to. Expanding it with ?include=user additionally requires the users::read permission and a token scope covering the users prefix.
Hourly rate this invoice was billed at, as a decimal string with two places. Never rounded or rescaled.
2 decimal places, not negative
Last-write timestamp; use for incremental sync. It also feeds the ETag revision, because a legacy invoice has no version field.
Variants
InvoiceList 11 fields
What a collection returns, and what ?view=summary returns on a single record.
The same fields as the detail object.
InvoiceSummary 3 fields
The embedded form: what you get when another resource carries this one and you did not include it.
Leaves out: project_id, project, user_id, user, description, created_at, updated_at, links
hourly_rate narrows from decimal (2 dp) ≥ 0 to decimal (2 dp).
InvoiceLinks 1 field
The links object on this resource.
Keys: self
Something wrong or missing on this page? Tell us