The question is never only what you billed.
It is what you sent, when you sent it, and to whom. A joint interest audit, a partner dispute, and an owner-relations call are all the same request for the same record — and that record either exists or it does not.
Who was sent what
Every statement is tied to the owner it was produced for and the run it came from. Not a folder of PDFs — a record with an owner on it.
When it left
Each send is timestamped at the moment it goes out, along with the address it went to and the result the mail server returned.
Whether it was opened
Opens and portal views are recorded against the owner, which is also how repeat non-openers get routed back to paper before they become a problem.
What was re-sent
Re-sends are logged as their own events rather than overwriting the original, so the history of a disputed period stays intact.
What consent exists
Electronic delivery consent is stored against the owner with the date it was given. Owners without it keep receiving paper.
What changed since last period
Run-over-run comparison for the period in question, so a partner's question about a movement can be answered with the movement.
Owner-scoped access
An owner sees their own statements and nothing else. Access is scoped to the owner record, not to a shared folder or a guessable link.
Encrypted in transit and at rest
Statements and owner data are encrypted on the wire and in storage. Statements are documents about people's money; they are treated that way.
Your data stays yours
Operator and owner data is used to run your statements. It is not sold, shared between operators, or used to build a mailing list.
Cloud or onsite
Run DropJib as a managed service, or install it inside your own network so statements and owner data never leave your infrastructure. The workflow is identical.
Cloud managed
DropJib runs the service. You drop the run and release the send. Updates, deliverability, and the portal are handled for you, and there is nothing for your IT to stand up.
Onsite
DropJib is installed inside your own network. Statements, owner records, and the delivery log stay on your infrastructure, under your controls, subject to your retention policy. The workflow does not change.
Working through a vendor security review or a specific control requirement? Tell us what your questionnaire asks for and we will answer it directly rather than pointing at a badge.
Ask us the hard version of the question.
Bring the audit scenario, the retention requirement, or the security review you are actually facing. We would rather answer it before you commit than after.
Drop. Jib. Done.