Enabling Event-Based Invoice Creation

Your organization's business may require to create an invoice as soon as a business event occurs – an order is activated, a case is closed, a milestone is completed.

Setting up event-based invoice creation involves the following steps:

• Preparing the source object
• Setting up the flow
• Processing the result

Preparing Source Object

The action reuses the generic invoice run configuration. If your source object is already set up for the generic invoice run, there is nothing left to prepare.

Otherwise, set it up as described in Billing Arbitrary Objects, which includes:

• Adding the required ON fields to the source object – either as a parent-child or a single object configuration.

  Two of these fields have a specific relevance for the event-based creation:

  API Name	Relevance
  ON_Invoice	Receives the ID of the produced invoice. In addition, it is the field that the duplicate protection evaluates before creating another invoice.
  ON_InvoiceBuildError	Receives the error text if the invoice build fails after the action has finished – that is, during the asynchronous processing.

• Creating an invoice run filter for the source object.

  Filter Field	Value
  Name	A unique name, like, for example, OrderActivationInvoice You only need it in the flow to disambiguate if the source object has more than one generic filter.
  Use Case	Generic
  Target	The API name of the source object, like, for example, Order or MyOrder__c Must match the records that you pass to the action.
  Child Relation	The child relationship name if the invoice line items originate from child records Leave empty if the source record itself holds the line item data (ON_IsItem = true, "is item" configuration).
  Transactional Suffix	The control field suffix, if used If set to Order, for example, the mapping reads the fields ON_...Order__c instead of ON_...__c.

In addition, make sure that the users who trigger the flow have read access to the source records as well as create and edit access to invoices and invoice line items. The action runs in the context of the calling user.

Setting Up Flow

1. Click to enter Setup, then navigate to Process Automation > Flows.
2. Click New Flow.

3. Select the flow type as required, then click Create.

   The action works in screen, autolaunched, scheduled and record-triggered flows.

4. Configure the Start element.

   Option	Description
   Object	The source object whose records are to be invoiced
   Trigger	The type of record change that triggers the flow
   Conditions	The use case-specific trigger conditions, one or more filter criteria for evaluating certain field values
   Optimize for	Actions and Related Records

5. Click and add the following Action element.

   Option	Description
   Action	The Apex action to call, must be Create Invoice from GIR (single source)
   Input Values	Source Record Id: the ID of the record to be invoiced, usually {!$Record.Id} Filter Name: only required to disambiguate if the source object has more than one generic filter Invoice Date: defaults to the current date if empty Period Start Date and Period End Date: the billing period, required for recurring filters

   Specify a label and an API name as required.

   For details about the individual parameters, see Create Invoice from GIR.

6. Add a Fault connector to the Action element.

   A configuration problem – an ambiguous filter, or a recurring filter without a billing period – does not come back as data. It makes the action fail, and no invoice is created for any of the passed records.

   Without a Fault connector, a screen flow displays the default Salesforce error screen, while an autolaunched or record-triggered flow fails silently to the debug log.

   Route the fault path as required – for example, to an error screen that displays {!$Flow.FaultMessage}, which holds the exact reason.

7. Click Save.

   Specify a label and an API name as required.

8. Click Activate.

   When the defined conditions are met, JustOn Billing & Invoice Management starts creating the invoice for the triggering record.

For help about creating flows, see Flows in the Salesforce Help.

Processing Result

The action returns a collection of results, one per passed record, each holding a chain ID. Depending on your use case, you may need to evaluate it in the flow.

To branch on this distinction, add a Decision element that checks whether the chain ID is empty.