# What EduPay is and how it organises your school

> The path that connects a course to a charge, and the name the system gives each piece of that path.

## What you will get

The mental model of the system in five minutes. After that, the names in the menu
stop being abstract and you know where to look for each thing.

EduPay does one thing, from end to end: **it turns an enrollment into money in
the school's account**, with a signed contract along the way. Everything in the
system serves that line.

## The line, from course to money

```
Student  +  Course  +  Price table  →  Enrollment  →  Contract  →  Installments  →  Money
```

Each piece has its own name on screen:

| In the system | What it is, in plain words |
|---|---|
| **Students** | The person. A record with tax ID, address and contact details |
| **Academic Offerings** | What the school sells: a course, a year, a module |
| **Learning Trails** | A set of offerings sold together, like a full programme |
| **Cohorts** | The group the student will study in, with start and end dates |
| **Financial Plans** | The price table: amount, number of installments, due day, accepted payment methods |
| **Contract Templates** | The contract text, with gaps the system fills in on its own |
| **Enrollments** | What ties it all together: this student, on this course, with this price table |
| Installment | Each charge born from the enrollment |

## The three pieces you build once

This is what usually confuses newcomers: **three of these you build once and
reuse forever.**

- The **academic offering** — the course exists once, and everyone enrolls in it.
- The **financial plan** — the price table applies to every enrollment on that
  course, and you only create another when the terms genuinely change.
- The **contract template** — one text serves everyone, because the student's
  name, the amount and the dates fill themselves in on each generated contract.

What repeats for each student is only the **enrollment**. If you find yourself
recreating price tables or contracts for every new student, something is wrong.

## How to tell it worked

> [certo]
> You have the model when you can answer: "to enroll a student tomorrow, what has
> to be ready today?" The answer is: the academic offering, the price table and —
> if you want a signed contract — the contract template.

## If something goes wrong

> [erro]
> **"I created the student but cannot charge them."** A student on their own
> generates no charge. The charge is born from the enrollment, which needs a
> student plus a course plus a price table.
>
> **"I do not know whether to use an Offering or a Trail."** Start with the
> offering. Trails only make sense when you sell several offerings as a single
> package — if that is not your case, ignore them.
>
> **"Cohorts and offerings look like the same thing."** The offering is *what* is
> studied; the cohort is *with whom and when*. The same course can have three
> cohorts at different times.


---

https://edupay.estudiosite.com/en/ajuda/getting-started/what-is-edupay
2026-08-05