Forum Widgets
Recent Discussions
Suspend a recurring job account for non-payment
I own a residential lawn and yard maintenance business. Recurring job visits is our bread and butter. Mowing is about half of our revenue. We require a credit card on file, and auto-pay after each visit. We use Jobber's payment feature for this. This works really well, and eliminates accounts receivable. Occasionally a customer's credit card does not process. At that point, we receive an email from "The Jobber Team". The heading is: Automatic payment for "John Customer" failed. That is helpful. I would like to see the following in Jobber, with automated functions. The owner (me) could set parameters/thresholds for the activities. But I really want to automate this process! Instantly when card is declined: Customer automatically receives an email and text, letting them know that their card failed. The email and text include the invoice, payment link, and link to update their card. The email and text are re-sent every day until payment is received. The job is automatically suspended. In other words, the future visits are flagged or suspended in Jobber until the account is paid and a card is on file. A report that shows on the dashboard for all credit cards that were declined.
Invoice numbers and QBO
Am I the only person having problems with invoices not syncing to Quickbooks due to duplicate invoice numbers? Our old software allowed a job prefix that would allow for unique invoice numbers per customer. I've tried using the assigned job number plus a digit for the invoice number but even that returned a duplicate number in QBO. Jobber doesn't appear to allow anything but numbers -- no hyphen, period, etc. How are you overcoming this?
How Are Contractors Handling Processing Fees Legally with Jobber Payments?
How Are Contractors Handling Processing Fees Legally with Jobber Payments? This has been a huge topic for us, and I'm curious how other contractors are handling it. Every other contractor and supplier, even coffee stands, seems to be charging customers at least a 3% card processing fee. We won't bake these fees into our overhead costs because doing so makes us less competitive on estimates. We want to give our customers the choice of how to pay: cash, check, ACH, or credit/debit card. We thought we had solved this issue when Jobber told us we could simply add the processing fee as a line item on our invoices, giving customers a choice. That is what we have been doing until a customer recently questioned the 1% ACH fee and whether we are permitted to pass that charge along. Even more importantly, Jobber Payments doesn't distinguish between credit and debit cards for surcharging purposes. Debit cards cannot be subjected to credit card surcharges under payment-network rules, even when processed as credit. Yet Jobber Payments does not provide a way for us to distinguish between the two when applying processing fees. This puts us, as the contractor sending out the invoice with a 3% fee, in a legally vulnerable position. Jobber previously recommended adding the processing fee as a separate line item rather than building it into our pricing. However, this potentially exposes contractors to violations of payment-network rules since Jobber Payments accepts both credit and debit cards without distinguishing between them for surcharge purposes. How are we supposed to protect ourselves from the associated liability? Additionally, if Jobber Payments is advertised as being "included" in our program fee, why are we being charged these additional processing fees without the tools necessary to pass them along compliantly? This raises serious concerns for us. It would be great if Jobber Payments could be updated to automatically distinguish between debit and credit cards and allow customers to choose their payment method, including ACH, with any legally permissible associated fees clearly displayed. I'd really like Jobber to clarify how contractors are supposed to implement their recommendation to add processing fees as a separate line item without violating debit-card surcharge restrictions. How are other contractors handling this? Are you absorbing the fees, building them into your estimates, or have you found another solution that works within Jobber? We want to continue using Jobber Payments, but we also need a system that allows us to offer customers payment choices without exposing our businesses to unnecessary legal risks.
Invoice & payout
Jobber should make it easier and have the payment schedule on the app. As well as payout should be faster and with less of a fee and transaction fee. Why does the fee get charged to the company jobber should allow us to add it to the customers invoice. We are paying for a month membership why not priority your customers.
Setting up a "Recurring Job" with a warranty package in Jobber?
Hello, I'm new to the Recurring Visits in Jobber/ongoing billing. Essentially, I created an ongoing, yearly maintenance package for my carpet cleaning clients. It includes a full carpet cleaning and a 12 month warranty package on the areas that were cleaned. They will be signing up knowing it is a recurring package with auto-renewal. Meaning 12 months later, their card gets charged again and they receive their full maintenance clean plus another 12 months of spot cleanings. This package is still in phase 1 but I'm hoping for two main things : Create an invoice upon the initial clean and receive payment up front for the year (it is listed this way on the jobber quote. The ability to auto renew the package (automatically receive payment and re-book a full service job 1 year after the initial clean. Bonus: Be able to create additional visits for the spot treatments within the 1 year recurring job. This will help to track the time on site and gross margin for the entire package, not just the initial clean. I'm sure I won't be able to hit all of these marks but I would love to hear from those using yearly recurring visits or warranty programs within jobber.
The Jobber Time-Tracking Paradox: Why Time Capture Fails Basic Field-to-Invoice Engineering
Let’s skip the marketing gloss and look at the actual data flow of Jobber’s time-tracking feature. The core pitch for Jobber’s time-tracking and scheduling suite is simple: seamlessly capture billable hours, eliminate administrative friction, and protect your revenue. But when you examine how the software handles data structures from the field to the back office, it falls apart under basic operational logic. Consider this: the ONLY place the H:M format is actually used in Jobber is recording raw clock time (i.e., what time you started the timer, what time you stopped the timer or clocked out). Here is the technical reality of the workflow: 1. The Capture: The field timer records elapsed time natively in Hours and Minutes (H:M) (3h \ 42m). 2. The Disconnect: When you move to generate an invoice using an hourly line item, Jobber completely rejects its own captured format. It forces a hard stop, requiring a manual calculation of every time Hour + Minutes / 60 followed by manual entry in decimal hours 3.70. 3. The Payroll Dead End: It doesn't even serve internal payroll natively, because payroll engines also require decimal conversion to calculate wages and tax burdens. The Administrative Friction, Revenue Leak, and Hidden Costs Because H:M is stored in one format and billed in another, the software introduces the unnecessary manual conversion step that creates a massive cognitive load and a severe financial vulnerability: The Trap of Intuitive Error: When technicians or owners look at 42 minutes on a timer, human instinct or a hurried keystroke easily translates that into a raw decimal entry of 0.42 instead of the true mathematical fraction of 0.70. The Revenue Leak: Depending on the minute offset, an unverified entry can cause you to lose up to .43 decimal hours of billed labor on a single line item. At standard shop or field service rates, a simple keystroke mix-up translates to immediate, silent underbilling—leaving pure margin on the table through no fault of quality workmanship. The Actual Cost: The damage doesn't stop at an avoidable billing mistake. The true cost is the Recurring Added Labor And Cognitive Load imposed from now on—making it an actual hidden operational tax built right into your software subscription. The Question for Jobber Product & Support: If a software's native time-tracking mechanism records time in a format (H:M) that is completely incompatible with both invoicing and payroll requiring a manual calculation and translation step, how is it classified as an automated workflow tool rather than a digital stopwatch that creates administrative drag and revenue exposure? If the system captures the data, why is the user forced to manually calculate and bridge the translation gap just to get paid accurately? Let's hear how the product logic defends a feature that forces manual math to fix its own format disconnect.
