Fee billing to reconciliation
Issue approved charges, allocate confirmed receipts and investigate the remaining balance.
4 stages · 2 approvals
Reconcile student accounts and campus expenditure to reviewed financial postings.
Visible to: Finance Manager. Visibility does not establish approval authority.
| Number | Organization | Source Type | Source Number | Period | Currency |
|---|---|---|---|---|---|
| JE-26031 | ORG-6303 | ST-714 | JE-97031 | PRD-963 | CRR-887 |
| JE-62706 | ORG-9697 | ST-610 | JE-42043 | PRD-824 | CRR-561 |
| JE-30305 | ORG-2932 | ST-489 | JE-85477 | PRD-717 | CRR-156 |
| JE-22174 | ORG-4355 | ST-846 | JE-62834 | PRD-483 | CRR-162 |
| JE-30113 | ORG-6364 | ST-777 | JE-40402 | PRD-555 | CRR-157 |
| JE-68876 | ORG-1870 | ST-703 | JE-81755 | PRD-434 | CRR-142 |
Student collections, campus expenditure and intercompany allocations reach the ledger through identifiable source documents. Finance needs to explain the difference between an enrollment, a charge, a receipt and recognized income. Keep each posting linked to the source and the accounting period. A payment collected before the teaching service is delivered may need a different treatment from a settled receivable; the institution’s accounting policy determines that treatment.
Use separate books for distinct legal entities and a reviewed account mapping for each source type. Journals must balance in the appropriate currency before posting. Closed periods should reject ordinary edits. Correct a posted entry with an authorized reversal and replacement, retaining the original source reference. Consolidation needs reconciled intercompany balances rather than a simple sum of campus receipts.
Bring opening balances, the account structure, fee recognition policy and reconciliation reports from the current finance system. Agree whether ERP.AI owns the ledger or supplies reviewed postings to an existing accounting platform. Test duplicate posting requests and an adjustment across a closed period. Finance should approve the reconciliation before the campus team expands the pilot.
A student withdraws after an original fee charge has been posted and a partial receipt has been allocated. The operational team needs to record the withdrawal, the bursar needs to apply the institution’s adjustment policy, and finance needs to preserve the original accounting history. Those are related actions with different owners.
Create the authorized adjustment against the original charge and retain the receipt allocation. If the accounting period is already closed, follow the reviewed correction procedure rather than editing the posted journal. A refund obligation and the bank’s confirmation of an actual refund should remain separate until the payment is confirmed.
Rehearse the case with the bursar and finance manager together. The student account should explain the original charge, received money, approved adjustment and any remaining amount due or refundable. The ledger reconciliation should reach the same financial position while preserving the original source documents, posting dates and correction references.
Use the close review to investigate differences between student-account balances and ledger control accounts. Operational dashboards remain separate from statutory statements and their accounting judgments.
Review the implementation plan and the data model before preparing your import files.
Review applications and carry accepted students into the right campus, program and term.
Keep student identity, enrollment history and session attendance connected.
Connect approved fee plans, concessions, due dates, receipts and outstanding balances.
Plan teaching assignments and publish sessions without room or faculty conflicts.
Route departmental requests through the right campus and budget owner.
Reconcile student accounts and campus expenditure to reviewed financial postings.
Issue approved charges, allocate confirmed receipts and investigate the remaining balance.
4 stages · 2 approvals
Review departmental expenditure and reconcile it in the correct entity books.
4 stages · 2 approvals
Create your ERP.AI account and get started with Proto.
We use essential cookies to run the site and optional cookies for features, analytics, and relevant content. See Cookie policy
We use cookies to enhance your experience, analyze site traffic, and serve relevant content. By clicking "Accept All," you agree to our use of cookies. You can customize your preferences at any time.
Learn more about how we use cookiesThese cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
These cookies enable additional features that enhance your experience, such as live chat, video playback, personalized content recommendations, and remembering user preferences.
These cookies help us understand how visitors interact with our site by collecting anonymous usage data. This allows us to measure performance, detect issues, and continuously improve the user experience.
These cookies allow us and advertising partners, including X, to deliver ads tailored to your interests. They track browsing habits across sites to provide relevant advertising and measure ad effectiveness.