Expected payments

What creates an expected payment

• A sale recorded via POS (if payment was not collected up-front).
• An invoice scanned from a supplier or manually created.
• A manual entry from the Expected Payments dashboard.

Anatomy

Each expected payment records:

• counterparty — customer or supplier name.
• expected_amount and currency.
• due_date — when the money is expected.
• source — the sale, invoice, or manual entry that created it.
• status — pending, partial, paid, overdue, or cancelled.

Matching to bank transactions

When you import a bank statement, reconciliation matches incoming deposits to the expected-payments pool. Each payment event updates the expected payment:

• If the deposit matches the full expected amount, status flips to paid.
• If the deposit is partial, status flips to partial with a running balance.
• Once the due date passes without full payment, status flips to overdue.

The Expected Payments dashboard

Dashboard → Expected Payments is your single pane for all open receivables:

• Summary cards: total outstanding, overdue, and paid this period.
• Filter by counterparty, status, source, or due-date range.
• Drill into a payment to see its source document and any matched bank transactions.
• Mark partial or manual payments when needed (e.g. off-book cash).

Exporting

Export the aged receivables list as CSV or push to Google Sheets for your accountant.

Plan access

Expected payments and reconciliation both require Pro or Enterprise.

Next steps

• Bank reconciliation — how bank deposits clear expected payments.
• Point of Sale — sales that create expected payments automatically.