Billing Booth One icon

Billing Booth One

Interact with Billing Booth One API

Actions476

Overview

This node interacts with the Billing Booth One API to update ledger entry types. It allows users to modify properties of a ledger entry type such as its name, whether it can be a debit or credit, if it is reversible, and if it is a system type that cannot be modified. This is useful in financial or accounting workflows where ledger entry types need to be programmatically updated based on business rules or external triggers.

Use Case Examples

  1. Updating the name of a ledger entry type to reflect a new accounting standard.
  2. Changing the 'is_debit' or 'is_credit' flags to control how entries of this type are processed in the ledger.
  3. Marking a ledger entry type as reversible or non-reversible depending on transaction policies.

Properties

Name Meaning
Id Unique identifier of the ledger entry type to update, required for specifying which entry type to modify.
Additional Body Fields Optional fields to update on the ledger entry type, including Id, Name, Is Debit, Is Credit, Is Reversible, and Is System flags.

Output

JSON

  • json - The JSON response from the Billing Booth One API after updating the ledger entry type, containing the updated ledger entry type details or error information.

Dependencies

  • Billing Booth One API with an API key credential

Troubleshooting

  • Ensure the 'Id' property is correctly set to the ledger entry type you want to update; otherwise, the API call will fail.
  • If the node throws an error about missing routing information, verify that the resource is set to 'Ledgers' and operation to 'Update Ledger Entry Type'.
  • Errors related to authorization indicate issues with the API key credential; check that the credential is valid and has the necessary permissions.
  • If the API returns validation errors, check that the body fields conform to expected types and constraints (e.g., boolean flags).

Links

Discussion