Taggun

@taggun process this receipt URL and extract the merchant, date, total, and line items: https://example.com/receipts/lunch-2024.jpg

The receipt from *Joe's Diner* dated January 15, 2024 shows a total of $42.87. Line items include: Caesar Salad ($12.00), Cheeseburger ($15.50), Fries ($4.50), Iced Tea ($3.00), plus tax ($2.87) and tip ($5.00). Payment method was Visa ending in 4532. This illustrative example shows how Taggun extracts structured data from a receipt image URL—actual results depend on image quality and receipt format.

This example uses the URL Verbose tool for comprehensive extraction. Requires a publicly accessible image URL (not behind auth). OCR accuracy varies with receipt clarity, lighting, and format. API key must have sufficient credits; each call consumes one transaction from your Taggun quota.

@taggun export the full list of known merchants from our account so I can audit which vendors are already in the system

Exported 247 known merchants from your Taggun account. Sample entries include: *Starbucks Coffee* (ID: merch_8x2k), *Amazon.com* (ID: merch_9p4j), *Shell Gas Station* (ID: merch_3n7w), *Whole Foods Market* (ID: merch_5q1r). The complete list is available as a structured dataset showing merchant names, IDs, and any custom aliases you've configured. This example illustrates a read-only export—actual merchant count and names reflect your account's training history.

This example uses the Export Known Merchants tool to retrieve your account's merchant registry. Useful for syncing with accounting systems or auditing recognition accuracy. No side effects—purely a read operation. The merchant list grows as Taggun learns from your receipts over time.

@taggun generate a sample CSV of 50 mock merchants so I can test the bulk import workflow before uploading our real vendor list

Generated a CSV file at `/tmp/taggun_merchants_sample_20240115.csv` containing 50 mock merchant entries. Each row includes: merchant name, optional alias, category (e.g., 'Restaurant', 'Retail', 'Gas Station'), and a sample tax ID. Example entries: *Acme Hardware Supply*, *Bella's Bistro*, *QuickStop Fuel*. You can download this file and use it to test your import pipeline without affecting production data. This illustrative example shows the tool's output format—actual file path and merchant names vary per request.

This example uses the Generate Merchants CSV tool to create test data for import workflows. Returns a temporary file path valid for the session. No write to your live merchant registry occurs—this is purely for testing bulk import mechanics before committing real vendor data.

When Taggun speeds up monthly expense close for distributed teams

A 12-person remote startup closes expenses on the 5th of each month. Team members snap receipts on phones, upload to Slack or email, and finance chases down missing data. Taggun's URL processing tools let you drop receipt image links into Switchy and extract vendor, date, total, and line items in seconds—no manual re-keying. The 'URL Verbose' tool pulls comprehensive data including tax breakdowns, which matters if you're filing multi-state or international. This works best when your team already uses a cloud storage or chat tool that generates public links. If receipts arrive as email attachments or PDFs behind auth, you'll need a preprocessing step to host them. For teams under 20 people closing fewer than 100 receipts a month, Taggun in Switchy cuts close time from two days to two hours.

Why Taggun fits high-volume refund ops but not fraud investigation

A 6-person support team at a DTC brand processes 40-60 refund requests daily. Customers submit purchase receipts via Zendesk; support needs to confirm the merchant, date, and amount before issuing credit. Taggun's 'Process Receipt via URL' tool extracts those three fields in under two seconds per receipt, and the 'URL Validation' tool checks against campaign rules (like date range or merchant whitelist) without writing custom logic. This setup works when your refund policy is rules-based and receipts are standard retail formats. It doesn't work for fraud cases where you need to cross-reference transaction IDs or inspect image metadata—Taggun only parses visible receipt data. For straightforward refund ops where speed matters more than forensic depth, Taggun in Switchy turns a 90-minute daily task into 15 minutes.

When Taggun's merchant export unlocks quarterly spend review

A 4-person finance team at a 50-employee company reviews vendor spend each quarter to renegotiate contracts and spot duplicate subscriptions. Receipts live in Expensify or Ramp, but those tools don't surface a clean merchant registry. Taggun's 'Export Known Merchants' tool dumps the full list of vendors Taggun has seen across all processed receipts, which you can load into Switchy and cross-reference against your AP ledger. The 'Generate Merchants CSV' tool is useful for testing bulk imports before you commit to a new expense workflow. This approach works when you process at least 200 receipts a quarter and need a vendor-centric view, not just transaction totals. If your spend is under 50 receipts a quarter, manual tagging in your accounting tool is faster. For mid-size teams doing quarterly vendor audits, Taggun gives you the merchant dimension your expense tool doesn't.