The tunable company wide Daily Close Parameters can be accessed
from the window in the Company
Parameters.
Refer to the Daily Close Overview for
procedural information and process flow.
Check this box to post only one division at a time in Daily Close 1.
This results in a separate DBR (Daily Business Report) for each
division. This is necessary if each division must balance its own
cash.
This processing must also be activated to provide the ability to post payment postings to separate bank accounts according to the division, as setup in Method Of Payment Codes when using the Cash Over/Short feature.
Note: If Post DBR Division feature is not used the
Post Customer Payments could cause file
locking for all divisions when the Daily Close is run, or for
specific divisions when Post DBR by Division is
activated.
Refer to Daily Close 1 - 'Posting Control'
for details.
Uncheck this box if your firm does manual cash
reconciliation.
G/L journal entries are then required to clear the payment clearing
accounts and to complete the bank deposits.
Check this box to activate automatic cash-out process.
Cash discrepancies will be posted by currency to the Cash
Over/Short account assigned in Default
Accounts.
Prior to activating this Cash Over/Short processing, post
all outstanding DBR's through the Daily Close
1: Invoice Edit.
Click Deposit Amt option to display the initial
Opening Cash amount as fully deposited in the Less Bank
Deposits field, with the associated deposit distribution by
payment method in the "Deposit, Closing Cash, and Cash
Over/Short" window.
The Actual Closing Cash field is zero until deposits amounts
are adjusted in the "Deposit, Closing Cash, and Cash
Over/Short" window.
Click Deposit+Payment option to initially display the
total of the payments taken this day in the Less Bank
Deposits and the Opening Cash amount displays the
amounts carried forward from the last reconciliation.
In the "Deposit, Closing Cash, and Cash Over/Short" window,
the dollar amounts taken for each payment method show in the
Deposit Amount field and the Cash On Hand and the
Over/Short fields are zero, except for the dollars carried
forward from the previous balancing.
Note: Post Customer Payments could
cause file locking for all divisions when the Daily Close is run,
or for specific divisions if Post DBR by Division is
used.
Refer to Daily Close 1 - 'Posting Control'
for details.
Uncheck this box to suppress printing the Performance Summary report from Daily Close 1.
Check this box to write the ASCII files RSIHA and RSDPA during
Daily Close 2.
The ASCII files created in the posting, can then be pulled into
other software applications.
Import Daily Close 2 ASCII File can be
used to re-import the ASCII file as required.
Note: When this is activated, the options to Clear Posted G/L Details File and to Post On Account Invoices As Paid are enabled in the Support Application Parameters.
If entering a freeze time, use the 24 hour clock.
e.g. 7:30 PM would be entered as 1930
Leave the freeze time blank, if no freeze is required.
Note: The freeze time can also be set from the Daily Close #1 Freeze Option.
Check this box to provide the option to post any unposted customer payments that were entered in Counter Customer Payments, as part of the Daily Close posting when Daily Close 2 is initiated.
This option in Daily Close 2 ensures that outstanding counter
payments get posted and are not overlooked.
It does not prevent posting from Post Customer
Payments.
Note: Counter Customer Payments for Batch CTR can also be
setup to post automatically by the ARCP10 job in Automatic Reporting.
This is useful if Daily Close 2 is rarely run manually because it
is being automatically posted in Automatic
Reporting.
Check this box to write the Daily Close reports to an ASCII
transaction file instead of to the printer.
When the reports are accepted, the transactions are saved in a text
file in the specified directory.
The files can be viewed before they are accepted in Daily Close 3 and also later in View A Text File.
To ensure system functionality only the SCS operator can change the file directory, xml export directory, and xml parser
Note: This processing should not be used in the SaaS environment because of the length of the directory pathname.
Note: If multiple closes are done on the same day, the transaction file will be over-written and replaced by the latest file of the day.
Uncheck this box if multiples Daily Close 3's are run each day and thus multiple reports must be saved each day.
Additional exports not generated through the Daily Close but exported from a utility or CRON job to the defined folder on the fileserver, include:
The following XML data exports can also be generated automatically as a CRON JOB when set to run in Automatic Job Scheduling:
* Note: If XMLEXP4A - Export A/P Invoices or XMLEXP5A - Export A/R Invoices has been included to be run automatically in the Automatic Job Scheduling then the corresponding export will NOT be triggered by the Daily Close posting process as well.
To ensure system functionality only the SCS operator can change
the file directory, xml export directory, and xml parser
Define what and how the data is exported as follows:
If this directory is not valid or does not exist, any XML Exports run from the Automatic Job Scheduling will fail.
Note: If exported in Playdata the resulting XML files will be prefixed with 'play_'.
Use of a parser is not required, however if an XML export option
is selected, a parser needs to be entered to avoid triggering an
error reading the log file when it attempts to determine the
success or failure of the export.
Default Parser
A default parser is provided to
validate the output files and return an OK status.
The XML documents will be left in the export directory previously
defined.
Email
To trigger an email with the exported output
append the parser name, with a space and then --email
i.e. xml_parser.py --email
The email will be sent to the address defined for the operator
that generated the export files, as setup in Operators.
The sender will be the user logged in at the LINUX level.
Custom Parser
If your firm has a preferred parser,
enter the program which will be used to parse the xml file.
This will also need to be on the server and the full path name and
parser should be defined.
i.e. c:\scsbin\srm_parser.exe
Parsers may optionally move the XML files to an existing
'processed' subdirectory underneath the original export
directory.
Note: Contact Texada Support for assistance customizing a parser.
Check this box to capture invoices when they are moved
successfully from batch status to history in Daily Close 2.
These "printable" invoices will be marked to be exported to XML.
After Daily Close 2 has completed, all marked invoices will be
exported to an XML file which includes the G/L Revenue Account for
the transaction.
Note: Invoices generated directly to history from Post Customer Payments for Trade Discounts given,
are also captured in the XML IHIH file.
For more information on this discount feature refer to the Trade Discounts.
The XML file naming convention is TRS_IHIH_00000000000000000161.xml where TRS represents your 3 digit company code, IHIH (Invoice History) is the data type, and 00000000000000000161 is the sequential XML transaction number that is referenced in XML Data Exports Menu.
Check this box to capture G/L transactions as part of the
Daily Close 3.
After the posting of the A/R invoices is completed in Daily Close 3, any G/L transactions including
journals and GL checks, that have been posted since the last
running of Daily Close 3, are exported to an XML file.
The XML file naming convention is TRS_GLGL_00000000000000004912.xml where TRS represents your 3 digit company code, GLGL (General Ledger) is the data type, and 00000000000000004912 is the sequential XML transaction number that is referenced in XML Data Exports Menu.
Note: If the Post A/R Invoice portion of Daily Close 3 is not completed then the XML export
will not execute.
Records will post with the next Daily Close
3 that is completed.
Automated G/L Export
The data export for G/L transactions can be triggered automatically
by including XLMEXP3 in Automatic
Reporting to output any G/L transactions that have not yet been
exported to an XML file and date-stamp them as exported.
When the XML file is created, a summary of the Debit and Credit
totals is emailed to the addresses specified in the Auto-Reporting
program.
Check this box to capture A/P invoices as part of the Daily Close 3.
After the posting of the A/R invoices is completed in Daily Close 3, the information from any A/P
invoices that have been posted since the last running of Daily
Close 3, is exported to an XML file.
The exported data fields include those that are viewable in the
header of Vendor Account Inquiry.
The XML file naming convention is TRS_APAP_00000000000000000334.xml where TRS represents your 3 digit company code, APAP (Accounts Payable) is the data type, and 00000000000000000334 is the sequential XML transaction number that is referenced in XML Data Exports Menu.
Note: If the Post A/R Invoice portion of Daily Close 3 is not completed then the XML export
will not execute.
Records will post with the next Daily Close
3 that is completed.
As an alternative, the A/P Invoice information can be exported to an XML file regularly using the Automatic Job Scheduling by scheduling the job XMLEXP4A.
Check this box to capture A/R invoices as part of the Daily Close 3.
After the posting of the A/R invoices is completed in Daily Close 3, any A/R transactions including
invoices, credit invoice, and finance charges, that have been
posted since the last running of Daily Close 3, are exported to an
XML file.
The exported data fields include those that are viewable in the
header of Customer Account Inquiry.
The XML file naming convention is TRS_ARAR_000000000000000104556.xml where TRS represents your 3 digit company code, ARAR (Accounts Receivable) is the data type, and 00000000000000104556 is the sequential XML transaction number that is referenced in XML Data Exports Menu.
Note: If the Post A/R Invoice portion of Daily Close 3 is not completed then the XML export
will not execute.
Records will post with the next Daily Close
3 that is completed.
As an alternative, the A/R Invoice information can be exported to an XML file regularly using the Automatic Job Scheduling by scheduling the job XMLEXP5A.
Check this box to capture Purchase Orders as part of the
Daily Close 3.
After the posting of the A/R invoices is completed in Daily Close 3, any P.O. information for vendors
tagged for EDI, that has been entered since the last running of
Daily Close 3, is exported to an XML file.
The XML file naming convention is TRS_INPO_000000000000000174316.xml where TRS represents your 3 digit company code, INPH (Inventory Purchase Orders) is the data type, and 00000000000000174316 is the sequential XML transaction number that is referenced in XML Data Exports Menu.
Note: If the Post A/R Invoice portion of Daily Close 3 is not completed then the XML export
will not execute.
Records will be written with the next Daily
Close 3 that is completed.
Window to view the Parser Log as outlined in View Application Log or to export the data to
Excel.
After viewing the data in the spreadsheet format, the option is
provided to delete log records in that reporting range.
Note: If a custom parser is called to do further processing, the
parser needs to write a log file (i.e.
TRS_GLGL_00000000000000004912.xml.log in the same directory
as the original XML file, with a one-line status message that
either starts with "OK" or "ERROR errormessage" according to
the export results.
Without this log file the status logging will not work, even though
the files could still be parsed.
| Converted from CHM to HTML with chm2web Pro 2.85 (unicode) |