Skip to main content
Each row is one sub-account / instalment / line item under a Borrower Account. It’s used by lenders whose accounts split into discrete obligations (for example, BNPL instalment plans).

Fields

Sample row

Date formats differ by field. submitted_date and due_date are returned exactly as stored — DD/MM/YYYY strings (e.g. 15/06/2026), not ISO-8601. The system timestamps created_at / updated_at are ISO-8601. See Date & time formats.

Pagination characteristics

This dataset is via — it is filtered to your tenant by joining through its parent (borrower_account_idBorrowerAccounts). On multi-tenant databases a single response may contain fewer rows than your limit even when more data exists. The cursor still advances correctly — keep paging until nextCursor is null. See Pagination → Variable page size.
This is the highest-volume via dataset (millions of rows per multi-tenant DB). For interactive use, always pass a since window to bound the scan. A time window is also required when using ?includeTotal=true.

Use cases

  • Instalment-level balance trail.
  • Per-plan reconciliation against payments.
  • Delinquency-bucket movement over time.

Need Help?

Our support team is available Monday-Friday, 9 AM - 6 PM GST. Reach out at support@cleargrid.co or visit our help center.