You use this program to manage details about your SYSPRO companies according to the terms of your software license agreement. This program is accessed from the SYSPRO Login Window.
Field | Description |
---|---|
Select | Uses the currently highlighted company in the list view (only enabled when browsing on companies from the SYSPRO Login window). |
Add | Adds a new company. |
Change | Changes details for the highlighted company. |
Set Company Password |
This function appears once the company maintenance window is displayed. It enables you to configure a password for the company that will be requested whenever an operator attempts access. |
Field | Description | ||||
---|---|---|---|---|---|
Company license | |||||
Company name |
This must reflect the company name as specified on the registration form supplied with the software. A blank company name is not permitted. |
||||
License expiry year |
This field must reflect the year in which your Software License Agreement expires. |
||||
Expiry month |
This indicates the month in which your license expires, if this is specified within the terms of your Software License Agreement. This applies to temporary licenses. |
||||
License start date | This applies to temporary licenses and indicates the date from which the license is valid. | ||||
Registration number |
This field must reflect the registration number assigned to your company. |
||||
Import License |
Select this to import the LICENSE.XML file into your system. Once you have imported this file you can apportion your licenses across various operators. You must run this function to access any e.net Business Object or Web-based Application, and when using the Document Flow Manager.
|
||||
System settings - Configured using System Setup | This indicates the number of users currently licensed
to use the system as well as the number of licensed seats
for:
These numbers cannot be amended here and are defined using the System Setup program. |
||||
Installed Modules | This list view displays the list of available modules
and which ones are installed. Your selections must match the list of modules indicated on your Software License Agreement. To install a module, enable the checkbox alongside the required module.
|
||||
Licensed e.net Run Time Products | Select this to view a list of e.net Run Time Products
licensed for the current company. This information is generated when you import the license.xml file into the current company. |
Field | Description |
---|---|
Company name and address | |
Company name | Reflects the company name as entered at the Company name field on the Registration tab. |
Multimedia (icon) |
Loads the Multimedia program to view and maintain multimedia objects for the company. |
Custom forms (icon) |
Loads the Custom Forms Entry program to view and enter custom form data for the company. |
Reference | Optionally enter a free format reference for the
company. You could, for example, indicate that this is your
test company. This field is purely documentary for your own information. It is not used by SYSPRO and is not validated. |
Company address | Indicate the company's address details that can be printed on any free-format stationery. |
Delivery address |
Indicate the company's physical address to which goods must be delivered. This is used by the Purchase Orders module. |
Field | Description | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Company values | |||||||||||||||
Company tax registration number | Indicate the company tax registration number. This can be printed on delivery notes, invoices, statements and purchase orders. | ||||||||||||||
Company registration number | Indicate your company registration number. This can only be printed on delivery notes, invoices, statements, creditor's remittance advices and purchase order requisitions. | ||||||||||||||
Default warehouse |
This is the warehouse displayed as the default at most Warehouse fields in the system. Specifying a default warehouse is useful if you are only using one warehouse in the system and do not want to have to re-enter the code repeatedly. You can override the default warehouse at operator level. |
||||||||||||||
Local currency |
Indicate the default currency in which you want to process transactions within the system. You cannot change this currency once you have added the company. |
||||||||||||||
Local currency description |
Enter the description for the Local currency code assigned to the company. |
||||||||||||||
Accounting periods per year | This is typically determined by the frequency of your
company's financial and management reporting cycles. It also determines the relationship between the General Ledger and the sub-ledgers with regard to the posting of the sub-ledger transactions into the General Ledger. Once defined, you should not change the number of accounting periods per year, or you may lose historical information (i.e. the history buckets for transactions written to the files in the sub modules are not moved, adjusted or corrected when you change the accounting periods per year). |
||||||||||||||
4 |
Indicates that the General Ledger Period end function must run after every 3 months of trading activity and all sub-ledgers to have 12 months in the year.
|
||||||||||||||
6 |
Indicates that the General Ledger Period end function must run after every 2 months of trading activity (i.e. 6 times per year) and all sub-ledgers to have 12 months in the year.
|
||||||||||||||
12 | Indicates that the General Ledger Period end function must run after every month of trading activity (i.e. 12 times per year) and all sub-ledgers to have 12 months in the year. | ||||||||||||||
13 | Indicates that the General Ledger Period end function must run after every four weeks of trading activity and all sub-ledgers to have 13 periods in the year. | ||||||||||||||
GL information | You define these accounts using the General Ledger Integration program. You can only access these fields when you are adding a new company and you require the General Ledger module to be installed. | ||||||||||||||
Forced balance account |
This is the account used by the system to correct an out-of-balance situation in the General Ledger. It does so by posting an entry to this account to correct the imbalance. The value posted can then be journalized out to the correct ledger code manually. The following programs add a GL Account called FORCED if it doesn't exist on the GenMaster file: Company Maintenance, Add New Company Wizard, and Company Setup (when it first creates the 00 record on ADMCTL). |
||||||||||||||
Forced balance description |
Indicates the description for your forced balance account. |
||||||||||||||
Retained earnings account |
This account is updated with the net income/loss for the year when you run the Year end function of the General Ledger. It is also used if you select to close out your expense and revenue accounts when you run the year end. |
||||||||||||||
Retained earnings description |
Indicates the description for your retained earnings account. |
||||||||||||||
Edit Date Format | Although always stored in a CCYYMMDD format, this option enables you to define how you want dates to be displayed and requested within SYSPRO, at company level. | ||||||||||||||
Edit Nationality Code | |||||||||||||||
Edit Email/SMTP Settings |
Configures SMTP (Simple Mail Transfer Protocol) default settings for the company. SMTP is a TCP/IP protocol that is used to send and receive Email. The SMTP Default Addresses function enables SYSPRO to send messages using a specific SMTP server and to define an Email address to identify the sender of the message. See Edit SMTP Defaults. |
Field | Description | |||||||||
---|---|---|---|---|---|---|---|---|---|---|
Company date presentation format | ||||||||||
Override system date format with company format |
This overrides the date format settings made within the System Setup program. |
|||||||||
User defined date formats |
Your selection here provides an alternative way of viewing and printing dates and does not affect the way in which dates are physically stored on file. |
|||||||||
Long date format |
Select how you want the system to display the long version of the date for this company.
|
|||||||||
Short date format |
Select how you want the system to display the short version of the date for this company.
|
|||||||||
Report prepared date |
Select how you want the system to display dates on reports printed within this company.
|
|||||||||
Test date |
The date entered here is used by the samples below to confirm that you have correctly configured your user-defined dates. |
|||||||||
Test Formats |
Select this function to apply your date settings to the Test date entered, thereby confirming that you have correctly configured your dates. |
|||||||||
Long date sample |
Displays how the setting for the Long date format will appear in the system. |
|||||||||
Short date sample |
Displays how the setting for the Short date format will appear in the system. |
|||||||||
Report date sample |
Displays how the setting for the Report date format format will appear in the system. |
Field | Description |
---|---|
Company nationality code | |
Override system nationality code with company code | Enables you to set your nationality code at company level (i.e. overrides the setting made within the System Setup program, unless this conflicts with an existing tax option that has been defined). |
Nationality code |
This indicates the nationality of your company (e.g. USA - United States of America; GB - Great Britain; AUS - Australia; CAN - Canada; RSA - South Africa). The nationality entered here affects the display of region-specific fields within the system (e.g. tax). |
Field | Description | ||||
---|---|---|---|---|---|
Use this method when emailing | Select the method to use when emailing.
|
||||
Microsoft Outlook | Uses Microsoft Outlook as your preferred method of
sending email within SYSPRO. You would typically select this
option if you want to use simple MAPI mail.
|
||||
Microsoft Outlook using Outlook email client | Uses Microsoft Outlook with Outlook's rich email
client interface as your preferred method of sending Email
within SYSPRO. The system attempts to locate the SYSPROEmailClient.exe file in your \Base folder. If the file exists, it is executed and the email parameters are passed to it in XML format. The SYSPROEmailClient.exe file is a standalone executable file which you can replace with your own custom UserEmailClient.exe file, if required. You would typically do this if you were using an email system that is not Outlook.
You can, at a later stage, revert to using simple MAPI mail by selecting the Microsoft Outlook option if required. |
||||
Macro using VBScript |
Uses any COM-aware Email subsystem (e.g. Groupwise or Lotus Notes) to send Email in SYSPRO. This is achieved by selecting the Macro function to define VBScript macros for events (see Send Email). These events enable you to indicate which script to run when each of the following options are selected:
|
||||
SMTP Default Addresses | |||||
SMTP server IP address |
Indicates the default IP address of the specific SMTP server that SYSPRO will use to send messages. |
||||
Outgoing email address |
Indicates the default e-mail address of the sender of the message. |
||||
User name |
Enter the user name for the email account specified above. |
||||
Password |
Enter the password for the email account specified above. |
||||
Server port |
Indicate the server port to be used. |
||||
Use SSL | Enable this option to specify that communication with the SMTP server requires SSL encryption (i.e. send email via an SSL connection). |
Field | Description | ||||
---|---|---|---|---|---|
Options | |||||
Job logging required | Creates a log file detailing each program that is
accessed by each operator. You can enable job logging selectively by module and program using the Security Access function of the Groups program. |
||||
Job logging for business objects | Includes job logging entries for business objects in
the log file. Enabling this option may lead to excessive entries in the log from automated and semi-automated processes. Disable this option if you don't want to create log entries for business objects invoked from e.net Solutions, Web-based applications, DFM and VBScripting (from forms, customized panes, etc). If a regular SYSPRO program (e.g. Sales Order Entry) invokes a business object to perform a database update or query, then a job log entry is created as normal. |
||||
Job logging for SRS reports | Includes job logging entries for the running of SRS reports. The log file lets you see the date, time and name of the operator who ran the report. | ||||
Print operator name on journals | Prints the name of the operator who made any postings
to the journal file, on the report. This applies to following journals:
|
||||
Print report options selected | Prints the report options you selected for a report on
the first page of any system report. You would typically use this option to indicate why some entries were included/excluded from a report, as well as if you print multiple copies of the same report with different report options. SRS Reports will take longer to run when you select this option. |
||||
Edit postal/zip codes as 5-4 |
Prints and displays postal codes as a 5-4 field (i.e. the first five characters entered are separated from the remaining four characters by a dash). |
||||
Close previous month automatically |
Closes a sub-ledger month automatically when you complete a month end within the relevant module. You would typically use this if you generally only post to the current month. If you need to post transactions to a prior month then you will have to reopen the month manually. |
||||
Shared inventory for custom forms | If are using shared inventory, then this indicates that
custom forms configured for the shared company must be used
for each of the companies sharing the same inventory
files. (See the Shared inventory considerations topic (Custom Forms Overview). |
||||
Shared inventory for multimedia | If you are using shared inventory, then this indicates
that multimedia objects configured for the shared company must
be used for all the companies sharing the same inventory
files. You won't be able to view any Inventory multimedia that is configured in the individual shared companies. |
||||
Style for tax rate | |||||
Number of decimals | Indicate the default number of decimals to use for all
tax rates. This is applied to the Tax rate
decimals field in the Tax Code Setup program. You can still change the number of decimals for individual tax codes which will override your selection here.
|
||||
Shared companies |
These options enable you to share inventories across companies with different currencies and general ledgers across companies with differing accounting periods. If both Inventory and General Ledger are shared, then the Inventory Interface setup in the Inventory 'holding' company is used to determine the General Ledger accounts to which transactions processed using the Inventory Movements program are posted. If only Inventory is shared, then Inventory transactions update the files of the 'holding' company and the General Ledger side of the transactions are posted to that company's own General Ledger files. It is not advisable to share Inventory files across companies that have different base currencies (generally accepted accounting practice assumes that the value of inventory is stated in the local currency of the company). However, if no transactions are processed across the companies' warehouses (e.g. you want to share Inventory for query purposes only) then this can be done without compromising the integrity of the General Ledger. Refer to Shared files and tables for a list of files/tables which are shared. |
||||
Ledger file company |
Indicate the company that will be the holding company for all the general ledger master, history and detail transactions. This defaults to your current company, but can be changed. You would typically use this facility if you want to produce consolidated financial reports for more than one company using the Financial Report Writer. Although general ledger data for each company is stored in the same physical database, only the Financial Report Writer can access the data of other companies.
|
||||
Inventory file company |
Indicate the company that will be the holding company for inventory data. This defaults to your current company, but can be changed. You would typically use this facility if all companies sell the same inventory and you require a consolidated view of the stock holding of all companies.
|
||||
Numeric formatting | |||||
Decimal character |
Indicate the type of decimal character you want to use for numeric fields that contains decimals (e.g. values, costs, prices, quantities, units of measure conversion factors, currency conversion factors, etc). This character must be different from the 1000's separator character. You can override this at operator level. In a client/server environment, the decimal character entered here must match the character defined in the Regional Settings on the client machine. Otherwise incorrect values could be saved for transaction entries processed in SYSPRO. Windows Regional Settings affect the formatting of numbers in SYSPRO graphs and currency values in SYSPRO Analytics. In addition, variables have been added to the System Information section of all SRS reports to indicate the number of decimals to display (DecimalsToDisplay) and the decimal character to use (DecimalCharacter). This, in conjunction with the SeparatorToUse variable, can be used to format reports to meet your requirements. |
||||
Use1000 separators | Defines a delimiter for numeric values over 999.00 (e.g. a value of 123456789.12 can be displayed as 123,456,789.12. | ||||
1000's separator character |
Indicate the character (symbol) to use as the 1000's separator. This character can be a space (for example, if you want to have 1 000.00). This character must be different from the decimal character. In a client/server environment, the separator character entered here must match the character defined in the Regional Settings on the client machine. Otherwise incorrect values could be saved for transaction entries processed in SYSPRO. |
||||
Style for values |
These options enable you to indicate how transaction values must be printed/displayed in SYSPRO. Reports changed to support extended field sizes remain visually unchanged unless the printed values exceed the available print space, in which case the report print line could change to print two lines instead of one. You can override these settings at operator level. |
||||
Number of digits after decimal | Indicate the number of decimals you want to use for
numeric values. If you enter zero in this field then decimals are removed from entry and display/print fields when values are used.
This does not affect free format stationery that assumes a minimum of two decimals for any price field, and three decimals for any Inventory unit cost field. |
||||
Style for costs/prices | |||||
Use1000 separators (reports) |
Indicates how you want to print costs/prices on reports. Reports changed to support extended field sizes remain visually unchanged unless the printed values exceed the available print space, in which case the report print line could change to print two lines instead of one. |
||||
1000's separator character (reports) |
Indicate the character (symbol) to use as the 1000's separator (e.g. a value of 123456789.12 can be printed as 123,456,789.12). |
||||
Minimum number of decimals to print | This indicates the minimum number of decimals that must
be printed for a cost/price field (e.g. a price of
123456789.12000 may be printed as
123,456,789.120 if the decimal option is
set as 3). This does not affect free format stationary, which assumes a minimum of two decimals for any price field and three decimals for any inventory unit cost field. |
||||
Style for quantities in list views | |||||
Edit qty's using decimals |
Displays stock code-related quantities in list views according to the Maximum number of decimals defined against the stock item (Stock Codes). |
||||
Style for labor times | |||||
Maximum number of decimals to print | Indicates how many decimal places to print for all
labor times in reports. This applies to the printing of all Work in Progress operation times (such as run time, teardown time, wait time, etc.) on reports. It defaults to four decimal places, but can be set anywhere from zero to six. |
||||
Multiple currency options | |||||
Triangulation required |
Converts from one currency to another using an intermediate currency (to conform with European Monetary Union regulations). |
||||
Print triangulation audit |
Prints a currency exchange audit line for each foreign currency transaction using triangulation. |
The following table indicates the files/tables that are shared when you select to share Inventory across your companies:
SQL Table Name | C-ISAM File Name |
---|---|
All table beginning with INV, except the following:
|
All file names beginning with INV, except the following:
|
All tables beginning with BOM | All file names beginning with BOM |
All tables beginning with IOP | All file names beginning with IOP |
All tables beginning with ECC | All file names beginning with ECC |
All tables beginning with CFG | All file names beginning with CFG |
All tables beginning with GTR | All file names beginning with GTR |
All tables beginning with LCT, except the following:
|
All file names beginning with LCT, except the following:
|
All tables beginning with LOT | All file names beginning with LOT |
Table: ArcBomRef | File: ARCBOM |
The following table indicates the files/tables that are shared when you select to share General Ledgers across your companies:
SQL Table Name | C-ISAM File Name |
---|---|
GenMaster | GENMST |
GenTransaction | GENTRN |
GenHistory | GENHST |
GenAltCurCtl | GENACC |
GenAltCurDet | GENALD |
GenAltCurHst | GENALH |
GenControl | GENCTL |
GenBudgets | GENBUD |
GenGroups | GENGRP |
GenBudAltDesc | GENPAR |
GenApportion | GENAPP |
GenCommitDetail | GENPCD |
GenCommitment | GENPCM |
GenAnalysisSection | GENGLA |
GenAnalysisCommit | GENGLU |
GenAnalysisBudget | GENGLB |
GenJournalCtlPrd | GENCJN |
GenLastRevalRate | GENLRR |
GenRevalLog | GENRLG |
GenCopyAltCtl | GENCAC |
GenCopyAltDet | GENCAD |
GenCopyAltHst | GENCAH |
GenCopyBudgets | GENCBU |
GenCopyCommmitDet | GENCCD |
GenCopyCommmitment | GENCCM |
GenCopyControl | GENCCT |
GenCopyGroups | GENCGR |
GenCopyHistory | GENCHS |
GenCopyMaster | GENCMS |
GenCopyBudAltD | GENCPA |
GenCopyTrans | GENCTR |
Field | Description | ||||
---|---|---|---|---|---|
Company data format |
Indicate whether your company data is ISAM or SQL Server-based. This option cannot be accessed if your data for all companies is defined as C-ISAM-based or is a mix of C-ISAM and SQL Server (System Setup). |
||||
Database name |
Indicates the name of the database in which your company data is stored. |
||||
Migrate to SQL format |
Migrates your C-ISAM data for this company into a database format that will be accessed using SQL Server. A wizard guides you through this process (ISAM to SQL Migration Wizard). |
||||
Reset Company to ISAM format |
Resets a SQL Server-based company to enable access C-ISAM data files without actually migrating data from SQL Server to C-ISAM. You would typically use this function if you have migrated your data to SQL Server, but are not yet in possession of a license number. You should not process any transactions as they will be posted to the C-ISAM database and will no longer match the SQL Server data. It will require you to either remove the SQL Server database or remove the data in the tables and redo the migration to SQL. |
||||
C-ISAM data file path definition |
|
||||
All files in a single path |
Select this to hold all your data files for this company in one folder. |
||||
Multiple paths |
Select this to assign different folders for selected data files. This is particularly useful if you want to locate large files on a different physical drive or file system. The directory path must still be from one of the nine pre-defined data directories (System Setup). This option only applies when you specify more than one Data path name (Folders). |
||||
Define Paths |
Assign different folders for different data files (C-ISAM only). |
The Multiple Data Path Definition listview pane indicates a list of your data files (up to a maximum of 1000) together with the current path details that have been assigned.
To change the path of a data file, highlight the required data file and choose one of the entries at the Available paths field. The data file is assigned the path when you select the Apply Path function.
You can use your mouse pointer together with the Ctrl key to assign multiple data files to one of the available paths. Alternatively, you can use your mouse pointer together with the Shift key to assign a contiguous block of data files to one of the available paths. |
Key type | Description |
---|---|
Supplier |
This must be numeric if you want automatic supplier numbering. |
Customer | This must be numeric if you want automatic customer numbering. |
AR Invoice number |
This must be alpha if you want invoice numbering by branch as well as use prefixes for each branch's invoices. Do not change the key type for the AR Invoice number to Numeric after defining the prefixes against each branch, otherwise you will not be able to access any invoices, debit or credit notes processed using prefixes. If set to alphanumeric and your invoice numbering is By company (Set Key Information) then you cannot add retentions to a contract in the Projects and Contracts module (specifically in the P&C Contract Maintenance program). |
Stock code |
If set to numeric, you are restricted to using a maximum of 15 characters. If set to alpha, you can use a maximum of 30 characters. Must be numeric when Stock code numbering method is Automatic (Set Key Information). |
Purchase order |
Must be numeric when Purchase order numbering method is By company or By warehouse (Set Key Information). Must be alphanumeric when Purchase order numbering method is By warehouse with prefix. |
Sales order |
Must be numeric when Sales Order numbering method is By company (Set Key Information). Consider setting this to alphanumeric when Sales Order numbering method is By branch to enable using the branch code as a prefix to the sales order number. This makes it easy to identify the branch that generated the document. |
GRN number |
Must be numeric when GRN numbering is By company (Set Key Information). Must be alphanumeric when GRN numbering is By warehouse with prefix. |
Requisition |
Must be numeric when Requisition numbering method is Automatic (Set Key Information). |
Serial number |
Must be alphanumeric to enable Manual serial number tracking (Set Key Information). |
Lot |
Must be numeric when Automatic lot numbering is enabled (Set Key Information). |
Quotation |
Quotation numbering is set up in the Set Key Information program. If you are using alphanumeric numbering, you also have the ability to add a prefix to the quotation numbers. You can define the length of both the quotation number and the prefix. The length of the quotation number will include the prefix, so for example you can not have a prefix length of 10 and a quotation length of 8. If you enable numbering by branch, you will need to enter the prefix (if required) and the next quotation number for the branch in the AR Branches program |
Job |
Job numbering is set up in the Set Key Information program. If you are using alphanumeric numbering, you also have the ability to add a prefix to the inspection numbers. You can define the length of both the job number and the prefix. The length of the job number will include the prefix, so for example you can not have a prefix length of 10 and an job number length of 8. If you enable numbering by job classification, you will need to enter the prefix (if required) and the next document number for the job class in the Job Classification program. Additionally, if you enable numbering by job classification, it is necessary that the option Job classification required is enabled in the Work in Progress Setup program. |
Asset code |
Set to numeric if you want to enable automatic asset numbering (Set Key Information). |
Dispatch note |
This cannot be numeric when the Dispatch numbering method is Automatic per order. This cannot be alphanumeric when Dispatch numbering method is Automatic (Set Key Information). |
GIT reference |
Must be numeric when Goods in transit reference is By company or By warehouse (Set Key Information). Must be alphanumeric when Goods in transit reference is By warehouse - with prefix. |
WIP inspection |
WIP inspection reference numbering is set up in the Set Key Information program. If you are using alphanumeric numbering, you also have the ability to add a prefix to the inspection numbers. You can define the length of both the WIP inspection number and the prefix. The length of the WIP inspection number will include the prefix, so for example you can not have a prefix length of 10 and a WIP inspection number length of 8. If you enable numbering by job classification, you will need to enter the prefix (if required) and the next document number for the job class in the Job Classification program. Additionally, if you enable numbering by job classification, it is necessary that the option Job classification required is enabled in the Work in Progress Setup program. |
RMA number | Must be numeric when RMA numbering
method is By company or
By branch (Set Key Information). Must be alphanumeric when RMA numbering method is By branch - with prefix. |
Payment run |
Defines the key type for AP payment runs created using the Payment Cycle Maintenance program. If set to alpha, you will not be able to define automatic payment run numbering (Set Key Information). Must be numeric when Payment run numbering method is Automatic. |
Capex code | Set to numeric if you want to enable automatic capex numbering (Set Key Information). |
This screen is displayed when you select to maintain a Key type.
Field | Description |
---|---|
Key | This indicates the Available key you are currently maintaining. |
Key type | |
Alpha | Defines the key as alphanumeric (i.e. the key can
consist of alphabetic and numeric characters). Data is left-aligned with trailing blanks. |
Numeric | Defines the key as numeric (i.e. the key can only
consist of numeric characters). Data is right-aligned with preceding zeros. Only the digits 0 to 9 are allowed. |
Case | This applies only to Key types
defined as Alpha. The capability of automatically converting key fields to upper or lowercase is supported in all forms, toolbars and data grids, but is not supported in entry fields located on the old style screens (Dialog boxes). |
Mixed | Select this if the key can consist of both upper and lower characters. No conversion of case is performed. |
Upper | Automatically converts any alphabetic characters in the key to uppercase. If the key is typed in as lowercase, then the system converts it into uppercase. |
Lower | Automatically converts any alphabetic characters in the key to lowercase. If the key is typed in as uppercase, then the system converts it to lowercase. |
Field | Description | ||||
---|---|---|---|---|---|
Prevent further logins |
Prevents access to this company by any operator who does not have administrator privileges. Administrators are warned if access is attempted. This is useful if you are maintaining a company and want to restrict other operators from entering data.
|
||||
Reason |
Enter the message you want to display to any unauthorized operator attempting to access the company while the Prevent further logins option is selected. |
Field | Description |
---|---|
Module |
This indicates a list of newly-installed modules. |
Year |
This indicates the calendar year in which the current financial year ends. |
Month |
This indicates the month in which your company is running in relation to the start of your financial year. |
Month End Dates |
Defines the month end dates for the Previous and Current year of the installed modules. Although these dates are updated after each month end, they are used by the Period end programs to warn operators when a month end is not being run on the day anticipated by the system. If you defined 12 accounting periods in the year, then the month end dates entered here automatically define your first 12 ledger period end dates (the 13th period end date is used for year end adjustments). If you defined 4, 6 or 13 accounting periods in the year, you have to enter your ledger period end dates. For example, Asset month end dates are set to the last day of each month when you have 12 accounting periods in the year and cannot be changed. When you have 4, 6 or 13 accounting periods, you have to enter the required period end dates. Note that the period end date affects the depreciation calculations. The last seven month end dates (starting from your current month) are used by the system to age your Accounts Receivable invoices if your invoices are aged using the Statement Ageing setup option (Accounts Receivable Setup). |
For a new company, you are required to enter the year and month for each of the modules that still requires the financial year to be defined.
Once you have added a new company, you can change the current financial year or month for a given module within the various module Setup programs, providing that you have not already captured any data for that module. |
Field | Description |
---|---|
Year |
This indicates the calendar year in which your current financial year ends. |
Month |
This indicates the month in which your company is running in relation to the start of your financial year. It cannot be less than 1 or greater than the number of accounting periods in the year. For the General Ledger module, this field refers to the General Ledger period. |