User arguments for Invoice Processing

User argument	Description	Sample value
accountingEntity	Accounting entity of M3. Concatenates the company and division values "company_division"	770_BBB
company	M3 Company.	770
configurationFolder	Defines the internal working path where all scanned documents are placed along with the Logs and InProgress folders. For attended mode, ensure that you have access to the computer drive or server, and have no restrictions to create files and directories. For unattended mode, ensure that robot user have read and write access to this folder.	C:\Invoices_770_BBB
distributionType	Determines the recipient of an ION Notification generated after the RPA process execution is complete. Set this to USER for a specific user to receive the notification or to GROUP for a user group to receive the notification.	USER or GROUP
division	M3 Division.	BBB
emailFolder	Email folder that RPA accesses for reading emails. The folder in outlook must be parallel to Inbox and not inside Inbox.	Invoices_770_BBB
emailSource	If you are using Outlook (Office 365) through a web browser, specify GraphEmail. If you are using the Outlook client application, specify OutlookClient.	GraphEmail or OutlookClient
numberOfEmails	Maximum number of unread emails to process in each run. Specify an integer from 1 to 100.	50 or 100
outlookClientEmailAccount	If the value of emailSource is OutlookClient, specify the email address that receives invoice documents. If the value of emailSource is GraphEmail, specify NA.	user@company.com or NA
enableReviewCenter	Controls whether the RPA job also processes invoices that users correct and release from the Review Center, in addition to new invoices from email or folders. Specify one of these options: True: Use this option in most production setups so that user corrections in the Review Center are picked up automatically the next time the scheduled RPA job runs. On every run, RPA first reads all invoices marked Ready for reprocessing in the Review Center for the current company and division and sends them back through the normal validation and posting flow. After that, the same run continues with any new invoice documents picked up from the configured email inbox or shared folder. No separate job is needed for Review Center corrections. False: Use this option only if you deliberately separate Review Center reprocessing. The RPA run only handles new invoice documents from email or folders. Invoices that users correct in the Review Center and mark as Ready are not automatically reprocessed by this job.	True or False
reviewCenterReprocessingCount	Specify the maximum number of unread document form review center to process in each run.	50 or 100
header_line_matching	This is the default method. It is possible to make exceptions from this on supplier level, through an ION business rule. Select Header for invoice-level matching, Lines for line-level validation or Expense Invoice if you do not work with purchase order matching and want to handle a majority of received invoices as expense invoices.	Header or Lines or Expense Invoice
userIdentifier	If the distributionType is set to USER, the value in Security User GUID for the user must be configured. The value is found in OS > Security > Manage > Users. This user receives an ION Notification in the M3 Inbox when the RPA process execution is finished. If distributionType is set to GROUP, the name of the user group created in OS > Security > Manage > Groups must be configured. Users connected to this group receives an ION Notification in M3 Inbox when the RPA process execution is finished. Note: A user with the UserAdmin role is required to access this information.	ABCGROUP e39b4084-6ae6-4e28-aqb8-23175b14f67p

accountingEntity

Accounting entity of M3.

Concatenates the company and division values "company_division"

770_BBB

company

M3 Company.

770

configurationFolder

Defines the internal working path where all scanned documents are placed along with the Logs and InProgress folders.

For attended mode, ensure that you have access to the computer drive or server, and have no restrictions to create files and directories.

For unattended mode, ensure that robot user have read and write access to this folder.

C:\Invoices_770_BBB

distributionType

Determines the recipient of an ION Notification generated after the RPA process execution is complete. Set this to USER for a specific user to receive the notification or to GROUP for a user group to receive the notification.

USER

or

GROUP

division

M3 Division.

BBB

emailFolder

Email folder that RPA accesses for reading emails. The folder in outlook must be parallel to Inbox and not inside Inbox.

Invoices_770_BBB

emailSource

If you are using Outlook (Office 365) through a web browser, specify GraphEmail.

If you are using the Outlook client application, specify OutlookClient.

GraphEmail

or

OutlookClient

numberOfEmails

Maximum number of unread emails to process in each run. Specify an integer from 1 to 100.

50

or

100

outlookClientEmailAccount

If the value of emailSource is OutlookClient, specify the email address that receives invoice documents.

If the value of emailSource is GraphEmail, specify NA.

user@company.com

or

NA

enableReviewCenter

Controls whether the RPA job also processes invoices that users correct and release from the Review Center, in addition to new invoices from email or folders. Specify one of these options:

True: Use this option in most production setups so that user corrections in the Review Center are picked up automatically the next time the scheduled RPA job runs. On every run, RPA first reads all invoices marked Ready for reprocessing in the Review Center for the current company and division and sends them back through the normal validation and posting flow. After that, the same run continues with any new invoice documents picked up from the configured email inbox or shared folder. No separate job is needed for Review Center corrections.
False: Use this option only if you deliberately separate Review Center reprocessing. The RPA run only handles new invoice documents from email or folders. Invoices that users correct in the Review Center and mark as Ready are not automatically reprocessed by this job.

True

or

False

reviewCenterReprocessingCount

Specify the maximum number of unread document form review center to process in each run.

50

or

100

header_line_matching

This is the default method. It is possible to make exceptions from this on supplier level, through an ION business rule.

Select Header for invoice-level matching, Lines for line-level validation or Expense Invoice if you do not work with purchase order matching and want to handle a majority of received invoices as expense invoices.

Header

or

Lines

or

Expense Invoice

userIdentifier

If the distributionType is set to USER, the value in Security User GUID for the user must be configured. The value is found in OS > Security > Manage > Users. This user receives an ION Notification in the M3 Inbox when the RPA process execution is finished.

If distributionType is set to GROUP, the name of the user group created in OS > Security > Manage > Groups must be configured. Users connected to this group receives an ION Notification in M3 Inbox when the RPA process execution is finished.

Note: A user with the UserAdmin role is required to access this information.

ABCGROUP

e39b4084-6ae6-4e28-aqb8-23175b14f67p