Modern Treasury · Schema

ledger_transaction_create_request

FintechPaymentsACHWiresTreasury

Properties

Name Type Description
description string An optional description for internal use.
status string To post a ledger transaction at creation, use `posted`.
metadata object Additional data represented as key-value pairs. Both the key and value must be strings.
effective_at string The timestamp (ISO8601 format) at which the ledger transaction happened for reporting purposes.
effective_date string The date (YYYY-MM-DD) on which the ledger transaction happened for reporting purposes.
ledger_entries array An array of ledger entry objects.
external_id string A unique string to represent the ledger transaction. Only one pending or posted ledger transaction may have this ID in the ledger.
ledgerable_type string If the ledger transaction can be reconciled to another object in Modern Treasury, the type will be populated here, otherwise null. This can be one of payment_order, incoming_payment_detail, expected_p
ledgerable_id string If the ledger transaction can be reconciled to another object in Modern Treasury, the id will be populated here, otherwise null.
View JSON Schema on GitHub

JSON Schema

modern-treasury-ledger-transaction-create-request-schema.json Raw ↑
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "$id": "#/components/schemas/ledger_transaction_create_request",
  "title": "ledger_transaction_create_request",
  "type": "object",
  "properties": {
    "description": {
      "type": "string",
      "description": "An optional description for internal use.",
      "nullable": true
    },
    "status": {
      "type": "string",
      "enum": [
        "archived",
        "pending",
        "posted"
      ],
      "description": "To post a ledger transaction at creation, use `posted`."
    },
    "metadata": {
      "type": "object",
      "description": "Additional data represented as key-value pairs. Both the key and value must be strings.",
      "additionalProperties": {
        "type": "string"
      },
      "example": {
        "key": "value",
        "foo": "bar",
        "modern": "treasury"
      }
    },
    "effective_at": {
      "type": "string",
      "format": "date-time",
      "description": "The timestamp (ISO8601 format) at which the ledger transaction happened for reporting purposes."
    },
    "effective_date": {
      "type": "string",
      "format": "date",
      "description": "The date (YYYY-MM-DD) on which the ledger transaction happened for reporting purposes."
    },
    "ledger_entries": {
      "type": "array",
      "items": {
        "$ref": "#/components/schemas/ledger_entry_create_request"
      },
      "description": "An array of ledger entry objects."
    },
    "external_id": {
      "type": "string",
      "description": "A unique string to represent the ledger transaction. Only one pending or posted ledger transaction may have this ID in the ledger."
    },
    "ledgerable_type": {
      "type": "string",
      "enum": [
        "expected_payment",
        "incoming_payment_detail",
        "payment_order",
        "return",
        "reversal"
      ],
      "description": "If the ledger transaction can be reconciled to another object in Modern Treasury, the type will be populated here, otherwise null. This can be one of payment_order, incoming_payment_detail, expected_payment, return, or reversal."
    },
    "ledgerable_id": {
      "type": "string",
      "format": "uuid",
      "description": "If the ledger transaction can be reconciled to another object in Modern Treasury, the id will be populated here, otherwise null."
    }
  },
  "required": [
    "ledger_entries"
  ]
}