FieldPulse recurring jobs, explained: setup, what you can change later, and where a maintenance agreement needs more

Published September 2, 2026 · Help-center quotes verified on September 2, 2026

• Every step and limit on this page was checked against FieldPulse's help center, changelog and feature pages on September 2, 2026, with links at the bottom. FieldPulse publishes no prices, so there's no cost math here; what's known about the quote is on the FieldPulse pricing page.
• I build Deepsel, a maintenance-agreement tool that runs beside FieldPulse. That's relevant to exactly one section of this page, and it's labeled.

FieldPulse recurring jobs create a job once and repeat it on an interval you choose, with a customer, a workflow, assigned techs and an optional end date. They schedule work. Recurring Billing collects the money on its own calendar, and Maintenance Agreements tie visits, billing and assets to one record. None of the three counts visits owed against visits delivered.

That's the short version. The rest of this page is the setup, click by click, and the three places where a recurring job stops being a maintenance agreement.

Does FieldPulse have recurring jobs, and which plans include them?

Yes, and the help center's own description is the plainest one: "you can create a job once, and then set it to re-occur on a regular basis at an interval you choose."¹ The feature page pitches it for "repeat service calls, maintenance contracts, and inspections," with "daily, weekly, monthly, or custom recurrence intervals," and says a recurring job can link to a project and to Recurring Billing.²

Which package it sits in, I can't tell you. FieldPulse's pricing page lists Essentials, Professional and Enterprise, each with a Request Pricing button, and the feature list under every package runs from Customer Management to Open API without naming recurring jobs or maintenance agreements.³ The migration guides for shops leaving Jobber and Housecall Pro both map "Recurring Job" straight across to "Recurring Job," and the Housecall Pro guide maps "Service Plan" to "Maintenance Agreement."⁴ That reads like a core feature. Get it written on the quote anyway. The seat-based quote and the one-year contract are covered on the FieldPulse pricing page.

How to set up a recurring job in FieldPulse

Six steps on the web app, all from FieldPulse's own guide.¹ Menu and field names are theirs.

1. Open the Recurring list. Go to Jobs in the left-side menu, then select Recurring from the top menu. This page lists every existing recurring job and is where you edit them. Click Create Recurring Job. (The other route: Jobs, Create Job, then choose Create Recurring Job instead of filling in a one-off.)
2. Link a customer. Pick an existing customer or create one. The location and contact fill in from the customer record.
3. Name the work and pick its path. Enter a title that describes the job, then select the Workflow and Status Action Flow (FieldPulse calls this ClearPath) that each generated job should follow.
4. Set the frequency and the first date. Choose the interval, then a first occurrence and a start time. Pick No End Date if it should run until you stop it, or set the date and time of the last occurrence.
5. Assign and annotate. Select team members, which the guide notes "can be changed for future occurrences," and add job tags and notes. Press Save.
6. Bill it, if you want it billed. The recurring job now appears on your schedule and under Jobs. To attach money to it, open the recurring job record and choose Actions, then Create Recurring Billing.⁵ More on what that does below.

One rule from the FAQ worth knowing before you build a "third Tuesday" schedule. If a recurring job is set for a weekday occurrence that doesn't exist in a given month (the guide's example is "5th Monday"), "the job will skip that occurrence entirely. There is no fallback to the nearest or last available day."¹ Monthly by date is safer for tune-ups.

On mobile, the Recurring sub-tab arrived in December 2024, and the release note says "Users can view, edit, and create all recurring jobs from their mobile devices."⁶ So a tech can set one up from the driveway. The billing can't be, and that's the next section but one.

What you can and can't change after it's created

You can edit the series and you can archive it. A July 2024 release added both routes:

"Modify your recurring jobs from the job record by clicking the edit button or selecting Actions > Archive Recurring Job to archive the job. Edit or archive jobs from the Recurring Jobs tab as well by using the pencil (edit) or trash can (archive) icons."⁷

Assignments are flexible: team members "can be changed for future occurrences."¹ And archiving, rather than deleting, is the documented way to stop a series, which is friendlier than some platforms where ending a recurring schedule wipes the history.

What the help center doesn't describe, as of September 2, 2026: editing one occurrence without touching the rest, skipping a single date, what happens to already-generated jobs when you change the frequency, and how far ahead future jobs are generated. The recurring jobs guide, both release notes and the current changelog are silent on all four.^{1, 6, 7} That doesn't mean FieldPulse can't do them. It means you watch the rep do each one on a live series before you move 150 agreement customers onto it. Ask specifically: "Push this one spring visit two weeks without moving the fall one."

How recurring jobs bill in FieldPulse

A recurring job by itself bills nothing. It creates job records, and each one is invoiced the way any FieldPulse job is invoiced, when someone invoices it. Automatic money comes from a second object, Recurring Billing, which you enable under Company Settings, Features & Plugins, and attach to the recurring job from its Actions menu.⁵

Recurring Billing has its own settings: an Invoice Frequency ("Weekly, Monthly, Annually, etc."), an Occurrence Date, a Starting Month, auto-send or preview, a default status of Draft or Invoiced, and an end after a set number of occurrences or on a date, after which "Records with a status of 'Completed' cannot be edited."⁵ Payment is either a link on each invoice or an automatic charge to a saved card or ACH account.⁵ Saving a payment method requires FieldPulse Payments, ACH on file has to be switched on by a FieldPulse team member, and "Recurring Billing setup is web app only."⁸

Here's the sentence that matters for agreement work. Recurring Billing runs pay-as-you-go: "the system creates one invoice at a time, right on the day it's due," and "the behavior is the same across all three" cases, standalone, linked to a Maintenance Agreement, or created from one.⁵ The invoice fires on its date. It doesn't check whether the visit happened. Linking a recurring job and a recurring billing puts them on the same customer; it doesn't make one wait for the other.

And when a card fails, nobody really has a system, FieldPulse included. From the Recurring Billing FAQ:

"Yes, the recurring billing will continue. The invoice will not be marked as paid, and if you have notifications set up (outside of FieldPulse), you should also receive an alert from the payment provider."⁵

No retry. No text to the customer. The recurring job keeps generating visits for a member whose last two invoices sit unpaid. Two more mechanics from the saved-payment guide: deleting a card from the customer record "doesn't remove it from existing recurring invoices," and stopping automatic charges means opening the Recurring Billing record and removing the method or ending the schedule.⁸ Expired cards do get a red expiry date on the customer record.⁸

The one lever FieldPulse gives you is Customer Communications. Its automatic triggers include "When invoice is overdue and not yet fully paid," which fires "on the date an invoice is past due" with the invoice link, and "Set Time Prior to job Start Date/Time," which is how appointment reminders go out for any scheduled job.⁹ Turn the first one on and a declined recurring charge at least produces a message.

Recurring jobs vs Recurring Billing vs Maintenance Agreements vs a full agreement ledger

FieldPulse has three objects that touch repeat work. The Maintenance Agreements record is the most complete: a service frequency and optional end date, a job template, a billing frequency with price per bill, automatic email reminders, linked assets that copy onto every visit, an e-sign contract, and the option to auto-create "a rolling basis of 12 months of future occurrences," left unscheduled by default.¹⁰ That module gets its own line-by-line treatment on the FieldPulse maintenance agreements page. Here the point is where each object stops.

Read the middle column carefully. Recurring Billing was built, in FieldPulse's words, "specifically for our customers who regularly perform maintenance work, such as landscaping and pool maintenance."⁵ Weekly mowing is a subscription. An HVAC agreement is a prepaid obligation with a deadline. Same engine, different promise.

When recurring jobs are enough, and when they aren't

Enough: any work that happens on a fixed interval, at a fixed address, whether or not anyone calls first. A monthly filter route for a property manager. Quarterly commercial PM on a rooftop unit with standing access. A weekly pool or lawn stop. The recurring job puts it on the calendar, and if you want it billed on autopilot you attach Recurring Billing and let the invoices fall on their dates. That's what the feature was written for.^{2, 5}

Not enough: a residential maintenance agreement. Three reasons, and each one is a place the recurring job goes quiet.

• The visit needs a homeowner. A recurring spring tune-up generates a job at 9 a.m. on a date the customer never agreed to. Somebody in the office still calls, texts or emails every member to land a real slot, and the appointment-reminder trigger only helps once the job has a confirmed time.⁹ With 200 agreements that's 400 conversations a year that the schedule doesn't start for you.
• The money and the visit don't know about each other. Recurring Billing charges on its date, the job happens on its date, and nothing reconciles the two.⁵ A member who paid for two visits and got one looks, in FieldPulse, like a customer with a paid invoice and a job that got cancelled in a busy no-cool week.
• Nothing ends loudly. The series has an end date or it doesn't. No one is told 60 days out that a plan year is closing with a paid visit still undelivered, and no one is told when a card has failed twice.^{1, 5} Agreements lapse silently, and you find out on the emergency call in July when the customer mentions they "have a plan."

I looked for FieldPulse shops complaining about any of this on Reddit (r/HVAC, r/ProHVACR, r/Plumbing, r/electricians, r/smallbusiness) and found no thread about recurring jobs at all, positive or negative. So I won't pretend there's a pile of pain here. There's a paperwork gap, the same one I keep finding across platforms; see how to track HVAC maintenance agreements for the five fields the ledger needs.

The workaround shops on FieldPulse run

Two shapes, depending on whether Maintenance Agreements is switched on in your account.

1. Recurring job plus tag plus sheet. One recurring job per member (spring and fall as two series, or one series every six months), a job tag such as "Agreement" so the Jobs list filters cleanly, Recurring Billing on the card if the member pays monthly, and a spreadsheet with one row per agreement: plan, price, renewal date, visits owed, visits delivered, last visit, card status. The free version with those columns and a visits-at-risk filter is here. Build the job from a template with the tune-up form attached, so every generated visit carries the checklist.¹¹
2. Maintenance Agreements plus a reconciliation sheet. Build the agreement with Automatic job creation so the 12 months of visits appear unscheduled, schedule them from the hourglass tool as members book, attach Recurring Billing, and link the assets so filter sizes ride along on every job.^{10, 12} Keep the same sheet for the three lists the module doesn't produce: cards that failed this month, plan years closing in 60 days with a visit still unscheduled, and members with fewer visits delivered than paid. The module's documented and undocumented list, plus eight demo questions, is on the FieldPulse maintenance agreements page.

Either way, put the overdue-invoice trigger on.⁹ It's the closest thing FieldPulse has to a failed-card message, and it costs nothing.

Running the agreement ledger beside FieldPulse

This is the part I have a product in, so weigh it accordingly. Deepsel is agreement software that works beside FieldPulse. It owns the one record FieldPulse's three objects don't add up to, and it leaves scheduling, dispatch and invoicing exactly where they are.

There's no FieldPulse integration, and I'd rather say that plainly than imply one. You export your customer or agreement list from FieldPulse (a report export works, or the spreadsheet you're running today), and Deepsel imports it. From there it keeps the ledger: plan, tier, covered equipment by model and serial, filter sizes off a nameplate photo, card on file, renewal date, and visits owed vs delivered per unit. It charges renewals itself, retries a failed card, and flags the ones that stay failed. Each spring and fall it emails every member who's due (texts on Pro) a reminder that carries your FieldPulse booking-portal link or your office number, so the member books and your dispatcher creates the FieldPulse job the way they'd create any other. Before a paid visit expires unused, you and the member both get warned.

Pricing is flat: Starter is $79 a month with unlimited users, Pro is $159 (coming soon; Starter is live), and there's no percentage taken on membership revenue. I can't put a stack price next to FieldPulse because FieldPulse doesn't publish one. If your recurring jobs are doing the scheduling fine and the sheet is what's hurting, $79 a month beside the package you already have is the thing to price. Details are on the pricing page; the cross-platform comparison is in the best HVAC maintenance agreement software roundup.

Frequently asked questions

Does FieldPulse have recurring jobs?

Yes. The help center describes the feature as a way to "create a job once, and then set it to re-occur on a regular basis at an interval you choose."¹ Each recurring job carries a customer, a title, a workflow, a start date and time, an optional end date, assigned team members, tags and notes. The feature page lists daily, weekly, monthly and custom intervals.² None of FieldPulse's three package feature lists names recurring jobs, so confirm the feature on your quote.³

How do I set up a recurring job in FieldPulse?

Go to Jobs, select Recurring, and click Create Recurring Job. Link a customer, enter a title, pick a Workflow and Status Action Flow, set the frequency, the first occurrence and start time, then either No End Date or the last occurrence. Assign team members, add tags and notes, and press Save.¹ To bill it, open the record and choose Actions, Create Recurring Billing.⁵

Can I edit or stop a recurring job in FieldPulse?

Yes. Since July 2024 you can modify a recurring job from the job record's edit button or archive it with Actions, Archive Recurring Job; the Recurring Jobs tab has a pencil icon to edit and a trash can to archive each series.⁷ Team members can be changed for future occurrences.¹ The help center doesn't describe editing a single occurrence on its own or skipping one date, so test those on the demo.

Do FieldPulse recurring jobs bill the customer automatically?

Not on their own. A recurring job creates job records. To bill automatically you attach Recurring Billing (Actions, Create Recurring Billing), set a weekly, monthly or annual invoice frequency, and choose a payment link on each invoice or an automatic charge to a saved card or ACH account.⁵ Saved payment methods need FieldPulse Payments, and Recurring Billing setup is web app only.⁸ The billing runs on its own dates whether or not the job happened.⁵

What happens when a customer's card declines on a FieldPulse recurring billing?

Per the Recurring Billing FAQ, "the recurring billing will continue. The invoice will not be marked as paid," and any alert comes from the payment provider outside FieldPulse.⁵ No retry and no customer message are documented. The recurring job keeps generating visits regardless. The workaround is a Customer Communications trigger for overdue invoices, which fires on the date an invoice becomes past due.⁹

What is the difference between recurring jobs and maintenance agreements in FieldPulse?

A recurring job is a schedule: the same job, repeated on an interval, with no price, no card and no count of visits.¹ A Maintenance Agreement is a record on the customer that holds the service frequency, an optional end date, a job template, a billing frequency with price per bill, automatic email reminders, linked assets and an e-sign contract, and it can auto-create 12 months of visits as unscheduled jobs.¹⁰ Neither one counts visits owed against visits delivered or warns before a paid visit expires.

Can I create recurring jobs on the FieldPulse mobile app?

Yes. The Recurring sub-tab came to the mobile app in December 2024, and the release note says users "can view, edit, and create all recurring jobs from their mobile devices."⁶ The exception is the money: "Recurring Billing setup is web app only,"⁸ so the billing side of a recurring job gets set up at a desk.

Does Deepsel integrate with FieldPulse?

No. Deepsel imports your customer and agreement list from a FieldPulse report export or a spreadsheet, keeps the ledger (plan, equipment, visits owed vs delivered, card on file, renewal date), charges renewals with retries, and emails members each season with your booking link or office number. Your office creates the booked visit in FieldPulse as a normal job. FieldPulse stays your system for scheduling, dispatch and invoicing.

Sources

1. FieldPulse Docs, "Recurring Jobs": "you can create a job once, and then set it to re-occur on a regular basis at an interval you choose"; create from Jobs, Recurring, Create Recurring Job or from Jobs, Create Job, Create Recurring Job; link a customer, title, Workflow and Status Action Flow (ClearPath), frequency, first occurrence and start time, "No End Date" or last occurrence; team members "can be changed for future occurrences"; tags and notes; "Your recurring job will now be added to your schedule and listed under Jobs"; FAQ: a "5th Monday" occurrence that doesn't exist in a month is skipped, "There is no fallback to the nearest or last available day." help.fieldpulse.com, retrieved September 2, 2026.
2. FieldPulse, "Job Management Software" feature page, "Automate Recurring Jobs" section: "Set up recurring jobs to save time on repeat service calls, maintenance contracts, and inspections"; "Flexible Scheduling Options: Choose daily, weekly, monthly, or custom recurrence intervals"; "Link to Projects"; "Link to Recurring Billing: Connect recurring jobs with invoices." fieldpulse.com/features/job-management, retrieved September 2, 2026.
3. FieldPulse pricing page: Essentials, Professional and Enterprise packages, each "Request Pricing"; package feature lists (Customer Management, Scheduling & Dispatching, Work Order Management, Estimates & Invoices, Mobile App, Workflow Automation, Project Management, QuickBooks Sync, Multi-location Management, Open API) with no recurring jobs or maintenance agreements entry; "FieldPulse is seat-based." fieldpulse.com/pricing, retrieved September 2, 2026.
4. FieldPulse Docs, "Jobber to FieldPulse: Migration Guide" (terminology table: "Recurring Job" to "Recurring Job"; "Automatic Payments" to "Recurring Billing with Card on File"), help.fieldpulse.com; "HouseCall Pro to FieldPulse: Migration Guide" (terminology table: "Service Plan" to "Maintenance Agreement"; "Recurring Job" to "Recurring Job"), help.fieldpulse.com. Both retrieved September 2, 2026.
5. FieldPulse Docs, "Recurring Billing": "created this feature specifically for our customers who regularly perform maintenance work, such as landscaping and pool maintenance"; enable under Company Settings, Features & Plugins; fields Invoice Frequency ("Weekly, Monthly, Annually, etc."), Occurrence Date, Starting Month, Automatically Send Invoice to Customer, Default Invoice Status (Draft or Invoiced), Next Occurrence; payment options "Include a Payment Link with each Invoice" or "Automatically charge the customers credit card that is on file"; end after a number of occurrences or on a date, status Completed, "Records with a status of 'Completed' cannot be edited"; "Adding Recurring Billing to a Recurring Job" via Actions, Create Recurring Billing on the recurring job record; FAQ "the system creates one invoice at a time, right on the day it's due" and "the behavior is the same across all three"; FAQ on a declined card, "Yes, the recurring billing will continue. The invoice will not be marked as paid, and if you have notifications set up (outside of FieldPulse), you should also receive an alert from the payment provider." help.fieldpulse.com, retrieved September 2, 2026.
6. FieldPulse Help Center, "December 2024" release notes, "Recurring Jobs Are Now on Mobile": "The Recurring sub-tab is now available on our mobile app! Users can view, edit, and create all recurring jobs from their mobile devices." help.fieldpulse.com, retrieved September 2, 2026.
7. FieldPulse Help Center, "July 2024" release notes, "Recurring Job Updates": "Modify your recurring jobs from the job record by clicking the edit button or selecting Actions > Archive Recurring Job to archive the job. Edit or archive jobs from the Recurring Jobs tab as well by using the pencil (edit) or trash can (archive) icons." help.fieldpulse.com; the same item appears in the current changelog, help.fieldpulse.com/changelog. Both retrieved September 2, 2026.
8. FieldPulse Docs, "Saving a Payment Method on File": prerequisites "FieldPulse Payments is enabled in your account" and "ACH must be enabled by a FieldPulse team member"; "Saved payment methods power recurring billing too"; "Recurring Billing setup is web app only"; expired cards "show a red expiry date with an error icon"; troubleshooting row "Recurring billing keeps charging after the method was deleted from the customer record: Removing a method on the customer record doesn't remove it from existing recurring invoices"; FAQ "How do I stop automatic recurring payments? Open the Recurring Billing record and either remove the saved payment method or end the recurring schedule." help.fieldpulse.com, retrieved September 2, 2026.
9. FieldPulse Docs, "Customer Communications": templates for "Appointment reminders"; automatic triggers including "When invoice is overdue and not yet fully paid (with Dynamic Invoice Link)," which "will send on the date an invoice is past due and include the invoice link," "When job is newly created," "Set Time Prior to job Start Date/Time," and "When job status is changed to [Status]"; without Engage, triggers send "through a no reply toll-free number from FieldPulse." help.fieldpulse.com, retrieved September 2, 2026.
10. FieldPulse Docs, "Maintenance Agreements": "Maintenance Agreements let you set the schedule once and FieldPulse handles the job creation, reminders, and billing"; Service Frequency with optional End Date; Occurrence Creation with a Job Template and a Job Creation Method of Manual or Automatic, "maintaining a rolling basis of 12 months of future occurrences. These jobs will be left unscheduled by default"; Recurring Billing toggle; Billing Frequency and price per bill with the annual price calculated; "Automatic email service reminders can be sent to customers and team members"; linked Assets applied to every generated occurrence; Contracts tab with e-signature; This Month and Next Month tabs and the hourglass scheduling tool. No renewal-reminder setting, member-discount field or visits-owed count appears in the guide. help.fieldpulse.com, retrieved September 2, 2026.
11. FieldPulse Docs, "Job Templates": "Save recurring jobs as templates with prefilled details, forms, and material lists"; templates pre-fill title, location, notes, scheduling parameters, custom forms and material lists; edit or delete under Jobs, Templates. help.fieldpulse.com, retrieved September 2, 2026.
12. FieldPulse Docs, "Managing Unassigned & Unscheduled Jobs": create a job with Clear Dates to leave it unscheduled; view from Jobs, Unassigned, or from the hourglass icon on any Schedule view; drag an unscheduled job onto a date and time to schedule it. help.fieldpulse.com, retrieved September 2, 2026.