Skip to main content
The revenue object is the versioned commercial relationship between you and a customer: the agreement, its amendments, the usage metered against it, the entitlements it grants, the invoices it produces, the payments against them, and the history of all of it. It is the record every stage of the chain reads from. Read this page when you want to understand why an amendment in Alguna changes billing, entitlements, and revenue recognition at once without touching an invoice that was issued under earlier terms. A company’s revenue systems all depend on the same commercial agreement, but each usually holds its own version. Sales has the quote, finance has the invoice, engineering has the usage and the entitlements. Every change then becomes an exception someone carries across systems: a renegotiated commitment that billing hasn’t heard about, a credit that collections keeps pursuing, an expansion the customer can’t use until someone works out how to quote and bill it. Alguna removes the translation. The activated quote becomes the billing schedule, the subscription is the contract the rep quoted, and the invoice, revenue schedule, and customer portal read from the same record.

Why it is versioned

Commercial relationships change mid-term, and the changes don’t all apply to the same activity. An amendment changes the terms for the activity it covers; an invoice already issued keeps the terms it was issued under. Treating every action as if it happened under the latest agreement would re-bill the past; treating the agreement as fixed would block the change. Each subscription in Alguna therefore carries versions with effective dates. Usage is rated against the version in force when it occurred. Entitlements update on the effective date of the version that grants them. Revenue schedules derive from the agreement and its amendments. A receivable stays attached to the terms and approved adjustments that apply to it, even while a later amendment waits for approval.

One change, six teams

A customer on a $120k annual usage commitment adds a product and raises the commitment midway through the term. Usage keeps accruing, and an earlier invoice is still unpaid. One commercial decision creates six connected pieces of work: These activities overlap in time. The revenue object connects them without forcing every action onto the same version of the agreement: effective dates, calculation logic, and approvals decide which terms apply to each.

What reads from it

Agents on the record

Alguna’s agents operate on the revenue object rather than on a copy. They start in draft mode when deployed; you expand their authority as you gain confidence, and quotes, credit notes, CRM updates, and signature envelopes remain subject to approval. Proposed changes show their consequences and are checked against your limits, and every action carries an audit history. The same holds for an external assistant connected through the MCP server: an employee’s assistant requesting a quote, or a customer’s accounts-payable agent investigating an invoice, acts under the same terms and permissions.

Where it lives

The revenue object is not a single API resource. It is the set of linked records the public API exposes as accounts, subscriptions and their versions, usage events, entitlements, invoices, and payments, held together by Alguna. See the API reference for each resource and How Alguna Works for how they chain.