# Charging by bank slip: instalments and due day

> The two fields that build the student's payment book, and how the system picks the first due date.

## What you will get

A plan that produces the payment book the way your school charges. Ticking
**Bank slip** under the accepted payment methods reveals four fields — and two
of them do all the work.

![Bank-slip block on the plan form, with number of instalments and due day filled in](/Apps/edupay/ajuda/plano-formulario.png)
*The top two fields build the payment book. The bottom two, late interest and late fee, are out of this article — the reason is at the end.*

## Number of instalments

How many parts the course value is split into. It takes 1 to 255.

**The maths is simple:** course value ÷ number of instalments, rounded to cents.
A R$ 1,200.00 course in 12 parts gives twelve instalments of R$ 100.00.

**When the division is not exact, cents are left over or missing.** R$ 1,000.00
in 3 parts gives three instalments of R$ 333.33, adding up to R$ 999.99 — one
cent short of the contract. In 7 parts, seven of R$ 142.86 add up to R$ 1,000.02,
two cents over.

The system does not adjust the last instalment to close the gap. If the
difference bothers your reconciliation, pick a number of instalments that divides
the value evenly — or adjust the course value on the enrolment.

## Due day

The day of the month the instalments fall due, 1 to 31. The same for all of them.

**Short months:** with day 31, February falls due on the 28th (or 29th). The
system uses the last day of the month when the chosen day does not exist, and
returns to the 31st the following month.

## Where the first due date comes from

This is the part that surprises people. The system looks for **the first date on
or after a reference date whose day matches the due day**.

And the reference date is chosen in this order:

1. **The billing start date**, if you filled that field in on the enrolment.
2. **The cohort's start date**, if it falls after the enrolment date.
3. **The enrolment date**, if neither of the above applies.

In practice: enrol someone on 5 August under a plan with due day 10, and the
first instalment falls due on **10 August**. If the cohort only starts in
February, the first one falls due on **10 February** — which is what most schools
want, without doing anything.

## How you know it worked

> [certo]
> Make a test enrolment and look at the instalment panel: the count matches what
> you configured, all with the same amount, falling due on the same day of
> consecutive months. Then cancel the test enrolment.

## The two late fields

**Late interest rate** and **Late fee** are deliberately out of this article. The
calculation they feed does not match what the screen's labels promise, and the
matter is under review.

Meanwhile: leave both blank and, when issuing a second copy, **check the proposed
amount against your contract's rule before saving**.

## If something goes wrong

> [erro]
> **The first instalment fell due earlier than you expected.** Check the cohort's
> start date and the billing start field on the enrolment — one of the two drove
> the calculation.
>
> **The instalments do not add up to the course value.** That is the rounding
> explained above. The difference is cents.
>
> **You need different due days for the same course.** Create one plan per due
> day. It is the most common reason to have several plans.
>
> **The student wants fewer instalments.** That is a different plan, picked on the
> enrolment. A plan does not offer "1 to 12" — it has one fixed number.


---

https://edupay.estudiosite.com/en/ajuda/getting-started/charging-by-bank-slip
2026-08-05