Real humans, on your calendar.
Two ways to get help: file a ticket, or book a 30-minute video call. A person handles both — and that person has personally built or debugged the connector you are asking about.
File a ticket
Write to us and it lands with a human, not a queue. Replies land in your inbox, where you can find them later.
Honestly, “ticket” is a fancy word for an email we actually answer.
Existing customers can also call 1-628-888-6331.
Book a video call
A 30-minute videoconference with someone who knows the product. Good for connector coverage, a stubborn portal, or walking a new bookkeeper through a first close.
Pick a slot that suits you; the scheduling calendar is right below.
Not a customer yet?
Pricing, multi-entity rollouts, custom connectors, and firm reseller terms go to sales, not support: sales@statementkeep.com or 1-628-888-6331. The Enterprise tier is quoted on a call.
Pick a slot.
Choose a time on the calendar and you will get a confirmation with the videoconference link.
How a review works.
Sometimes helping means looking at something of yours. That access is yours to give, scoped to what you granted, and on a timer you chose. Here is the whole sequence.
1
You book a call and we join it
Pick a slot on the calendar above. At the appointed time, a person from StatementKeep is on the videoconference with you and whoever on your team owns the close.
2
You grant access, if we need it
If we need to see anything of yours, you grant access to exactly that item, from your browser. Access starts when you grant it, typically right at the start of the call, and never before.
3
The clock starts
Access runs for the review window you picked: 24 hours, 3 days, 7 days, or 30 days. The timer starts at the grant, not at the booking.
4
It ends on its own
Access expires when the window does, or you revoke it sooner. Either way, every view was logged while it lasted.
Support sees only what you granted, for only as long as you granted it. The full security story
Frequently asked questions.
How does StatementKeep log in to our accounts?
You store each portal’s credentials once; they are encrypted and kept in your per-customer vault. When a run starts, our automation signs in, navigates to the statement page, and downloads the monthly PDF. The same steps your bookkeeper would take, done for you.
Are our credentials and statements safe?
Credentials are never stored in plain text. They are sealed in an encrypted vault, and statements are encrypted at rest with per-customer keys and in flight over TLS. Statements stay encrypted until someone on your team downloads them.
What happens when a bank asks for a verification code?
If a portal challenges the login with a one-time code, StatementKeep pauses and prompts you in the dashboard. Enter the code and the download continues. Nothing is skipped silently, and we never claim a code was sent unless the portal confirmed sending it.
What do we get back for the close?
The original PDF statement, plus a machine-readable CSV produced by OCR, ready for import into QuickBooks. The PDF stays filed as the audit trail behind the beginning balance, ending balance, and statement date your controller reconciles against. Download items individually or as a ZIP.
How far back can statements go?
Up to 12 months per account, as far back as the portal still offers. Most portals only surface the last 6 to 8 months, so the sooner an account is connected, the more history the archive holds.
Can our accountant or bookkeeping firm get access?
Yes, and accountant seats are free. Invite them from the Team page with a read-only role. They can browse statements and exports but never see your stored credentials, and you can revoke access at any time.
We run several entities. Does that work?
That is the case we were built for: one owner, dozens of accounts, several businesses, one archive. Accounts are grouped by entity so each set of books reconciles against its own statements.
What is a sign-in recording?
To learn how to sign in to an account for you, we ask you to sign in to it yourself, twice, in a secure browser, and we record each sign-in. For each screen, a recording holds a picture of the screen, a description of the buttons and boxes on it, a cleaned copy of the page’s code, and where you clicked. For what you typed, it holds only how many characters you typed and how quickly, never the characters themselves. Before anything is saved, every text box in every picture is blacked out, whether or not you typed in it, and so is any text with four or more digits in a row. In the descriptions, every run of four or more digits is replaced with dots, and every email address is masked. In the page code, every run of four or more digits is replaced with dots, and the values of form fields and the contents of inline scripts are removed. The sign-in automation we build from it is code for that institution, so it can also sign in for other customers who use the same institution. Your recordings themselves are never shown to another customer.
Who can see our sign-in recordings?
Three AI agents read recordings: a scout, an author and a supervisor, which together build and check the sign-in for your account. Each gets its own access to one account’s recordings for one run, and that access expires within 24 hours. Our support staff cannot open a recording unless you give one named support person access, for one support ticket, for 24 hours at most. Being on staff opens nothing by itself. On a team, admins who manage accounts can view recordings; read-only members see only small previews. The automation that fetches your statements never reads a recording. Every read of a recording is written to an access log. Recordings are processed by our AI providers, with personal information masked first: what you typed is never recorded, and text boxes and long numbers are blacked out before a recording is saved. Only the masked version of a recording is ever sent. A picture can still show other things on the screen, such as your name on a welcome page. The pictures, descriptions and page code in each recording are encrypted with that recording’s own key, and that key is locked with your account’s own encryption key in our secrets vault, so one customer’s recordings are cryptographically separate from another’s. Click positions and typing counts, which contain nothing you typed, are stored without that extra layer of encryption.
How long do you keep sign-in recordings?
We keep the current recording for each account until you finish recording that account again, remove the account, or delete your StatementKeep account. When you finish recording an account again, we delete the recording it replaces 30 days later. A recording you start but do not finish is kept until you remove the account or delete your StatementKeep account. When you delete your StatementKeep account, we delete all of your recordings with it and destroy the encryption key that protected them. We keep the access log for as long as you have your account, plus 1 year after you delete it, and then delete it. The log says who read a recording and when; it holds no pictures and nothing you typed.
Stuck mid-close? That’s what we’re for.
Send a note, book a call, or ring the line. Either way, a person answers.