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:
- Create the batch.
- Enter the correct deposit total.
- Add applicable adjustments.
- Assign individual payments.
- Review posted totals.
- Check the difference.
- Investigate discrepancies.
- Confirm the difference reaches zero.
- 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.