What we do with your data, and what we do not claim.
Docket AP will hold supplier invoices and a connection to your accounts. This page says how it is designed to look after them, and is just as plain about what is not in place yet.
Docket AP is in development. Everything under “By design” is how the first release is being built. Everything under “Planned” does not exist yet. We will update this page as each item ships, and before anyone’s live data is in the system.
What the first release is built with.
- Stored in Australia
- The application, its database and your stored invoice files are in Australia (Google Cloud, Sydney region). Some processing happens elsewhere; the list is below.
- Sign-in with Google or Microsoft
- Your team signs in with the work accounts they already have, so Docket AP does not keep its own passwords for them, and your existing sign-in rules, such as two-step verification, apply.
- Role-based access
- Four roles: Admin, AP clerk, Approver and Read-only auditor. People see and do only what their role allows.
- Audit log
- Each action on a bill is recorded with who did it and when: received, edited, sent for approval, approved, declined, exported. The record is written together with the action itself, so one cannot happen without the other.
Also part of the design
These follow from how the product is being built. We will confirm each one here when the first release is ready.
- MYOB connection without a password
- You connect by signing in to MYOB and approving access. Docket AP does not ask for or store a company-file username and password. The access tokens MYOB issues are stored encrypted.
- One place that writes to MYOB
- Only the export of an approved bill writes to your company file. Nothing else in the product can change your ledger.
- Signed approval links
- The approve links in emails are signed and expire. For amounts above a limit you set, the approver has to sign in first.
- Each customer’s data kept apart
- Every record belongs to one organisation, and that is enforced twice: in the application and again in the database itself.
- Private file storage
- Invoice PDFs are stored privately and served through short-lived links to signed-in users, not public URLs.
Where an AI model is used, and where it is not.
An AI model reads each invoice: it turns the page into fields. It does not decide whether a bill is paid. Arithmetic, duplicate matching and bank-detail comparison are done by ordinary code, and a person approves every bill unless a rule you wrote says otherwise.
Reading an invoice means sending it to an AI model. That model runs on Google Cloud in the United States, not in Australia; see the list below.
What is processed or held overseas.
Your records are stored in Sydney. These parts of the service run elsewhere, and you should know which before you send us an invoice.
- Invoice reading
- Each invoice is sent to an AI model running on Google Cloud in the United States, read, and the result stored back in Sydney. No AI model we use is offered from an Australian region there.
- Invoices you forward, and the approval emails we send, pass through an email provider in the United States, which keeps a copy of each message for a limited time. The invoice itself is filed in Sydney.
- Sign-in
- Sign-in is handled by a Google service that runs in the United States. It holds names, email addresses and sign-in records, not invoices.
- Error monitoring and usage analytics
- These tools also run outside Australia. They are being set up so that invoice contents, supplier names and amounts are not sent to them.
The full list of sub-processors, by name, will be published here before launch.
Not in place yet.
You will be asked about these by your own auditors, so here is the straight answer.
- Security certification Later
- Docket AP holds no security certification today: not ISO 27001, not SOC 2, nor any other. Independent certification is planned. We will not describe ourselves as certified or compliant until an auditor has said so.
- SAML single sign-on Later
- Sign-in through your own identity provider. Google and Microsoft sign-in come first.
- Bank-detail change control Coming
- A second person must confirm a supplier’s changed bank details. In the first release a change is detected and the bill is held; see checks.
- Sub-processor list and data processing terms
- To be published before launch, along with the final privacy policy and terms.
- Retention and deletion
- How long invoices are kept, and how you export or delete your data when you leave, will be set out in the terms before launch. Australian and New Zealand record-keeping rules will shape the defaults.
- Independent penetration test
- Planned before general availability. We will say here when it has been done and by whom.
Questions your IT or audit team will ask
If you have a security questionnaire or a specific requirement, mention it in the early access form. Knowing what mid-sized finance teams are actually asked for helps us put the right things first.
Be one of the first to use it.
Docket AP is in development. We’re opening early access to a small group of businesses on MYOB AccountRight. Tell us a little about your accounts payable and we’ll be in touch.