Analyze Accounting Transactions

Form ID: (GL510000)

Note: This form appears in the system if the GL Anomaly Detection feature is enabled on the Enable/Disable Features (CS100000) form.

On this form, you can perform initial training of the machine learning model, analyze transactions, and get the results of transaction analysis.

The form provides information about only companies that have the Use for Anomaly Detection check box selected on the Companies (CS101500) form. For each company included in processing, the system detects the financial periods from which it is possible to select posted transactions. Then the system sends the transactions to the cloud service. After training or analysis has been performed, the system loads the response from the service and updates the data in the table.

The form is visible to only users that are assigned to the Administrator, GL Admin, or AcumaticaSupport role on the User Roles (SM201005) form.

Tip: You can create an automation schedule for each process that can be run on this form.

Form Toolbar

The form toolbar includes standard and form-specific buttons and commands. For the list of standard buttons, see Form Toolbar and More Menu. The form-specific commands are listed in the following table.


Button	Description
Process	Initiates the action specified in the Action box for the selected companies.
Process All	Initiates the action specified in the Action box for all companies listed in the table.

Selection Area

In this area, you select an action to be performed in the Action box.


Element	Description
Action	The action that the system will perform when you click Process or Process All on the form toolbar. The following options are available: [1]olga.karevaCreated AC-2267052022/01/1910:21:12+03:00Train Model: When the option is selected, the system loads active companies for which the Use for Anomaly Detection check box is selected on the Companies (CS101500) form. To use this action, the service status of each company should be Pending Training, Training Failed, or Ready for Analysis. The system then sends the GL transactions of each company to the cloud service by using an API. This action is performed for initial training of the model based on all companies after a system upgrade, for initial training based on a new company, or for training based on existing companies. Initial training is performed based on 6[2]olga.kareva62022/07/2815:24:25+03:00[3]olga.karevainsert2022/07/2815:24:25+03:0018 [4]olga.karevainsert2022/07/2815:25:11+03:00previous calendar monthsmost recent closed p[5]olga.karevamost recent closed p2022/07/2815:25:15+03:00eriods[6]olga.karevaeriods2022/07/2918:07:28+03:00[7]olga.karevainsert2022/07/2815:25:31+03:00 and an anomaly score is assigned to each group of parameters.. The minimum number of periods for initial training is 2.[8]olga.kareva. The minimum number of periods for initial train.. 2022/07/2815:24:54+03:00 Analyze Transactions: When the model has been trained and you select this option, the system loads active companies for which the Use for Anomaly Detection check box is selected on the Companies (CS101500) form. To use this action, the service status of each company should be Ready for Analysis. The system then sends GL transactions from the first open period of each company to the cloud service by using an API. You can send transactions for analysis as many times as needed before closing a financial period[9]olga.kareva before closing a financial period2022/07/2918:07:52+03:00. In this case, only newly posted transactions will be sent to the cloud service. Get Status: When you begin processing for all companies or only selected ones and select this option, the system loads all companies with the service status of Training in Progress and Analysis in Progress. For companies with the Training in Progress status, when training is completed successfully, you can send transactions from an open period for analysis. For companies with the Analysis in Progress status, when the results of transaction analysis are ready, the cloud service returns the [10]olga.karevainsert2022/07/2918:08:19+03:00anomalyconfidence[11]olga.karevaconfidence2022/07/2918:08:21+03:00 scores to the system. You can view the[12]olga.karevainsert2022/07/2918:08:31+03:00 anomaly confidence[13]olga.kareva confidence2022/07/2918:08:33+03:00 scores on the[14]olga.karevainsert2022/07/2815:26:31+03:00 Review Anomaly Predictions <xref href="../UserGuide/GL_40_40_00.dita"/>[15]olga.kareva <xref href="../UserGuide/GL_40_40_00.dita"/>2022/07/2815:26:40+03:00 (GL40[16]olga.karevainsert2022/07/2815:26:45+03:0064[17]olga.kareva42022/07/2815:26:44+03:00000) form by selecting the needed selection criteria[18]olga.karevainsert2022/07/2815:27:07+03:00. and clicking <uicontrol>Show Predictions</uicontrol> on the form toolbar.[19]olga.kareva and clicking <uicontrol>Show Predictions</uicont.. 2022/07/2815:27:13+03:00

Table 1. Table Columns
Column	Description
Included	An unlabeled check box that you select to include this company in processing when you click Process on the form toolbar.
Company ID	The company ID of a company that is active and has the Use for Anomaly Detection check box selected on the Companies (CS101500) form.
Company Name	The company name of the company.
Service Status	The current status of the GL anomaly detection service for each selected company. The following statuses are available. Pending Training: Initial training has not been performed for the company. This status is the default one after an upgrade and for new companies created after the upgrade. Training in Progress: Data has been sent by the training process, and the model is not yet ready. Training Failed: The training failed because the model could not perform training on the data that was sent to it. Ready for Analysis: The model is ready for transaction analysis and prediction. Analysis in Progress: Data has been sent for analysis, and the model has not yet returned confidence scores. A confidence score is an indicator that the transaction is likely an erroneous one. The higher the confidence score, the more likely the transaction is to be erroneous.
From Period	This column is filled in by the system depending on the action selected in the Action box and the service status of the company. The value in this column is calculated by the system based on the To Period value. If Train Model is selected and the service status is Pending Training, the system fills in the sixth [20]olga.karevasixth 2022/07/2918:09:22+03:00period [21]olga.karevainsert2022/07/2918:09:26+03:00corresponding to the 18th month in the past from the To Period setting. If Train Model is selected and the service status is Training Failed or Ready for Analysis, the system fills in [22]olga.karevainsert2022/07/2918:10:02+03:00the earliest unsent perioda closed period earliest of closed unsent periods[23]olga.karevaa closed period earliest of closed unsent periods2022/07/2918:10:22+03:00. If Analyze Transactions is selected and the service status is Ready for Analysis, the system fills in the first open period. You can select another period. <p>If <i>Get Status</i> is selected and the service status is <i>Training in Progress</i> or <i>Analysis in Progress</i>, the system fills in the period that was sent to the cloud service.</p>[24]olga.kareva<p>If <i>Get Status</i> is selected and the servi.. 2022/07/2918:10:54+03:00 An empty value in this column means that no transactions will be sent if this company is selected for processing, and the system displays a warning message.
To Period	This column is filled in by the system depending on the action selected in the Action box and the service status of the company. <p>If <i>Train Model</i> is selected and the service status is <i>Pending Training</i>, the system fills in a closed period with at least one reclassified transaction, if this period is within one calendar year from the most recently closed period. If the most recently closed period does not have reclassified transactions, the system searches for an earlier period in the past. If the system detected a period earlier than the most recently closed period, the value in the <uicontrol>From Period</uicontrol> column is shifted to keep the length of a 6-month historical period.</p><p>If <i>Train Model</i> is selected and the service status is <i>Training Failed</i> or <i>Ready for Analysis</i>, the system fills in the most recent closed period of unsent periods with at least one reclassified transaction. If the most recently closed period does not have reclassified transactions, the system searches for an earlier period in the past. This column can be empty when all closed periods were sent and the next period is still open or there is no closed period with reclassified transactions.</p>[25]olga.kareva<p>If <i>Train Model</i> is selected and the serv.. 2022/07/2918:16:39+03:00 If Analyze Transactions is selected and the service status is Ready for Analysis, the system fills in the [26]olga.karevainsert2022/07/2918:17:07+03:00period previous to the period of the business datefirst open period[27]olga.karevafirst open period2022/07/2918:17:23+03:00. You can select another period. <p>If <i>Get Status</i> is selected and the service status is <i>Training in Progress</i> or <i>Analysis in Progress</i>, the system fills in the period that was sent to the cloud service.</p>[28]olga.kareva<p>If <i>Get Status</i> is selected and the servi.. 2022/07/2918:17:32+03:00 An empty value in this column means that no transactions will be sent if this company is selected for processing, and the system displays a warning message.