Set the product plan on contacts from paid line items (payments and invoices)

Outcome. Every paying contact carries the plan they actually bought and the date it started, read from the line items behind their payment or invoice, so segmentation and onboarding stop relying on a rep remembering to set the field by hand.

Workflow map Enrollment, branches and actions at a glance data-quality-050

flowchart TD
    A[Contact has a paid payment or invoice] --> B[Custom code: associations to line items to products]
    B --> C{result_code}
    C -->|found| D[Set Product plan, Plan start date, source]
    C -->|not_found| E[Set source = Not found]
    C -->|error| F[Create task for the operations owner]

When to use it, when not to

• UseUse it when you collect money inside the CRM through payments or invoices, and the plan a customer bought is visible on the line items attached to that payment or invoice.
• UseUse it when marketing and service need plan-level segmentation (upgrade campaigns, plan-specific onboarding, plan-specific SLAs) and the plan today lives only in the billing system.
• SkipDo not use it when billing happens entirely in an external system with no payment or invoice records synced into the CRM. In that case, sync the plan as a contact property from the billing system directly, and skip the workflow.
• SkipDo not use it as your revenue source of truth. It copies a label for segmentation. Amounts, proration and refunds stay in the billing system.