By Daniel Reeves, field-service reporting analyst with 9 years of experience reviewing job margins, technician performance, and operational dashboards
Last reviewed: July 21, 2026
FieldPulse includes dashboards, raw-data reports, report templates, filters, exports, and job-costing tools for tracking jobs, sales, payments, labor, and profit. A wrong KPI usually begins with the selected date field, report filter, source record, or user permission rather than the chart itself.
This independent guide is not operated by or affiliated with FieldPulse.
Check the source data first. Skip changing a dashboard target merely because one widget does not match a spreadsheet or accounting report.
What is FieldPulse reporting?
FieldPulse is field service management software for scheduling, dispatching, customers, estimates, invoices, payments, technician activity, and operational reporting. Its reporting system can build custom reports from jobs, estimates, invoices, payments, timesheets, projects, maintenance agreements, assets, customers, orders, inventory records, and several other record types.
The reporting tools answer different questions.
The Pulse Dashboard provides a current visual overview. Raw Data Reporting provides detailed records and fields. Reporting Templates offer prebuilt report structures. Job Costing compares projected and actual revenue, cost, and margin on an individual job.
Those tools should not be expected to return identical numbers unless the same records, dates, filters, and calculation rules are being used.
A dashboard can show invoice activity by creation date while another report uses payment date. Both can be accurate.
Pulse Dashboard or raw-data report?
The Pulse Dashboard is designed for fast visibility. FieldPulse says it displays business widgets, recent activity, and quick-create controls for records such as jobs, customers, estimates, and invoices. Users can also choose the dashboard, Team Schedule, Team Timesheets, Estimates, Invoices, Customers, or Projects as their default homepage.
Raw Data Reporting is built for detail.
The documented route begins under Management, then Reporting, followed by the desired record type and Raw Data. The user selects a date range and chooses Load Data before configuring the report further.
Use the dashboard to notice a pattern. Use raw data to investigate it.
A sales widget that appears low should lead to questions about the selected period, invoice status, user filter, and date basis. It should not immediately lead to an assumption that invoices disappeared.
Short rule: chart first, records second.
Why two FieldPulse reports show different totals
Different totals usually come from different definitions.
One report may use invoice creation date. Another may use payment date. A job report might include completed jobs, while a saved view excludes archived records. A technician-sales report may group revenue by invoice creator, assigned employee, or another field.
FieldPulse’s prebuilt reporting library includes separate templates for Sales by Technician, Total Sales, Sales by Lead Source, Sales by Invoice Creator, Payment History, Overdue Invoices, Unpaid Invoices, and Estimate Conversion Rate. The existence of separate templates reflects separate business questions.
Check these items before comparing totals:
| Check | Why totals may differ |
|---|---|
| Record type | Jobs, invoices, and payments represent different events |
| Date field | Created, service, due, paid, and completed dates can differ |
| Status | Draft, sent, paid, voided, or archived records may be included differently |
| User field | Creator, assigned technician, and commission recipient are not interchangeable |
| Saved filter | One view may retain filters the other does not use |
| Permissions | A manager may not have access to every source record |
Do not force two reports to match until their definitions match.
Date selection is a common reporting mistake
FieldPulse requires users to select a date range before loading raw report data. The meaningful date may differ by report type.
Consider an invoice created on June 28, sent on July 1, paid on July 8, and tied to a job completed on June 30.
That single transaction can reasonably appear in:
- A June invoice-created report
- A July payment report
- A June completed-jobs report
- A July cash-receipts review
One record. Four periods.
Do this first: write down the business question in plain language. “How much did we invoice in June?” is not the same as “How much money did we collect in June?”
Skip broad labels such as “monthly revenue” unless the company has defined whether that means invoices created, work completed, or payments collected.
The selected definition should remain consistent across meetings and spreadsheets.
How FieldPulse filters affect what you see
FieldPulse filters can narrow records by status, team member, tags, customer, and custom fields. Job and Project views also support filters such as job title, assigned team, invoice status, active or archived state, notes, creation dates, recurring-job status, and other record-specific options.
Saved filters can be stored under My Filters. Job and Project filters can also be saved as named views that appear as pinned tabs. Those views can later be reordered, renamed, or deleted under Manage Views.
This creates a subtle friction.
A dispatcher opens a pinned view called “Open Jobs” and assumes it displays every open job. The saved view may also contain an old team, date, tag, or customer filter that was useful when the view was created.
Review the active filters first.
Do not recreate a missing job merely because it is absent from one saved view. Open the broader Jobs list, clear filters, and search the underlying record.
A saved name describes the user’s intention. It does not prove the filter still matches that intention.
Dashboard widgets retain their own setup
The Pulse Dashboard allows users to move or remove widgets, and FieldPulse says dashboard changes are stored for later visits. Certain widgets, including Payments Collected and Invoices & Estimate Sales by Created Date, also support filtering.
That persistence is useful, but it can surprise another user.
One manager may see a dashboard filtered to a team or business segment. Another may compare it with a broader report and conclude that the dashboard is wrong.
Check the widget settings.
Skip assuming that every FieldPulse dashboard is a company-wide standard view. A saved configuration may reflect the individual user’s prior choices.
Businesses that use dashboards in weekly meetings should document:
- Which widgets are reviewed
- Which date range applies
- Which filters should remain active
- Whether the metric is invoiced, paid, scheduled, or completed
- Who owns corrections to the underlying data
Without that discipline, the meeting can become a debate about numbers rather than an operational review.
Using report templates without rebuilding everything
FieldPulse provides downloadable report templates for common use cases. The library currently includes jobs by status, sales by technician, estimate conversion, estimate status, total sales, sales tax, overdue and unpaid invoices, lead-source sales, commissions, and payment history.
The documented import process begins by downloading a template as a .json file. The user then opens the appropriate Raw Data area, loads the report screen, and imports the template into the FieldPulse account.
Templates save setup time. They do not remove the need to validate the result.
A Sales by Technician report still depends on how the business assigns technicians and attributes sales. An Estimate Conversion Rate report depends on consistent estimate statuses. An Overdue Invoice report depends on accurate due dates and payment status.
Use the template first. Skip rebuilding a common report from zero.
Then test five known records against the output. A report that correctly handles known examples is safer to use across thousands of records.
How FieldPulse job costing works
FieldPulse Job Costing compares projected and actual financial performance for each job. Projected performance can use estimates and material lists, while actual performance can use final invoices, timesheet or labor records, purchase orders, and configured costing sources.
The Job Costing tab shows anticipated and actual profit, margin, revenue, and costs. FieldPulse also separates costs into categories such as products and materials, labor, and commission.
Administrators configure the calculation under Company Settings, Jobs, and Job Costing. The settings determine which records drive projected cost, projected sales, actual cost, and actual sales. Commissions and discounts can also be included or excluded according to the company’s accounting approach.
That configuration is decisive.
Two companies can use FieldPulse and calculate actual job cost differently because one uses invoices as the cost source while another uses purchase orders or material lists.
Do not compare margins between companies or historical periods until the costing rules have been confirmed.
Why job margin can look too high
An unexpectedly high margin often means a cost source is missing.
The final invoice may be present while technician labor was never logged. Purchase orders may not be attached to the job. Materials may have been used physically but not recorded in the material list. A service item may also be categorized incorrectly.
FieldPulse allows a service item to be marked as Service – Labor, which classifies its associated costs as labor in job-costing calculations. Existing service items can be updated to use that item type.
Check these records:
- Final invoice
- Timesheets
- Material lists
- Purchase orders
- Commission
- Discounts
- Labor-designated service items
Do not reduce the selling price or manually overwrite the margin to make the report “look realistic.”
Correct the missing source. The displayed margin should follow the underlying records.
Why a manager sees incomplete job costing
Only Admin and Team Manager users can access the Job Costing tab, according to FieldPulse’s current documentation. Even when the tab is enabled, the visible calculation reflects only the records that the user has permission to access, including invoices, estimates, material lists, purchase orders, and timesheets.
This can produce an apparent calculation error.
An administrator sees labor, materials, and invoices. A Team Manager sees invoices but lacks access to purchase orders. Their job-costing views can differ because one source is unavailable to the manager.
Check permissions first. Skip changing the global costing configuration until both users are viewing the same source records.
Permissions protect business information, but they can also limit reporting completeness. Companies should decide whether managers need full costing visibility or only operational job access.
Exporting data for review
Raw Data Reporting is intended to let users select relevant fields, filter the results, and export the data for further review. FieldPulse supports reporting across numerous record types rather than requiring one universal export.
Exports are useful for accounting review, trend analysis, and reconciliation, but the exported file carries the same source and filter choices as the report.
Before relying on an export, record:
- Report type
- Date field
- Date range
- Status filters
- User or team filters
- Custom fields
- Export time
A spreadsheet without that context can be misread later.
The figure “$184,230” is not self-explanatory. It may represent invoices created, payments collected, completed-job sales, or a filtered technician group.
Keep the report definition with the file.
FieldPulse pricing and support
FieldPulse uses seat-based pricing. Full-access seats include the broader platform, including reporting, while field-only seats are intended for mobile employees who do not need back-office functions. Pricing is customized according to team size and setup.
A pricing request should identify the number of reporting users, managers, field technicians, business units, custom-dashboard needs, job-costing requirements, and accounting integrations.
The FieldPulse Help Center contains dedicated sections for Raw Data Reporting, Custom Reporting Dashboard, Pulse Dashboard, and Reporting Templates.
When reporting a data issue, include the report type, date field, filters, user role, expected record, and an example that is missing or calculated incorrectly. Do not include credentials or confidential payment information.
Frequently asked questions
Does FieldPulse have custom reports?
Yes. Raw Data Reporting supports many FieldPulse record types.
Why does my dashboard not match my invoice report?
The widget may use different dates, filters, statuses, or record definitions. Check the widget configuration and the report’s selected date field before comparing totals.
Can FieldPulse save filters?
Yes. Filters can be saved, and Job or Project filters can be stored as named views.
Does FieldPulse provide report templates?
Yes. Templates include sales, jobs, tax, payment, invoice, commission, and estimate reports.
Why is job profit too high?
Labor, materials, purchase orders, commissions, or other cost sources may be missing or configured incorrectly.
Can technicians see job costing?
Current documentation limits the Job Costing tab to Admin and Team Manager users.
Why do two managers see different margins?
Their permissions may expose different estimates, invoices, timesheets, purchase orders, or material lists.
What should I verify before exporting a report?
Confirm the record type, date basis, date range, filters, statuses, permissions, and several known records before using the export for a business decision.
