Table of Contents
Summary
Access to various applications is available per company within an organization in the Asamco Platform. You can access and navigate these applications through each company. The current document enlists the functions, available within these applications, and provides a visual representation of those.
Getting started
To navigate through the organizations and companies, log in to the platform. The company to be accessed can be selected through the overview page of the organizations available or through the “Switch between companies” button in the upper left corner of the page.
After selecting a company, the applications, available for that same company, are displayed in the company overview.
Evolution Online
After logging in to the Evolution Online application, you will be directed to the dashboard. There you will find a list for quick access to customers, suppliers, GL accounts, foreign currency and projects. Access to these is also available through the left menu tree.
Customers & Suppliers
Under the "Customers" and "Suppliers" tabs you can find a list of the according accounts. For each account the following actions are available, using the buttons on the right side: (1) View AR/AP transactions; (2) Edit; (3) Delete. New accounts can be added, using the "+" button in the upper right side of the pages.
When adding a new account various information is to be provided in the system. The new information entered is saved, using the "Save" button in the upper right corner.
GL Accounts
For GL accounts, solely the "View transactions" option is available through the online application. Further, the status of each account (Active/Inactive) is displayed in the list.
Projects
Under the "Projects" tab you can find a list of the according projects. The status of each project (Active/Inactive) is displayed in the list. Further, you can edit and/or remove projects, using the buttons on the right of each project. You can add new projects, using the "+" button.
When adding a new project you will need to specify a code, project name and project description. The information can then be saved, using the "Save" button in the upper right corner.
Foreign currency
Under the "Foreign currency" tab you can find a list of the existent currencies. You can edit and/or remove these, using the buttons on the right of each currency. You can add new currencies, using the "+" button.
When adding a new currency you will need to specify a code, description, and currency symbol under "Currency". The information can then be saved, using the button in the upper right corner.
Under "Exchange rate" the daily exchange rates are to be filled. A history of the exchange rates per day is also available in the tab. The information can then be saved, using the button in the upper right corner.
Cashbook batches
Under the "Cashbook batches" tab you can find a list of the existent batches. These can be edited, using the "Edit" button on the right of each batch from the list.
In editing a cashbook batch, the reference number, bank account workflow, deposits and payment can be modified. New rows can be added, using the "+" button. When finalized, the changes can be saved and the batch can be validated and posted, using the according buttons in the upper right corner.
Bank statements
You could process bank statements with the bank statement pages. The main page is the bank statements page. Here you could upload bank statement files, edit bank statement lines, and process them. Bank statement settings page is to setup the general/default settings for bank statements. Bank statement template pages are to manage CSV templates for uploading CSV bank statements.
Bank statements
Upload statement files
To use bank statements, first add a file by drag-and-drop or the "+" button. Current support file formats are .MT940, .OFX, and .CSV.
After adding a file, there may be error or warning. Please read the warning carefully and decide if you are going to continue.
Most errors of .CSV files could be solved by using a corresponding template or change the file according to the selected template. Users could also select bank account for csv files.
When the template fits the file, there will be no error.
You could also download sample files, to check their formats.
When you are ready with the files, use the "Upload" button to upload, then the file will appear in the "Files imported" part.
Filter statement files and statement lines
You could filter the files by their status
and filter statement lines by selecting statement files, or the filters in the "Statement lines" part.
Editing and post statement
You could edit, split, merge, ignore, unignore, validate, and process a statement line by its action buttons when it is not processed. The available actions depend on the line's status, for example, an ignored line can only be unignored.
Bank statement settings
Clicking the "Settings" button on the bank statement page will direct to the bank statement settings page.
Here you could setup bank statement transaction code, default CSV template, if project is required, if sales rep is required, the fall back bank, AP, and AR accounts, and machine learning settings.
Bank Statement templates
On bank statement template overview page, you could add a new template, or download sample file of, edit, or delete existing templates.
On bank statement template detail page, you could set all the properties of a template, view its sample text, and download its sample file. Below is the explanation of each property.
- General: the settings to parse all the values.
- Name: the name you want to give to the template.
- Name: the name you want to give to the template.
- File type: always be CSV.
- Column location method: how do the .CSV file columns match the bank statement (line) properties. When by name, the .CSV files should have a header row that specifies the column name; when by index, the .CSV files do not need a header row, but use the column indexes to match statement (line) properties.
- Header date time format (to merge, currently statement header and statement line can only use the same date time format): the date time format for statement header. For example, "yyyy-MM-dd" would require the date columns of statement header to be the format of "2022-03-26".
Field delimiter: the separator of the .CSV file values.
Decimal separator: the separator of decimals.
- Text qualifier: the character to specify where .CSV file value fields begin and end. When a value does not contain the field delimiter, it does not have to begin and end with the qualifier.
- Bank statement line: the settings to parse bank statement line values.
- The number of first rows to ignore (to merge): how many first lines in the .CSV files should be ignored when parse statement lines.
- The number of last rows to ignore (to merge): how many last lines in the .CSV files should be ignored when parse statement lines.
- Date time format (to merge, currently statement header and statement line can only use the same date time format): the date time format for statement line. For example, "yyyy-MM-dd" would require the date columns of statement line to be the format of "2022-03-26".
- Ignore row conditions (to merge): if a row in the .CSV files fit the conditions, it will be ignored when parse statement lines.
- The tag box lists all available fields from the "column settings" part to create conditions. You could add more fields as you wish. To add condition fields according to column index, use "Column_{index}" format; to add condition fields according to column name, use "{column_name}" format.
Use the filter builder to create conditions. For example, the filter "["Column_1","contains","123"]" can be created as shown below, and it will only parse the .CSV rows whose first column contains "123" into statement lines.
- Noted: if "Column location method" is "Name", both column indexes and column names can be used in condition fields; while if "Column location method" is "Index", only column indexes can be used in condition fields.
- Column settings: the settings to parse each useful .CSV column into statement (line) property.
- Column class: if the column is for statement header or statement line. If a column is for both statement header and statement line, then add two column settings for it.
- Class field: which the statement (line) property the column is for. If a column is for multiple properties, then add multiple column settings for it.
- Column name (only if "Column location method" is "Name"): the .CSV file header row value of that column.
- Column index (only if "Column location method" is "Index"): the .CSV column index.
- Row index: the .CSV file row index. Noted: for statement line, the row index must be 0 (and can be filtered out by the settings in the "Bank statement line" part); for statement header, the row index must be a positive or a negative integer. For example, 1 means the first row, -1 means the last row in the .CSV files.
- Noted:
- Two or more column settings for the same bank statement (line) property is now allowed.
- One column setting for StatementLine.ValueDate is required.
- One column setting for StatementLine.Amount or two column settings for StatementLine.Credit and StatementLine.Debit are required.
If a column setting for StatementLine.Amount or StatementLine.IsPayment presents, no column setting for StatementLine.Credit or StatementLine.Debit is allowed, and vice versa.
- Sample file: the sample text for the current template. To get sample text of an unsaved template or changes, use the refresh button.
