DetailOAR
Log in Start your free trial

DetailOAR Field Manual · Reports and integrations

Read Reports, Connect Integrations, and Troubleshoot Common Problems

Run date filters, read business metrics without overclaiming causation, export rows, set up optional adapters, and chase down problems in a safe order.

Intermediate12 min readAction: 35 minUpdated July 16, 2026

Written by Marcus Burk · Reviewed by DetailOAR Product Team

Start guide
Save or use this guide
Download checklist

Reporting dashboard showing revenue, outstanding balance, estimate conversion, and date filtersView full size
Contents
01

Start

Know the outcome.

02

Steps

Do the work in order.

  1. Step 1

    Apply and read a report

    1. Open Reports.

    2. Pick a named report such as Revenue, Accounts receivable, Sales by service, or Recurring snapshot.

    3. Set From and To dates, then choose Apply. Stick to one time zone and comparable periods.

    4. Read the metric definition before you interpret anything. Collected cash, invoiced revenue, scheduled value, and outstanding balances answer different questions.

    5. Look closely at empty and zero states. Zero can be a correct result; a loading or failed state is not zero.

    6. Choose Export CSV and check the row totals reconcile to the on-screen result.

  2. Step 2

    Export for reconciliation

    1. Choose Export CSV for the current report or accounting view.

    2. Use Export for QuickBooks (.iif) only when the accounting workflow supports that import and the accounts are mapped correctly.

    3. Reconcile totals against payment-provider deposits, cash/check records, refunds, tips, tax liabilities, and outstanding balances.

    4. Keep the source export and the adjustment explanation. Don’t edit a report just to force a match with an unrelated bank period.

  3. Step 3

    Connect optional integrations

    1. Open Settings, Integrations.

      Reporting and integration status showing exports, saved filters, provider state, and troubleshooting guidanceView full size

    2. Take one provider at a time: Payments, Email, SMS, Google Calendar, Storage, Maps/VIN, Accounting, Monitoring, or Webhooks as available.

    3. Read the Unconfigured status and the required environment/settings fields. Secrets go only in protected fields or deployment secret storage.

    4. Save, refresh the status, and run the smallest provider test.

    5. Write down the account owner, renewal/billing responsibility, webhook URL, permissions/scopes, and disconnect procedure.

    6. Keep the demo adapter active anywhere credentials are intentionally absent.

  4. Step 4

    Troubleshoot in a safe order

    1. Start by confirming the workspace, signed-in user, role, record ID, and time range.

    2. Read the exact UI error and browser/network response — without copying private data into a public ticket.

    3. Check the integration status, message/payment/event log, and audit trail.

    4. Use the Health endpoint and deployment logs to tell browser, app, database, and provider failures apart.

    5. Reproduce with seeded demo data when possible.

    6. Retry only after confirming the original action didn’t already succeed — payments, messages, bookings, and webhooks depend on idempotency.

03

Reference

Use the detail when you need it.

Interpret without inventing causation
  • Estimate conversion: accepted or converted estimates divided by eligible sent estimates, per the report definition.
  • Average ticket: eligible sales divided by eligible jobs/invoices — deposits and refunds shift the definitions.
  • New versus repeat: comes from customer history, not whether staff remembers the person.
  • Lead source performance: only useful when source capture is consistent.
  • Employee/service results: weigh assignment, job duration, mix, cancellations, and data quality before comparing people.
Common problems
  • Numbers differ: line up status, date basis, time zone, currency, refunds, tax, and cash-versus-accrual interpretation.
  • Calendar item missing: check connection status, the selected calendar, scopes, the event sync log, and whether the appointment was confirmed.
  • Provider shows configured but the action fails: refresh status, look for revoked credentials/scopes, and read the provider logs.
  • CSV looks wrong in spreadsheet software: import as UTF-8 and keep phone, plate, VIN, and source IDs as text.
  • Dashboard empty for staff: check permissions — hiding financials may be intentional.
04

Finish

Check the result and close the loop.

Final checklist
  • Report definition and date basis understood.
  • CSV reconciled.
  • No private data sent to analytics/support unnecessarily.
  • Integration owner and disconnect path recorded.
  • Provider test passed or status remains visibly unconfigured.
  • Idempotency checked before retry.
05

More

Continue only where it helps.

Prerequisites

Connect Payments and Send Your First Invoice12 min readConfigure the Lead Pipeline and Lead Sources12 min read

Learning paths with this guide

Set Up DetailOAR8 guides
Frequently asked questions
Why does collected differ from revenue?

Collected counts payments actually received; other revenue views may run on invoice or job timing and include outstanding amounts.

Should I connect every integration immediately?

No. Only connect providers with a clear workflow, owner, credentials, cost, and tested disconnect path.

What data should go to analytics?

Coarse product events only. Never include customer notes, vehicle identifiers, private media, payment details, or message bodies.

Sources and review

Reviewed by DetailOAR Product Team on July 15, 2026. Verify current labels, interfaces, prices, and local requirements before acting.

  1. DetailOAR seeded application interface

Related field guides

Product screenshot

Open original in a new tab