The only two-way sync between DaisyBill and Google Sheets. Live AR aging, denial tracking, payment reconciliation, OMFS variance, and write-back — all without a single piece of your PHI touching a developer server.
Every workers' comp billing team hits the same wall. DaisyBill has the data. Google Sheets is where you actually run your AR meeting. And the bridge between them is a rotation of stale exports, brittle Zapier hacks, and "updated_at" bugs that quietly drop late payments on the floor.
Download. Format. Paste. Redo tomorrow. Eight hours a week gone.
Naive integrations filter on created_at. A payment posted to a 90-day-old bill? Never shows up.
You can pull bills, but you can't push SBR-1 appeals, write-offs, or new bills back. The sheet becomes read-only.
Delta sync on updated_at. Near-real-time webhooks. Mark SBR-1 on a row — it's filed.
Each template maps to a real billing workflow — not a generic data dump. Switch the tabs below to see the exact columns, filters, and derived metrics that ship with each one.
Unpaid bills bucketed by days outstanding. Live. Sortable. With the adjuster contact info already joined in.
Bills denied or rejected, with submission history and an on-deadline SBR-1 countdown. Mark a row and file the appeal from the sheet.
SBR-1 → dispute is filedNon-voided payments joined to their bills with deposit and post dates. Deduplicated by check number so per-service-line-item payments don't double-count.
Every bill with DOS, submission date, and live payment rate %. The default template for a weekly billing review.
Check-level view — one row per deposited check, with linked bills listed inline. The view your CFO actually wants on Monday morning.
Every bill, every submission, every payment for each patient — all on one scrollable sheet. Answer "where does this patient's account stand?" without clicking into DaisyBill.
Every feature exists because a workers' comp biller asked for it. No ornamental AI gimmicks. Just the stuff that saves you four hours a week.
The subtle bug in every naive DaisyBill integration: filtering on created_at means payments on older bills silently disappear. DaisySync uses updated_at[gteq] — every status change, every new payment, every denial comes through.
Type a flag in the Sync Status column. DaisySync calls the right API.
DaisyBill pushes events; the queue fires a delta sync within seconds. No more waiting for an hourly cron.
Upload your state's fee schedule. Expected, Variance, Variance % columns populate — underpaid bills surface themselves.
Hourly delta + weekly full refresh. Set once per sheet. Sync-all across every configured sheet with a single schedule.
As you edit filters in the Configure dialog, an estimated match count updates in real time — sampled from your cached bills. Know what a filter will return before committing to a full sync.
Unpaid Only · Denied Only · Aging 90+ · SBR-1 Candidates · Underpaid vs OMFS · Has Any Payment. Combine with custom rules and AND/OR logic.
Every sync — timestamped, attributed, and row-counted. HIPAA §164.528 accounting of disclosures, already handled.
DaisySync runs entirely inside your own Google Apps Script environment. There are no developer-owned servers in the data path — which means there's no surface area where we could accidentally (or intentionally) touch your PHI.
Your DaisyBill API token lives in your Google Workspace UserProperties — per-user scoped and never transmitted outside your account.
For covered entities on Google Workspace Business Plus+ with an executed Google BAA. Based on HHS's model agreement.
Every sync recorded in a hidden audit sheet. Log lines PHI-redacted by default (names, DOB, claim numbers stripped).
Disconnect & Wipe removes your token, every config, every trigger, and every hidden cache sheet — atomically.
spreadsheets.currentonly — current sheet only
go.daisybill.com — only destination
Open a Google Sheet → Extensions → Get add-ons → search DaisySync → Install. Grant the Sheets-current-only scope.
Paste your DaisyBill API token from Integration → API Tokens. The status pill turns green. Your token stays in your per-user properties.
Click the gear on a sheet. Pick a template. Select fields. Set filters. Hit sync. Your data shows up — correctly formatted, frozen header, currency-aware.
DaisySync is in private preview with a handful of workers' comp billing practices. Request access and we'll onboard you this week — including the BAA if you need it.
Full access to every template, write-back, webhook, and OMFS feature. Locked-in founding pricing when we leave preview.
No. DaisySync runs entirely inside your own Google Apps Script environment. There are no developer-owned servers in the data path. Your DaisyBill API token lives in your per-user Google Workspace properties, and every sync happens directly between your Google account and DaisyBill's API. The only global configuration we keep is a hash-to-spreadsheet directory for optional webhook routing — no credentials, no PHI, ever.
DaisySync's architecture is HIPAA-ready. Because no PHI ever touches the developer's infrastructure, compliance is a function of your own Google Workspace configuration. Business Plus or higher with an executed Google BAA is the minimum viable edition for HIPAA workflows. A DaisySync BAA — based on HHS's model agreement — is available on request for covered entities.
CSV exports are point-in-time snapshots that go stale immediately. DaisySync keeps the sheet live — delta-syncing whenever you reopen it, whenever a webhook fires, and on your scheduled refresh. You also get: joined injury + patient + adjuster data, derived columns (aging buckets, payment rate %, OMFS variance), and the ability to push write-backs — things no CSV export does.
Any edition works for non-PHI use. For workers' comp billing (which is PHI by definition), you need Business Plus or higher with an executed Google BAA. Free @gmail.com accounts cannot sign a BAA and should not be used.
Our delta sync queries DaisyBill with updated_at[gteq]=<last_sync> — not created_at. That means payments, status changes, and denials on bills created months ago still flow into your sheet automatically. It's the subtle bug that breaks most naive DaisyBill integrations.
Yes. Mark a row's Sync Status column with CREATE to push a new bill, WRITE_OFF to close it, or SBR-1 to file a Second Review appeal. DaisySync calls the appropriate DaisyBill endpoint and records the result back in the sheet. You can also create patients, injuries, and multi-line-item bills from the Create Record dialog.
No. Scheduled polling works fine on its own. Webhooks are optional and they make sync near-real-time when you're actively using the spreadsheet — events queue up and trigger a delta sync within seconds. You can use DaisySync with pure polling and never enable webhooks.
Upload your state's Official Medical Fee Schedule as CSV (CPT, Modifier, Expected $/unit). DaisySync computes Expected, Variance, and Variance % columns per bill so you can filter every bill where you were paid less than the fee schedule requires — then queue them for SBR-1 appeal with a single click.
DaisySync is currently in early access with founding-customer pricing. It will be a per-spreadsheet monthly subscription priced for billing teams, not enterprise IT budgets. Email us for details.
Ten templates, two-way sync, HIPAA-ready — running inside Google Sheets in under five minutes.
Request early access