Summary
iPaaS.com Transactions of type Invoice can be transferred from Jobber invoices through Jobber invoice events, a scheduled poll or a Manual Sync. Each transfer sends the invoice number, status, totals, dates and the client's customer and email, and five child collections send the invoice's line items, payments, taxes, billing address and discount in the same transfer. Your accounting and other connected systems then receive the work you billed in Jobber through their own collections.
The parent collection is Add/Update Jobber Invoice TO iPaaS.com. Its children are Add/Update Jobber Invoice Line TO iPaaS.com, Add/Update Jobber Invoice Payment TO iPaaS.com, Add/Update Jobber Invoice Tax TO iPaaS.com, Add/Update Jobber Invoice Address TO iPaaS.com and Add/Update Jobber Invoice Discount TO iPaaS.com.
ID Format
Manual Sync ID Format
On the iPaaS.com Manual Sync page, enter the number at the end of the invoice's web address in Jobber: open the invoice in Jobber and enter the digits that follow /invoices/ in the address. The invoice's Jobber API id is accepted too, and both update the same linked transaction.
Web address number: the digits only, as they appear after /invoices/ in the invoice's Jobber web address. For the invoice at secure.getjobber.com/invoices/179946883, enter 179946883.
Jobber API id: the invoice's encoded Jobber API id, the long string of letters and digits Jobber gives apps for the invoice, for example Z2lkOi8vSm9iYmVyL0ludm9pY2UvMTc5OTQ2ODgz.
The child collections have no Manual Sync of their own: resend the invoice to resend its lines, payments, taxes, address and discount.
External ID Format
After a successful transfer, iPaaS.com saves the invoice's Jobber API id (for example Z2lkOi8vSm9iYmVyL0ludm9pY2UvMTc5OTQ2ODgz) as the external ID on a dedicated external-ID record for the transaction. Later transfers of the same invoice find the transaction through that link and update it instead of creating a second one. The invoice number is not the link: it is carried in TransactionNumber and must be unique (see Invoice Numbers under System Caveats).
The child records have no external-ID link of their own: they are kept on the transaction and updated with it, so a changed invoice keeps the same line, address and discount records instead of adding new ones.
Deleted Record Support
Deleting an invoice in Jobber does not delete the iPaaS.com transaction, and these collections include no delete mappings. Delete is not implemented: a delete request stops with JOBR-VALD-1004 ("Deleting invoices or work requests in Jobber is not supported by this integration."). Void the invoice in Jobber instead; the void is sent as a Cancelled status. An invoice voided before it was ever sent to iPaaS.com is skipped and creates no transaction.
Custom Field Support
Jobber invoice custom fields can be sent to iPaaS.com transaction custom fields on the parent collection. None are mapped by default. To send one:
In iPaaS.com, create the transaction custom field that should receive the value.
In the subscription's custom fields for Jobber invoices, add a custom field whose name is the Jobber custom field's label exactly as Jobber shows it (for example PO Number).
In Add/Update Jobber Invoice TO iPaaS.com, add a Field mapping from that Jobber custom field to the iPaaS.com transaction custom field, and save.
Every Jobber custom field type arrives as text. A custom field with no value in Jobber is sent empty. The child collections do not support custom fields.
Mapping Collection Status
Status: Enabled (the parent and all five children).
Trigger Events: the Jobber events INVOICE_CREATE (an invoice is created in Jobber) and INVOICE_UPDATE (an invoice is changed in Jobber, including a payment recorded on it), and the poll scope INVOICE_POLL (invoices changed in Jobber since the last poll). The child collections have no trigger of their own; they run with the invoice.
Whether an invoice is added or updated depends on whether it is already linked to an iPaaS.com transaction, not on which event arrived.
Duplicate or Conflicting Mappings
Add/Update Jobber Request FROM iPaaS.com sends iPaaS.com orders to Jobber as work requests, not as invoices, so the two collections do not write the same records. If a store or point-of-sale system already sends an order to your accounting system, and the work for that order is also invoiced in Jobber, the accounting system receives the sale twice: choose one side to send each sale.
No other collection writes invoices, invoice lines, payments, taxes, addresses or discounts TO iPaaS.com. If you add a second collection of any of these types, give the two filters no record in common: every collection whose filter matches a record runs, and each one replaces the whole record.
Collision Handling
These collections have no Collision Handling Method. An invoice is matched to its transaction only through the external-ID link described under ID Format. An invoice whose number another iPaaS.com transaction already holds is refused as a duplicate and is not linked (see Invoice Numbers under System Caveats). The invoice's client is matched separately, by email, when the client is sent first (see Prerequisite Handling).
Unmapped Field Overwrite Risk
Warning: iPaaS.com replaces the whole record on each update, so any field a collection does not map is emptied every time an invoice is sent. A value another system put in one of these fields is cleared on the next update from Jobber. The same applies to any mapping you remove.
Add/Update Jobber Invoice TO iPaaS.com: ShippingAmount and TotalQty.
Add/Update Jobber Invoice Line TO iPaaS.com: DiscountAmount, DiscountPercent, EstimatedTaxAmount, OriginalUnitPrice, QtyShipped, TaxPercent and Weight. Jobber does not hold these values on an invoice line.
Add/Update Jobber Invoice Payment TO iPaaS.com: the default template maps every payment field.
Add/Update Jobber Invoice Tax TO iPaaS.com: OriginalAmount. Jobber does not hold this value.
Add/Update Jobber Invoice Address TO iPaaS.com: Address3, Company, FirstName, LastName, IsPrimaryShipping, ShipDate, ShippingAmount, ShippingMethod and ShippingMethodDescription.
Add/Update Jobber Invoice Discount TO iPaaS.com: CouponCode and DiscountMethod.
To keep a value another system sets, add a Dynamic Formula mapping for that field to the collection, for example:
return DestinationValue != null ? DestinationValue.ShippingAmount : null;
Use the field's name in place of ShippingAmount.
Supported Child Collections
Parent: Add/Update Jobber Invoice TO iPaaS.com
Add/Update Jobber Invoice Line TO iPaaS.com: the invoice's line items, each with its item's iPaaS.com SKU.
Add/Update Jobber Invoice Payment TO iPaaS.com: the payments recorded on the invoice in Jobber.
Add/Update Jobber Invoice Tax TO iPaaS.com: the invoice's tax, one record per tax rate.
Add/Update Jobber Invoice Address TO iPaaS.com: the invoice's billing address, when it has a street or a city.
Add/Update Jobber Invoice Discount TO iPaaS.com: the invoice-level discount, when the invoice has one.
Each child moves with the invoice and is kept on its transaction; none can be sent on its own. A collection that tries to send a child record on its own stops with JOBR-VALD-1017.
System Caveats
Jobber Caveats
Only issued invoices: draft invoices are skipped by the parent filter. Voided invoices are sent, so a void reaches iPaaS.com as Cancelled. Jobber quotes and jobs are not sent.
One-off lines need the Fallback Line SKU: a line typed on the invoice with no saved Jobber item takes the SKU in the subscription's Fallback Line SKU setting. When that setting is empty, the invoice stops with JOBR-VALD-1013 (see Fallback Line SKU under Setup Requirements).
Payments are recorded in Jobber: payments reach iPaaS.com only as Jobber records them on the invoice, by hand or through Jobber Payments. Jobber's bookkeeping entries on an invoice (a void, a bad-debt write-off, a correction) are not payments and are not sent; the invoice's status carries them.
Billing address only: Jobber invoices carry a billing address and a service property. Only the billing address is sent, so the transaction has no shipping address from Jobber.
One discount per invoice: Jobber holds a single invoice-level discount, so a transaction from Jobber has at most one discount record.
Tax group amounts: Jobber gives apps the invoice's total tax, not the amount for each rate in a tax group, so each group record's amount is calculated (see Add/Update Jobber Invoice Tax TO iPaaS.com). It can differ by a cent from the per-rate figure Jobber shows; the total always matches.
Large invoices: an invoice with more than 100 lines (JOBR-VALD-1009) or more than 50 payment records, bookkeeping entries included (JOBR-VALD-1014), is not sent. Enter that invoice in the receiving system by hand.
Rate limiting: Jobber limits how much an app can request from its API in a short time. When the limit is reached, the transfer is rescheduled automatically to run once the limit resets; no action is required.
iPaaS.com Caveats
A customer, company or email on every transaction: iPaaS.com refuses a transaction with none of them. Keep CustomerId and EmailAddress mapped.
Every line needs a product SKU: iPaaS.com refuses a Product line whose SKU is not one of your iPaaS.com products, so a Fallback Line SKU that names no product stops the invoice.
No payment date: iPaaS.com transaction payments have no date field, so the date a payment was recorded in Jobber does not reach iPaaS.com.
An invoice voided before it was sent: it is skipped and creates no transaction. iPaaS.com may log an error-level line saying the transfer is missing its payload data; no transfer error is recorded and nothing needs fixing.
Invoice Numbers
Jobber numbers each account's invoices 1, 2, 3 and so on, while iPaaS.com transaction numbers must be unique across your whole company. An invoice whose number another iPaaS.com transaction already holds, for example one another system sent, is refused with NFND-1029 ("Duplicate transaction found!"), is not linked, and each retry is refused the same way until the numbers no longer clash.
If another system also sends plain numbers, change the TransactionNumber mapping from a Field mapping to a Dynamic Formula that adds a prefix before the first invoice is sent. The formula is the prefix in quotes, a + and the Jobber invoice number:
return "JOB-" + InvoiceNumber;
With this formula, Jobber invoice 1042 is sent as transaction number JOB-1042. Choose a prefix no other system uses. iPaaS.com checks the number only when a transaction is created, so changing the formula after invoices have been sent can leave two transactions with the same number.
Setup Requirements
iPaaS.com Configuration
Fallback Line SKU: before the first invoice is sent, create (or pick) an iPaaS.com product for one-off lines, for example one with SKU MISC-SERVICE, enter that SKU in the subscription's Fallback Line SKU setting and click Apply. One-off lines, and item lines whose item could not be sent to iPaaS.com, then carry MISC-SERVICE. The line's description (for example Lawn mowing - Front and back yard) keeps those lines readable when they share the SKU.
TransactionNumber formula: choose the TransactionNumber mapping (plain number or prefixed) before the first invoice is sent (see Invoice Numbers).
Payment Method translation: set every entry of the Jobber Payment Type TO iPaaS.com translation to one of your own iPaaS.com Payment Methods before the first invoice with a payment is sent (see Add/Update Jobber Invoice Payment TO iPaaS.com).
Client and item collections: keep Add/Update Jobber Client TO iPaaS.com and Add/Update Jobber Product or Service TO iPaaS.com in place, with filters that include the clients and items your invoices use: the invoice sends its client and items through them.
Transfer triggers: in the subscription configuration's Inbound Data Flows section, turn on the Jobber events INVOICE_CREATE and INVOICE_UPDATE. When you turn them on, iPaaS.com registers them with your Jobber account, and invoices created or changed in Jobber are sent within moments. No automatic transfers occur until these events are turned on.
Poll (optional): create a scheduled Webhook Poll Request event for this subscription with the poll scope INVOICE_POLL and the Filter left empty (see Jobber Installation Instructions). Once a day is a sensible safety net with the Jobber events on, or to load existing invoices the first time. The Transaction Poll Days setting controls how far back the first poll looks.
Jobber Configuration
No Jobber-side setup is needed beyond connecting the subscription to your Jobber account (see Jobber Installation Instructions). Make sure each client you invoice has an email address in Jobber.
Integration Flow
An invoice is created or changed in Jobber (the INVOICE_CREATE or INVOICE_UPDATE event), found by the INVOICE_POLL poll, or entered on the Manual Sync page.
The integration reads the invoice from Jobber, with its line items, payments, tax, billing address, discount and custom fields. An invoice with more than 100 lines stops with JOBR-VALD-1009, and one with more than 50 payment records stops with JOBR-VALD-1014. An invoice voided before it was ever sent to iPaaS.com is skipped.
Each line is given its SKU: a line whose Jobber item is already in iPaaS.com takes that product's SKU; any other line takes the Fallback Line SKU. A one-off line with the setting empty stops the invoice with JOBR-VALD-1013.
The parent filter is applied: a draft invoice is skipped. A draft invoice, or any invoice the filter skips, sends neither its client nor its items, and no transaction is created.
The prerequisites are sent, in this order (see Prerequisite Handling):
The client, when the invoice has a client and that client is not linked to an iPaaS.com customer yet.
The items, once each, for every line whose Jobber item is not in iPaaS.com yet. When any item was sent, the lines are given their items' real SKUs.
The parent mappings run, and the transaction is created, or the linked transaction is updated.
The child collections run in the same transfer to add or update the transaction's lines, payments, taxes, billing address and discount.
Steps 2 and 3 run as the invoice is read from Jobber, so their checks (the line and payment limits, the one-off line SKU check and JOBR-EXTN-1005) apply before the parent filter. The parent filter in step 4 runs before any prerequisite is sent, so an invoice the filter skips sends nothing to iPaaS.com. The prerequisites in step 5 are sent before the parent mappings run.
Prerequisite Handling
An invoice needs its client and its items in iPaaS.com. The integration sends them automatically, in the invoice's own transfer, once the invoice has passed the parent filter; you do not need to send them first. A draft invoice, or any invoice the filter skips, sends neither its client nor its items, and no transaction is created. For an invoice that passes the filter:
The client: when the invoice's Jobber client is not linked to an iPaaS.com customer yet, the client is sent through Add/Update Jobber Client TO iPaaS.com. A client whose email matches an existing iPaaS.com customer is linked to that customer, and the invoice lands on it. A client already linked is not sent again.
The items: for each line whose Jobber item is not in iPaaS.com yet, the item is sent through Add/Update Jobber Product or Service TO iPaaS.com, and the line then takes the item's SKU. Items already in iPaaS.com are not sent again.
If the client or an item cannot be sent first, for example because its collection's filter skips it, the invoice is still sent. Only two prerequisite outcomes stop the invoice:
JOBR-VALD-1016: the client is not in iPaaS.com and has no email address, so it cannot be sent. Add an email to the client in Jobber, then resend the invoice with a Manual Sync: an invoice that stopped with this error is not retried on its own.
JOBR-VALD-1013: a line still has no SKU, because its item is not in iPaaS.com and the Fallback Line SKU setting is empty. Enter a Fallback Line SKU, or make sure Add/Update Jobber Product or Service TO iPaaS.com is on and its filter accepts the item, then resend the invoice.
When the Fallback Line SKU has a value, a line whose item could not be sent takes that SKU, and the invoice goes ahead.
Mappings
Add/Update Jobber Invoice TO iPaaS.com
iPaaS.com data type: Transaction
Mapping Filter
// Sends issued invoices only: a draft is not a sale yet. Voided invoices are sent, so the void reaches // iPaaS.com as a Cancelled status. return Status != "draft";
Filter Description: an invoice whose Jobber Status is anything other than draft passes and is sent, voided invoices included, so a void reaches iPaaS.com as Cancelled. A draft invoice fails the filter and is skipped: it logs nothing and needs no action, its client and items are not sent either, and it is sent once it is issued.
Description: creates and updates iPaaS.com Transactions of type Invoice from issued Jobber invoices, with the invoice number, status, totals, dates and the client's customer and email.
Mapping Type | Source Field (Jobber) | Destination Field (iPaaS.com) | Description |
Dynamic Formula |
| SystemId | Required. Records this Jobber subscription as the system the transaction came from. Do not change this formula. |
Field | InvoiceNumber | TransactionNumber | Required. The Jobber invoice number. It must be unique across your whole iPaaS.com company; to add a prefix, see Invoice Numbers. |
Dynamic Formula |
| CustomerId | Recommended. The iPaaS.com customer of the invoice's Jobber client, so the invoice appears on that customer. iPaaS.com requires every transaction to carry a customer, a company or an email address, so keep this and EmailAddress mapped. A client not in iPaaS.com yet is sent first (see Prerequisite Handling). |
Static |
| Type | Required. Every Jobber invoice becomes an iPaaS.com transaction of type Invoice. |
Lookup | Lookup Translation: Jobber Invoice Status TO iPaaS.com | Status | Required. The transaction status, translated from the invoice's Jobber status (see the translation table below). |
Field | CustomerEmail | EmailAddress | Recommended. The primary email address of the invoice's client in Jobber. |
Field | DiscountAmount | DiscountAmount | Recommended. The invoice-level discount amount in Jobber. An invoice with a discount also carries it as a discount record. |
Field | TaxAmount | TaxAmount | Recommended. The invoice's tax amount in Jobber, 0 when no line is taxed. The tax is also sent as tax records, one per tax rate. |
Field | Subtotal | Subtotal | Recommended. The total of the invoice's line items before tax, as Jobber calculates it. |
Field | Total | Total | Recommended. The invoice total in Jobber, tax included. |
Dynamic Formula |
| TransactionCreatedDateTime | Recommended. The date the invoice was issued in Jobber; an invoice with no issue date uses the date it was created in Jobber. |
Dynamic Formula |
| TransactionUpdatedDateTime | Optional. The date and time the invoice last changed in Jobber. |
CustomerId (Source Field):
// The iPaaS.com customer linked to the invoice's Jobber client. return await GetSpaceportIdAsync(ClientId, "Customer", SpaceportSystemId);
TransactionCreatedDateTime (Source Field):
// The invoice's issue date; its creation date when it has none. return DateTimeOffset.Parse(IssuedDate ?? CreatedAt);
TransactionUpdatedDateTime (Source Field):
// When the invoice last changed in Jobber. return DateTimeOffset.Parse(UpdatedAt);
Lookup Translation: Jobber Invoice Status TO iPaaS.com
Source Value (Jobber) | Destination Value (iPaaS.com) | Notes |
awaiting_payment | Awaiting Payment | Issued and not yet paid. |
sent_not_due | Awaiting Payment | Sent to the client and not yet due. |
past_due | Awaiting Payment | Past its due date and not yet paid. |
paid | Complete | Paid in full in Jobber. |
voided | Cancelled | Voided in Jobber. An invoice voided before it was ever sent is skipped. |
bad_debt | Cancelled | Written off as bad debt in Jobber. |
draft | Draft | Applies only if you change the filter to send drafts. |
To change how a status is recorded, edit the value on the right, using an iPaaS.com transaction status, and keep a row for every Jobber status.
Add/Update Jobber Invoice Line TO iPaaS.com
iPaaS.com data type: Transaction Line
Description: sends each line of the Jobber invoice as an iPaaS.com transaction line, with its SKU, description, quantity, unit price and line total. This collection has no filter: every line of an invoice that the parent sends is sent with it.
Mapping Type | Source Field (Jobber) | Destination Field (iPaaS.com) | Description |
Static |
| Type | Required. iPaaS.com requires a type on every transaction line. Every Jobber line, whether for a product, a service or a one-off entry, is sent as Product, since every line carries the SKU of an iPaaS.com product. |
Static |
| Status | Required. iPaaS.com requires a status on every transaction line. Every line of an issued Jobber invoice has been billed, so each line is sent as Complete. |
Field | Sku | Sku | Required. The iPaaS.com SKU the integration gives the line: its item's SKU, or the Fallback Line SKU for a one-off line (see Line SKU Handling below). Do not remove this mapping. |
Dynamic Formula |
| Description | Recommended. The line's name in Jobber, followed by a dash and its description when it has one (for example Lawn mowing - Front and back yard). |
Field | Quantity | Qty | Recommended. The line's quantity on the Jobber invoice. |
Field | UnitPrice | UnitPrice | Recommended. The line's unit price on the Jobber invoice. |
Field | TotalPrice | ExtendedPrice | Recommended. The line's total as Jobber calculates it on the invoice. |
Description (Source Field):
// The line's name, then its description when it has one. return string.IsNullOrEmpty(Description) ? Name : Name + " - " + Description;
Line SKU Handling
A line for a Jobber product or service: carries that item's iPaaS.com SKU. An item that is not in iPaaS.com yet is sent TO iPaaS.com first, in the same transfer, and the line then carries its SKU.
A one-off line: a line typed on the invoice with no Jobber item carries the Fallback Line SKU, for example MISC-SERVICE. So does an item line whose item could not be sent TO iPaaS.com, when the setting has a value.
No SKU to send: a one-off line, or an item that is not in iPaaS.com, with the Fallback Line SKU setting empty, stops the invoice with JOBR-VALD-1013.
Linked product with no SKU: when the iPaaS.com product linked to a line's item has no SKU, or its SKU cannot be read, the transfer stops with JOBR-EXTN-1005. When the SKU could not be read, the cause is usually temporary and the invoice is retried; when the product has no SKU, give the iPaaS.com product named in the error a SKU and resend the invoice.
Lines under the fallback product: a line whose Jobber item never reached iPaaS.com (for example an item hidden in Jobber before it was ever sent) arrives under the Fallback Line SKU product. Send the item TO iPaaS.com and resend the invoice to give the line its real SKU.
Add/Update Jobber Invoice Payment TO iPaaS.com
iPaaS.com data type: Transaction Payment
Description: sends each payment recorded on the Jobber invoice as an iPaaS.com transaction payment, with its amount, payment method, details and a Completed status. This collection has no filter: every payment of an invoice that the parent sends is sent with it. Recording a payment in Jobber updates the invoice, so with the Jobber invoice events on, a new payment is sent with its invoice.
Mapping Type | Source Field (Jobber) | Destination Field (iPaaS.com) | Description |
Dynamic Formula |
| MethodInfo | Optional. For a card payment taken through Jobber Payments, the card brand followed by ending and the card's last four digits. Every other payment, including a card payment recorded by hand, gets no method information. Validate this in a staging subscription before relying on it in production. |
Lookup | Lookup Translation: Jobber Payment Type TO iPaaS.com | Method | Required. The iPaaS.com Payment Method, translated from the payment's Jobber payment type (see the translation table below). A payment Jobber records with no type is sent as OTHER, so every payment finds an entry. |
Field | Details | Description | Optional. The payment's details or reference, as entered on the payment in Jobber. A payment with no details gets no description. |
Field | Amount | Amount | Recommended. The amount of the payment applied to the invoice in Jobber. |
Static |
| Status | Recommended. Every payment is sent as Completed: Jobber lists a payment on the invoice once it is recorded. The processing status Jobber Payments keeps for a card payment is not sent. |
MethodInfo (Source Field):
// Card brand and last four digits, for Jobber Payments card payments only. return string.IsNullOrEmpty(CardLastDigits) ? null : CardBrand + " ending " + CardLastDigits;
Lookup Translation: Jobber Payment Type TO iPaaS.com
Each entry must be set to one of your own iPaaS.com Payment Methods. The values the template ships are examples: before the first invoice with a payment is sent, open the translation and replace each value on the right with the name of the Payment Method your iPaaS.com company uses for that kind of payment.
Source Value (Jobber) | Destination Value (iPaaS.com) | Notes |
CASH | CASH | Example value. A cash payment. |
CHEQUE | CHECK | Example value. A check payment. |
CREDIT_CARD | CRCARD | Example value. A card payment recorded by hand. |
JOBBER_PAYMENTS | CRCARD | Example value. A card payment taken through Jobber Payments. |
EPAYMENT | Online payment | Example value. An online payment. |
BANK_TRANSFER | Other | Example value. Its own Payment Method if you have one, or a general method. |
ACH_BANK_PAYMENT | Other | Example value. Its own Payment Method if you have one, or a general method. |
E_TRANSFER | Other | Example value. Its own Payment Method if you have one, or a general method. |
MONEY_ORDER | Other | Example value. Its own Payment Method if you have one, or a general method. |
CASH_APP | Other | Example value. Its own Payment Method if you have one, or a general method. |
ZELLE | Other | Example value. Its own Payment Method if you have one, or a general method. |
PAYPAL | Other | Example value. Its own Payment Method if you have one, or a general method. |
VENMO | Other | Example value. Its own Payment Method if you have one, or a general method. |
CONSUMER_FINANCING | Other | Example value. Its own Payment Method if you have one, or a general method. |
OTHER | Other | Example value. Also used for a payment Jobber records with no type. |
Make sure every entry names one of your Payment Methods, so the systems that receive the transaction see a method they recognize, and check one invoice with a payment in a staging subscription before relying on it in production.
Payments and the Payment Date
Payments are recorded in Jobber: a payment is sent once it is recorded on the invoice in Jobber, by hand or through Jobber Payments. Payments recorded in another system do not reach Jobber and do not mark the Jobber invoice paid, because Jobber does not let apps record invoice payments. Record the payment in Jobber; it then reaches iPaaS.com with the invoice.
No payment date: iPaaS.com transaction payments have no date field, so the date a payment was recorded in Jobber does not reach iPaaS.com.
Bookkeeping entries: Jobber's bookkeeping entries on an invoice (a void, a bad-debt write-off, a correction) are not sent as payments; the invoice's status carries them.
Refunds, Deposits and Card Details
These behaviors are described from how the integration is built. Validate each in a staging subscription before relying on it in production.
Refunds and failed bank payments: a refund, and a Jobber Payments bank payment that failed, are sent as negative payments. Validate this in a staging subscription.
Deposits: a deposit applied to the invoice is sent as a payment. Validate this in a staging subscription.
Card details: for a card payment taken through Jobber Payments, MethodInfo carries the card brand followed by ending and the card's last four digits; no other payment carries method information. Validate this on one Jobber Payments card payment in a staging subscription.
Add/Update Jobber Invoice Tax TO iPaaS.com
iPaaS.com data type: Transaction Tax
Description: sends the invoice's tax as iPaaS.com transaction tax records, with the tax rate's name, its percent and its amount. This collection has no filter: every tax record of an invoice that the parent sends is sent with it.
Mapping Type | Source Field (Jobber) | Destination Field (iPaaS.com) | Description |
Field | Name | Authority | Recommended. The tax rate's name in Jobber, or for a tax group, the name of each rate in the group (for example GST and PST). A single tax rate with no name is sent as Tax. |
Field | Amount | Amount | Recommended. The tax amount for this rate (see How Tax Records Are Built below). |
Field | Rate | TaxPercent | Recommended. The tax rate in percent, as set on the rate in Jobber (for example 5 for a 5% rate). |
How Tax Records Are Built
Single tax rate: one tax record carrying the invoice's whole tax amount, the rate's name and its percent.
Tax group: one tax record per rate in the group (for example GST and PST), each with its own name and percent. The invoice's tax amount is split in proportion to each rate, and any rounding difference goes on the last record, so the records always add up to the invoice's tax.
No tax: an invoice with no tax gets no tax record.
Add/Update Jobber Invoice Address TO iPaaS.com
iPaaS.com data type: Transaction Address
Description: sends the invoice's billing address as the transaction's primary billing address, with the street lines, city, state or province, ZIP or postal code and country. This collection has no filter. The integration sends the billing address only when it has a street or a city: an invoice whose billing address has neither is sent without an address, and without an error.
Mapping Type | Source Field (Jobber) | Destination Field (iPaaS.com) | Description |
Static |
| IsPrimaryBilling | Recommended. Marks the address as the transaction's primary billing address. Only the billing address is sent, so this is always true. |
Field | Street1 | Address1 | Recommended. The first line of the invoice's billing address in Jobber. |
Field | Street2 | Address2 | Optional. The second line of the billing address. |
Field | City | City | Recommended. The city of the billing address. |
Field | Province | Region | Recommended. The state or province of the billing address. |
Field | Country | Country | Recommended. The country of the billing address, sent as the text Jobber holds, with no conversion to a country code. |
Field | PostalCode | PostalCode | Recommended. The ZIP or postal code of the billing address. |
Add/Update Jobber Invoice Discount TO iPaaS.com
iPaaS.com data type: Transaction Discount
Description: sends the invoice-level discount as an iPaaS.com transaction discount, with the amount and, when the discount was entered as a percentage in Jobber, the percentage. This collection has no filter. The integration sends a discount record only for an invoice whose discount amount is not zero.
Mapping Type | Source Field (Jobber) | Destination Field (iPaaS.com) | Description |
Field | Amount | DiscountAmount | Recommended. The discount in money as Jobber calculates it on the invoice (for example 10.50 for a 10% discount on a 105.00 subtotal). The parent also sends this amount in the transaction's own DiscountAmount. |
Dynamic Formula |
| DiscountPercent | Optional. The discount percentage, when the discount was entered as a percentage in Jobber (for example 10 for 10%). A discount entered as a fixed amount is sent with no percentage; its value is in DiscountAmount. |
DiscountPercent (Source Field):
// The percentage, only when the discount was entered as a percentage. return DiscountType == "Percent" ? Rate : null;
Error Handling
Errors appear in Dashboard / Integration Monitoring / Error Logs. The full list is in Jobber Error Messages.
JOBR-VALD-1016: "Jobber invoice {number}'s client {name} (clients/{number}) has no email address, and iPaaS.com customers need one. Add an email to the client in Jobber, then resend the invoice." The invoice's client is not in iPaaS.com and has no email. Resolution: add an email to the client in Jobber, then resend the invoice with a Manual Sync; it is not retried on its own.
JOBR-VALD-1013: "Invoice line "{name}" is a one-off line and the subscription's Fallback Line SKU setting is empty. Enter the SKU of the iPaaS.com product used for one-off lines in the subscription settings, then resend the invoice." or "Invoice line "{name}" uses a Jobber item that is not in iPaaS.com, and the subscription's Fallback Line SKU setting is empty. Send the item TO iPaaS.com (check the Product TO collection and its filter, or run a Manual Sync of the item) or enter a Fallback Line SKU, then resend the invoice." Resolution: enter a Fallback Line SKU (for example MISC-SERVICE) and click Apply, or make Add/Update Jobber Product or Service TO iPaaS.com send the item; then resend the invoice.
JOBR-EXTN-1005: "Could not read the SKU of iPaaS.com product {id} for invoice line "{name}": {details}" or "iPaaS.com product {id} for invoice line "{name}" has no SKU." Resolution: a SKU that could not be read is usually temporary and the invoice is retried; for a product with no SKU, give the iPaaS.com product named in the error a SKU and resend the invoice.
JOBR-VALD-1009: "Jobber invoice {number} has more than 100 line items; this integration sends invoices of up to 100 lines." Resolution: enter that invoice in the receiving system by hand.
JOBR-VALD-1014: "Jobber invoice {number} has more than 50 payments; this integration sends invoices with up to 50 payments." Bookkeeping entries count toward the 50. Resolution: enter that invoice and its payments in the receiving system by hand.
NFND-1029: "Duplicate transaction found!" Another iPaaS.com transaction already holds the invoice number. Resolution: see Invoice Numbers; each retry is refused until the numbers no longer clash.
JOBR-VALD-1017: "This record moves with its transaction; transfer the transaction, and remove any collection that sends this record type on its own." Resolution: resend the parent invoice instead. Never remove the default child collections.
JOBR-VALD-1004: "Deleting invoices or work requests in Jobber is not supported by this integration." Resolution: void the invoice in Jobber instead.
JOBR-EXTN-1003: "Jobber request limit reached while {action}: retry after {n}s." or "Jobber query cost limit reached while {action}: retry after {n}s." Resolution: no action; the transfer is retried automatically after the limit resets.
Testing & Validation
Test Scenarios
New invoice: issue an invoice in Jobber for a client and items already in iPaaS.com. Confirm the iPaaS.com transaction of type Invoice appears with the invoice number, status, totals, dates, customer and email, and with its lines, tax, billing address and discount.
Update: change a line or the discount on the same invoice. Confirm the same transaction is updated, with the same line, address and discount records, and no second transaction.
New client and item: issue an invoice for a client and an item that are not in iPaaS.com yet. Confirm the client and the item are sent first and the invoice lands on that customer with the item's SKU.
One-off line: add a line with no saved Jobber item. With Fallback Line SKU set to MISC-SERVICE, confirm the line carries MISC-SERVICE; with the setting empty, confirm the invoice stops with JOBR-VALD-1013.
Client with no email: issue an invoice for a new client with no email. Confirm the invoice stops with JOBR-VALD-1016; add the email and resend it with a Manual Sync.
Payment: record a payment on the invoice in Jobber. Confirm the payment arrives with the Payment Method your translation names, the amount and a Completed status.
Tax group: issue an invoice with a tax group. Confirm one tax record per rate and that the records add up to the invoice's tax.
Void and draft: void a sent invoice and confirm the transaction becomes Cancelled; save a draft and confirm it is not sent.
Manual Sync: run a Manual Sync with the number at the end of the invoice's Jobber web address, and again with its Jobber API id; confirm both update the same transaction.
Invoice number clash: in a staging subscription, send an invoice whose number another transaction holds and confirm it is refused with NFND-1029; then confirm the prefixed TransactionNumber formula avoids the clash.
Validation Checklist
The Fallback Line SKU names an existing iPaaS.com product.
The TransactionNumber mapping was chosen before the first invoice was sent.
Every entry of the Jobber Payment Type TO iPaaS.com translation names one of your Payment Methods.
The INVOICE_CREATE and INVOICE_UPDATE events are turned on.
Add/Update Jobber Client TO iPaaS.com and Add/Update Jobber Product or Service TO iPaaS.com are in place, with filters that include your invoices' clients and items.
Refunds, deposits and Jobber Payments card details were validated in a staging subscription.
Additional Notes
Out of Scope
Quotes and jobs: only invoices are sent; Jobber quotes and jobs are not.
The service property: the property where the work was done is not sent as an address.
Payments back to Jobber: payments recorded in another system are not written to Jobber.
Deleting invoices: deletes are not sent; void the invoice instead.
Related Documents
Related Mapping Documentation


