Audit-Rule: General tab

Complete the fields on the General tab as follows.

Field Contents



Enter a mandatory name for the Audit-Rule. This is the logical name that is used to reference the Audit-Rule object throughout the software. Respect the naming conventions.


The Version is a numeric reference that you enter manually to designate which version of a given Audit-Rule this represents.[FOR DETAILS Versions and validity periods]


Enter an optional free-text description for the Audit-Rule. This text appears in the Entity Browser (Label field) and as the tooltip hint when you position the cursor over the Audit-Rule object.


This field displays the current status of the Audit-Rule, set to ToBeChecked by default. You cannot directly change the status in this field. [FOR DETAILS: life cycle and statuses]





From the drop-down list, select a version of a Business-Document which describes the format of the Output-Events where you apply the audit trace.

If you change the Business-Document, AccountingIntegrator Enabler displays the warning message: "Selected Business-Document object has been changed: do you want to keep compatible audit fields?" If you answer:


Then AccountingIntegrator Enabler...


Only deletes those fields referenced in the Audit-Rule that are not compatible with the new format.

Compatible fields must have the same name, but can have different data types or definitions. When AccountingIntegrator Enabler checks the Audit-Rule object it verifies the coherence of fields referenced in the Rule.


Deletes all fields referenced in the Audit-Rule.


Validity periods

[FOR DETAILS Versions and validity periods]

Any given version of an Audit-Rule is only valid and applicable during a specific time period, referred to as the validity period.

To define this period, you specify its start date and end date, as follows.

Start date



Use to set the start and end dates of the validity period.

End date



Output trace


Select one or both of the following check boxes to specify when to set the audit trace on the Output-Events.

  • Detailed sets the audit trace on individual Output-Events prior to applying any Aggregation-Rule that you specified in the Input-Event Processing tab.
  • Aggregated sets the audit trace on a group of Output-Events after applying any Aggregation-Rule that you specified in the Input-Event Processing tab.

Back to top

Related Links