LEDGERS icon

LEDGERS

Interact with LEDGERS API
Join our community

Actions34

Overview

This node facilitates the creation of sales invoices specifically for the India region within a financial or accounting system. It allows users to input detailed contact information, itemized product or service details, and additional invoice metadata to generate an official invoice document. This is particularly useful for businesses operating in India that need to automate invoice generation compliant with local tax regulations such as GST (Goods and Services Tax).

Typical use cases include:

  • Automating invoice creation after a sale is confirmed.
  • Integrating with CRM or ERP systems to streamline billing processes.
  • Generating invoices with accurate tax calculations based on Indian GST rules.
  • Sending invoices with optional notifications and payment links to customers.

Example: A company selling goods in Tamil Nadu can create an invoice by specifying customer contact details, items sold with GST rates, seller branch, and other relevant fields, then automatically send the invoice to the customer.

Properties

Name Meaning
Contact Collection of customer contact details including:
- Business Country (e.g., INDIA)
- Business Name
- Contact ID
- Contact Name
- Email
- GSTIN (tax identification)
- Mobile number with country code
- Place of Supply (Indian state or international)
Items Multiple item entries each containing:
- Description
- Discount amount
- GST Rate (various percentages and special categories like Exempted Supply)
- HSN/SAC Code (tax classification)
- Item ID and Name
- Item Type (Goods or Service)
- Price Type (Inclusive or Exclusive of GST)
- Quantity
- Rate
- Taxable and Non-Taxable amounts per item
- Variant ID
Seller Branch ID Identifier for the seller's branch location (required).
Additional Fields Optional extra invoice details including:
- Bank ID
- Billing Address (lines, city, state, country, pincode)
- Billing Currency (many global currency options)
- Currency Info (name, exchange rate, time)
- Exchange Time and Rate
Invoice Date Date of the invoice (date only, no time).
Invoice Number Custom invoice number string.
Notification Option to send notification ("Yes" or "No").
Payment Link Option to include a payment link in the invoice ("Yes" or "No").
Shipping Address Shipping address details similar to billing address, including GSTIN.
Terms Conditions Text field for terms and conditions related to the invoice. Default text provided about inspection, returns, payment terms, and title retention.
Validity Date Expiry date of the invoice validity (date only).

Output

The node outputs JSON data representing the created invoice record. This includes all the submitted details along with any response data from the backend API confirming invoice creation. The output structure typically contains:

  • Invoice identifiers and status.
  • Detailed contact and item information as submitted.
  • Calculated tax and totals.
  • Metadata such as timestamps and branch info.

There is no indication of binary data output; the output is purely structured JSON reflecting the invoice entity.

Dependencies

  • Requires an API key credential for authentication with the external LEDGERS API service.
  • Needs valid credentials including email, password, API URL, and API key configured in n8n.
  • Relies on the LEDGERS API endpoints for login and invoice creation.
  • Network connectivity to the LEDGERS API endpoint is necessary.

Troubleshooting

  • Authentication Failures: Errors indicating failed login usually mean incorrect API key, email, or password. Verify credentials in n8n settings.
  • Missing Required Fields: Ensure mandatory fields like Seller Branch ID, Contact collection, and Items are properly filled.
  • Invalid GST or HSN Codes: Use valid GST rates and HSN/SAC codes as per Indian tax regulations to avoid rejection.
  • API Endpoint Issues: If the API URL is incorrect or unreachable, requests will fail. Confirm the API URL configuration.
  • Notification or Payment Link Options: Selecting invalid options or incompatible combinations may cause errors; use "Yes" or "No" exactly as specified.
  • Data Format Errors: Input data must conform to expected types (e.g., numbers for quantity, strings for names). Invalid types may cause request failures.

Links and References

Discussion