For the complete documentation index, see llms.txt. This page is also available as Markdown.

Statement

The Statement object represents entries generated in the scope of an agreement from the corresponding ledger. Statements are visible to clients, enabling them to reconcile their consumption as necessary.

This object contains the following attributes:

Field
Type
Description

id

string, core

(Read-only) The unique identifier for the statement. No nesting exists for this identifier.

ledger

object

(Read-only) (Optional) Represents the ledger object for automated billing.

Example:

customLedger

object

Represents the customLedger object for manual billing.

externalIds

object

(Optional) Represents the external identifiers used for the client and for vendor/operations systems.

type

enum

(Optional) The type of statement. Allowed values are debit or credit.

billingType

enum

The type of billing. The allowed values automated or manual are based on the source of the statement, such as manual upload (manual) or journal (automated).

status

enum

The status of the statement. Allowed values are:

  • Generated

  • Queued

  • Error

  • Cancelled

  • Pending

  • Issued

currency

string

The currency of the statement.

client

object

(Read-only) Represents the client account object.

buyer

object

(Read-only) Represents the buyer object.

Example:

vendor

object

(Read-only) Represents the vendor account object.

Example:

seller

object

(Read-only) Represents the seller object.

Example:

product

object

(Read-only) (Optional) Represents the product object.

Example:

agreement

object

(Read-only) (Optional) Represents the agreement object.

Example:

licensee

object

(Read-only) (Optional) Represents the licensee object.

Example:

externalId

string, core

(Optional) The identifier in the ERP system.

audit

object

(Read-only) Represents the audit object. Allowed values: created or updated.

price

object

(Read-only) Represents the statementPriceSummary object with aggregated price values for all statement charges.

The statementPriceSummary object inherits from PriceSummary and adds totalST and totalGT. Note that not all fields are visible to all actors.

processing

object

(Read-only) Represents the statement processingSummary including the total charges and counts of ready, error, split, cancelled, and completed charges.

statusNotes

object

(Read-only) (Optional) Contains additional notes or messages about the status of the statement, if applicable.

error

object

(Read-only) (Optional) Represents the error object containing error details associated with the statement entry, if any.

Example:

invoice

object

(Read-only) (Optional) Represents the Invoice object.

Example

Last updated

Was this helpful?