Use case
RDOC# for Billing
Extrajudicial notification needs one thing: proof. RDOC# generates this proof automatically, from sending to the IP of the person who read it.
Why charge for RDOC#
Extrajudicial collection is a common step before legal action. But the biggest pain for those who collect is not the unpaid bill — it is proving, later, that the debtor was notified. SMS disappears, email goes to spam, call has no record. RDOC# delivers notification with timestamp, IP and audit PDF.
Each charge becomes a notification on the panel. You can track in real time who viewed, who ignored, who requested contact. When it comes time for legal action, the audit PDF goes directly into the petition as proof of a formal collection attempt.
Common billing scenarios
- Extrajudicial notification — Before protesting, check that the debtor has been formally notified.
- Notice of condominium default — notify the condominium owner with individual proof.
- Collection of school fees — proof that the person responsible was notified before blocking access.
- Notification of breach of contract — formal evidence using the contact email registered in the contract.
What goes in the audit PDF
- ✓ Exact notification text
- ✓ Unique link per recipient (access hash)
- ✓ Send date and time + sender's name
- ✓ Recipient address (registered email)
- ✓ Status: sent / read / signed / no response
- ✓ Individual viewing and signature timestamp