Actions39
- Catalog Operation Actions
- Common Operation Actions
- Contact Operation Actions
- HRMS Operation (India) Actions
- Purchase Operation Actions
- Sales Operation Actions
- Tax Operation (India) Actions
Purchase Operation → List Purchase Invoices
AI-generatedOverview
This node interacts with the LEDGERS API to list purchase invoices. It allows users to retrieve a list of purchase invoices with customizable filters such as date range, order by column and direction, payment status, and limit on the number of results. This is useful for accounting, auditing, and financial management scenarios where users need to fetch and analyze purchase invoice data from their LEDGERS account.
Use Case Examples
- A business owner wants to retrieve the last 10 unpaid purchase invoices to review outstanding payments.
- An accountant needs to generate a report of purchase invoices sorted by purchase invoice date in descending order for a specific date range.
Properties
| Name | Meaning |
|---|---|
| Limit | Specifies the maximum number of purchase invoices to retrieve (page size). This controls how many records are returned in one request. |
| Filters | A collection of optional filters to refine the list of purchase invoices. Includes 'From Date' and 'To Date' to specify the date range, 'Order By' to set ascending or descending order, 'Order Column' to choose the column to sort by, and 'Payment Status' to filter invoices by their payment status (Fully Paid, Part Paid, Unpaid). |
Output
JSON
purchaseInvoices- An array of purchase invoice objects returned from the LEDGERS API, each containing details about individual purchase invoices such as invoice number, date, seller, amount, and payment status.
Dependencies
- Requires an API key credential for the LEDGERS API, including authentication with email and password to obtain an API token.
Troubleshooting
- Authentication failures due to incorrect API key, email, or password. Ensure credentials are correct and have necessary permissions.
- Empty or malformed responses if filters are incorrectly set or if there are no purchase invoices matching the criteria.
- API rate limits or connectivity issues with the LEDGERS API endpoint.