Dividing responsibilities
ERP systems excel at general ledger, procurement, payroll and HR. They are rarely designed for student-level fee plans, concessions and parent-friendly receipts. The planned pattern keeps student billing in Acadlytic and posts summarised, reconciled entries to the ERP.
Planned flows
| Data | Direction |
|---|---|
| Fee invoices and receipts (summarised by account code) | Acadlytic → ERP |
| Refunds and adjustments | Acadlytic → ERP |
| Chart of accounts and cost centres | ERP → Acadlytic |
| Staff directory and departments | ERP/HR → Acadlytic |
Planned controls
- Posting batches with approval before export
- Account mapping maintained by finance, not IT
- Reconciliation reports for every posting period
- Audit trail for mapping changes
Frequently asked questions
Do we still need our ERP?
Usually yes, for the general ledger, payroll, HR and procurement. Acadlytic is designed to handle student-facing finance and post summaries to the ERP.
How often are entries posted?
Posting frequency is agreed with your finance team; daily or per accounting period are common, always with a reconciliation report.
Who maintains account code mappings?
Your finance team maintains mappings through the administration screens, with every change recorded.