Feature
Data Exporting
Export payroll, billing, and utilization data in the formats payers, accountants, and auditors require.
Exporting capabilities at a glance
- General ledger exports in the layouts common accounting packages accept
- Payer and state reporting files in required formats
- Grant and program reporting on funder-defined schedules
- Custom extracts with saved, reusable definitions
- CSV, fixed-width, and delimited output
- Scheduled recurring exports with delivery logging
Data has to leave the system as often as it enters it — to accountants, payers, state agencies, grant funders, and auditors, each wanting a different cut in a different format on a different schedule. ArborSoft treats that as configuration rather than as a series of one-off requests.
Feed the accounting system
Payroll and vendor payment activity exports as general ledger journal entries in the layouts common accounting packages accept, with account mapping configured once and applied every period.
Because the export derives from posted transactions rather than a summary, the general ledger reconciles to the payroll detail without a bridging spreadsheet.
Meet payer and state reporting requirements
State agencies and payers require periodic reporting beyond claims: service utilization, encounter data, participant counts, and expenditure summaries. Formats are prescribed and unforgiving.
ArborSoft produces these to the required layout, with the same validation applied to magnetic media filings — the file is checked before it is sent.
Report on grant programs
Grant-funded programs report on the funder’s terms: expenditure by category and period, participants served, service units delivered, and administrative-versus-direct cost splits.
Export definitions are saved and reused, so a quarterly report becomes a scheduled run rather than a rebuild. When a funder changes their template, the change is made once.
Build custom extracts
Beyond the standard set, custom extracts can be defined against any data in the system — selected fields, filters, date ranges, sort order, and output format — then saved and re-run.
This is what absorbs the ad-hoc requests. A payer asking for an unusual cut of last quarter’s utilization is a saved definition, not a support ticket.
Schedule and log delivery
Recurring exports run on a schedule with results reported through notifications. Every run is logged with its definition, parameters, record count, and destination, so the record of what was sent and when is retained alongside the import history in the other direction.
Exporting is one module of the ArborSoft fiscal agent platform — see how it fits into self-directed care and FMS operations.
Works alongside Exporting
Every ArborSoft module shares one record set, so data entered once flows everywhere it is needed.
- ImportingImport authorizations, demographics, and payer files on a schedule, with validation and full error reporting.
- BillingBuild 837P and 837I claims from verified service data, auto-post 835 remittances, and reconcile payer payments in one place.
- PayrollComplete payroll inside the platform, generating checks and direct deposits for employees and vendors without a third-party processor.
See Exporting in ArborSoft
Request a walkthrough of the platform and we will show you how authorizations, EVV, payroll, billing, and tax filing work together in a single system.