For the purposes of this Use Case, the focus is on Cash Management where Invoicing is generated within ITAS but the Invoice Authorisation (pre-payments for example) is managed in a 3rd party Financial Management system. This is typical in larger Enterprises, where the financing department can operate at a Corporate level and may or may not use ITAS for the authorisation/processing of Invoices.
EVENTSMAP allows nomination of the styles of accounting document that need to be included in the Cash Management workflow. This is achieved by assigning a mapping code that will be passed through in the notification. For example, if it is only necessary to pass through Purchase Invoices then mapping codes associated with these can be assigned with these invoice types (provisional, final, reversal).
It is also possible to control a default lock status if appropriate (see DOCSTATE). This is useful in this scenario to prevent actions such as reversals whilst the invoice is in the process of being authorised/approved. Through configuration, 'Locking' an Invoice will flag it for other ITAS applications to follow due process (warn or prevent altogether a reversal request for example).
* A similar workflow can be built around simple notifications when an Invoice is posted; corresponding endpoint is PostedTransaction