How it works
Three steps from your books to a dispute package — pick how Drumtap finishes it.
Today Drumtap reads the CSV uploads from your books and the GC portal, labels every discrepancy with a Drumtap internal code (G-01..G-06), and finishes the loop on Starter (you send — the only shipped plan today). Walkthroughs for Pro (upload-based pre-drafted send, on your one-click review) and Auto (within-rules send + banking-feed verification + audit log) are planned and not yet live.
Phased email path — Drumtap does not currently ingest email.
- Today: customers upload CSV exports from QuickBooks (or equivalents) and from the GC portal. Drumtap does not currently ingest email directly and drafts (or sends) emails only on the cadence your tier currently supports.
- Next (planned): a secure forwarding path for the dispute email and the portal-ready refile packet — once that capability ships, Drumtap will send only on your approval.
- Later (planned, optional): read-only Gmail / Microsoft mail monitoring for portal-notice ingestion. Drumtap will never read your unrelated email traffic; only matching vendor / portal notices will be considered.
An email payment notice from the GC is not cleared funds. Drumtap does not currently mark invoices "cleared" from a payment notice alone; clearing is your book record.
Bring in your data
On Starter (Upload + self-send), export a CSV from your accounting software and the GC portal, then upload both. On Pro and Auto today, Drumtap reads the uploads the same way — Connect (planned — Coming next) / Auto-send (planned — Coming next) are planned and not active yet.
Drumtap reconciles every row
Drumtap crosses every AR line against the GC portal's submission log and payment ledger — on each CSV upload on Starter, on each CSV upload (live connections planned — Coming next) on Pro, on each CSV upload (live connections planned — Coming next) on Auto (live connections planned, not active). Missing invoices, short payments, rejected submissions, and portal-only line items each get a Drumtap internal discrepancy code and the evidence the dispute requires.
Dispatch matches your plan
Starter — Read-only — Drumtap builds the evidence package; you send it yourself. Pro — Coming next — Drumtap drafts upload-based dispute emails for your review before they go out. Auto — Coming next — Drumtap sends dispute emails within the rules you approve and prepares upload-based refile packets; nothing leaves Drumtap on Auto today.
Starter
Upload + self-send — no connections required.
on each CSV upload. Read-only — Drumtap builds the evidence package; you send it yourself.
Step 1 · Upload
Drop in your QuickBooks invoice CSV
Drag-and-drop the QuickBooks invoice export from your desktop — no template to fill in, no manual reformatting. The parser auto-maps your column headers and the run previews each row before it kicks off so column mismatches catch you instead of the GC.
Step 2 · Reconcile
Drumtap reads every row from your upload
Drumtap reads your export, pairs each invoice against the portal export you also uploaded, and labels the gaps — on-time, late, missing, short, rejected. Cadence: on each CSV upload. The work queue lands as a short, sorted list you can hand to your PM.
Step 3 · You send
You send the evidence package, on your letterhead
For each flag Drumtap assembles the right evidence bundle (PO, change order, daily logs, photos for rejected rows). You open it, decide what to send, and email AP or refile through the portal yourself. Drumtap is read-only against your portal on Starter — no connections, no writes; Drumtap does not currently send emails on your behalf.
Pro
Connect (planned — Coming next) — roadmap, not shipped.
Today Pro reconciles on each CSV upload — the live-connection + pre-drafted send path is planned. Coming next — Drumtap drafts upload-based dispute emails for your review before they go out.
Step 1 · Connect (planned — Coming next)
When Pro ships: Drumtap connects to your books and supported GC portals
Drumtap will hold read-only connections to QuickBooks Online and each supported GC portal — tokenized OAuth, single-user approval, and Drumtap will not store the underlying credentials. Portal uploads remain yours; Drumtap never writes to vendor portals.
Step 2 · Reconcile
Drumtap reconciles every row — on each CSV upload (live connections planned — Coming next)
Every reconcile re-runs the line-by-line match between your books and the GC portal's submission log — on each CSV upload (live connections planned — Coming next). Each gap is labelled with its Drumtap internal discrepancy type (G-01..G-06) and the evidence it would need to clear.
Step 3 · You approve (planned — Coming next)
When Pro ships: Drumtap drafts every dispute email — you approve each one
For each flagged discrepancy Drumtap will draft a dispute email and the portal-ready refile packet, attach the right evidence (PO + CO + daily logs for partial; photos added when the row was rejected), and park both in your approval queue. You skim, click Send, and the email goes out — one row at a time, never in bulk.
Auto
Auto-send (planned — Coming next) — roadmap, not shipped.
Today Auto reconciles on each CSV upload — the live-connection + banking-feed + within-rules-send path is planned. Coming next — Drumtap sends dispute emails within the rules you approve and prepares upload-based refile packets; nothing leaves Drumtap on Auto today.
Step 1 · Connect + bank-read (planned — Coming next)
When Auto ships: Drumtap connects to books, portals, and a read-only bank feed
Drumtap will authenticate QuickBooks Online, the supported GC portals, and a read-only banking provider so cleared payments can be verified. Customers will set the rules up front — amount caps, GC allow-lists, timing windows — and Drumtap will send only within those guardrails. Drumtap will not store bank credentials and will not move funds.
Step 2 · Reconcile + track
Drumtap reconciles + tracks responses + cleared payments — on each CSV upload (live connections planned — Coming next)
Every reconcile pairs AR against the portal submission log (on each CSV upload (live connections planned — Coming next)). Drumtap will then watch each open flag — portal response threads, payments clearing the bank, work that lands but never got invoiced — and refresh status on every tick once that path is live.
Step 3 · Auto-send + audit (planned — Coming next)
When Auto ships: Drumtap sends within rules — flags every gap — audits every action
Drumtap will send every dispute email within the rules you approved and prepare portal-ready refile packets you upload yourself. For every row the portal never saw, Drumtap will flag the gap and assemble the dispute package your existing evidence composes — Drumtap will not synthesise a new invoice to QuickBooks. An audit log will record every action Drumtap took on your behalf — what was sent, when, to whom, and the response. Only exceptions reach your inbox.
Ready to stop reconciling by hand?
Pick the plan that matches how involved you want to be.
Founding access is open
Founding access is open
Drumtap is onboarding its first 25 trade contractors at locked-in beta pricing. Create your account now and we will get you set up on Starter (manual upload) today; Pro and Auto sit on the waitlist until those capabilities ship.