Mid-Term Adjustment

Version: Not versioned (stub)
This version: 2026-09-01
Status: Stub. Scope indicated only; not yet open for comment.
Licence: CC BY 4.0 (text). Schemas, when published, under Apache 2.0.
Conventions: RFC 2119 keywords and addressed roles
Steward: Marrow (onmarrow.com), on behalf of the Agent Mediated Insurance (AMI) working group
Interaction: Mid-Term Adjustment (MTA)
Action risk class: 2 Transact

This is a scope stub, not a standard. It records the shape of an interaction that will be specified in a later version, so that an implementer building against New Business today can see what is coming and where it will attach. It states no requirements.

Scope

Mid-Term Adjustment is the interaction that changes a live policy: adding a driver, changing a vehicle, changing an address, changing a sum insured. It is an action risk Class 2 interaction, because it changes a contract and can move money, so it requires authenticated identity and the amend scope defined in the Consent, Authority and Scopes Standard. It reads policy data under read:policy, and where the adjusted premium would fall outside the granted cap it triggers step-up confirmation on the same terms as a bind.

Distinctive requirements

These are the requirements that distinguish MTA from New Business. They will be specified in full in a later version.

• Authentication to the existing policy, not merely to the person.
• Re-rating of the changed risk.
• The mid-term additional premium or refund, and its disclosure to the customer before the change is made.
• Possible re-underwriting and referral, where the change moves the risk outside appetite.
• Effective date handling: when the change takes effect, and what the customer is covered for in the meantime.

Authority and cap semantics are not restated here. They are defined in the scope ladder (Consent, Authority and Scopes 4.2) under amend, read:policy and pay:limit.

Not yet open for comment. Scope indicated so implementers can see the direction of travel.