How do I sync Salesforce Account billing addresses for AR?

Loopfour's Salesforce integration reads the Account object's Billing* fields — BillingStreet, BillingCity, BillingState, BillingPostalCode, BillingCountry — directly, since Salesforce has no separate billing-address object. The integration polls Account records rather than reacting to webhooks, so a workflow needs to schedule that poll rather than expect real-time updates.

By Zuny Fester, Head of Operations and Marketing

Reviewed by Zuny Fester

Published September 14, 2026Last reviewed September 14, 2026Editorial policy

Part of the finance integrations guide.

Object read	Account, using its Billing* prefixed fields (a compound BillingAddress on the Salesforce side)
Sync mechanism	Polling only — no webhook/event handler exists for Salesforce in this integration
Field names to map	BillingStreet, BillingCity, BillingState, BillingPostalCode, BillingCountry
Contrast	HubSpot exposes the same concept as flat, non-prefixed fields (address/city/state/zip/country) and supports webhooks; Salesforce does neither

Why Account, not a separate billing object

Salesforce doesn't have a dedicated billing-contact or remittance-address object in its standard schema — a customer's billing address lives directly on the Account record, as a set of Billing*-prefixed fields (BillingStreet, BillingCity, BillingState, BillingPostalCode, BillingCountry) that together make up what Salesforce calls the BillingAddress compound field. Loopfour's Salesforce integration reads these fields straight off the Account object rather than a separate related record.

Setting up the sync

Map each of the five Billing* fields individually — there's no single compound value to pull in one step through the integration's Account actions. Because the Salesforce integration has no webhook handler (unlike HubSpot's contact/company change events in this same matrix), the workflow has to poll Account records on a schedule rather than react to an update the moment it happens; how frequently depends on how quickly billing-address changes need to reach downstream AR documents.

What to check before going live

Confirm which Account record actually represents the paying entity — Salesforce Accounts commonly nest parent/child hierarchies for large customers, and the field values live on whichever specific Account record is the billing party, not necessarily the top-level parent. Also confirm the poll interval against how fast your team needs an address change (a customer moving, a re-incorporation) to reach an invoice before it goes out with a stale address.

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.

Book a workflow review

Field mapping

Salesforce Account Billing* fields to map for AR

Salesforce field	Compound component	Maps to
BillingStreet	BillingAddress.street	Address line 1
BillingCity	BillingAddress.city	City
BillingState	BillingAddress.state	State/province
BillingPostalCode	BillingAddress.postalCode	Postal/ZIP code
BillingCountry	BillingAddress.country	Country

Frequently Asked Questions

BillingAddress exists as a compound field in the Salesforce UI and in some API responses, but the individual Billing* fields are what most integrations, including this one, read and write directly — map each one separately.

Salesforce has no webhook/change-event handler wired up in Loopfour's integration, unlike HubSpot in this same matrix — Account data is read on a poll, not pushed on update.

They're independent compound fields — a populated BillingAddress with an empty ShippingAddress is normal and doesn't affect AR sync, which only reads the Billing* fields.

Sources

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…

Topic

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…

Diagnostic

What breaks when a HubSpot quote line item is missing recurringbillingfrequency?

HubSpot's recurringbillingfrequency property on a quote line item isn't required or enforced — a line item can be created and a quote published without it. A workflow reading that quote to build a revenue recognition schedule can't tell a one-time charge from a recurring one without it, so the line has to default to one-time or get flagged for manual review.

Diagnostic

What breaks when Salesforce billing address fields don't sync to AR?

Loopfour's Salesforce integration polls Account records, so an address update sits unsynced for the poll interval — an invoice can go to a stale address if generated inside that window. The other break: Salesforce's Billing* fields are named differently from HubSpot's flat address fields, so a mapping copied between the two CRMs maps to nothing.