Author: latonyabarker197@gmail.com

OASIS Batch Job Monitor is part of the background-processing architecture used to execute and monitor automated OASIS tasks. For advanced users and administrators, understanding job states, expected runtime, scheduling patterns, service configuration, and error output can make troubleshooting much more efficient.

Ingen Software’s Batch Job Monitor documentation describes an architecture consisting of the OASIS database, job initiator, job monitor, job code, OASIS user interface, and Windows Service. The interface is primarily used to configure and monitor jobs, while configuration information and job output are stored in the database.

This guide explains the main components of the OASIS Batch Job Monitor environment and how administrators can interpret common job states.

What Is the OASIS Batch Job Monitor?

The Batch Job Monitor is part of the infrastructure responsible for supervising background OASIS processes.

OASIS documentation describes periodic background tasks that can exchange information, perform recurring work, or handle functions such as database backups.

The system is designed so automated jobs can run without requiring a user to manually start each process.

OASIS Batch Architecture

The documented architecture contains several important components:

• OASIS GUI
• OASIS Database
• Windows Service
• Job Initiator
• Job Monitor
• Job code

Each component has a different role.

Understanding these roles helps administrators identify where a problem may be occurring.

OASIS GUI

The OASIS user interface is primarily used to configure and monitor jobs.

Administrators can review job definitions and change applicable configuration through the software interface.

The interface is therefore the administrator’s primary control point rather than the component actually performing every background task.

OASIS Database

The database stores Batch Job configuration information and job output.

This allows the system to maintain information about scheduled jobs and their execution results.

Database availability is therefore important to successful batch processing.

Job Initiator

The Job Initiator reviews jobs defined in the OASIS database.

When a job’s time parameters match the current time, the initiator launches a Job Monitor for that job.

This makes the initiator the component responsible for recognizing when a configured job should begin.

Job Monitor

The Job Monitor supervises the execution of the job.

OASIS documentation states that the monitor regularly updates job state information in the database and can terminate a job when it exceeds configured runtime limits under applicable settings.

Monitoring is important because background tasks can otherwise fail without being immediately visible to users.

Windows Service

OASIS Batch Jobs can use a Windows Service so background processing continues even when a user is not logged into the computer.

The service starts with the computer and can support persistent automated processing.

This differs from starting the initiator through the OASIS GUI, where closing the application can terminate that manually started processing environment.

Configuring OASIS Batch Jobs

The Batch Job listing shows defined jobs along with information such as name, time pattern, and current state.

Opening a job provides access to configuration fields.

Documented settings include:

• Job Name
• Affinity Host
• Time Pattern
• Run As
• Expected Runtime
• No Overtime

Each field influences how and where the job executes.

Job Name

Job Name identifies the automated task.

Clear names make administration easier, particularly when an OASIS environment contains many background jobs.

Administrators should avoid changing names without understanding how the job is referenced elsewhere.

Affinity Host

Affinity Host identifies the computer where the job should run.

This can be important when an organization has multiple servers or workstations.

If a job is configured for an unavailable or incorrect host, execution may not occur as expected.

Run As

Run As identifies the OASIS user under whose identity the job operates.

OASIS notes that this user’s ID can appear in updated-by information.

The selected account should therefore have the appropriate access required by the job.

Expected Runtime

Expected Runtime defines the maximum anticipated runtime in minutes.

This setting helps the monitoring environment identify processes that run significantly longer than expected.

Administrators should set realistic values based on actual workload.

A limit that is too short can cause legitimate long-running processes to be treated as failures.

No Overtime

When No Overtime is enabled and a non-zero Expected Runtime is configured, the monitor can terminate a job that exceeds the allowed runtime.

This can prevent a stuck process from running indefinitely.

However, administrators should investigate why a job exceeded its expected duration rather than simply increasing the limit repeatedly.

OASIS Job States

The Batch Job Monitor uses several states to describe job execution.

Documented states include:

• Never Run
• Setup
• Spawned
• Running
• Stopped
• Unknown
• Terminated
• Exception
• End

Understanding these states can significantly improve troubleshooting.

Never Run

Never Run indicates that the job has not executed previously.

For a newly created job, this can be expected.

For a job that should already have run, administrators should review scheduling and service configuration.

Setup

Setup indicates that the initiator has begun preparing the job.

This is an intermediate state in the execution process.

Spawned

Spawned indicates that the initiator has attempted to start the monitor for the job.

If a job remains around this stage unexpectedly, administrators may need to investigate whether the monitor or underlying process launched correctly.

Running

Running indicates that the Job Monitor has started the job code.

OASIS Batch Services provide the processing infrastructure used to run automated background jobs in OASIS. Instead of requiring a user to manually initiate every repetitive task, batch technology allows configured processes to execute in the background according to system settings.

OASIS Online documentation explains that batch technology is responsible for automatic processes such as updating Tiles and emailing Scheduled Reports. Administrators can manage this environment through Batch Services, Batch Jobs, and Job Administration. Access to these features requires Admin access to Software.

Understanding OASIS Batch Services is important for administrators because a batch job can be configured correctly but still fail to execute as expected if the service responsible for processing jobs is inactive, outdated, overloaded, or incorrectly configured.

This guide explains how OASIS Batch Services work, where administrators can find them, which service attributes matter, how concurrent processes are configured, and how to troubleshoot common background-processing problems.

What Are OASIS Batch Services?

OASIS Batch Services are part of the software infrastructure responsible for executing background jobs.

A batch job is a process that can run without continuous user input. OASIS describes a Batch Job as a feature that runs in the background and notes that jobs can be standard OASIS functionality or custom code created for a customer.

Batch Services provide the environment in which these automated jobs can operate.

Examples of batch-related automation can include:

• Scheduled reports
• Tile updates
• Email reminders
• Database-related processes
• Other recurring background tasks
• Customer-specific automated processes

The exact jobs available depend on the OASIS installation and configuration.

Where to Find OASIS Batch Services

In OASIS Online, administrators can access batch technology from the Configuration area.

The documented path is:

1. Open the OASIS menu.
2. Select Configuration.
3. Open the Jobs menu.
4. Select Batch Services.

The same Jobs menu also provides access to Batch Jobs and Job Administration.

Because these functions affect automated software operations, OASIS requires Admin access to Software for users who want to view or manage them.

Active and Not Active Batch Services

OASIS Online organizes Batch Services into two categories:

• Active
• Not Active

An active service is currently available for batch processing, while a service shown as Not Active is not currently operating as an active batch service.

This distinction provides administrators with a quick way to review the overall batch environment.

If automated jobs unexpectedly stop running, checking whether the expected Batch Service appears as active is a useful early troubleshooting step.

Batch Service Viewer

Opening a service displays the Batch Service Viewer.

OASIS currently documents several important service attributes:

• Software
• State
• Update
• Active
• Server
• Processes

The Software field identifies the software version used by the service. The State field shows service status. Update indicates when the service last responded, and OASIS states that this value should normally update every two to five minutes.

These fields can provide valuable diagnostic information.

Understanding the Active Field

The Active value indicates whether the service is running.

OASIS displays true when the service is running and false when it is not.

If jobs are not processing, administrators can check this field before making more complicated configuration changes.

An inactive service may explain why otherwise valid jobs are waiting rather than executing.

Understanding the Server Field

OASIS Batch Services can distinguish between servers and non-server services.

The Batch Service Viewer displays Y when the service has been identified as a server. OASIS documentation notes that non-server services normally do not run jobs while designated servers are available.

This architecture can help organizations control which machines are primarily responsible for batch processing.

It also means that administrators troubleshooting jobs should understand which machine is intended to function as the server.

Concurrent Batch Processes

The Processes value controls how many batch job processes can run concurrently on a service.

OASIS allows administrators to edit this number through the Batch Service Editor.

Concurrency matters because a service with multiple scheduled jobs may need to process several tasks during the same period.

However, simply increasing the process count is not always the correct response to slow processing.

Administrators should consider:

• Server capacity
• Database workload
• Job complexity
• Expected runtime
• Scheduling patterns
• Other system activity

Changing concurrency without understanding the workload can create additional resource pressure.

Editing an OASIS Batch Service

Authorized users can edit a Batch Service from the Batch Service Viewer.

Current OASIS documentation allows administrators to change the number of processes permitted to run concurrently and identify whether the Batch Service should be treated as a server.

These settings can influence how jobs are distributed across available services.

Changes should be made carefully because they can affect multiple automated processes.

OASIS Batch Service Restart Behavior

OASIS Online documentation states that each installation contains an implementation of the OASIS Batch Service that becomes active when OASIS starts. The service also restarts when the computer restarts.

This behavior is especially relevant for machines dedicated to batch processing.

Administrators should understand how system restarts, OASIS updates, and service availability interact before diagnosing failed jobs.

Software Version and Updates

Software version is another useful diagnostic field.

OASIS notes that if a new software version is deployed, a Batch Service can take itself offline until OASIS is restarted and the new version is loaded.

If batch processing stops after an update, administrators should therefore verify:

• Software version
• Service state
• Last update response
• Whether OASIS has been restarted
• Whether the expected server is active

This can be more effective than immediately editing individual jobs.

OASIS Batch Services and Batch Jobs

Batch Services and Batch Jobs are related but different.

A Batch Job defines the work to be performed.

A Batch Service provides processing capacity for running that work.

A simple conceptual model is:

Batch Job = what should run.

Batch Service = where or how the job receives processing capacity.

Job Administration = tools for managing and reviewing the automated environment.

Understanding these distinctions makes troubleshooting much easier.

Email Reminders Batch

OASIS provides a practical example of batch automation through its Email Reminders Batch.

Documentation explains that email reminders can be sent automatically through a Batch Job running through the OASIS Batch Service. The documented setup can send reminder emails periodically from the server running the service.

This demonstrates why Batch Services matter: the reminder functionality depends on background processing rather than a user manually sending every reminder.

Batch Service and Email Configuration

Automated email jobs can require additional configuration.

For the Email Reminders Batch, OASIS notes that the Batch Service user must have appropriate email preferences configured. SMTP is recommended for batch job usage.

If a job appears to run but emails are not delivered, the problem may therefore involve email configuration rather than the Batch Service itself.

Administrators should distinguish among:

• Service problem
• Job problem
• Email configuration problem
• Recipient information problem

Batch Service Status Troubleshooting

When automated OASIS processing stops, begin with basic service information.

Check:

• Is the expected service Active?
• What is the State?
• When did Update last change?
• Is the service identified as a Server?
• How many Processes are configured?
• Is the software version current?

OASIS states that the service response time shown under Update should normally refresh every two to five minutes.

A stale response can therefore provide a useful troubleshooting signal.

Batch Jobs Running Slowly

Slow jobs can result from many factors.

Potential causes include:

• Limited concurrent processing
• Long-running jobs
• Database workload
• Server resource limitations
• Multiple jobs scheduled simultaneously
• Job-specific errors

Administrators should review both service capacity and individual job behavior.

Increasing concurrent processes without investigating job runtime can simply move the bottleneck elsewhere.

OASIS Desktop Batch Services

Batch-related configuration also exists within OASIS Desktop.

Current OASIS Desktop documentation identifies Batch Services within Software configuration and describes this area as the place to configure the Batch Service, view existing batches, and check statuses.

Organizations using Desktop, Online, or hybrid workflows should therefore understand which environment their automated process belongs to before following configuration instructions.

Batch Services and Database Backups

OASIS Batch Job Monitor documentation identifies database backup as one example of a standard background job. The documented architecture allows batch processing to run periodic tasks that share information or back up the OASIS database.

Automating these processes can reduce manual administrative work, but administrators should still monitor results and confirm that critical jobs complete successfully.

OASIS Batch Service Security

Batch Services can execute automated processes with significant system access.

Administrative permissions should therefore be restricted appropriately.

Organizations should protect:

• Administrator accounts
• Batch configuration
• Database access
• Email credentials
• Job output
• Server access

Never provide OASIS administrative credentials to an independent informational website.

Frequently Asked Questions

What are OASIS Batch Services?

They are part of the OASIS background-processing infrastructure used to execute automated Batch Jobs.

Where can I find Batch Services in OASIS Online?

Administrators can open Configuration, select Jobs, and choose Batch Services.

Who can manage OASIS Batch Services?

OASIS states that Admin access to Software is required for these features.

What does Active mean?

The Active field indicates whether a Batch Service is currently running.

What does Processes mean?

Processes indicates how many Batch Job processes the service is allowed to run concurrently.

Why might a Batch Service go offline after an update?

OASIS notes that a service can take itself offline after a new software version is deployed until OASIS is restarted and the new version is loaded.

Final Thoughts

OASIS Batch Services provide the processing foundation for automated background jobs. Administrators can use the Batch Services environment to review active services, software versions, service status, response times, server designation, and concurrent process limits.

Successful batch administration requires understanding both sides of the system: Batch Jobs define automated tasks, while Batch Services provide the environment that executes those tasks.

When background processing fails, administrators should review service health and job configuration systematically before making major changes.

An OASIS Payment Batch is used to organize and reconcile payments associated with a bank deposit. Instead of reviewing individual payments without a common reference, users can create a batch representing the deposit, assign payments to it, record applicable adjustments, and monitor the remaining difference until the batch balances.

Ingen Software’s OASIS documentation explains that payment batches improve accounting accuracy by allowing users to balance individual payments against the deposit amount. As payments are attached and posted, the Difference value should approach zero.

This guide explains how an OASIS Payment Batch works, how to create one, how the Total, Posted, Adjustments, and Difference fields interact, and what users should verify before posting.

What Is an OASIS Payment Batch?

A payment batch is essentially a reconciliation container for a bank deposit.

The batch identifies the expected total deposit while individual payments are assigned to it.

OASIS then compares the amounts.

The primary values are:

• Code
• Total
• Posted
• Adjustments
• Difference

Together, these fields allow accounting users to see whether the batch has been fully reconciled.

Why Use Payment Batches?

Payment batches improve organization.

Without a batch, users may have individual payments but less visibility into whether those transactions collectively match a specific bank deposit.

A batch helps answer questions such as:

• Which payments belong to this deposit?
• What was the expected deposit total?
• How much has been posted?
• Are adjustments required?
• Is anything missing?
• Does the batch balance?

This can improve accounting accuracy and make discrepancies easier to investigate.

Creating a New OASIS Payment Batch

OASIS documentation provides a specific workflow for creating a new batch.

Users navigate to Payments, select File, hover over New, and choose New Batch. The Batch Editor then opens.

The user enters the batch information and saves it before applying payments.

OASIS Batch Code

The Code field provides a tracking identifier for the deposit.

OASIS notes that the deposit date is often used as the tracking code.

A consistent coding system can make historical research easier.

For example, accounting teams may want codes that allow them to quickly associate a batch with a deposit date or internal reconciliation process.

OASIS Batch Total

The Total represents the total deposit amount.

This value should match the amount expected to reach the bank.

Accuracy is important because the Difference calculation depends on the Total.

If the Total is entered incorrectly, the batch may appear out of balance even when every payment has been assigned correctly.

OASIS Posted Amount

Posted represents the sum of payments using the batch code.

As payments are applied and posted, OASIS updates this value automatically.

Users can therefore monitor progress without manually adding every payment amount.

OASIS Adjustments

The Adjustments field represents the sum of adjustments associated with the batch.

Users can add adjustments through the Adjustments tab in the Batch Editor.

Adjustments should be used according to the organization’s accounting procedures.

Users should also document unusual adjustments clearly when appropriate.

OASIS Difference

Difference shows whether the batch balances.

OASIS calculates it as the Total minus Adjustments minus Posted.

The goal is generally for Difference to reach zero before the batch is posted.

If the difference is not zero, investigate the transactions rather than forcing the batch to close.

Applying a Batch to a Payment

Once the batch exists, users can assign individual payments to it.

Open a payment from the Payments page and use the Batch drop-down menu in the Payment Editor to select the appropriate batch code.

This creates the link between the payment and the deposit batch.

Watching the Batch Update

As payments are applied and posted, the batch entry updates to show posted dollars and the remaining difference.

This makes it possible to monitor reconciliation in real time as accounting work progresses.

Why a Batch May Not Balance

A non-zero Difference can have several causes.

Potential problems include:

• Missing payment
• Wrong payment amount
• Payment assigned to another batch
• Incorrect batch Total
• Missing adjustment
• Incorrect adjustment
• Duplicate transaction

Investigate these possibilities systematically.

Finding Missing Payments

When the Difference indicates that the batch is short, review payments expected for the deposit.

Compare:

• Deposit documentation
• OASIS payment records
• Batch assignments
• Individual amounts

A payment may exist in OASIS but simply have the wrong batch code.

Incorrect Batch Assignment

A payment assigned to the wrong batch can cause two batches to appear incorrect simultaneously.

One batch may be short while another is over.

Review batch codes carefully before creating additional adjustments.

Correcting the assignment may resolve both discrepancies.

Using Attachments

OASIS allows attachments to be added through the Batch Editor.

Attachments can support reconciliation by preserving appropriate documentation with

OASIS Batch Processing is the background automation system used to execute scheduled or repetitive tasks without requiring a user to manually start each process. Within OASIS Online, batch technology supports automatic functions such as Tile updates and Scheduled Report emails, while OASIS batch jobs can also be used for activities such as downloading information, processing reports, and synchronizing databases.

For administrators, understanding batch processing is important because an automated task can continue running even when ordinary users are not actively interacting with it. Proper configuration, scheduling, monitoring, and error review help ensure that background processes operate reliably.

This guide explains OASIS Batch Processing, Batch Services, Batch Jobs, scheduling patterns, job cycles, administration, monitoring, and common troubleshooting techniques.

What Is OASIS Batch Processing?

OASIS batch processing allows software tasks to run in the background according to configured rules.

A batch job can be a standard OASIS feature or custom functionality created for a specific customer. OASIS documentation notes that batch jobs have been used for more than a decade for tasks including factory-data downloads, report processing, and database synchronization.

Instead of requiring someone to manually initiate every repetitive task, administrators can configure jobs to run automatically.

OASIS Online Batch Technology

OASIS Online includes dedicated administration areas for batch technology.

Authorized administrators can access:

• Batch Services
• Batch Jobs
• Job Administration

These options are available from the Jobs menu within OASIS Online Configuration. Users must have Admin access to Software to manage these features.

What Is an OASIS Batch Service?

The Batch Service provides processing capacity for background jobs.

OASIS Online documentation states that every OASIS installation includes a full implementation of the batch service. The service becomes active when OASIS starts and restarts when the computer restarts. It can be disabled, although the underlying process itself cannot simply be stopped through the normal configuration workflow.

Batch Services are categorized as:

• Active
• Not Active

Administrators can inspect each service to understand its current state.

Batch Service Information

The Batch Service Viewer displays several useful attributes.

These include:

• Software version
• State
• Last update
• Active status
• Server status
• Number of concurrent processes

OASIS states that the Update value should normally refresh every two to five minutes.

This information can help administrators determine whether a service is responding normally.

OASIS Batch Jobs

A Batch Job is a background task that runs without ordinary user input.

OASIS Online organizes Batch Jobs into three categories:

• Active
• Not Active
• Disabled

The Batch Job Viewer displays the job name, status, summary, schedule, affinity, disabled status, and historical cycles.

This provides administrators with a central location for reviewing automated activity.

OASIS Batch Job Status

Job status helps administrators understand what a background process is doing.

Common statuses include Running and End. OASIS also uses Never Run when a job has not yet executed.

Legacy Batch Job Monitor documentation describes additional states including Setup, Spawned, Stopped, Unknown, Terminated, and Exception.

An abnormal state can indicate that further investigation is necessary.

Scheduling OASIS Batch Jobs

Batch Jobs can use Time Patterns to determine when they run.

Current OASIS Online documentation includes scheduling concepts such as:

• ONCE
• ALWAYS
• DELAY
• YEAR
• MONTH
• MDAY
• WDAY
• HOUR
• MINUT

These patterns allow administrators to configure one-time, recurring, or calendar-based processing.

ALWAYS Batch Jobs

An ALWAYS job attempts to run whenever processing resources are available.

This type of configuration can be useful for tasks that need to execute continuously or as frequently as system capacity allows.

Administrators should use continuous processing carefully because it can consume resources.

DELAY Batch Jobs

A DELAY pattern allows a job to wait a specified number of minutes before attempting to run again.

For example, a recurring background task might complete, wait for the configured delay, and then become eligible to execute again.

This is useful for tasks that need frequent processing without running continuously.

Calendar-Based Scheduling

Administrators can also schedule jobs according to calendar values.

Examples include:

• Specific year
• Month
• Day of month
• Day of week
• Hour
• Minute

This allows automated jobs to align with business processes such as reporting schedules or recurring maintenance.

Batch Job Affinity

OASIS Batch Jobs support affinity configuration.

Affinity can determine which host or database is allowed to run a job.

Current documentation allows administrators to configure Affinity Host and Affinity DB values.

This can be particularly useful in environments where several machines or databases participate in OASIS processing.

Editing a Batch Job

Authorized administrators can edit Batch Jobs.

Available settings include:

• Disabled status
• Number of historical cycles retained
• Affinity Host
• Affinity DB
• Time Pattern
• State

Administrators can also force a job to run as soon as possible through the available restart functionality.

Changes should be made carefully because they can affect automated business processes.

OASIS Batch Job Cycles

Each execution of a Batch Job is called a cycle.

OASIS maintains historical cycles according to the Keep Cycles setting.

A cycle can contain:

• Standard Output
• Standard Error

Standard Output provides information about background processing, while Standard Error contains errors generated during execution.

Reviewing cycles is one of the most useful troubleshooting techniques.

Standard Output

Standard Output functions similarly to a processing log.

It can help administrators understand what happened while a Batch Job was running.

Depending on the job, output may describe:

• Records processed
• Updates completed
• Files handled
• Other job-specific activity

This information can help confirm whether a job completed the expected work.

Standard Error

Standard Error records errors generated during a Batch Job cycle.

OASIS states that when an error occurs, the current job cycle ends and the system attempts to run the job again during the next scheduled cycle.

Administrators troubleshooting failures should therefore inspect the Standard Error information rather than simply restarting the job repeatedly.

Job Administration

OASIS Online also includes Job Administration.

This area can be used to specify the default database for newly created Batch Jobs. OASIS notes that Tiles rely on batch jobs for automatic data updates, and administrators can select the database where newly created jobs should be assigned.

The setting is not retroactive, so existing jobs may require separate configuration.

OASIS Tiles and Batch Processing

Tiles in OASIS Online depend on batch processing for automatic data updates.

If Tile information is not refreshing as expected, administrators may need to investigate the associated Batch Job configuration or service status.

This illustrates how batch technology can affect features visible to ordinary users even though the processing itself happens in the background.

Scheduled Reports

Scheduled Report emails are another example of automated OASIS Online processing.

Batch technology can handle the background work required to send reports according to configured schedules.

If scheduled reports stop arriving, batch processing may therefore be one area to investigate.

Email Reminder Batch

OASIS also supports an Email Reminders Batch.

Documentation explains that this job can automatically email reminders to the assigned user based on the reminder date, time, and email configured for that user’s account.

When run through the server batch service, the service user must have appropriate email preferences configured.

OASIS Batch Processing Architecture

Legacy technical documentation describes several components in the OASIS batch architecture:

• OASIS GUI
• OASIS Database
• Windows Service
• Job Initiator
• Job Monitor
• Job code

The GUI is primarily used for configuration and monitoring, while configuration information and job output are stored in the database.

Job Initiator

The Job Initiator reviews jobs defined in the OASIS database.

When configured time parameters match the current time, it launches a Job Monitor for the appropriate task.

This component therefore helps connect job scheduling with actual execution.

Job Monitor

The Job Monitor tracks execution and updates the job’s state.

Legacy OASIS documentation explains that the monitor periodically reports status to the database and may terminate a job if it exceeds configured runtime limits.

Monitoring helps administrators distinguish between normal processing and jobs that may have stalled.

Checking Batch Service Status

OASIS Desktop provides a way to review when the Batch Service last ran.

Documentation explains that users can open Batch Jobs and review the recorded date, time, and host. If the date is old, the service may need to be restarted.

A recent status can indicate that the service itself is functioning even if an individual job still has a problem.

Troubleshooting OASIS Batch Processing

When automated processing fails, troubleshoot systematically.

Start by checking:

• Batch Service status
• Job status
• Time Pattern
• Affinity settings
• Job history
• Standard Output
• Standard Error
• Database configuration

Do not immediately change multiple settings because doing so can make the original problem harder to identify.

Batch Processing Security

Batch Jobs can affect business information and automated workflows.

Administrative access should therefore be restricted.

OASIS Online specifically requires Admin access to Software for management of Batch Services, Batch Jobs, and Job Administration.

Users should also protect OASIS administrator credentials and avoid sharing privileged accounts.

Frequently Asked Questions

What is OASIS Batch Processing?

It is the background processing environment used to run scheduled or automated OASIS tasks.

What is an OASIS Batch Job?

A Batch Job is a feature that runs in the background without ordinary user input and can perform standard or custom automated processing.

What are Batch Services?

Batch Services provide processing capacity for OASIS background jobs and can be reviewed through OASIS configuration.

What is a Batch Job cycle?

A cycle is one execution of a Batch Job. Historical cycles can contain Standard Output and Standard Error information.

Who can manage OASIS Online Batch Jobs?

Users need Admin access to Software to view and manage OASIS Online batch technology.

Why is my OASIS Batch Job failing?

Potential causes include job configuration, service problems, affinity settings, scheduling, database configuration, or an error generated by the job itself. Review the job cycle and Standard Error information.

Final Thoughts

OASIS Batch Processing provides the automation layer behind many recurring and background tasks. Batch Services provide processing capacity, Batch Jobs define automated work, Time Patterns control scheduling, and Job Administration helps determine where new jobs run.

Administrators can use job history, Standard Output, Standard Error, service status, and affinity settings to understand how automated processes are operating.

Because batch technology can affect reports, Tiles, database operations, reminders, and other important business processes, configuration changes should be made carefully and only by authorized users.

OASIS Batch is a term associated with batch processing functions available within OASIS software environments. Depending on the task, users may be looking for information about payment batches, automated Batch Jobs, Batch Services, Job Administration, scheduled processes, or troubleshooting background tasks.

OASIS Online documentation describes batch technology as the system responsible for several automated processes, including functions such as Tile updates and emailing Scheduled Reports. Administrators can access dedicated Batch Services, Batch Jobs, and Job Administration areas from the OASIS Online configuration environment.

OASIS also uses batches for payment processing. A payment batch can be used to track a bank deposit, connect individual payments with the appropriate deposit, account for adjustments, and verify that the batch balances before it is posted.

Understanding these two related concepts is important. An OASIS payment batch organizes financial transactions, while OASIS batch technology can also refer more broadly to automated background jobs and services.

What Is OASIS Batch?

OASIS Batch can refer to functionality that groups transactions or executes automated processing within an OASIS software environment.

In payment processing, a batch provides a structured way to group payments associated with a bank deposit.

In OASIS Online administration, batch technology supports automated jobs that run according to configured processes.

Depending on the user’s role, OASIS Batch tasks may involve:

• Creating payment batches
• Assigning payments to batches
• Recording adjustments
• Reconciling deposit totals
• Posting completed batches
• Configuring Batch Services
• Managing Batch Jobs
• Reviewing Job Administration
• Monitoring background processes
• Troubleshooting failed jobs

The exact features available depend on the OASIS environment and user permissions.

OASIS Payment Batch

One of the clearest uses of an OASIS batch is payment reconciliation.

OASIS support documentation explains that a batch is used to track bank deposits. Payments are attached to a batch so users can compare the expected deposit total with the payments and adjustments associated with that deposit.

This provides a more organized accounting workflow.

Instead of treating every payment as an isolated transaction, the system allows related payments to be grouped under one batch code.

How an OASIS Payment Batch Works

A typical payment batch begins with the expected bank deposit amount.

Users then associate individual payments with that batch.

As transactions are added, OASIS calculates how much has been posted and compares the result with the expected total.

A payment batch can include values such as:

• Batch code
• Total
• Posted amount
• Adjustments
• Difference

The objective is generally to reconcile the batch so the difference reaches zero before final posting.

Creating a New OASIS Batch

OASIS documentation describes a straightforward process for creating a payment batch.

Users navigate to the Payments area, select File, choose New, and then select New Batch.

The Batch Editor then allows the user to enter the required information.

This can include:

• Code
• Total
• Notes
• Adjustments
• Attachments

The batch code serves as a tracking identifier for the deposit.

OASIS notes that the deposit date is commonly used as a batch tracking code.

OASIS Batch Code

The batch code helps identify the deposit associated with a group of payments.

A useful code should make it easy for authorized accounting users to determine which deposit the batch represents.

Because OASIS documentation notes that the deposit date is often used, organizations can develop consistent naming practices around their accounting workflow.

Consistency becomes increasingly important when users need to search historical batches or reconcile large numbers of transactions.

OASIS Batch Total

The Total field represents the total amount expected for the deposit.

As individual payments are assigned to the batch, OASIS can compare those payments against the expected amount.

The total should therefore be entered accurately.

An incorrect total can create a difference even when all individual payments have been entered correctly.

Posted Amount

The Posted value represents the sum of payments associated with the batch according to the OASIS workflow.

As additional payments are linked and posted, this value changes.

Users can compare the Posted amount against the batch Total and applicable Adjustments to determine whether the deposit has been fully reconciled.

OASIS Batch Adjustments

Not every deposit necessarily matches the simple sum of individual payments without additional accounting considerations.

OASIS provides an Adjustments area within the Batch Editor.

Authorized users can add relevant adjustments and include them in the reconciliation calculation.

Organizations should follow their own accounting policies when entering adjustments.

OASIS Batch Difference

Difference is one of the most important values when reconciling a batch.

OASIS calculates the difference using the total, posted payments, and adjustments.

As transactions are correctly assigned to the batch, the difference should move toward zero.

A remaining difference can indicate that:

• A payment is missing
• A payment is assigned incorrectly
• The total is wrong
• An adjustment is missing
• An amount was entered incorrectly

Users should investigate discrepancies before posting the batch.

Applying a Batch to a Payment

After creating the batch, individual payments can be associated with it.

OASIS documentation explains that users can open a payment in the Payment Editor and select the appropriate batch code from the Batch drop-down menu.

This links the payment to the batch.

As more payments are connected, the batch information updates to reflect the posted amount and remaining difference.

Reconciling an OASIS Batch

Reconciliation is the process of ensuring the batch corresponds with the actual deposit.

A practical workflow can include:

1. Create the batch.
2. Enter the correct deposit total.
3. Add applicable adjustments.
4. Assign individual payments.
5. Review posted totals.
6. Check the difference.
7. Investigate discrepancies.
8. Confirm the difference reaches zero.
9. Post the batch.

Users should avoid rushing through the final steps because reconciliation errors can make accounting records more difficult to correct later.

Posting an OASIS Batch

Once all relevant payments have been applied and the difference reaches zero, the batch can be posted.

OASIS documentation warns that after a batch is posted, it cannot be unposted.

This makes the final review particularly important.

Before selecting Post Batch, verify:

• Correct batch code
• Correct total
• Correct payments
• Correct adjustments
• Zero difference
• Appropriate supporting documentation

After verification, authorized users can complete the posting process.

OASIS Batch Attachments

The Batch Editor also supports attachments.

Attachments can help users maintain documentation associated with the batch.

Depending on organizational procedures, supporting material can help explain transactions, adjustments, or reconciliation activity.

Users should follow company policies regarding which financial documents can be stored in the system.

What Is OASIS Online Batch Technology?

OASIS Online also includes a broader batch technology environment for automated background processes.

OASIS support documentation states that batch technology performs several automatic processes exclusive to OASIS Online.

Examples include:

• Tile updates
• Scheduled Report emails
• Other configured automated jobs

This technology is managed separately from the normal payment-batch workflow.

OASIS Batch Services

Batch Services is one of the administration areas available within OASIS Online.

Authorized administrators can reach batch technology configuration through the OASIS Configuration area.

From there, the Jobs menu provides access to:

• Batch Services
• Batch Jobs
• Job Administration

These tools are intended for administrative users who need to manage automated OASIS processes.

OASIS Batch Jobs

A Batch Job represents a configured automated process.

Batch jobs can perform repetitive or scheduled tasks without requiring a user to manually start every operation.

This can improve efficiency for processes that need to occur regularly.

Examples of automated functionality can include scheduled reporting or system updates.

Exact jobs depend on the OASIS configuration.

Job Administration

Job Administration provides another area for managing or reviewing OASIS batch activity.

Administrators can use batch administration tools to understand how automated tasks are configured and operating.

Because these settings affect system processes, access is generally restricted.

OASIS documentation specifies that users need Admin access to Software to view and manage the relevant OASIS Online batch technology features.

Why Batch Processing Matters

Batch processing is useful because many business operations are repetitive.

Without automation, users might need to perform the same tasks manually at regular intervals.

Batch technology can help:

• Reduce repetitive work
• Standardize processes
• Schedule recurring tasks
• Improve consistency
• Automate reporting
• Support system maintenance

However, automation also requires monitoring because a failed background process may not be immediately visible to ordinary users.

OASIS Batch Job Monitor

OASIS documentation also describes a Batch Job Monitor architecture used to manage background processes.

The documented architecture includes elements such as:

• OASIS GUI
• OASIS database
• Job initiator
• Job monitor
• Job code
• Windows Service

The OASIS interface can be used to configure and monitor jobs, while configuration and job output are stored within the database.

This architecture helps explain how automated OASIS processes can run separately from normal interactive user activity.

OASIS Batch Troubleshooting

When a payment batch does not balance, begin with the financial data.

Check:

• Batch total
• Individual payments
• Batch assignments
• Adjustments
• Duplicate entries
• Missing payments

When an automated Batch Job fails, troubleshooting is different.

Administrators may need to review:

• Job configuration
• Batch Service
• Job status
• Service availability
• Job output
• Scheduling
• System permissions

Users should avoid changing administrative configuration without understanding the effect on other automated processes.

OASIS Batch Permissions

Not every OASIS user should have access to batch administration.

OASIS Online documentation specifically notes that Admin access to Software is required for users who want to view and manage batch technology features.

Role-based access is important because batch settings can affect automated system operations.

Organizations should grant administrative permissions only to appropriate users.

OASIS Batch Security

Financial batches and system jobs can involve sensitive business information.

Users should protect:

• OASIS credentials
• Accounting records
• Payment information
• Batch documentation
• Administrative access

Never share administrator credentials.

Users should also verify that they are accessing the authorized OASIS environment before entering passwords.

Independent informational websites should never collect OASIS administrator credentials.

Frequently Asked Questions

What is an OASIS batch?

An OASIS batch can refer to a group of payments used to track and reconcile a bank deposit or to broader automated batch-processing functionality within OASIS Online.

What is an OASIS payment batch used for?

Payment batches help users group payments associated with a deposit and reconcile posted payments and adjustments against the expected deposit total.

What does Difference mean in an OASIS batch?

Difference represents the remaining amount after comparing the batch total with posted payments and applicable adjustments.

When should an OASIS batch be posted?

The batch should generally be fully reviewed and reconciled before posting. OASIS documentation notes that a posted batch cannot be unposted.

What are OASIS Batch Jobs?

Batch Jobs are automated processes configured within the OASIS Online batch technology environment.

Where are OASIS Batch Jobs managed?

Authorized administrators can access Batch Services, Batch Jobs, and Job Administration from the Jobs area within OASIS Online Configuration.

Who can manage OASIS batch technology?

OASIS documentation states that Admin access to Software is required to view and manage these batch technology features.

Is oasisbatch.com an official OASIS or Ingen Software website?

Unless an official affiliation has been independently established, the site should be presented as an independent informational resource. Users should use authorized OASIS or Ingen Software resources for software login, administration, technical support, and private business information.

Final Thoughts

OASIS Batch functionality supports two important business workflows: financial reconciliation and automated processing.

Payment batches allow users to group payments around bank deposits, track posted amounts and adjustments, identify differences, and post a batch after reconciliation. Automated OASIS Online batch technology handles background processes through Batch Services, Batch Jobs, and Job Administration.

Understanding which type of OASIS Batch function you are working with is the first step toward using the system correctly.

Accounting users should focus on accurate payment reconciliation, while system administrators should carefully manage automated jobs and monitor background processing.

For actual software configuration, account access, or technical troubleshooting, users should rely on authorized OASIS documentation and support resources.