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 invoice template settings for an organisation. It allows users to configure various templates and fonts used for invoices, credit notes, usage statements, and related documents. The node is useful for automating the customization of billing document templates in a billing system, ensuring consistent branding and formatting across all generated documents.

Use Case Examples

  1. Updating the invoice template and font for an organisation to match new branding guidelines.
  2. Configuring the credit note and usage statement templates with specific fonts and layouts.
  3. Setting the line item sort mode to control how invoice line items are displayed.

Properties

Name Meaning
Organisation Id Unique identifier of the organisation whose invoice template settings are being updated.
Invoice Template The invoice template content or identifier to be used for invoices.
Invoice Template Font Font used by the invoice template.
Credit Note Template The credit note template content or identifier to be used for credit notes.
Credit Note Template Font Font used by the credit note template.
Cdr Template Usage statement template content or identifier.
Cdr Template Font Font used by the usage statement template.
Line Item Sort Mode Mode to sort line items on invoices, either by creation date or period start.
Additional Body Fields Optional additional settings for invoice and credit note display, statement templates, and usage statement formatting.

Output

JSON

  • json - The response from the Billing Booth One API after updating the invoice template settings, typically including confirmation or updated template details.

Dependencies

  • Billing Booth One API
  • An API key credential for authentication

Troubleshooting

  • Ensure the organisation ID is valid and exists in the Billing Booth One system to avoid errors.
  • Verify that all required template fields and fonts are provided and correctly formatted.
  • Check API credentials and base URL configuration to ensure successful authentication and connection.
  • Common error messages may include missing routing information for the selected resource and operation, or missing binary property if binary data is expected. These can be resolved by verifying node parameters and input data.

Discussion