Companion Policies

For ease of reference, we’ll refer to the primary grower/tenant policy as the “source” policy. The secondary grower/landlord policy is referred to as the “companion” policy, which is the policy that linked coverage information will be copied to.

The source policy is the policy on which Acreage Reporting records should be processed. When the companion policy is linked to the source policy, the data in the source policy will be pushed to the companion policy, overwriting and filling in certain detail line values in the companion policy for linked coverages, which we’ll discuss later in this video.

To successfully link policies, both the source and companion policies must meet specific requirements.

The Source Policy

A source policy must have:

1.

A plan code of 01, 02, 03, 04, 05, 06, or 90 (Category B crops only, not perennials or downed rice ). This plan code does not have to be the same as the companion policy’s plan code.

2.

A detail line with a share less than 100%.

3.

At least 1 associated shareholder for each detail line that is to be linked.

The Companion Policy

To be linked to a source policy, the companion policy must have:

1.

An active coverage in the same county as the source policy being linked that also has a plan code of 01, 02, 03, 04, 05, 06, or 90 (Category B crops only, not perennials or downed rice ). Again, the plan codes do not have to match.

Additionally, the units you want to link to on that active coverage must have the same County, Type, and Practice as the source policy’s units.

2.

The same Reinsurance Year, Agency, and State as the source policy.

Also, you must be able to access both the source and companion policies. If you have access to/are the agent on a source policy but the companion policy is assigned to an agent whose policies you don’t have access to, then you cannot create a link between the policies.

Only specific detail line information will be synced when source and companion policies are linked. The following Detail Line information is synced:

•

Practice Code

•

Type Code

•

Rate Class

•

Map Area

•

Reported Acres

•

Plant Date

•

Guarantee Reduction Flag

•

Skip Row Factor/Row Width/Plant Pattern

•

UI Reason (Including Enrolled in ARC indicator)

•

Modified Acreage Code

•

Interval Acres Percent

•

Commodity Cropping Type Code

•

NonPremium Acreage Code

•

PP Indicator

•

Comments/Print Comments Indicator

•

Crop Options, if the companion coverage contains the same option as the source coverage at the detail line level

•

Acreage Type

•

No Longer Farming Designation

•

CLU Tolerance Flag

•

Unreported NS Year List (Native Sod)

Plus, all Land IDs and CLUs from the source record will sync to linked companion records. When a link is initially established, any existing Land ID and CLU records on the companion records will be overwritten with source record information. New and/or modified Land IDs and CLUs on the source record from that point forward will sync to the linked companion record.

Data on the source record is editable until the lockout date; however, the synced data on the linked companion record is not editable unless the link is broken.

Any changes made to the source record before the lockout date will be carried to the companion record on save.

What Data is not Synced

Since APH history is not required to match between source and companion records, no APH information will be synced from source units.

Additionally, no Shareholders will be synced to the companion during the initial rollout.