Read-only by default
Propacc works on an imported copy of your prelim. Your production ERP is never connected to or changed during review. There's no path by which the engine writes to your books on its own.
Security & trust
Your financial data, handled the way you’d want it handled.
Property accounting data is sensitive. Here’s exactly how Propacc treats it.
How your data moves
The only write path to your books runs through you. The engine reviews a copy; it never posts.
Your ERP
fair copyUntouched during review. Behind your own access controls.
import a copy
Propacc
read-onlyRough copy. Review, test, draft — zero risk to production.
you approve & export
Your ERP
you postYou upload the clean, approved JE file. The engine never does.
Nothing posts without your approval
The only thing that ever reaches your system of record is a journal entry file you reviewed, approved, and exported yourself. You upload it. Propacc never does.
A full trail of every decision
Every flag the engine raises, and how it was resolved, is recorded — so the work is reviewable and auditable, not a black box.
Safer than sharing a login
An imported, read-only copy is structurally safer than handing anyone your live ERP credentials. The system of record stays behind your own access controls.
Where your data lives
We document storage location, encryption at rest and in transit, access controls, and our retention and deletion policy as part of diligence. Ask us for the current details and we’ll walk you through them directly.
Certifications & posture
We’ll be straight about where our formal security posture stands rather than claim a certification we don’t hold. If a specific framework matters to your diligence, ask and we’ll tell you exactly where it is.