If you have reports that go to “Pending” and never process after changes have been made in your workstation, the problem usually is that your station ID has changed. When processing reports in OGwin, you have an option to save the report print selections. Simply check the box on the Output Options tab to “Save these settings as the default settings for this report and user.”

One of the settings is the station ID used to process the report. OGwin provides an option to prevent your future reports from going to “Pending”—even in cases of a change in the station ID.

Here’s what to do:

• In Output Options, click the Task Schedule tab
• Change the station ID to run on your new station ID under “Run on Station”
• Go back to the Output Options tab and click the “Save these settings as the default settings for this report and user”

This procedure will re-record the new settings for each of your reports. Repeat the procedure once for each report that goes to pending.

To run the “currently pending” reports:
• Press the Task Manager (F5 key) and click on “Schedule”
• Change the “Run on Station” ID to your new station ID
• When you click “OK,” the report will process
• Delete any duplicate reports still pending in Task Manager

Between Major Changes . . . Downloadable Updates

Periodically, we send you CDs with major changes to OGwin . . . to update your release version. Meantime, we continuously update our software and post downloadable, interim changes on our website as service packs. A service pack quickly updates programs, so it just takes a few seconds to download and apply to your database. It’s a good idea to check our website, http://www.ogsys.com, for interim updates. Find the service packs in the “Support” section of the website.

Positive Pay vs. Check Fraud

Check fraud is becoming a bigger problem each year. To help prevent check fraud, many banks today provide a positive pay solution for their customers. To expedite the feature, OGSYS now offers an optional Excel Macro that translates your check register to a bank-required format. For more information or to purchase this custom feature, contact .

New Procedures for Voucher Tagging

Over the past several months, in response to client issues, OGSYS has initiated several significant changes to the voucher tagging in the OGwin posting routines.

Here’s the new procedure—
• Posting routines default to post all vouchers in the module you are working
• If you go into the voucher selection line, the default changes to Tagged Vouchers for the User ID you used to sign-on to OGwin
• When you retrieve the vouchers, only the nonposted vouchers that user entered will appear
• To view all nonposted vouchers (regardless of user), enter a nonvalid User ID in the User ID to Process field
• When you retrieve the vouchers, OGwin will display all nonposted vouchers for that module (regardless of the User ID)
• You may tag and untag the vouchers you wish

Navigate the Latest SOX Enhancements and Master File Controls

OGSYS has been making changes to comply with SOX (Sarbanes-Oxley) requirements and to allow for more control over master file changes.

For many years, OGwin has included the Event Log in the Supervisor menu. It monitors entry into the database and marks the date and time a user enters an application. The system also allows you to designate certain applications to monitor in the Event Log Maintenance by check marking the application. At any time, you may view or print the log in the Event Log Maintenance.

Change List reports have always been available in many of the master file “Run Reports.” These Change List reports identify the number of changes made to a master file record since the change count was zeroed.

OGSYS also has created new OGwin options for password requirements.
Option 193 sets up a 30- or 60-day expiration for user passwords. The user must change their password when alerted by OGwin. The system no longer allows the OGwin supervisor to view user passwords.

Option 195 raises the minimum required password characters from four to eight. The required password remains alphanumeric.

Option 49 allows the OGwin Supervisor exclusive responsibility to zero the change count in the master file Run Report feature.

Here’s how to use this feature to monitor changes in the Master File (when a supervisor is logged in):

1. As a starting point, print the full list from all Master File-Run Report screens.
2. Check the box next to “OK to zero the change-count also?” This will print the Master Files as currently saved and mark the change count as zero for each master file.
3. Create a log of Master File changes. Use the log to maintain copies of approved master file changes, indicating what specific change was made, the user who made the change in OGwin (with the date and time), and any approvals required by your company.
4. In Supervisor-Event Log Maintenance, use a green check mark to designate each master file menu item that you want to monitor. This will make a log entry in the Event Log every time a user makes a change in the master file – it logs only the user ID, date, and time. It does NOT log exactly what was changed.
5. Weekly, supervisors should print a Changes List from master file maintenance and check the box next to “OK to zero the change-count also?”
6. Compare the Changes List to the log of Master File changes. If a master file record is listed as changed (but no record is found in the log), print the Event Log and determine what user(s) accessed that master maintenance menu item without an entry in the log.

In order to meet requirements, OGwin version 2.0 (now in beta testing) will make available additional changes. The new version will track changes to any data item or record that has a bearing on disbursements (checks). Examples include items such as vendor or owner name and address, bank information, and decks. “Tracking” involves noting when such things change, asking the user for a brief note or reason for the change, and creating a change history record in a new file (HC) tagged with the user ID, workstation, date and time.

You may request the change note for bank maintenance, vendor maintenance, owner maintenance, wire-transfer maintenance, deck maintenance (expense, revenue, and deck entity), and Lease Maintenance financial controls. Other changes – such as mass code changes that may affect decks – also will have a change history entry. When decks are involved, OGwin will try to protect against unauthorized changes, and substantially enhance the way deck changes are integrated into normal processing and posting.

In version 2.0, OGwin will provide a Disbursement Change History report. This report will have various filters, a time period entry, and will allow you to fully audit changes to any of the data items that are being tracked. It also will provide a separate section for owners, vendors, decks, etc. In addition, the upgrade will include a continuity section to prove that the change history itself has not been altered.