Hospital Accounting - Statements, Finance Charges, and Peoplesoft
- Andrew Hanneman
- Cathy Allison
Hospital Statements
Description: This job runs on a specific day for each month and generates the client statements for the previous month.
The default date is the 1st of the month, but you can adjust this date to any date based on your organization's account preferences.
These statements, once created, can be review and sent via email, or printed on paper and mailed out in a batch mail process.
Processor Intensive
As this batch may be processor intensive, VetView recommends that you run it after hours on a dedicated API server. It may also cause database slowdowns depending on your system configuration.
Hospital Finance Charges
Description: This cron job runs once a month at the designated time and applies client finance charges.
(This was previously included with Hospital Statements, but was moved to its own separate job for clarity of purpose.)
This job can also be Manually Executed on a specific date by someone in your accounting department, rather than running on a timer.
Additional Setup on Hospital Setup Screen
You will need to fill out the information on the Hospital Late Fees tab in Hospital Setup for this job to be able to run correctly. See the Late Fees Tab for information on setting this up.
Hospital Peoplesoft Interface
Description: Hospital Peoplesoft Interface
VetView can communicate with most PeopleSoft interfaces to sent desired accounting information from the local hospital system to the organization's Peoplesoft accounting system.
These messages use SOAP protocols and Peoplesoft's custom XML.
Job Settings
Vetview recommends running this job on a dedicated API server.
if this job is to be run automatically, it may be best to set it to run after hours. Messages can also be generated and sent manually for specific dates as needed.
Additional Settings
These settings will need to be configured for your organization's specific Peoplesoft interface. You will need the specific Account code given to you by Peoplesoft, and the username and password needed to post SOAP forms to the Web Service URL for your organization's Peoplesoft integration.
The SOAP actions for your organization will also be unique, and will need to be programmed externally to ensure accurate data capture.
Interface Logs
Message Log Search
You can filter logs by date to review the most recent messages.
Successful messages will appear marked with an S, whereas failed messages will appear marked with an F.
If there have been changes to the Peoplesoft configuration, the messages may fail and you will need to modify the SOAP actions to match the changes.
Message Details
Click on any of the sent or failed messages to view the raw XML that was sent via the SOAP action.