What happens to items that stay unmatched at the end of the day?
Two documented paths. Match Later parks a transaction with a reason and a comment while the missing notification is still expected, and it stays visible in the Pending queue until the data arrives. Withdraw removes a transaction from totals and from further matching when a match will never come, and it requires a dedicated permission. Both stay in the logs with timestamp, user and reason.
In detail
There are two documented paths, and each leaves a trace.
Match Later
Match Later parks a transaction with a reason and a comment while the missing notification is still expected. It stays visible in the Pending queue until the data arrives, and the cascade can then complete the match. This suits timing gaps, such as a terminal that processed offline or a provider file that lands the next day.
Withdraw
Withdraw removes a transaction from totals and from further matching when a match will never come. It requires a dedicated permission, so only authorized users can take items out of the reconciliation. Withdrawn tickets remain visible to authorized users afterward.
Both actions stay in the logs with their timestamp, user and reason. Nothing is deleted silently, and the reason recorded explains the decision to anyone who reviews the period later.
Why the distinction matters
Treating every gap the same way either inflates the exception queue or hides real problems. Separating what is late from what is final keeps the Pending queue meaningful, and gives finance teams a clear basis for closing a register. When the day ends, the Close Out summary shows matched transactions, pending matches and withdrawn tickets, so the state of each register is explicit.