The point where built-in reports stop being enough
Nobody outgrows their job system's reports on purpose. It happens one board meeting at a time. The operations dashboard is fine, the revenue screen is fine, and then a director asks something that crosses a line: revenue after credit notes, sales won against contracts set up, this year against a year that predates the system. Somebody exports two CSVs, a workbook appears, and from then on that number is produced by hand every month.
This page is a fair look at that line. It credits what built-in field service management (FSM) reporting does well, using Uptick and Simpro as the examples people search for most, and it shows exactly which kinds of question break it and why. The short version: the reports are strong on anything the job system owns, and weak by design on anything it does not.
What Uptick and Simpro reporting does well
Start with what you already pay for. Uptick's Insights and Reporting article lists dashboards for operations, finance, clients and properties, sales and quoting, and technicians. Among them are a Task Completion Dashboard, a PM Forecast covering the next twelve months, a Revenue Report you can group and pivot by client, date, status and branch, Task Profitability pivoted by category, cost centre, technician and property, and a Work in Progress report. Report configurations can be bookmarked, most reports can be exported, and a KPI Report compares nine measures against benchmarks from similar companies. For the people who run the work every day, that is a lot of answers with no extra tooling.
Simpro positions its reporting the same way: a library of standard reports inside the product, plus a separate business intelligence option for building your own views. We could not open Simpro's help guide to confirm report names or plan details, so we are not listing them here. Check what your own subscription includes before assuming something is missing.
The pattern holds across the category. If the question is about jobs, visits, quotes, technicians or invoices raised in the job system, the built-in report is usually the quickest and most trustworthy place to get it. It uses the vendor's own definitions, it knows the status rules, and nobody has to maintain it.
Three ways cross-system questions break it
Built-in reports fail in predictable ways, and none of them are bugs. They follow from a report only being able to see its own database.
Joins. A credit note raised directly in Xero, an invoice for consultancy that never went through a job, a deal stage in HubSpot, a budget in a spreadsheet: none of these exist in the FSM. Any figure that needs them is outside the report's reach, however good its filters are.
History. Reports group by the values a record holds. If the attribute you group by can change (account owner, branch, contract value, service line), you need to know what it was at the time, not what it is today. That history often lives in the CRM or in nobody's system at all. Older years may sit in a legacy tool or an archived workbook the FSM never imported.
Definitions. A vendor KPI uses the vendor's clock. Your contract with a client may define response time, completion or "on time" differently, and a board pack needs one agreed version. A report you cannot edit cannot hold your definition.
Timing matters too. Uptick's article says most dashboards refresh every 60 minutes and the Financial Performance Dashboard syncs overnight, which is sensible, but it means two screens can disagree mid-morning. Knowing which snapshot a number came from is part of trusting it.
Built-in reports check · Thornbeck Fire & Security
4 of 12 board questions are answered well inside the job system.
The rest need care, or data the job system never sees: CRM owners, credit notes raised in the accounts, budgets in a spreadsheet.
- Answered well
- 4 / 12
- Single-system questions
- With care
- 3 / 12
- Depends on history or definitions
- Needs a join
- 5 / 12
- CRM, accounts or spreadsheet
- Touch another system
- 7 / 12
- At least one source outside the FSM
Twelve questions a board pack asks, and where they get answered
| Question | Asked by | Systems | Built-in reports |
|---|---|---|---|
| How many routine visits were due and done this month, by branch?Visits, due dates and branches all live in the job system. | OD | FSM | Answers it |
| Which technicians have the most open work today?Live scheduling data; the job system is the source of truth. | OD | FSM | Answers it |
| What did we invoice this month, by client and service line?Holds for invoices raised in the job system. | FD | FSM | Answers it |
| How many defect quotes were sent and approved?Quotes and their status sit next to the jobs that raised them. | MD | FSM | Answers it |
| What is the gross margin on each task or job?Right if every cost is booked to the job; overheads and late supplier bills are not. | FD | FSM | With care |
| What is revenue by client once credit notes are netted off?Credits and invoices raised directly in the accounts never reach the job system. | FD | FSM + Finance | Needs a join |
| Which clients owe us money past terms?Payment status is owned by the accounts package. | FD | Finance | Needs a join |
| Did every deal sales won turn into a contract and routines?The deal lives in the CRM; the contract lives in the job system. | MD | CRM + FSM | Needs a join |
| Revenue by account manager, using who owned the client at the timeNeeds owner history from the CRM, not just today’s owner. | MD | CRM + FSM + Finance | Needs a join |
| Is this quarter better than the same quarter two years ago?Fine if the system holds that history; not if older years sit in a legacy tool or workbook. | MD | FSM + Spreadsheet | With care |
| Are we hitting the contract KPIs in the client’s own definition?Built-in KPIs use the vendor’s definition; the contract may define the clock differently. | OD | FSM + Spreadsheet | With care |
| Do budget and forecast agree with actuals by branch?The budget usually lives in a spreadsheet the job system cannot see. | FD | Spreadsheet + Finance + FSM | Needs a join |
FSM = field service management (job) system. Verdicts are a general judgement about single-system reporting, not a test of any one vendor.
Question 9, answered two ways · Q3 2026 (July to September)
Kittiwake Leisure: Tom → Kerry, 1 Sep
| Account manager | Job system, today’s owner | Governed, owner at the time | Difference |
|---|---|---|---|
| Priya | £49,815 | £46,775 | −£3,040 |
| Tom | £37,235 | £57,810 | +£20,575 |
| Kerry | £81,390 | £65,350 | −£16,040 |
| Total | £168,440 | £169,935 | +£1,495 |
Job system, today’s owner Governed, owner at the time
Governed revenue = job system invoices − credit notes raised only in the accounts + invoices raised only in the accounts, credited to whoever owned the client in the CRM that month. The total moves by £1,495; the league table changes order.
The data model behind a cross-system answer
Take question nine from the table: revenue by account manager, crediting whoever owned the client at the time. It is a common commission and performance question, and it needs three systems.
Fields
| System | Record | Fields used |
|---|---|---|
| FSM (Uptick, Simpro or similar) | Invoice | invoice number, client, invoice date, net amount |
| Accounts (Xero or similar) | Invoice and credit note | number, contact, date, net amount, reference, whether it originated in the FSM |
| CRM (HubSpot or similar) | Company | company record, owner, owner change history |
| Your mapping table | Client crosswalk | FSM client ID, accounts contact ID, CRM company ID |
Joins
| From | To | Key | Watch for |
|---|---|---|---|
| FSM client | Accounts contact | Crosswalk table | Trading names that differ between systems |
| FSM client | CRM company | Crosswalk table | Duplicate companies in the CRM |
| Accounts document | FSM invoice | Origin flag or synced document ID | FSM and accounts invoice numbers need not match, so never join on number alone |
| Invoice month | CRM owner | Owner valid on that date | An owner change mid-month needs a rule (we use the owner on the invoice date) |
Formulas
| Measure | Formula |
|---|---|
| Accounts-only credits | sum of credit notes in the accounts with no matching FSM document |
| Accounts-only invoices | sum of invoices in the accounts with no matching FSM document |
| Governed revenue | FSM invoiced − accounts-only credits + accounts-only invoices |
| Revenue by owner at the time | governed revenue for each client-month, summed by the CRM owner valid in that month |
The crosswalk table is the unglamorous part that makes everything else work. Build it once, review new clients weekly, and every later report inherits it.
Worked example (illustrative, fictional)
Thornbeck Fire & Security is an invented contractor. Its MD wants Q3 2026 revenue by account manager for a quarterly review. Six clients, three account managers: Priya, Tom and Kerry. On 1 September, Kittiwake Leisure moved from Tom to Kerry.
What the job system shows. FSM invoices for the quarter total £168,440. Grouped by each client's current owner, that gives Priya £49,815, Tom £37,235 and Kerry £81,390. Kerry looks like the clear leader and Tom looks well behind.
What the accounts add. Finance raised three credit notes directly in the accounts: £2,015 for Wendlow Care Group in September, £1,025 for Fellgate Logistics in August and £1,530 for Kittiwake Leisure in July, £4,570 in total. They also raised two invoices outside the job system: £3,410 to Marrowby Schools Trust and £2,655 to Kittiwake Leisure, both in August, £6,065 in total. Governed revenue is £168,440 − £4,570 + £6,065 = £169,935.
What the CRM history changes. Kittiwake's July and August revenue belongs to Tom: (£9,525 − £1,530) + (£6,515 + £2,655) = £17,165. Only September's £12,710 belongs to Kerry.
The result.
- Priya: Wendlow £28,245 + Fellgate £18,530 = £46,775 (£3,040 lower than the FSM view).
- Tom: Marrowby £40,645 + Kittiwake July to August £17,165 = £57,810 (£20,575 higher).
- Kerry: Ruddock Street £25,440 + Ostley £27,200 + Kittiwake September £12,710 = £65,350 (£16,040 lower).
The company total moved by only £1,495, which is why nobody spotted a problem. But Tom went from third to second, and the gap between him and Kerry fell from £44,155 to £7,540. If commission or a performance conversation rests on that table, the single-system version is wrong in a way no filter can fix.
Signs you have outgrown the built-in reports
- The same export-and-paste workbook is rebuilt every month, and only one person knows how.
- Two directors bring different revenue figures to the same meeting, and both are "right" for their system.
- A question begins "compared with when…" and the answer needs data from before the current system or from before a client changed hands.
- The KPI in the contract and the KPI on the dashboard use different definitions.
- Someone asks for a figure that needs the CRM, the job system and the accounts together.
None of these mean the FSM is the wrong tool. They mean the question has moved above it.
Your options, honestly
Keep the built-in reports for what they own. Operational dashboards in the job system should stay where they are. Moving them elsewhere adds work and removes the vendor's own definitions.
Add a BI tool on top. This is a common next step, and our guide to Power BI for field service reporting covers what it takes. With Uptick, note the route: its API fair use policy says warehouse, BI and reporting syncs must use the Uptick connector for Airbyte, and its Airbyte guide says the API cannot be connected directly to a BI tool. Data has to land in a database first.
Hire someone to stitch it together. A reporting analyst can build and own the joins, though the knowledge sits with one person. We look at what that really costs in the cost of a reporting analyst.
Use a governed data layer. Land every source in one warehouse, keep the crosswalk, the history and the definitions as tested rules, and run reports from there. That is what IVP.ai does.
How IVP.ai handles it
The IVP.ai Data Layer connects to Uptick through Airbyte, in line with Uptick's rules for reporting syncs, and to your CRM, accounts and spreadsheets alongside it. Client crosswalks, owner history and your own KPI definitions are stored once and reused by every report or agent. Deskless by IVP.ai can watch for exceptions, such as a new client with no crosswalk entry, and flag them for a person to resolve.
A national fire safety and security company used this approach to bring HubSpot, Uptick and its finance spreadsheets into one governed view, and now saves 10+ hours a week on reporting (case study). See the platform, the Uptick integration, the Simpro integration and our field service reporting overview.
If your board pack is full of questions marked "needs a join", start a free 48-hour pilot. We connect up to three sources, clean the data and have one report or agent running on your real data within 48 hours of read-only access. You then have 14 days of access to decide on a plan or walk away.