Creating manual revenue

Alongside automatic generation, you can create a revenue row by hand against a specific invoice line item — useful for adjustments, one-off recognition, or deferrals. In the app: Recognition → Create revenue. Via the API: POST /revenue.

Fields

Field	Required	Notes
`invoiceItemId`	yes	The line item the revenue is recognized against.
`value`	yes	The recognized amount (may be negative for adjustments).
`type`	yes	`billed` or `unbilled`.
`period`	yes	Any date within the month the revenue should be recognized in — the API derives the full calendar-month `startDate`/`endDate` from it (e.g. `2026-03-15` and `2026-03-01` both produce the same March row).

deferred_without_date is no longer accepted for manually created revenue — every manual entry now always covers exactly one calendar month. Existing rows of that type from before this change still work as before; see Editing & deleting revenue.

billed is only accepted while the parent invoice is raised, paid or has a credit note issued — the same invoice statuses the revenue reports count as billed. On a draft, unbilled, approved or cancelled invoice, use unbilled. The form hides the Billed option until the selected invoice qualifies.

Example

curl --request POST \
  --url https://api.getenso.ai/revenue \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '{
    "invoiceItemId": "iim_...",
    "value": 500,
    "type": "billed",
    "period": "2026-03-01"
  }'

Required policy action: RevenueService:createRevenue (granted to both AdminAccess and SystemAccess).

Manual billed rows on a line item can be overwritten when that line item is re-synced (see How revenue is generated). Use unbilled for adjustments you want preserved.

To change or remove an existing row afterwards, see Editing & deleting revenue.

Get Started

Core concepts

Revenue recognition

How to?

Creating manual revenue

Fields

Example

​Fields

​Example

Fields

Example