xMatix
Sign in Request demo
xMatix
PRODUCTS
SalesField Sales & SFACRMRewardsClaimsInventoryProcurementWarehouse ManagementField ServiceServiceSupportTelephony & MessagingFinance & AccountingPayrollExpense ManagementCommercePortalsAnalytics & ReportingData StudioMobile AppSee all products →
PLATFORM
Platform overviewApp BuilderAutomationIntegrationsSecurity & GovernanceChange ManagementDevelopers
SENSE AI
Sense AI overviewSense AssistSense ControlSense VisionAI StudioTrust & governanceIn Claude & ChatGPTUse cases
SOLUTIONS
Auto DMSConsumer Goods DMSSales Force Automation (SFA) FMCG & DistributionManufacturing & Dealer NetworksAutomotive & DealershipsPharma & HealthcareConsumer DurablesAgri-InputsBuilding MaterialsService NetworksWarehousing & 3PLFinancial AccountingERP SoftwareIndia GST ComplianceUAE VAT & e-InvoicingSaudi ZATCA & VATAll solutions →
RESOURCES
Knowledge CenterDeveloper & CLIBlogGuidesWhat is xMatix?Company facts
COMPANY
AboutCareersPartnersEventsContactAuthorsLegal
Sign in Request demo
Home/Docs/Entity Reference/Branch Postal Code — entity reference
REFERENCE · Last reviewed

Branch Postal Code — entity reference

Maps one postal code to the branch, and the company (partner account), that serves it. When a lead is saved with a postal code that matches a Postal Code row, xMatix copies Branch and Partner Account from the oldest mapping for that code onto the lead, on every save, unless an assignment definition sets those fields on leads. Assignment rules can also look these rows up. No screen searches for a nearby branch by postal code or city. Hidden when the organization works from a single location; not in any shipped app menu.

Fields

FieldLabelTypeRequiredWhat it does
BranchIdBranchLookup → BranchThe branch that serves the postal code. Only branches of the chosen partner account are offered. Built-in routing copies it to the lead without checking whether the branch is active.
CoverageTypeCoverage TypePickListAn optional classification of the mapping. The shipped values (All, Marketing, Sale) are inactive, so the choice list is empty until an administrator activates or adds values. Built-in lead routing ignores it; only assignment rules that filter on it use it.
CreatedByIdCreated ByLookup → UserAccountYes
CreatedDateTimeCreated DateDateAndTimeYes
IdIdGuidYes
LastModifiedByIdLastModifiedByGuid
ModifiedByIdModified ByLookup → UserAccountYes
NameNameTextYesA generated record number from the BP numbering series, filled on save.
OwnerIdOwnerLookup → UserAccountYes
PartnerAccountIdPartner AccountLookup → AccountThe company that serves the postal code. Built-in lead routing copies it to the lead even when it is empty, which clears the lead's partner account and makes the lead fail validation, so always fill it.
PostalCodeIdPostal CodeLookup → PostalCodeThe postal code record this mapping covers. When importing, resolve it with a PostalCode.Code column, because the postal code record's name is a generated number, not the code.
RecordTypeIdRecord TypeGuid, hidden
UIPropsUI PropsText
UpdatedDateTimeModified DateDateAndTimeYes

Actions

ActionLabelTypeWhat it does
BulkDeleteDeleteDeleteDelete the selected records.
CloneCloneServerAction (Clone)Clone
DeleteDeleteDeleteDelete
DeleteInListDeleteDeleteDelete in a list page
EditEditEditEdit
EditInLineEditEditInlineEdit in page.
EditInListEditEditEdit in List Header
EditListHeaderEditEditInlineEditListHeader
NewNewNewNew

Lookup filters

FilterLookup fieldNotes
Branch For Partner AccountBranchId