Frequently asked questions

Yes. Clark is available in the United States for audit and accounting teams.

An EBP audit is a check of an employee benefit plan's financial reports and supporting records. An independent auditor checks whether the reports fairly show the plan's finances under the accounting rules that apply, then gives an opinion. It looks at the plan's finances, rather than the employer's own finances.

Month-end close means finishing and checking the books for the month. The team records anything missing, checks account balances against bank statements and other records, and makes any needed corrections. This helps the business prepare reliable financial reports for the month.

Different audits check different things. Financial statement audits check whether financial reports fairly show the finances. Compliance audits check whether rules are being followed. Operational audits look at how well the work gets done, while IT audits check technology systems and their safeguards. Internal and external describe who does the audit and their relationship to the business. An employee benefit plan audit focuses on a benefit plan's financial reports.

Clark connects client requests, evidence, procedures, workpapers, review, and sign-off in one engagement record. Your team sets the methodology and review process. Ava, the AI teammate inside Clark, prepares work with supporting evidence attached so reviewers can follow it from source to conclusion.

Yes. Clark's Excel Add-in works beside your existing formulas, schedules, and workbook structure. Teams can extract data, prepare reconciliations and workpapers, and trace figures to source documents. Audit teams can also select samples and test evidence within Excel.

Your firm's methodology sets how the work is done. Firm-approved templates define procedures, workpapers, dependencies, and review steps. Ava follows the methodologies and instructions your team provides, while your people retain responsibility for review and sign-off.

Clark supports both audit and accounting work. Accounting workflows include cash and bank reconciliations, rollforwards, lead sheets, variance analysis, and financial statement tie-outs. Audit teams can also use it for population extraction, sampling, substantive testing, and supporting workpaper preparation.

Clark connects with SharePoint, Box, Google Drive, QuickBooks, Slack, and Excel. Ava can communicate through Slack, Microsoft Teams, or email. Bring your system list and the workflows you want to connect to the demo so the team can confirm the integration details for your deployment.

Bring a workflow you want to improve, the systems your team uses, and the review requirements the finished work must meet. For example, walk through a reconciliation or a sample-testing procedure from source documents to reviewer sign-off. That gives your firm a concrete way to assess how Clark would fit its work.

No. Firm and client data in the Clark product is not used to train models or shared for model learning across firms. Hosting, subprocessors, and the data handling that applies to your deployment are covered separately in the security review.

Request Clark's SOC 1 Type 2 and SOC 2 Type 2 reports and ISO/IEC 27001 certificate. Your team can also submit its own security questionnaire. Review the documents' scope and reporting periods alongside your requirements for hosting, encryption, data residency, subprocessors, and retention.

Roles and permissions determine who can prepare, review, approve, and sign off on work. Define who needs access to each engagement and who has approval authority. Confirm those access boundaries and administrator permissions during the deployment review.

Identity-provider support and SSO configuration are confirmed before rollout. Share your provider, sign-in policies, and multifactor authentication requirements so the Clark team can confirm the supported setup for your deployment.

Account provisioning, role changes, and access removal are covered in the deployment review. Confirm who manages each step and how the process fits your firm's offboarding procedures, including changes to engagement access when responsibilities change.

The subprocessors that apply to your deployment are documented during the security review. Request that information alongside hosting and processing locations so your team can assess which providers handle client information and how they fit your firm's vendor requirements.

Yes. Approvals and sign-off are recorded in the engagement workflow. Confirm which additional events are captured, how long records are retained, and what can be exported during your review. Engagement review records and the security logs your IT team requires should be assessed separately.

Clark supports HIPAA and GDPR requirements through security, privacy, access, and data-handling controls. Confirm the safeguards, processing roles, data locations, and supporting agreements that apply to your firm's use. Review these details for the information your deployment will handle.

Export and exit terms need to be confirmed with the Clark team before rollout. Establish which records and supporting evidence can be exported, the available formats, and how remaining data will be retained or deleted. These details should be reviewed alongside your firm's recordkeeping requirements.