Match, manually resolve or ignore a transaction
Verify the actual transaction and target ledger entry before confirming a suggested or manual match.
Before you start
Verify the actual transaction and target ledger entry before confirming a suggested or manual match.
Follow these steps
- Open the staged batch and inspect the suggested ledger reference.
- If the suggestion is wrong or absent, use the visible ledger candidates to identify the intended Ledger ID.
- Check property, tenant, type, amount and direction yourself before choosing Match.
- For an intentionally excluded transaction, choose Ignore after reviewing its reason.
- Reopen the batch and inspect matched/ignored state and the resulting ledger entry.
Check it worked
A rent credit creates a source-linked receipt and allocates through the current-tenant oldest-first process. Other matches mark the selected ledger entry paid.
If something does not look right
Manual matching does not enforce every business equivalence between the transaction and the entry. It is not a partial-payment editor for costs. Do not match a historical tenant’s charge through the current-tenant receipt path without an approved correction process.
Questions and answers
Is confirming the same rent row repeat-safe?
The reconciliation source-row identity prevents creation of another rent receipt for that same source row. Re-uploading the CSV creates a different batch and is not the same identity.
Can I undo an ignored or matched row on this screen?
The current controls do not expose an undo. Ask the authorised finance team to correct the operational records through a supported process.
Why can I not see someone else’s batch?
Delegated finance/property scope can restrict batches, suggestions and matches.