|
Matching Existing Jobs & Payment Obligations
Rosemark strives to keep a Job and its corresponding Payment Obligation in sync. As necessary, it will add Payment Obligations or Jobs to match their counterparts, if they are missing. In each of the possible cases, a number of criteria must be met before the QuickBooks Connection will make changes.
In order for a Payment Obligation to be considered for syncing, it must meet the following criteria:
| • | Has an Active Service that has at least one billable Shift. |
| • | If the Service is not currently Active, has a billable Shift during the Shift Export time period. |
| • | The Service Type is not blank |
| • | The Client name is not blank |
| • | Has a Customer and their name is not blank |
In order for a Job to be added to QuickBooks, it must meet the following criteria:
| • | Not previously connected |
| • | Customers are connected (or are being connected) |
| • | Not a match (Service Type and Client Name) with an unconnected QuickBooks Job of the connected customer |
In order for a Payment Obligation to be added to Rosemark, the following criteria must be met:
| • | Not previously connected |
| • | Customers are connected (or are being connected) |
| • | Is a second-level QuickBooks Customer:Job |
| • | Job Active in QuickBooks |
| • | Not marked as "skip" in QuickBooks Customer or Job RSS fields |
| • | Name (Service Type, Client Name) uniquely matches one Rosemark Service |
| • | Rosemark Customer has no matching (Service Type, Client Name) unconnected Payment Obligation |
In order for an existing Payment Obligation and an existing Job to be connected, they must meet the following criteria:
| • | Not previously connected |
| • | Customers are connected (or are being connected) |
| • | Is a considered RSS payment obligation or an Active QuickBooks Job |
| • | Is a second-level QuickBooks Customer:Job or is the included Job of a top-level Customer that has no subs |
| • | Has a name match (Service Type, Client Name) between a Rosemark Payment Obligation and one QuickBooks Job |
In some cases, a matching Payment Obligation is in place, but it has no Customer set. When the Payment Obligation and Job are connected, the Payment Obligation's Customer will be set, given that the following criteria are met:
| • | Not previously connected |
| • | Payment obligation has no customer |
| • | Is a considered RSS payment obligation or an Active QuickBooks Job |
| • | Is a second-level QuickBooks Customer:Job or is the included Job of a top-level Customer that has no subs |
| • | Not marked as "skip" in QuickBooks Customer or Job RSS fields |
| • | Has a name match (Service Type, Client Name) between a Rosemark Payment Obligation and one QuickBooks Job |
|
