REDA One Help Center
EN
Language
English EN Español ES Português PT Italiano coming soon Français FR Deutsch coming soon العربية coming soon
reda.one ↗
Home / REDA One / Lending / Lending / The Loan Repayment Schedule

The Loan Repayment Schedule

If you've come here looking for where REDA generates your amortization schedule, here's the honest answer up front: it doesn't. REDA does not build a repayment schedule from a loan's terms. Instead, a loan's schedule is the set of Loan Payment "Payment Due" rows you create — each a planned instalment with its own due date and the principal-and-interest split you calculate — and each counts only once you mark it completed. This article shows you how to lay a schedule out that way, how to read it, and why the balance only moves on completion. The mechanics and every validation for an individual payment are in the companion article Recording Loan Payments; here we take the schedule-level view. No prior REDA experience is assumed.

Getting there. Open the App Launcher (the grid icon at the top-left of any page) → REDA → the Opportunities tab, open the loan, and find the Loan Payments related list. Its rows, in due-date order, are the schedule. Click New to add an instalment.
Access you'll need. Recording and completing loan payments requires the REDA - Property Lending User permission set.

There is no auto-generated schedule

This is the core teaching, so we'll be direct. Entering an Interest Rate, an Amortize method, a Frequency, and an Interest Accrual Type on a loan does not cause REDA to lay out a schedule of instalments. There is no amortization engine in REDA. The only automation on a loan is system bookkeeping — flags, the auto-generated name, keeping the property in step, and rolling up totals.

So the schedule is something you build: a series of Loan Payment rows, each with the type Payment Due, ordered by Due Date. You compute each instalment; REDA records it. That's the model.

Don't confuse this with a "Payment Schedule." REDA does have records called Payment Schedule — but they belong to property sales, not loans. They're generated from a sale's payment plan when the sale activates, and their parent is the sale deal. A loan never generates Payment Schedule records. If you've seen the term elsewhere in REDA, it's a sales feature; your loan's schedule is the Loan Payment rows described here.

Building the schedule

Each instalment is one Loan Payment row of type Payment Due. From the loan's Loan Payments related list, click New, and:

Set the Payment Type to Payment Due. A repayment going out. (The other value, Principal Received, is for the lender funding you — see the next section.)
Enter the split you calculated. Put the principal portion in Principal Amount and the interest portion in Interest Amount — the interest you worked out, since REDA computes none. For an interest-only instalment, enter 0 in Principal Amount; for a principal-only one, enter 0 in Interest Amount. Enter the zero explicitly — a blank interest field is rejected.
Set the Due Date. This is the planned date, and it's how the schedule orders itself. It's required on a Payment Due row.
Save, and repeat. Each saved row joins the schedule as a plan. Add one per instalment across the term. None of them moves a balance yet.

Leave out the interest or the due date, and REDA names what's missing:

"Interest Amount must be provided for Loan Payment."
"Due Date must be provided for Loan Payment."

The funding receipt versus the instalments

The schedule of repayments is one side of the loan; the money the lender puts in is the other. Record the funding as a single Principal Received row — Principal Amount equal to the sum received, Interest Amount left blank (interest has no place on incoming principal), and a Payment Date entered up front. Everything after that — the repayments — are the Payment Due rows of your schedule.

Once completed, a Principal Received row raises the loan's Received Principal Amount (capped at the Loan Amount), while completed Payment Due rows raise Paid Principal Amount and Paid Interest Amount.

Reading the schedule

The Loan Payments related list, ordered by Due Date, is the schedule. Reading it comes down to one distinction: a row that is not completed is just a plan — a due date and some amounts — and moves no balance; a completed row has actually happened and counts. Here's what each column tells you:

ColumnWhat it means
Payment TypePayment Due (a repayment) or Principal Received (funding in)
Due DateThe planned instalment date — the schedule's running order
Principal Amount / Interest AmountThe split you computed
Total AmountPrincipal + Interest (computed)
Is CompletedWhether the instalment has actually happened — the gate
Payment Date / Payment ReferenceThe actual date and reference, required to complete

Completing an instalment counts it

An instalment moves the loan's balances only when you check Is Completed on its row — and that requires a Payment Date and a Payment Reference. So the schedule is a living thing: you build it as a plan, then tick each row off as instalments are paid. Miss a requirement and completion is blocked:

"Please provide Payment Reference."
"Please provide Payment Date to complete the payment."
"The Payment Date must be provided to complete the loan payment for the lending."

Before ticking Is Completed, check: the Payment Date is in, the Payment Reference is in, the Due Date and Interest Amount are already present (0 if interest-free), and any funding receipt stays within the Loan Amount cap. On save, the completed row rolls up to the loan's Paid Interest, Paid Principal, or Received Principal, and the computed Loan Principal Balance and Running Escrow move — as detailed in Escrow & Principal Balances and Property & Acquisition Loan Rollups.

Worked example: an interest-only schedule

Take the 500,000.00 loan on Harbour Tower — Interest Rate 9.000%, Frequency Monthly, Amortize Interest Only. The monthly interest is 500,000.00 × 9% ÷ 12 = 3,750.00 — a figure you calculate, because REDA computes none.

Record the funding. A Principal Received row, Principal 500,000.00, Payment Date on funding day, completed with a reference → Received Principal 500,000.00; Loan Principal Balance 500,000.00.
Build the schedule. Create twelve Payment Due rows, each Principal 0, Interest 3,750.00, with successive monthly Due Dates. (Enter the 0 principal explicitly.) These sit as a plan; no balance moves.
Complete each month. When an instalment is paid, tick Is Completed on that row with its Payment Date and Reference → Paid Interest grows by 3,750.00 per completed row; the principal balance is unchanged (it's interest-only). If you forget the reference or date, you'll meet the completion validations above.
Add a curtailment. A Payment Due row with Principal 50,000.00, Interest 0, completed → Paid Principal 50,000.00; Loan Principal Balance 450,000.00.
The Loan Payments related list on the loan, listing each payment row
The Loan Payments related list on the Harbour Tower loan (Stage Funded) — each row carries its Loan Payment #, Payment Date, Payment Type and Payment Reference, building up the schedule of activity against the loan.
A single Loan Payment record showing its fields
A single Loan Payment record. This one is a completed Principal Received row — Principal Amount 50,000.00, a Payment Date and Payment Reference, and Is Completed ticked — the state that lets its amount roll up to the loan's balances.

Reference: rows and rules

The two payment types side by side:

Payment Due (a repayment)Principal Received (funding in)
DirectionA repayment going outPrincipal the lender sends in
Principal AmountRequired (0 allowed)Required
Interest AmountRequired (enter 0 explicitly)Must stay blank
Due DateRequiredOptional
Payment DateRequired to completeRequired up front
Counts towardPaid Principal + Paid Interest (once completed)Received Principal (once completed)

The checks you may meet while building or completing the schedule, quoted exactly:

WhenMessage
Payment Due without an interest amount"Interest Amount must be provided for Loan Payment."
Payment Due without a due date"Due Date must be provided for Loan Payment."
Completing without a reference"Please provide Payment Reference."
Completing without a payment date"Please provide Payment Date to complete the payment."
Completing a Payment Due without a payment date"The Payment Date must be provided to complete the loan payment for the lending."

Where to go next

  1. Recording Loan Payments — the mechanics of a single payment, with all seven validations.
  2. Loan Terms & Allocation — the terms this schedule reflects.
  3. Escrow & Principal Balances — how completed rows move the loan's balances.
  4. Property & Acquisition Loan Rollups — where completed rows surface on the property.
  5. Disbursements & Payoffs — payoffs (retiring a loan) versus payments.

Frequently asked questions

REDA doesn't generate one. You build the schedule yourself as Payment Due rows — one per instalment, each with a Due Date and the principal-and-interest split you compute. The terms fields document the agreement; they don't drive a calculator.

No. Payment Schedules belong to property sales — they're generated from a sale's payment plan and parented to the sale deal. Loans don't generate them; your loan's schedule is its Loan Payment rows.

They aren't completed. A saved-but-not-completed row is only a plan. Tick Is Completed — which needs a Payment Date and a Payment Reference — to make an instalment count.

A Payment Due row requires the interest field, so a principal-only instalment still needs a value there — enter 0. Blank is rejected: "Interest Amount must be provided for Loan Payment."

With a Principal Received row: the amount in Principal Amount, Interest Amount left blank, and a Payment Date entered up front. See Recording Loan Payments.

No. You calculate each instalment's interest and enter it. REDA records what you enter and rolls it up; it does no interest math itself.

Was this article helpful?