Kapta · 15/09/2026
Separate the student, payer and purchased service. In an academy, a session may be included in a programme or purchased individually; the integration should reflect that model.
What Mentorflow workflow does Kapta describe?
The catalog describes a connection between students, sessions, payments and invoicing. Start by confirming the data and access available in the account using an operational example. Mentorflow integration.
Should session attendance issue an invoice?
Only where it matches the agreed rule for that sale. If a student has paid for a full programme, each attendance should not automatically invoice the programme again. List individual sessions, packs and memberships separately.
What if a company pays for several students?
Use the company as the billing entity where that matches the agreement and keep students associated with the service. The attendee may differ from the document recipient. Confirm details before issue.
How do I start with Kapta?
Prepare a programme purchase, individual session and cancellation. Identify the invoicing software and expected result for each case. This assessment confirms scope before automating data transfer.
