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 retrieve charge data specifically for reconciliation purposes. It supports querying charges within a specified date range, filtering by supplier, customer, or product IDs, and controlling the result set with pagination and sorting options. This node is useful for financial reconciliation workflows where detailed charge data needs to be fetched and processed, such as accounting automation or audit preparation.

Use Case Examples

  1. Fetch charges from the last month grouped by customer for reconciliation.
  2. Retrieve a limited number of charge entries filtered by specific supplier IDs.
  3. Sort charge data by customer and sell price for detailed financial analysis.

Properties

Name Meaning
From Start date to filter charges from.
To End date to filter charges to.
Grouped Whether the results should be grouped.
Limit Maximum number of charge entries to return.
Offset Starting offset for pagination of results.
Supplier Ids Filter charges by specific supplier IDs.
Customer Ids Filter charges by specific customer IDs.
Product Ids Filter charges by specific product IDs.
Sort Sort order of the results, supporting multiple comma-separated fields such as customer, product, sellquantity, sellprice, buyquantity, buyprice, margin with ascending or descending order indicated by a preceding minus sign.

Output

JSON

  • data - The main response data containing charge entries for reconciliation.

Dependencies

  • Billing Booth One API

Troubleshooting

  • Ensure the API base URL and access token are correctly configured in the credentials to avoid authentication errors.
  • Verify that date strings for 'From' and 'To' fields are in the correct format expected by the API to prevent query failures.
  • If no results are returned, check the filter criteria such as supplier, customer, and product IDs to ensure they match existing data.
  • Pagination parameters 'Limit' and 'Offset' should be set appropriately to avoid missing data or excessive data retrieval.

Discussion