Invoicing

Expose Linked Opportunity ID in Invoice Workflow Triggers
Current Limitation HighLevel allows invoices to be created directly from and linked to Opportunities. However, when an invoice triggers a workflow (Invoice Sent, Invoice Paid, Partial Payment, etc.), the linked Opportunity ID is not exposed as an available workflow field or API value. This prevents automations from identifying and updating the specific Opportunity associated with that invoice. Use Case A single contact may have multiple active Opportunities, each with its own invoice. For example: Opportunity A – Invoice #1001 Opportunity B – Invoice #1002 Opportunity C – Invoice #1003 When Invoice #1002 is paid, the workflow should automatically identify and update Opportunity B, without affecting Opportunities A or C. Currently, using Find Opportunity based on the Contact ID cannot reliably identify the correct Opportunity. Proposed Solution Expose the linked opportunityId in all invoice-related workflow triggers and webhook payloads. Allow the Find Opportunity action to use this ID directly. Automatically retain the linked Opportunity context when an invoice triggers a workflow. Make the linked Opportunity ID accessible through the Get Invoice API endpoint. Business Impact This would allow businesses to automate: Deposit and final payment tracking Opportunity payment status updates Pipeline stage changes based on payments Production and scheduling workflows Multiple projects and invoices under the same contact Expected Result: When an invoice is paid, HighLevel should automatically recognize which Opportunity the invoice is linked to and allow workflow actions to update that exact Opportunity. This would eliminate manual invoice tracking, prevent incorrect Opportunity updates, and enable reliable payment-driven automation.
0
·
New Feature
Automate partial payments with workflows (expansion of manual partial payment addition)
Dear Go High Level Team, I am an active user of Go High Level and would like to propose additional features to enhance the invoicing process, specifically focusing on automated partial payments and flexible invoicing. Automated Partial Payments: Allow users to specify the required deposit percentage when creating an invoice. Provide flexibility for users to set the percentage of the total invoice amount that must be paid as a deposit. Workflow Triggers for Partial Payments: Introduce a workflow trigger event for "Success - Partial Payment." Enable users to create customized workflows triggered by the successful receipt of a partial payment. Flexible Invoicing with Workflows: Enable users to create invoices that can be paid either in full or in part. Allow users to associate workflows with specific events (e.g., invoice creation, partial payment received) to automate subsequent actions. Customization of Partial Payment Conditions: Provide options for users to customize conditions related to partial payments, including automated reminders, follow-up communications, and other workflow-driven actions. Streamlined Invoicing Process: Address the need for a streamlined process to create invoices that can be paid in partial or full. Minimize the need for multiple invoices, allowing users to set conditions and preferences within a single invoice creation process. Benefits: Empower users to control the required deposit percentage for invoices. Enhance automation capabilities by allowing workflows triggered by partial payment events. Streamline the invoicing process, reducing the need for multiple invoices for automation. I believe that incorporating these features will significantly improve the invoicing experience for users who seek flexibility and automation. Your attention to these enhancements is highly appreciated, and I look forward to the continued evolution of Go High Level. Reference: Recently launched 12/20/23-12/22/23 manual partial payment option, my idea can expand on this and make it more streamlined for those that want partial payments paid not manually but by the customer based on % invoice (deposit/down payment) requirements set at the invoice level: https://ideas.gohighlevel.com/changelog/record-partial-payments-for-invoices Best regards,
23
·
New Feature
·
under review
Allow custom due date options (e.g., Net 30) in invoice templates used in automation workflows
Currently, when using the "Send Invoice" action within an automation workflow in GoHighLevel, invoices created from templates are automatically assigned a default due date of 7 days from the issue date. This default setting cannot be changed at the template level or within the workflow action itself. For many businesses—especially those offering B2B services, coaching programs, or contract-based work—flexible payment terms such as Net 15, Net 30, or Due Upon Receipt are essential and often contractually required. This limitation introduces significant inefficiencies: Manual intervention is required to adjust due dates after invoices are generated. Automations cannot reflect standard business billing practices. It causes misalignment between contracts and invoice payment terms. Requested Feature: Add functionality to: 1) Set a default due date (e.g., Net 30) at the invoice template level. 2) Optionally override the due date directly in the Send Invoice workflow action. 3) Include support for standard payment terms such as: 3a) Fixed date (e.g., due on the 15th of each month) 3b) Relative to issue date (e.g., Net 7, Net 15, Net 30, Net 60) 3c) Due upon receipt Business Impact: This feature would eliminate the need for workarounds or manual adjustments and would: Improve billing accuracy and consistency Increase automation flexibility Reduce administrative time Improve the client experience by aligning invoicing with contractual expectations
1
·
New Feature
Load More
→