How do I map Attio custom attributes for AR remittance addresses?
Attio's Company object has no built-in street, city, state, zip, or country fields — Loopfour's integration can only write domains and customAttributes. Before syncing AR remittance addresses, define a location-type custom attribute in Attio's workspace, then map to it by attribute slug rather than assuming a fixed field name, since the attribute has to be created before any data can land in it.
By Zuny Fester, Head of Operations and MarketingPart of the finance integrations guide.
| Built-in address fields | None — Attio's Company object has no fixed address schema |
|---|---|
| What Loopfour can write | domains and customAttributes only |
| Attribute model | System-defined and user-defined attributes, including a Location type |
| Prerequisite | The custom attribute must be created in Attio's workspace before a workflow can write to it |
Why Attio needs a setup step Salesforce and HubSpot don't
Attio's own API documentation describes its object model as attribute-based: standard objects ship with a set of system-defined attributes, but companies and developers create their own on top — there's no separate, always-present address schema the way Salesforce's BillingCity or HubSpot's city property exist by default. Attio's attribute types include a Location type, but it has to be added to the Company object before any workflow can write to it. Loopfour's Attio integration reflects this: createCompany and updateCompany accept only domains and a customAttributes map, with no dedicated address parameters.
Setting up the mapping
In the Attio workspace, add a custom attribute to the Company object using the Location type (or a set of separate text attributes, if you want street/city/state/zip/country as independent fields rather than one combined location value). Note the attribute's slug — not its display label — since that's what the API references. Map your AR remittance-address fields to that slug inside the customAttributes object on create and update calls.
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
AR remittance address → Attio custom attribute setup
| Step | Action |
|---|---|
| 1 | Create a Location-type (or text-type) custom attribute on Company in Attio's workspace UI or API |
| 2 | Note the attribute's API slug, not its display label |
| 3 | Write to it via the customAttributes map on createCompany/updateCompany calls |
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 moreHow-to
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.
Read more