Business reporting integration
Align metric definitions, grain, time periods and owners before combining CRM, orders and accounting.
Author：WeTech technical team · Updated： (Hong Kong time (GMT+8))
Define each metric’s calculation, source, time basis and grain before modelling and refreshing data. Matching charts do not establish correct numbers. Check duplicate joins, cancellations, time zones, access and failed refreshes.
When to use this guide
For businesses reconciling conflicting spreadsheets or commissioning sales, operations and management dashboards.
Reporting requirements checklist
| Item | Confirm | Acceptance |
|---|---|---|
| Metrics | Revenue, enquiry and status definitions | Owner-approved calculation |
| Grain | Customer, order or line-item rows | Test many-to-one relationships |
| Time | Zone, business date and refresh frequency | Period boundaries and late data |
| Use | Roles, export and stale-data warnings | Access and failed-refresh tests |
Give every metric a definition
Sales may mean ordered, paid, invoiced or recognised amounts. Do not merge figures solely by label. Document cancellations, refunds, test records, tax treatment and currency basis. Show missing data as unavailable rather than silently converting it to zero.
Validate relationships before charts
Customers, orders and order lines have different grains. A direct join can multiply revenue. Validate keys, relationship counts and aggregates using known samples before charting. Reconcile source totals with transformed totals and retain explanations for differences.
Make freshness visible
Display last successful refresh, covered dates and incomplete sources. A failed refresh may retain an earlier report but must be visible; partial updates are not complete current-day data. Include row-level access and exports in acceptance tests.
Illustrative scenario
Hypothetical example: sales tracks CRM opportunities while finance tracks paid orders. Keep the metrics and time bases distinct, then reconcile conversion using order identifiers. Different totals can be valid and should not be forced to match.
Frequently asked questions
Must data be real time?
Set freshness by decision needs; real-time delivery adds integration and operational requirements.
Will the dashboard tool reconcile everything?
No. Source owners still need to approve business definitions and rules.
Can missing data be shown as zero?
Only when confirmed as a genuine zero; otherwise preserve the missing-data state.
Brand and public case scope
WeTech Consulting, also called WeTech or WeTech AI HK, provides AI and IT consulting in Hong Kong. WeProperty HK and WeCredit HK are self-developed products. Their cases support the observable features listed: property, estate and transaction-reference entry points for WeProperty; submission, review and public-data masking for WeCredit. WeCredit is not a TU credit-rating service or a final determination of facts.
WeProperty HK · WeCredit HK (case studies in Traditional Chinese)
Reference sources
Official documents support the technical, risk and measurement concepts. Checklists, estimation methods and illustrative scenarios are WeTech planning recommendations, not official prices or client results. Check the supplier’s current plan and terms. Sources reviewed: (GMT+8)
Related guides
Discuss your project
Share your workflow, systems and goals. We will review scope before discussing deliverables, acceptance and a quotation.
Request an initial consultationExplore this service