LEDGERS icon

LEDGERS

Interact with LEDGERS API
Join our community

Actions34

Overview

This node interacts with a Purchase Operation API focused on Indian purchase invoices. Specifically, the "List Purchase Invoices" operation retrieves a paginated list of purchase invoices filtered and sorted according to user-defined criteria. This is useful for businesses needing to automate retrieval and processing of their purchase invoice data, such as for accounting, auditing, or reporting purposes.

Practical examples include:

  • Fetching recent purchase invoices within a date range to reconcile accounts payable.
  • Filtering invoices by payment status (e.g., unpaid) to prioritize payments.
  • Sorting invoices by purchase number or seller name for organized review.

Properties

Name Meaning
Limit The maximum number of purchase invoices to retrieve per request (pagination size).
Filters A collection of optional filters to refine the list of purchase invoices:
  From Date Start date to filter invoices from (inclusive).
  To Date End date to filter invoices up to (inclusive).
  Order By Sort direction: Ascending or Descending.
  Order Column Field to sort by: Bill Number, Purchase Invoice Date, Purchase Invoice Number, Seller Name, or Total Amount.
  Payment Status Filter invoices by payment status: Fully Paid, Part Paid, or Unpaid.

Output

The node outputs JSON data representing the list of purchase invoices matching the specified filters and pagination limit. Each item in the output array corresponds to a purchase invoice with its associated details as returned by the API.

No binary data output is indicated for this operation.

Dependencies

  • Requires an API key credential and authentication token to access the external Purchase Operation API.
  • The node performs login requests to obtain an API token before fetching purchase invoice data.
  • Requires proper configuration of API URL, email, password, and API key credentials in n8n.
  • Uses HTTP requests to interact with the remote API endpoints.

Troubleshooting

  • Authentication failures: If the node throws errors related to authentication, verify that the API key, email, and password credentials are correct and have sufficient permissions.
  • Empty or unexpected responses: Ensure that the filter parameters (dates, payment status) are valid and that there is data available in the target system.
  • API rate limits or connectivity issues: Network problems or API throttling may cause request failures; check network connectivity and API usage policies.
  • Invalid property values: Providing unsupported values for filters or order columns may result in errors or empty results.

Links and References

  • No direct external links provided in the source code.
  • Users should refer to the official documentation of the Purchase Operation API for detailed information on available fields and filtering options.

Discussion