The Transaction Run feature is the bridge between Unimarket’s Expense module and your institution’s financial system (ERP). It allows for the seamless extraction of approved expense data for reimbursement processing and general ledger posting.
The Transaction Run Process
Once expense claims have moved through the approval workflow and reached an Approved state, they are eligible for extraction.
- Extraction Logic: The system identifies all approved expense lines that have not yet been included in a previous extraction.
- Batching: These lines are bundled into a "Transaction Run," which generates a data file formatted specifically for your ERP.
Customized ERP Formats
Unimarket supports a variety of institution-specific file formats to ensure compatibility with different ERP systems. Common integrations include:
- Banner: Specialized formats for Ellucian Banner systems.
- Oracle: Formats tailored for Oracle Financials.
- Custom Formats: During the initial configuration, Unimarket can build customized extraction templates to match your internal requirements (CSV, XML, or Fixed-Width).
How to Execute an Extraction
While many integrations are automated, Administrators can view and manage these runs manually:
- Navigate to the Insights module.
- Select Transaction Runs.
- Locate the specific run for Expenses.
- Download the generated file to review or manually upload it to your ERP if an automated connection is not established.
Administrative Configuration
The behavior of the extraction—such as the schedule, file format, and the users notified of completion—is managed within the Expenses Administration Module.
Key administrative settings include:
- Mapping: Ensuring that Expense Categories in Unimarket map correctly to Account Codes in the ERP.
- Tax Handling: Defining how tax amounts are represented in the export file for reconciliation.
- Frequency: Setting the intervals for when the extraction occurs (e.g., daily or weekly).
Troubleshooting Integration
If a Transaction Run fails or if expenses do not appear in your ERP:
- Check Background Jobs: Verify if the run finished successfully in the administration logs.
- Error Reports: Review any error emails sent by the system, which typically identify invalid GL codes or closed fiscal periods that caused the ERP to reject the file.
Note: For more information on setting up the underlying rules for these extractions, please contact your Community Administrator.