What we hold, and what we do with it.
Bursar reads a client’s ledger, bank and card feeds, point-of-sale and delivery data, and the documents your clients send. Here is exactly what happens to each of those.
Tenancy is enforced in the code, not in the URL.
The most common way a multi-tenant product leaks is a route that takes a firm identifier as a parameter and trusts it. Bursar does not.
- Every route is denied by default; access is granted, never assumed
- The firm a request may touch comes from the verified sign-in token, never from the path
- Sign-in is single sign-on through Google or Microsoft - Bursar stores no passwords
- Sessions are short-lived and refreshable, and a replayed refresh token revokes the whole family rather than being honoured
- Granting someone the credential that lets them sign off a close is restricted to firm administrators and partners - it is not self-service
How a request is authorized
Your client never learns Bursar exists.
Document requests and reminders go out under your firm’s name, from your firm’s reply address. Reports carry your letterhead. Bursar is not named to the client - and the professional obligation to tell your client that your firm may use a service provider is your firm’s to discharge, which is why the product models it rather than assuming it away.
Ask for what your review actually needs.
A questionnaire, a client’s diligence request, a partner’s sign-off - send it and it gets answered.