A refund is requested, voted on and approved by different people
Who is involved
| Role | What they do |
|---|---|
| LMS operator | Raises the refund request for a payment. |
| LMS examiner | Casts one of the required approvals when the policy asks for it. |
| LMS manager | Approves or rejects the refund and processes it. |
Step by step
- LMS operator
Requests a refund for a payment with an amount, a reason type and a written reason, through the application programming interface (API).
What they see:The request is pending. If the matching policy needs a second person, an approval request opens with its expiry time; if the policy needs none it is approved at once.
- LMS examiner
Opens the approval requests through the AI Copilot or the API and approves with a comment.
What they see:The vote count rises; when the policy's number of different approvers is reached the approval request is resolved as approved.
- LMS manager
Approves the refund, or rejects it.
What they see:The refund shows Approved or Rejected and an audit entry names the manager.
- LMS manager
Processes the approved refund.
What they see:The refund is Refunded and the original payment is marked refunded.
- System
Tells Accounting about the refund when tax invoicing is on for the centre's branch.
What they see:Accounting issues a credit note and a refund payment for the original sale.
Who is told what
No alert is sent when a refund or an approval is waiting; approvers find it by opening the approval requests or asking the Copilot. The approval request and the refund are two linked records, and the manager approves the refund itself.
Related
- Learning & Certification (LMS)
- Accounting & E-Invoicing
- An employee shares a skills passport with a recruiter
- HR assigns a course and the employee completes it
- A candidate is registered, called in, tested and certified
- Finishing a course or earning a certificate earns a badge
- Learners are your employees
- Team workflows