Settlement checklist

Single-file API example

Not connected

The same API login as Cycles. Your bearer session is remembered until logout or expiry; your API key is never stored.

Open this example locally

Save this one file as settlement-checklist.html. In its folder run python -m http.server 8080 --bind 127.0.0.1, then open http://localhost:8080/settlement-checklist.html and choose your tenant and environment. Internet access and an updated API are required. Opening the file directly supports the demo only.

Required permissions: Checklist1 (10), Bank Read, Location Read and matching resource grants. Normal manager and tenant checks apply to every page.

Settlement control

Settlement checklist

—Read only

Review overdue bank settlements and location processing: invoices, soap invoices, soap credit notes and EasyPay. The latest period and its two numeric predecessors are included.

Not updated yet

Connect to view the checklist, or try the demo.

PeriodOrganisation / locationPeriod endsHardwareInvoiceSoap invoiceSoap creditEasyPayDetails

On small screens, scroll the table horizontally to compare all four statuses.

CompletedFailedRecreatingUnknown status is never treated as completed.
API operations and limitations

Requires Checklist1 (10), Bank Read, Location Read and matching grants. A location grant includes only that location, never the bank-wide row. Disabled or retention-hidden resources are excluded. Missing enabled settings default to enabled; invalid values are excluded. Banks below 1000 are excluded.

Status codes: 0 Waiting, 1 Created, 3 Completed, 8 Failed, 16 Recreating, 32 No data, 64 Not required. Unknown codes remain visible. Bank rows show the next settlement schedule; missing dates remain unknown. Details use the stored UTC period boundary.

This example is read-only. It does not restart jobs, recreate invoices or hide periods. Print shows the selected detail locally. Cursors expire after 15 minutes; refresh the first page if they expire or source data changes.