Actions34
- Banking Operation (India) Actions
- Catalog Operation Actions
- Contact Operation Actions
- HRMS Operation (India) Actions
- Purchase Operation (India) Actions
- Sales Operation (India) Actions
- Tax Operation (India) Actions
Overview
This node facilitates the creation of a sales receipt specifically for the India region within a financial or accounting system. It allows users to input detailed contact information, payment details, and other relevant fields to generate a receipt record. This is useful in scenarios where businesses need to document payments received from customers, track receipts against invoices, and maintain accurate financial records.
Practical examples include:
- Recording a customer payment for an invoice.
- Generating receipts for cash or electronic payments.
- Tracking receipt details including billing and shipping addresses, payment methods, and notes.
Properties
| Name | Meaning |
|---|---|
| Contact | Collection of contact details including address (line 1 & 2, city, country, pincode, state), business country, business name, contact ID, contact name, email, GSTIN, mobile number with country code, and place of supply. |
| Seller ID | Identifier for the seller creating the receipt. Required field. |
| Amount | The monetary amount for the receipt. Required field. |
| Payment Method Name or ID | The payment method used for the receipt. Options are dynamically loaded from available payment methods. Required field. |
| Additional Fields | Optional collection of extra details such as: |
| - Billing Address (line 1 & 2, city, country, pincode, state) | |
| - Currency (e.g., INR, USD, EUR, etc.) | |
| - Expense Name or ID (selectable from chart of accounts) | |
| - Note (text note about the receipt) | |
| - Notification (Yes/No to send notification) | |
| - Receipt Date (date only) | |
| - Receipt Number (string identifier) | |
| - Reconcile (collection to link this receipt to an invoice by invoice ID, number, amount, currency) | |
| - Shipping Address (line 1 & 2, city, country, pincode, state) | |
| - Transaction Number (string for payment transaction reference) |
Output
The node outputs JSON data representing the created receipt record. This includes all the receipt details submitted, such as contact info, amount, payment method, dates, and any linked invoices for reconciliation. The output can be used downstream in workflows for further processing, reporting, or integration with other systems.
There is no indication that the node outputs binary data.
Dependencies
- Requires an API key credential for authentication with the external LEDGERS API service.
- Needs valid credentials including API key, email, password, and API URL configured in n8n.
- Relies on the LEDGERS API endpoints for login, fetching payment methods, and creating receipts.
- Dynamic options like payment methods and chart of accounts are fetched via API calls during node configuration.
Troubleshooting
- Authentication Failures: Errors related to login usually indicate invalid or missing API credentials. Verify the API key, email, and password are correct and have necessary permissions.
- Missing Required Fields: Ensure required properties like Seller ID, Amount, and Payment Method are provided; otherwise, the API may reject the request.
- Invalid Data Format: Incorrect formatting of nested collections (e.g., contact address or reconcile fields) may cause errors. Follow the expected structure carefully.
- API Endpoint Issues: If the API URL is incorrect or the service is down, requests will fail. Confirm the API endpoint is reachable.
- Empty Option Lists: If dynamic option loading fails (e.g., payment methods), check credentials and network connectivity.
Links and References
- n8n Expressions Documentation
- LEDGERS API documentation (not publicly linked here; refer to your internal API docs)
- Country and State codes follow standard ISO and Indian states list respectively.
This summary is based solely on static analysis of the provided source and property definitions without runtime execution.