GTG DATA QUALITY EXAMPLE / PUBLIC SAMPLE PLAYGROUND
A GTG Service Report You Can Explain.
Two fictional exports disagree about GTG service invoices. See which records can enter a report, which are repeats, and which need clarification.
Explore This Workflow
Select a step, change its settings, then run the example to see what changes. The workflow follows a fixed sequence. No login is needed. Changes reset when you reload or leave this page.
This public playground uses fictional data. Your changes affect this fictional example only.
Showing the result for the current connections and settings.
THE STARTING POINT
Prepare a Fictional GTG Service Report
CRM and billing exports contain fictional GTG service-invoice records.
- Inputs
- Fictional CRM and billing exports
- Match on
- Invoice reference — not just the client name
- What to resolve
- 1 exact repeats and 3 rows needing clarification in the selected exports
- Reporting rule
- Include confirmed records; show every exclusion and unresolved difference
Illustrative GTG workflow with fictional data. Nothing is sent to GTG, a CRM, an email service, or a calendar.
Select a step to explore its role and settings. This walkthrough follows a fixed sequence.
CLIENT + INVOICE / SELECTED CONTEXT
Check Details
Normalize formatting and check that the invoice has a client reference and a usable amount.
Account references and email case are standardized. A missing client is not invented.
- Formatting
- “ northstar ” becomes NORTHSTAR
- Required
- Client reference, invoice reference, and a usable invoice amount
Configure Check Details
Settings apply to fictional sample data. Run the configured sample after a change.
6 source rows accounted for: 2 ready for the report, 1 duplicate excluded, 3 needing clarification.
- Rows received
- 6
- Ready for report
- 2
- Duplicates excluded
- 1
- Need clarification
- 3
THE BUSINESS OUTPUT
Report Preparation — Example
- Ready invoices
- GTG-INV-101 · NORTHSTAR; GTG-INV-104 · SUMMIT
- Report scope
- All confirmed clients
- What stays out
- Missing client details and conflicting invoices remain visible for clarification.
- Why this matters
- The same invoice is not counted twice, and conflicting values are not silently chosen.
| Row | Invoice / Source | Client Reference | Invoice Amount (USD) | Reporting Decision |
|---|---|---|---|---|
| R-01 | GTG-INV-101 CRM export | northstar | $1,500.00 | Ready for report Complete invoice; included once. |
| R-02 | GTG-INV-101 Billing export | NORTHSTAR | $1,500.00 | Duplicate excluded Same invoice and values as R-01; not counted twice. |
| R-03 | GTG-INV-102 CRM export | (missing) | $800.00 | Needs clarification Add the client reference for invoice GTG-INV-102. |
| R-04 | GTG-INV-103 CRM export | PINEHURST | $4,500.00 | Needs clarification Compare the conflicting client details or amounts for GTG-INV-103 before reporting it. |
| R-05 | GTG-INV-103 Billing export | pinehurst | $4,600.00 | Needs clarification Compare the conflicting client details or amounts for GTG-INV-103 before reporting it. |
| R-06 | GTG-INV-104 Billing export | SUMMIT | $2,400.00 | Ready for report Complete invoice; included once. |
What Needs Clarification
- R-03 · Add the client reference for invoice GTG-INV-102.
- R-04 · Compare the conflicting client details or amounts for GTG-INV-103 before reporting it.
- R-05 · Compare the conflicting client details or amounts for GTG-INV-103 before reporting it.
Bring your own business problem, systems, and constraints into a GTG discovery conversation.
Build Your Discovery Brief