Abillity - Customer and Site sync
Customer sync
Abillity stores the following Customer types:
Agents
Suppliers
Resellers
Carriers
Customers
These contain Sites
The integration between The Layer and Abillity is concerned with customers and sites. We do not sync the other record types.
Sites in The Layer can sync with a site or a subsite in Abillity. The Layer's own subsite type is not used as part of the integration
The Layer - Record Type | Abillity - Record Type |
Customer | Company (Customer type) |
Site (default per customer) | Billing Site & Head Office |
Site (other) | Subsite |
Subsite | N/A |
Initial sync events:
Lead conversion to customer via quote win
Manual lead conversion to customer (through "Sales" menu)
Sales order creation
Manual sync from Abillity menu on customer record
⚠ Customer record names in The Layer should be unique if they are to be synced to Abillity.
For companies with the same name, the Registered Company Name field can be used to store the common name.
Customer details
The following details are synced at customer / company level:
Customer status
Customer records in Live or Pending status will have the Customer option enabled under Contact Type in Abillity.
If a customer is synced in Cancelled status, the Customer option will be unchecked in Abillity.
This will be updated in Abillity whenever the status is changed in The Layer.
VAT Registration Status
It is currently not possible to sync a customer as VAT-Registered. This is a limitation of the Abillity API. This may change in the future.
Billing Details
The following custom fields may have been set up in your instance of The Layer, depending on your requirements.
They exist as customer-level fields in The Layer but they will sync to sites in Abillity.
The Layer (Customer) | Abillity (Site) |
Bill Run | Bill Run |
Payment Terms | Payment Terms |
Payment Method | Payment Method |
For this reason, all sites for a customer must have the same values for these fields. If you require sites to have e.g. a different Bill Run, we recommend creating another customer record in The Layer.
Site sync
Sites will sync to Abillity either as sites or subsites.
The Layer - Record Type | Abillity - Record Type |
Site (default per customer) | Site (aka Billing Site) |
Site (other) | Subsite |
Subsite | N/A |
For each customer, we will sync one Layer site as the billing site in Abillity.
All other sites from The Layer will sync as a subsite in Abillity.
While The Layer has its own concept of subsites, these will not be enabled if the integration is active.
Default Site / Billing Site
Marking a site on The Layer as the default will indicate that this site will be considered the billing / main site on Abillity.
⚠ The "default" flag will only determine which site is the billing site when the initial sync happens. If you want to change which site is the default site after syncing, you must make changes manually in both systems.
This limitation is in place to reduce the chance of accidentally losing data in Abillity.
Site details
The following details will sync against a site.
Site Address
One address will be synced per site. A site in The Layer can have multiple addresses, so you can indicate which one will be synced by checking the Site Default box from Manage - Sites - <Site> - Addresses.
Sites can be associated with a site using the Associate Address button. An address can be associated to multiple sites, and a site can have multiple addresses.
What if no default site is set?
An address will be synced even if a default is not assigned to a site. The priority for address sync against a site is:
Synced site default address
Default site default address
Quote invoice address
Customer default address
First address on customer record
Changes made to an address in The Layer will be resynced automatically.
Billing Contact
On initial sync, the Billing Contact field in Abillity will be populated.
If any site contact has a type with the Billing flag, they will be synced as the billing contact (how to configure).
If no site billing contact is present, the sync will use the contact that has been assigned to the quote.
⚠ Note that we do not resync this after the initial sync. The reason for this is that we do not want to overwrite any information that may have been manually entered in Abillity e.g. additional email addresses.
Sage Account Number
The Sage Account Number can be stored against a customer record in The Layer.
If your instance of The Layer has a Sage integration configured, it may pull the Sage number directly from Sage. In that case, the Sage Account Number will not be visible or editable as above.
This will sync to each site and subsite in Abillity, against the Ref field in the Account Settings section.
This will resync to Abillity whenever changed in The Layer.
Checking sync status
From a sales order, you can quickly check if the customer is synced by looking for the green tick icon near the top of the screen.
Clicking on the Sync Abillity Customer button in this menu will show you a summary screen, detailing synced sites and customers.
Clicking on the Continue button will perform a manual resync. This should not generally be necessary, as updates are performed upon customer record saves in the layer.
Manual customer sync
If a customer record has not yet been synced, the green tick icon will not be shown. This could happen if an automatic initial sync failed, or if a customer record is created directly (skipping the lead stage).
In such a case, you can use the Sync Abillity Customer button in the Abillity menu to attempt a manual sync.
Click on Continue to begin this process.
After a moment the Abillity Customer list will populate. This allows you to map to an existing customer record in Abillity.
If you wish to create a new customer record in Abillity, make no selection.
In either case, clicking on Sync Abillity Customer will attempt the sync.
Site Creation
Sites can be manually created from Manage - Sites on a lead or customer record.
If a lead record has no existing sites, one can be auto-created during lead or opportunity creation.
If a customer record is created manually, skipping the lead stage, a lead record will be created automatically.
Site Name and Reference Logic
When creating a site manually, the logic is as follows:
Site Name
This will be entered manually. Any sites created automatically during opp or quote creation will use the customer name by default.
Site Integration ID
This is an internal Layer field that will always be automatically generated. It will only be seen on customer sites, after the sync has occurred.
Site Ref
This will be be automatically generated for Abillity Integration users.
Automatic generation can be changed with the Auto-Generate Site Reference company customisation in Settings. This should not be disabled without good reason.
Description
If Sage sync is active, the customer's Sage reference will be used to form the description. This will only be seen at the customer stage, after the customer record has synced to Sage and Abillity.
Contacts
Contacts can be associated with a site from Manage - Sites with the Associate Contact button. Contacts sync to the People area in Abillity.
Whenever a customer record syncs or resyncs to Abillity, contacts will also be synced.
Contacts will be synced to their associated site or subsite, if one has been associated in The Layer.
If no site has been assigned to a contact, they will be assigned to the primary / billing site in The Layer, and synced to that site in Abillity.
TL Contact | Abillity Contact |
First Name | Name |
Last Name | Name |
Telephone | DDI |
Flag: Decision Maker / Primary | Flag: Main Contact |
Abillity shows all users for a company when viewing Company Information.
One-off vs repeat syncs
This table summarises which values sync only once and which will update when modified in The Layer.
TL Customer | Abillity Site | Syncs | When? |
Bill Run | Bill Run | One-off | Conversion of lead to customer |
Payment Terms | Payment Terms | One-off | Conversion of lead to customer |
Payment Method | Payment Method | One-off | Conversion of lead to customer |
Contact Name | Billing Contact (field) | One-off | Conversion of lead to customer |
Sage Reference | Ref. | One-off | Conversion of lead to customer |
Status (Pending / Live) | Contact Type ("Customer") | Repeated | On status change |
TL Site | Abillity Site | Syncs | When? |
Name | Site Name | Repeated | On site change |
Description | Site Ref. | Repeated | On site change |
Address | Address | Repeated | On address change |
TL Contact | Abillity Contact | Syncs | When? |
First Name | Name | Repeated | On contact change |
Last Name | Name | Repeated | On contact change |
Telephone | DDI | Repeated | On contact change |
Flag: Decision Maker / Primary | Flag: Main Contact | Repeated | On contact change |
Notes
If your company changes Billing Platform, we recommend raising a support ticket with us, instead of performing a bulk unmapping.
Any changes made in Abillity won’t be reflected in the Layer - this is a one-way sync.
If any customer custom fields are to be synced, they must be promoted in order to sync reliably.