Who this article is for: Authority Users
Overview
SwiftComply Backflow produces the backflow report your state requires at the end of the year. The report itself isn't something you build — SwiftComply handles the template and the calculations. Your job is to make sure the data it pulls from is complete and accurate. This article walks through the full flow so you know where your data comes from, how the report assembles it, and how to avoid the most common year-end surprises.
For the related, more hands-on articles:
Need to enter or edit state-specific values on an assembly? See Using Custom and State Report Fields on Assemblies.
Need to run or save the report itself? See Running and Generating State Reports.
The End-to-End Flow
State reporting in SwiftComply follows a consistent pattern regardless of which state you're in:
Your state is configured. SwiftComply sets your organization's state on your org profile and loads the matching report template on the back end. This happens during setup.
State-specific fields appear on your records. The fields your state requires show up in a dedicated accordion on assembly detail pages (and, in some states, on location detail pages).
Your team fills in the fields throughout the year. This happens as part of normal work — adding new assemblies, accepting test reports, updating existing records.
You run the report from the State Reports page. SwiftComply aggregates the data, drops it into the state's template, and renders the report on screen. No separate generate step.
📝 The biggest gotcha with state reporting is discovering at year end that fields weren't being filled in throughout the year. Once you know which fields feed your state's report, build the habit of checking them every time you touch an assembly or accept a test.
Where the Data Comes From
State reports pull from multiple record types in SwiftComply. The exact mix depends on your state's template, but the common sources are:
Source | What It Feeds |
Assembly records | Assembly type, make, model, size, compliance status, and State Report Properties on each assembly |
Location records | Address, premise type, and (in some states) location-level State Report Properties |
Accepted test reports | Tested-on dates, pass/fail results, and fields filled in on the test form |
Accepted surveys | Survey results and (where applicable) survey-driven compliance data |
Compliance rules | How the report counts compliant vs. overdue assemblies based on your Next Test Due logic |
For the fields specifically labeled "State Report Properties" on the assembly Details tab, see Using Custom and State Report Fields on Assemblies.
Keeping State Report Data Accurate
Track as you go
When you add a new assembly or accept a test report, check the State Report Properties accordion on the assembly's Details tab. Filling those fields in right then (while the record is already open) prevents the year-end scramble.
Check data quality before the report is due
When you run a state report, SwiftComply flags data issues at the top — duplicate serial numbers, bypass assemblies without a target, bypass targets at the wrong location, and similar. Each flag has a (view) link that jumps to the problem record so you can fix it.
Run the report earlier in the year than you strictly need. Giving yourself time to chase down data-quality flags is the single biggest difference between a smooth submission and a scramble.
Understand what the report pulls
Every state's report is different — Washington's Part 3B/3C structure doesn't look like California's or Colorado's. Once you've run yours for the first time, spend a few minutes reviewing the sections so you know which SwiftComply fields feed each count. That way, when something's off, you know where to look.
Changing What's in the Report
State report templates are configured by SwiftComply — authority users can't modify them from the UI. If you think the report is missing data, double-counting something, or miscategorizing an assembly, contact your CSM. We can look at the template and work with you on adjustments.
FAQ
Q: I'm in a state that's not currently supported. What appears on my assembly records?
A: No State Report Properties accordion appears on the Details tab, and no state report is available from the State Reports page. If you need state reporting added, let your CSM know — they can scope the work to add your state's template.
Q: If I correct historical data, will past state reports update automatically?
A: Yes. State reports pull live data from SwiftComply the moment you render them. If you correct data after you already submitted the report to your regulator, re-running the same year will show the corrected numbers. That's why saving a PDF at submission time matters — see Running and Generating State Reports.
Q: Can I generate a state report for multiple years at once?
A: No. You run one year at a time from the Select a Year dropdown. Switching years re-renders instantly, though, so comparing years is fast.
Q: Where exactly do I find the state-specific fields on an assembly?
A: On the assembly detail page → DETAILS tab → State Report Properties accordion (expanded by default). See Using Custom and State Report Fields on Assemblies for the full walkthrough.