Free bookkeeping services agreement template
with every clause that matters.

Why it matters: Identifying a personal name when a business entity is the contracting party — or listing the wrong entity within an accounting firm — shifts liability unpredictably and may affect whether the agreement binds the intended party at all.

What Clausio checks: That both parties are identified by legal name, that any company is identified as a legal entity (LLC, Corp, etc.), and that the signatory's role and authority are stated.

Legal basis: Restatement (Second) of Contracts §§ 9, 12–17 (1981) — contract formation requires identifiable parties with legal capacity; lack of capacity renders a contract voidable. [Confidence: medium — Restatement is widely adopted persuasive authority; ALI text is paywalled]

Why it matters: "Handle our bookkeeping" can mean recording transactions, reconciling accounts, processing payroll, preparing financial statements, managing accounts payable and receivable, or all of the above — each representing very different time commitments and skill sets. Without a defined scope, every task outside the bookkeeper's mental model becomes a dispute. Courts construe ambiguous scopes against the drafter (contra proferentem).

What Clausio checks: That specific included tasks are listed (e.g., monthly bank reconciliation, accounts payable entry, payroll processing), that the frequency of deliverables is defined, and that out-of-scope services (tax preparation, audit support, CFO advisory) are explicitly excluded. Flags vague scope without itemization.

Legal basis: Restatement (Second) of Contracts §§ 201–203 (1981) — ambiguities in a standardized agreement are construed against the party who supplied the language. [Confidence: medium — Restatement persuasive authority]

Why it matters: Bookkeepers who work for multiple clients, set their own hours, use their own software, and handle their own taxes are typically independent contractors — not employees. Without a written IC classification clause documenting the key indicia of the relationship, the IRS or a state agency may reclassify the bookkeeper as an employee, triggering retroactive payroll tax liability, benefits obligations, and potential penalties for the client.

What Clausio checks: That the agreement states IC status, specifies that the bookkeeper controls their own methods and schedule, uses their own tools, and is responsible for their own taxes and insurance. Flags if IC classification language is absent.

Legal basis (high confidence): IRS Common-Law Test — three categories: (1) behavioral control, (2) financial control, (3) type of relationship. No single factor is determinative. See IRS guidance. California applies the ABC test (Lab. Code § 2750.3 / AB5), which is significantly stricter.

Why it matters: A bookkeeper has access to the most sensitive financial data a business holds: bank account details, payroll records, vendor pricing, revenue figures, and cash-flow information. This information is commercially valuable and, in the wrong hands, dangerous. A written confidentiality clause with a DTSA whistleblower notice creates a contractual cause of action that is easier to enforce than trade secret law alone, and preserves the strongest federal remedies for willful misappropriation.

What Clausio checks: That financial data is expressly defined as confidential, that the bookkeeper's obligations during and after the engagement are stated, that data is not used for any purpose beyond the engagement, and that the DTSA § 1833(b) whistleblower immunity notice is included.

Legal basis (high confidence): Defend Trade Secrets Act (DTSA), 18 U.S.C. § 1836 — federal civil cause of action for trade-secret misappropriation; remedies include injunctions and up to doubled damages for willful misappropriation. 18 U.S.C. § 1833(b) — failure to include DTSA whistleblower notice forfeits eligibility for exemplary damages and attorney's fees. Uniform Trade Secrets Act (UTSA) — adopted by 48 states and DC, providing parallel state-level protection.

Why it matters: A bookkeeper typically holds login credentials for the client's accounting software (QuickBooks, Xero), bank portals, and payroll platforms. An agreement that doesn't specify what access is granted, how credentials are handled, and what happens to access on termination creates a security gap. Unauthorized access to a business's financial accounts carries federal criminal exposure under the Computer Fraud and Abuse Act.

What Clausio checks: That the agreement specifies the scope of authorized access, credential-handling procedures (storage, no sharing with third parties), and that access will be revoked promptly on termination with all data returned or deleted. Flags if the bookkeeper has financial account access but no credential clause exists.

Legal basis: Computer Fraud and Abuse Act, 18 U.S.C. § 1030 — unauthorized access to a protected computer is a federal offense; a written access authorization clause defines the scope of authorized access and protects both parties. [Confidence: medium — CFAA scope is context-dependent; statute is high confidence]

Why it matters: Without a defined reporting schedule, a bookkeeper has no contractual obligation to deliver monthly reports by a specific date — and a client who needs financial statements for a lender or investor has no contractual basis to demand them on time. The agreement should define what reports are produced (P&L, balance sheet, cash flow), at what frequency, and when they are due.

What Clausio checks: That specific deliverables (reports, reconciliations, summaries) are listed with frequency and due dates, and that an acceptance or review period is defined. Flags if deliverables are described only as "monthly reports" without itemization.

Legal basis: Restatement (Second) of Contracts § 226 — what constitutes satisfactory performance depends on the express terms of the agreement; without defined deliverables, courts apply an uncertain "reasonable" standard. [Confidence: medium — Restatement persuasive authority]

Why it matters: Bookkeeping accuracy depends entirely on the quality of the client's source data — receipts, bank statements, invoices, payroll records. If the client provides incomplete or erroneous source data, the bookkeeper cannot produce accurate records. Without a clause allocating responsibility for data quality, the bookkeeper may be blamed for errors that originate with the client.

What Clausio checks: That the agreement specifies what the client is responsible for providing (and by when), that the bookkeeper's obligations are conditioned on receiving complete and accurate source data, and that additional charges apply if the bookkeeper must reconstruct records due to incomplete client data.

Legal basis: Restatement (Second) of Contracts § 261 — performance may be excused when a basic assumption on which the contract was made turns out to be wrong (analogous principle: a bookkeeper is not liable for inaccurate records when the client's source materials were inaccurate). [Confidence: medium — general contract principle; specific application varies by facts]

Why it matters: Bookkeeping retainers are typically billed monthly. Without clear payment terms — when invoices are sent, when payment is due, and what happens if payment is late (interest, suspension of services, termination) — the bookkeeper's recourse on a missed payment is a lawsuit. NYC freelancers on contracts over $800 also have statutory payment protections.

What Clausio checks: That the monthly fee or hourly rate, billing cycle, payment due date, late-payment consequences, and any additional-services rate are specified. Flags if payment terms are absent.

Legal basis: Restatement (Second) of Contracts § 347 — measure of damages for breach is the expectation interest. N.Y.C. Admin. Code § 20-928 — NYC Freelance Isn't Free Act applies to freelance bookkeeping engagements over $800; failure to pay triggers double damages. [Confidence: medium for Restatement; NYC statute high]

Why it matters: A bookkeeping error — an incorrect entry, a missed reconciliation, a misclassified transaction — can cascade into tax penalties, audit findings, or lender concerns that far exceed the monthly retainer. Without a liability cap, a bookkeeper faces potentially unlimited exposure for errors in records they prepared from client-provided data. A cap tied to the fees paid in the prior period is standard in professional bookkeeping agreements.

What Clausio checks: That a liability cap exists, that categories of excluded damages (indirect, consequential, tax penalties caused by third-party assessment, lost business opportunity) are specified, and that the cap is not absent for a data-sensitive financial engagement.

Legal basis (high confidence): UCC § 2-719 — parties may contractually limit or exclude consequential damages unless unconscionable; limitation of commercial consequential damages is not prima facie unconscionable. Generally enforceable in US B2B contracts; courts apply heightened scrutiny for gross negligence or willful misconduct.

Why it matters: A bookkeeping retainer with no termination clause can leave a business without access to its own financial records if the relationship ends badly. The agreement should specify a notice period, what the bookkeeper delivers at termination (final reconciliations, a data export, access credentials), and the format of records handed off — so the next bookkeeper or accountant can pick up without gaps.

What Clausio checks: That the agreement specifies a notice period, what is owed through the termination date, and what records handoff the bookkeeper must provide on termination — including data export format and credential revocation. Flags if no termination or handoff clause exists.

Legal basis: Restatement (Second) of Contracts §§ 237, 241 — a party's duty to perform is suspended when the other commits a material breach; factors for materiality include extent of deprivation and adequacy of money damages. [Confidence: medium — Restatement persuasive authority]