Turning Silence Into Proof

A firm sends an invoice and calls the matter handled. Three separate claims hide inside that single act, and each can fail on its own.

• Sent means a message left your system. It says nothing about arrival.
• Received means it reached the other side. It says nothing about attention.
• Read means someone opened it and looked at it.

The gap between the three is where disputes live. A client who owes money has every reason to let them blur, then to assert the weakest reading: I never saw it. Silence is not receipt. Without a record, silence becomes whatever the other party later says it was.

Two events turn assumption into evidence. The first is passive: the moment a client first opens an invoice, logged the instant it happens, with no action required of them. The second is deliberate: a press of Acknowledge Receipt, an affirmative act with a name and a time attached to it.

The distinction matters. A view timestamp answers whether the document was opened. An acknowledgment answers whether the client accepted that it arrived. One is observation, the other is admission. In a dispute the admission is worth more, because the client made it against interest.

Mersal records both the first view and the Acknowledge Receipt press server side, and presents them in the portal in the client's own language.

Consider a fee dispute six months on. The client says the statement never reached them, so the window to object never opened. Many billing regimes give a client a fixed period to contest an invoice, and that clock starts on delivery. Delivery is precisely the fact in question.

A view timestamp and an acknowledgment close that question before it opens. The same record answers a notice argument: a deadline communicated, a filing shared, a status update delivered. The event is dated, attributed and fixed. A record removes the client's discretion to remember it differently, because characterization is what a record replaces.