This topic outlines various use cases for creating rules, including matching default behaviors, reflecting specific regional requirements, and handling invoice reversals.

This section lists common use cases for creating rules. For available objects and fields for creating the rules, see Objects and fields for creating rules .

Use case 1: By default, the country of the sold-to contact on the billing document is used to determine the business region. Create a rule that matches this default behavior for invoices, shown below. You can create the same rule for the credit memo and debit memo.

Use case 2: A company located in Germany requires its suppliers to only send an electronic invoice (ELR) when the document is above 10,000. Create a rule reflecting this requirement for invoices.

Use case 3: In Romania, companies that trade in products characterized as dangerous are required to issue an electronic fiscal document. The configuration needs to be done at the item level. Create a rule reflecting this requirement for invoices.

In this case, the Category is a custom field of the Product Rate Plan Charge object, and the Product Rate Plan Charge is the related object of the Invoice Item base object.

Use case 4: This is the scenario of the e-invoice rejected in Italy and a company needs to reverse the invoice without sending the Credit Memo to the government. Create a rule that prevents sending credit memos generated from invoice reversal.