Sixième Étoile — Documentation

Registering Payments

Record payments against invoices in Sixième Étoile — single payments, partial payments, payment methods, and automatic status updates.

Overview

When a client settles an invoice, the operator records the payment from within the Invoice Detail view. Sixième Étoile supports full payments, partial payments, and multiple successive payments against the same invoice. The invoice status updates automatically each time a payment is registered.


Opening the Payment Dialog

From the Invoice Detail (screen E-03), click Register Payment. The Payment Registration dialog (screen E-04) opens as a modal overlay.


Payment Fields

FieldRequiredDescription
Amount receivedYesThe amount paid, in euros. Must be greater than zero.
Payment methodYesSee payment methods below.
Payment dateYesDate the funds were received or cleared. Defaults to today.
ReferenceNoOptional free-text reference such as a bank transfer ID or cheque number.
NotesNoInternal note visible only to operators; not shown on the invoice PDF.

Payment Methods

MethodLabel in UITypical use case
Bank transferVirement bancaireCorporate clients, agencies
CardCarte bancaireRetail clients paying online or in person
CashEspècesOn-board cash payments
ChequeChèqueLess common; still used by some public bodies
OtherAutreDirect debit, platform escrow, or custom arrangements

Status Updates After Payment

Sixième Étoile evaluates the invoice balance after each payment is saved and updates the status automatically:

ScenarioResulting status
Amount covers the full remaining balancePAID
Amount is less than the remaining balancePARTIALLY_PAID
Invoice was OVERDUE and full balance is now coveredPAID
Invoice was OVERDUE and partial amount is receivedPARTIALLY_PAID

Once an invoice reaches PAID, no further payments can be added. If an excess amount was recorded by mistake, cancel the payment entry from the payment history section and re-register with the correct amount.


Partial Payments

Partial payments are fully supported. When a client makes an instalment payment or settles only part of the amount (for example, when disputing a line item), register the actual amount received. The invoice moves to PARTIALLY_PAID and the remaining balance is shown prominently in the detail view.

Subsequent payment registrations accumulate against the same invoice until the balance reaches zero and the status becomes PAID.

Example:

Invoice FAC-2026-0042   Total TTC: €1 200,00

Payment 1 — 2026-04-10 — Bank transfer — €600,00
  → Status: PARTIALLY_PAID   Remaining: €600,00

Payment 2 — 2026-05-05 — Bank transfer — €600,00
  → Status: PAID             Remaining: €0,00

Overpayments

If the amount entered exceeds the invoice balance, the dialog displays a warning:

Warning: The amount entered (€X) exceeds the remaining balance (€Y). Do you wish to continue?

Confirming registers the overpayment. The invoice is marked PAID and the excess appears in the payment history as a surplus. You can then:

  • Issue a credit note for the surplus amount and reimburse the client externally.
  • Apply the surplus as a deposit against a future invoice (manual reconciliation in the Finance Hub).

Payment History

The Invoice Detail view shows a chronological list of all payments registered against the invoice:

ColumnDescription
DatePayment date as recorded
AmountAmount paid in this entry
MethodPayment method used
ReferenceBank transfer ID, cheque number, etc.
Registered byOperator who recorded the payment

Each payment entry can be deleted by an operator with billing permissions as long as the invoice is not in a terminal state (PAID achieved by that very payment). Deleting a payment reverses the status change it caused.


Finance Hub Integration

All payment entries feed directly into the Finance Hub (screen LA-03, Payment Tracking view). Payments appear in the chronological payment timeline immediately after registration and are included in period KPI aggregations (collection rate, revenue recognized).


Practical Tips

  • Record payments promptly: the Finance Hub receivables aging buckets (0-30 days, 31-60 days, etc.) depend on accurate payment dates. A late entry creates misleading overdue counts.
  • Use the Reference field: always enter the bank transfer reference or cheque number. This makes reconciliation with your bank statement straightforward and reduces support queries.
  • Partial payment communication: when a client pays partially, update them on the remaining balance and the new due date before registering the partial payment so your records and theirs stay aligned.
Was this page helpful?

On this page