How do I sync HubSpot company address fields for AR?
HubSpot stores a company's billing address as flat, unprefixed properties — address, city, state, zip, country — not nested under a Billing* namespace the way Salesforce does. Map those five properties directly to your AR remittance-address fields, then subscribe to company.propertyChange webhooks so an address edit in HubSpot reaches AR in real time instead of on the next poll.
By Zuny Fester, Head of Operations and MarketingPart of the finance integrations guide.
| Address properties | address, city, state, zip, country — flat, no prefix |
|---|---|
| Sync mechanism | Webhooks v4 subscription on company.propertyChange (real-time), not polling |
| Object | Company (standard HubSpot CRM object) |
| Contrast | Salesforce uses Billing*-prefixed fields and has no equivalent webhook in Loopfour's integration |
Why the field shape matters before you map anything
HubSpot's Company object exposes address, city, state, zip, and country as five separate, flat top-level properties — confirmed directly in HubSpot's own API reference, which shows city and state as plain keys in a company's properties object, not nested under a prefix. This is a different shape than Salesforce's Account object, which prefixes the same concept as BillingStreet, BillingCity, and so on. If you're migrating a mapping from a Salesforce-based AR sync, the field names themselves have to change, not just the object.
Setting up the sync
Map each of the five properties directly to your AR system's remittance-address fields — there's no transformation needed beyond the field-name mapping itself, since HubSpot's fields are already atomic (unlike a single combined address-line field some systems use). Then register a webhook subscription for company.propertyChange scoped to those five properties, so an edit in HubSpot triggers an event rather than waiting for the next scheduled poll.
Next step
Map the finance workflow with the most exposure and prove the automation path.
Bring the invoice, contract, payment reconciliation, or customer finance workflow you have to defend at audit. Loopfour can map the trigger, controls, integrations, and approval loop.
Field mapping
HubSpot Company address fields → AR remittance address
| HubSpot property | AR remittance field |
|---|---|
| address | Street |
| city | City |
| state | State/Province |
| zip | Postal code |
| country | Country |
Frequently Asked Questions
Sources
Related
Topic
AR & Collections
Accounts receivable is the money customers owe a business for goods or services already delivered on credit — a current asset on the balance sheet until it's collected. AR and collections, as a practi…
Read moreDefinition
What is an AR aging report and how do I read it?
An AR aging report lists every open invoice grouped by how long it's been outstanding — current, 1-30, 31-60, 61-90, and 90+ days past due. Read it by tracking the bucket distribution over time, not just the total; a shrinking current bucket and growing 90+ bucket signal a collections problem before it shows up in a blended DSO figure.
Read moreTopic
Integrations
Every finance automation vendor publishes an integrations page: a grid of logos, a claim of "seamless" connectivity, and not much else. That page answers a marketing question — does this vendor touch…
Read moreDiagnostic
What breaks when HubSpot company address fields don't match Salesforce?
HubSpot stores a company's address as flat properties (city, state) while Salesforce prefixes the same concept (BillingCity, BillingState). A workflow or mapping built against one and pointed at the other silently writes to nonexistent fields or leaves AR remittance addresses blank — there's no error, because both systems accept the write and simply don't have a field by that name to reject.
Read more