Construction payment tracking and bank matching

Payments record the money that actually arrived, which is a different question from what was billed. Each receipt shows its date, amount, the invoice number it settles, the project behind that invoice, the method used — transfer, SEPA direct debit or card — and the bank reference the statement carried. Newest receipts sit at the top, the footer sums the visible rows, and the metric band counts anything still unassigned.

Bank import reads pasted statement lines or a CSV file with date, amount, payer and reference, skipping and counting rows it cannot parse. Nothing posts by itself: the software proposes an invoice when its number appears in the reference or when the amount matches an open balance exactly, and a person confirms or ignores every line. Checks and cash are entered directly, with the invoice locked for the duration of the write.

A confirmed match reduces the open amount of the invoice in one transaction: a full settlement flips it to paid with the value date, a partial payment leaves the rest open and still exposed to the next dunning run. Ignored rows change no invoice at all, which is what direct debits need. The invoice detail then lists every receipt against it including the discount note, and the whole log exports as CSV.