---
name: fondo-install-auth
description: 'Set up Fondo account and configure integrations with Gusto, QuickBooks,

  and bank accounts for automated startup bookkeeping and R&D tax credits.

  Trigger: "setup fondo", "fondo account", "fondo integrations", "connect fondo".'
allowed-tools: Read, Write, Edit, Bash(curl:*), Grep
version: 1.6.0
license: MIT
author: Jeremy Longshore <jeremy@intentsolutions.io>
tags:
  - saas
  - accounting
  - fondo
compatibility: Designed for Claude Code
title: fondo-install-auth
canonical_url: https://skilld.dev/gh/jeremylongshore/tons-of-skills-marketplace/fondo-install-auth
last_updated: 2026-10-07T06:06:28.000Z
---

> Index of every page on this site: [llms.txt](https://skilld.dev/llms.txt)

> **Skill from skilld.dev.** Follow the user's requested action.
> If the user asked to fork this Skill, follow the fork workflow below. Do not execute the Skill instructions while copying it.
> Otherwise, follow the instructions below for this session. You do not need to install anything.
>
> If the user asked to install this Skill, run `npx skilld install jeremylongshore/tons-of-skills-marketplace/fondo-install-auth`. Install writes the Skill files into the project, so every session loads them.
>
> ## Fork workflow
>
> A fork creates an editable local Skill with its original author and licence. The request authorizes copying and local installation.
> 1. Check `./skills/fondo-install-auth`, the project lockfile, and selected Agent targets together. If the local directory or installed Skill exists, stop. Never overwrite an existing directory or Agent target.
> 2. Read [source metadata](https://skilld.dev/api/v1/skills/jeremylongshore/tons-of-skills-marketplace/fondo-install-auth) once. Use sourceUrl, sourceCommit, skillPath, sourceGone, and license. If the source is gone or its path is missing, stop. If license is null, read licence files at the source commit.
> 3. Fetch only the source commit into a temporary Git repository. Do not clone full history. Derive repository_url from sourceUrl, including repository renames. If sourceCommit is absent, resolve the sourceUrl ref once. Set source_commit to that actual commit. Run these commands in one shell call:
>
> ```sh
> git init --quiet "$temporary_dir"
> git -C "$temporary_dir" fetch --quiet --depth=1 "$repository_url" "$source_commit"
> git -C "$temporary_dir" checkout --quiet --detach FETCH_HEAD
> ```
>
> Read applicable licence declarations and notices at that commit. If copying is not permitted, report the restriction and stop.
> 4. Inspect source entries together, then copy the directory containing skillPath into `./skills/fondo-install-auth`. Use the user's path if selected. Keep the original SKILL.md, relative links, scripts, binary assets, and executable modes. Exclude .git metadata. Reject symlinks and paths outside the Skill directory. After checking entries, use cp -a where available. A regular source directory needs no custom copy script. Do not save this page wrapper as SKILL.md.
> Preserve author credit, notices, and applicable licence files from repository or parent directories. Add PROVENANCE.md with the Skill page, source URL, actual commit, original path, and licence. Retain any existing PROVENANCE.md and record new provenance separately. Batch source inspection, copying, and provenance work where practical.
> 5. In the project root, run `skilld install ./skills/fondo-install-auth --mode copy --plain`. If skilld is unavailable, use `npx skilld install ./skills/fondo-install-auth --mode copy --plain`. This known command needs no help lookup. Install does not support --json. Use detected Agent targets, or add --agent for the targets the user selected. Install the local path, never the upstream selector. If installation fails, preserve the local copy and report the exact failure.
> 6. Confirm the local lockfile source and installed Agent copies once. Report the local path, actual commit, and Agent targets. After edits, reinstall the same local path. Upstream updates must not replace it. Do not publish or push unless the user asks.

# Fondo Install & Auth

## Output

Record authentication method, approved scope, secret-manager reference, validation time, owner, and revocation procedure. Never include keys, financial response data, or account identifiers.

## Examples

Use a scoped staging credential for a read-only fictional record, record the redacted outcome, and verify the old credential is denied after revocation.

## Overview

Set up Fondo for automated startup bookkeeping, tax filing, and R&D tax credits. Fondo is a managed platform (not an API-first service) that integrates with payroll providers, banks, and expense tools. Configuration happens through the Fondo dashboard and OAuth connections.

## Prerequisites

- US-incorporated startup (C-corp or LLC)
- Fondo account at [fondo.com](https://fondo.com)
- Active payroll provider (Gusto, Rippling, ADP, etc.)
- Business bank account

## Instructions

### Step 1: Create Fondo Account

1. Sign up at [fondo.com](https://fondo.com)
2. Select your plan: **TaxPass** (bookkeeping + taxes + R&D credits)
3. Complete company profile (EIN, incorporation date, state)

### Step 2: Connect Payroll Provider

| Provider | Connection Type | Data Synced |
|----------|----------------|-------------|
| Gusto | OAuth 2.0 | Payroll runs, employee data, tax filings |
| Rippling | OAuth 2.0 | Payroll, benefits, headcount |
| ADP | API key | Payroll summaries, tax deposits |
| Justworks | OAuth 2.0 | PEO payroll, contractor payments |
| QuickBooks Payroll | OAuth 2.0 | Payroll journal entries |
| Paychex | Manual upload | Pay stubs, tax forms |

Navigate to Fondo Dashboard > Integrations > Connect Payroll and authorize.

### Step 3: Connect Bank Accounts

```
Fondo Dashboard > Integrations > Banking
  → Connect via Plaid (most banks)
  → Or manual CSV upload for unsupported banks
  → Mercury, SVB, Brex, Chase all supported via Plaid
```

### Step 4: Connect Expense Tools

| Tool | What It Provides |
|------|------------------|
| Brex | Corporate card transactions |
| Ramp | Card spend, reimbursements |
| Expensify | Receipt data, categorized expenses |
| Bill.com | AP/AR, vendor payments |
| Stripe | Revenue data, payouts |

### Step 5: Verify Connection

After connecting, verify in Dashboard > Integrations:

- Green check = connected and syncing
- Yellow warning = needs re-authorization
- Red X = connection failed, re-connect needed

## Error Handling

| Issue | Cause | Solution |
|-------|-------|----------|
| OAuth expired | Token expiry (90 days typical) | Re-authorize in Dashboard > Integrations |
| Missing transactions | Bank feed lag | Wait 24h or upload CSV manually |
| Duplicate entries | Multiple connections to same account | Remove duplicate connection |
| Sync paused | Provider API change | Contact Fondo support |

## Resources

- [Fondo](https://fondo.com)
- [Fondo R&D Credits FAQ](https://fondo.com/blog/fondo-rd-credits-faq)
- [TaxPass Overview](https://fondo.com/taxpass)

## Next Steps

After setup, proceed to `fondo-hello-world` to verify your first financial sync.
