Sample XML Payloads for Events in the Account and Master Plan Instances Notifications Class
- Event 1001: Account Message Type “Account Activation” Requires Sending
- Event 1002: Account Message Type “Credit Card Expiry” Requires Sending
- Event 1003: Account Message Type “Dunning” Requires Sending
- Event 1004: Account Message Type “Invoice/Statement” Requires Sending
- Event 1005: Account Message Type “Password Reminder/Reset” Requires Sending
- Event 1006: Account Message Type “Contract Expiry/Renewal” Requires Sending
- Event 1008: Account Message Type “Account Deactivation” Requires Sending
- Event 1009: Account Message Type “Account Welcome” Requires Sending
- Event 1010: Message Type “Account Activation” Sent To Account Holder
- Event 1011: Message Type “Broadcast” Sent To Account Holder
- Event 1012: Message Type “Credit Card Expiry” Sent To Account Holder
- Event 1013: Message Type “Dunning” Sent To Account Holder
- Event 1014: Message Type “Invoice/Statement” Sent To Account Holder
- Event 1015: Message Type “Account Comment/Note” Sent To Account Holder
- Event 1016: Message Type “Other” Sent To Account Holder
- Event 1017: Message Type “Password Reminder/Reset” Sent To Account Holder
- Event 1018: Message Type “Contract Expiry/Renewal” Sent To Account Holder
- Event 1020: Message Type “Account Deactivation” Sent To Account Holder
- Event 1021: Message Type “Unknown” Sent To Account Holder
- Event 1022: Message Type “Account Welcome” Sent To Account Holder
- Event 1024: Message Type “ARC Resource Threshold Warning” Sent To Account Holder
- Event 1025: Account Message Type “Broadcast” Requires Sending
- Event 1026: Account Message Type “Electronic Collection Attempt” Requires Sending
- Event 1027: Account Message Type “Account Comment/Note” Requires Sending
- Event 1028: Account Message Type “Other” Requires Sending
- Event 1029: Account Message Type “Electronic Refund Processed” Requires Sending
- Event 1030: Account Message Type “Supplemental Service Plan Change” Requires Sending
- Event 1031: Account Message Type “MTD Usage Threshold Over” Requires Sending
- Event 1032: Account Message Type “MTD Usage Threshold Under” Requires Sending
- Event 1033: Account Message Type “PTD Usage Threshold Over” Requires Sending
- Event 1034: Account Message Type “PTD Usage Threshold Under” Requires Sending
- Event 1035: Message Type “Electronic Collection Attempt” Sent To Account Holder
- Event 1036: Message Type “Electronic Refund Processed” Sent To Account Holder
- Event 1037: Message Type “Supplemental Service Plan Change” Sent To Account Holder
- Event 1038: Message Type “MTD Usage Threshold Over” Sent To Account Holder
- Event 1039: Message Type “MTD Usage Threshold Under” Sent To Account Holder
- Event 1040: Message Type “PTD Usage Threshold Over” Sent To Account Holder
- Event 1041: Message Type “PTD Usage Threshold Under” Sent To Account Holder
- Event 1042: Account Message Type “XML Statement” Requires Sending
- Event 1043: Credit Note Message Distilled
- Event 1044: Credit Note Message Sent
- Event 1045: Account Message Type “Payment Method Removed” Requires Sending
- Event 1046: Message Type “Payment Method Removed” Sent To Account Holder
- Event 1047: Account Message Type “MTD Unit Usage Threshold Over” Requires Sending
- Event 1048: Account Message Type “MTD Unit Usage Threshold Under” Requires Sending
- Event 1049: Account Message Type “PTD Unit Usage Threshold Over” Requires Sending
- Event 1050: Account Message Type “PTD Unit Usage Threshold Under” Requires Sending
- Event 1051: Message Type “MTD Unit Usage Threshold Over” Sent To Account Holder
- Event 1052: Message Type “MTD Unit Usage Threshold Under” Sent To Account Holder
- Event 1053: Message Type “PTD Unit Usage Threshold Over” Sent To Account Holder
- Event 1054: Message Type “PTD Unit Usage Threshold Under” Sent To Account Holder
- Event 1055: Account Message Type “Master Plan Instance Deprovisioned” Requires Sending
- Event 1056: Message Type “Master Plan Instance Deprovisioned” Sent to Account Holder
- Event 1057: Account Message Type “Contract End: Terminate Service and Billing” Requires Sending
- Event 1058: Account Message Type “Contract End: Terminate Service and Billing (Proration)” Requires Sending
- Event 1059: Account Message Type “Contract End: Continue Service” Requires Sending
- Event 1060: Account Message Type “Contract End: Renew Automatically” Requires Sending
- Event 1061: Account Message Type “Contract End: Rollover” Requires Sending
- Event 1062: Message Type “Contract End: Terminate Service and Billing” Sent to Account Holder
- Event 1063: Message Type “Contract End: Terminate Service and Billing (Proration)” Sent to Account Holder
- Event 1064: Message Type “Contract End: Continue Service” Sent to Account Holder
- Event 1065: Message Type “Contract End: Renew Automatically” Sent to Account Holder
- Event 1066: Message Type “Contract End: Rollover” Sent to Account Holder
- Event 1067: Account Message Type “Credit Card Update Required” Requires Sending
- Event 1068: Message Type “Credit Card Update Required” Sent to Account Holder
- Event 1069: Account Message Type “Contract Expiry – Continue Existing Service without Contract” Advance Notification Requires Sending
- Event 1070: Account Message Type “Contract Expiry – Rollover Automatically” Advance Notification Requires Sending
- Event 1071: Account Message Type “Contract Expiry – Terminate Service and Billing (Proration)” Advance Notification Requires Sending
- Event 1072: Account Message Type “Contract Expiry – Terminate Service and Billing” Advance Notification Requires Sending
- Event 1073: Account Message Type “Contract Renewal – Renew Automatically” Advance Notification Requires Sending
- Event 1074: Message Type “Contract Expiry – Continue Existing Service without Contract” Advance Notification Sent to Account Holder
- Event 1075: Message Type “Contract Expiry – Rollover Automatically” Advance Notification Sent to Account Holder
- Event 1076: Message Type “Contract Expiry – Terminate Service and Billing (Proration)” Advance Notification Sent to Account Holder
- Event 1077: Message Type “Contract Expiry – Terminate Service and Billing” Advance Notification Sent to Account Holder
- Event 1078: Message Type “Contract Renewal – Renew Automatically” Advance Notification Sent to Account Holder
- General Notes for System Integrators
This document provides a sample XML payload for each event in the Account and Master Plan Instances Notifications class. Use these samples as a reference when configuring your event notification receiver or when validating your integration against the Version 3.3 XSD schema. For a complete list of events and their descriptions, see Events in the Account and Master Plan Instances Notifications Class. For field definitions, see Account and Master Plan Instances Notifications Event Fields.
Note: Always validate the <auth_key> value in each incoming payload against the authentication key configured in your Aria account before processing. Discard any payload that presents an unrecognized or mismatched key.
Event 1001: Account Message Type “Account Activation” Requires Sending
Aria sends this notification when a customer account activation message is distilled and queued for delivery.
<?xml version="1.0" encoding="UTF-8"?>
<apf2doc>
<request>
<version>3.1</version>
<sender>A</sender>
<transaction_id>100000001</transaction_id>
<action>A</action>
<class>N</class>
<auth_key>CLIENTAUTH12345</auth_key>
</request>
<client_no>10001</client_no>
<acct_no>12345678</acct_no>
<client_acct_id>CLIENT-ACCT-001</client_acct_id>
<userid>jsmith</userid>
<senior_acct_no></senior_acct_no>
<master_plan_instance_no>98765</master_plan_instance_no>
<client_plan_instance_id>MPI-STANDARD-001</client_plan_instance_id>
<resp_level_cd>0</resp_level_cd>
<resp_plan_instance_no></resp_plan_instance_no>
<in_event_scope_ind>1</in_event_scope_ind>
<msg_id>20001</msg_id>
<msg_class>A</msg_class>
<msg_class_label>Account Activation</msg_class_label>
<msg_creation_date>2026-06-15</msg_creation_date>
<msg_sent_date></msg_sent_date>
<msg_subject>Activate Your Account</msg_subject>
<msg_recipient_email_address>customer@example.com</msg_recipient_email_address>
<xml_statement_no></xml_statement_no>
<statement_no></statement_no>
<invoice_no></invoice_no>
<sequential_statement_id></sequential_statement_id>
<event_data>
<event_no>1001</event_no>
<event_label>Account Activation</event_label>
</event_data>
</apf2doc>
Note: Aria generates this event when a new account activation message has been distilled and is queued for delivery. Use this event to trigger downstream provisioning or CRM workflows that depend on confirmation that the activation notice has been prepared. Subscribe to event 1010 to confirm the message was delivered to your customer.
Event 1002: Account Message Type “Credit Card Expiry” Requires Sending
Aria sends this notification when a credit card expiry notification is distilled and queued for delivery.
<?xml version="1.0" encoding="UTF-8"?>
<apf2doc>
<request>
<version>3.1</version>
<sender>A</sender>
<transaction_id>100000008</transaction_id>
<action>A</action>
<class>N</class>
<auth_key>CLIENTAUTH12345</auth_key>
</request>
<client_no>10001</client_no>
<acct_no>12345678</acct_no>
<client_acct_id>CLIENT-ACCT-001</client_acct_id>
<userid>jsmith</userid>
<senior_acct_no></senior_acct_no>
<master_plan_instance_no>98765</master_plan_instance_no>
<client_plan_instance_id>MPI-STANDARD-001</client_plan_instance_id>
<resp_level_cd>0</resp_level_cd>
<resp_plan_instance_no></resp_plan_instance_no>
<in_event_scope_ind>1</in_event_scope_ind>
<msg_id>20002</msg_id>
<msg_class>C</msg_class>
<msg_class_label>Credit Card Expiry</msg_class_label>
<msg_creation_date>2026-06-15</msg_creation_date>
<msg_sent_date></msg_sent_date>
<msg_subject>Your Credit Card Is Expiring Soon</msg_subject>
<msg_recipient_email_address>customer@example.com</msg_recipient_email_address>
<xml_statement_no></xml_statement_no>
<statement_no></statement_no>
<invoice_no></invoice_no>
<sequential_statement_id></sequential_statement_id>
<event_data>
<event_no>1002</event_no>
<event_label>Credit Card Expiry</event_label>
</event_data>
</apf2doc>
Note: This event fires before the credit card expiry message is sent. Use it to flag the account for proactive outreach or to pre-stage a payment method update workflow. Subscribe to event 1012 to confirm the message reached your customer.
Event 1003: Account Message Type “Dunning” Requires Sending
Aria sends this notification when a dunning message is distilled and queued for delivery.
<?xml version="1.0" encoding="UTF-8"?>
<apf2doc>
<request>
<version>3.1</version>
<sender>A</sender>
<transaction_id>100000015</transaction_id>
<action>A</action>
<class>N</class>
<auth_key>CLIENTAUTH12345</auth_key>
</request>
<client_no>10001</client_no>
<acct_no>12345678</acct_no>
<client_acct_id>CLIENT-ACCT-001</client_acct_id>
<userid>jsmith</userid>
<senior_acct_no></senior_acct_no>
<master_plan_instance_no>98765</master_plan_instance_no>
<client_plan_instance_id>MPI-STANDARD-001</client_plan_instance_id>
<resp_level_cd>0</resp_level_cd>
<resp_plan_instance_no></resp_plan_instance_no>
<in_event_scope_ind>1</in_event_scope_ind>
<msg_id>20003</msg_id>
<msg_class>D</msg_class>
<msg_class_label>Dunning</msg_class_label>
<msg_creation_date>2026-06-15</msg_creation_date>
<msg_sent_date></msg_sent_date>
<msg_subject>Action Required: Outstanding Balance on Your Account</msg_subject>
<msg_recipient_email_address>customer@example.com</msg_recipient_email_address>
<xml_statement_no></xml_statement_no>
<statement_no></statement_no>
<invoice_no></invoice_no>
<sequential_statement_id></sequential_statement_id>
<event_data>
<event_no>1003</event_no>
<event_label>Dunning</event_label>
</event_data>
</apf2doc>
Note: This event fires when Aria has distilled a dunning notice. Use it to flag the account as delinquent in your CRM or to initiate a collections workflow. Do not suspend service until the dunning cycle is complete; subscribe to event 1013 to confirm the message was sent.
Event 1004: Account Message Type “Invoice/Statement” Requires Sending
Aria sends this notification when an invoice or statement notification is distilled and queued for delivery.
<?xml version="1.0" encoding="UTF-8"?>
<apf2doc>
<request>
<version>3.1</version>
<sender>A</sender>
<transaction_id>100000022</transaction_id>
<action>A</action>
<class>N</class>
<auth_key>CLIENTAUTH12345</auth_key>
</request>
<client_no>10001</client_no>
<acct_no>12345678</acct_no>
<client_acct_id>CLIENT-ACCT-001</client_acct_id>
<userid>jsmith</userid>
<senior_acct_no></senior_acct_no>
<master_plan_instance_no>98765</master_plan_instance_no>
<client_plan_instance_id>MPI-STANDARD-001</client_plan_instance_id>
<resp_level_cd>0</resp_level_cd>
<resp_plan_instance_no></resp_plan_instance_no>
<in_event_scope_ind>1</in_event_scope_ind>
<msg_id>20004</msg_id>
<msg_class>I</msg_class>
<msg_class_label>Invoice/Statement</msg_class_label>
<msg_creation_date>2026-06-15</msg_creation_date>
<msg_sent_date></msg_sent_date>
<msg_subject>Your Invoice Is Ready</msg_subject>
<msg_recipient_email_address>customer@example.com</msg_recipient_email_address>
<xml_statement_no></xml_statement_no>
<statement_no>500004</statement_no>
<invoice_no>INV-2026-1004</invoice_no>
<sequential_statement_id>704</sequential_statement_id>
<event_data>
<event_no>1004</event_no>
<event_label>Invoice/Statement</event_label>
</event_data>
</apf2doc>
Note: The <invoice_no> and <statement_no> fields identify the billing document associated with this notification. Cache these values so you can correlate the sent-message event (1014) with the correct invoice. Subscribe to event 1014 to confirm delivery to your customer.
Event 1005: Account Message Type “Password Reminder/Reset” Requires Sending
Aria sends this notification when a password reminder or reset notification is distilled and queued for delivery.
<?xml version="1.0" encoding="UTF-8"?>
<apf2doc>
<request>
<version>3.1</version>
<sender>A</sender>
<transaction_id>100000029</transaction_id>
<action>A</action>
<class>N</class>
<auth_key>CLIENTAUTH12345</auth_key>
</request>
<client_no>10001</client_no>
<acct_no>12345678</acct_no>
<client_acct_id>CLIENT-ACCT-001</client_acct_id>
<userid>jsmith</userid>
<senior_acct_no></senior_acct_no>
<master_plan_instance_no>98765</master_plan_instance_no>
<client_plan_instance_id>MPI-STANDARD-001</client_plan_instance_id>
<resp_level_cd>0</resp_level_cd>
<resp_plan_instance_no></resp_plan_instance_no>
<in_event_scope_ind>1</in_event_scope_ind>
<msg_id>20005</msg_id>
<msg_class>P</msg_class>
<msg_class_label>Password Reminder/Reset</msg_class_label>
<msg_creation_date>2026-06-15</msg_creation_date>
<msg_sent_date></msg_sent_date>
<msg_subject>Reset Your Password</msg_subject>
<msg_recipient_email_address>customer@example.com</msg_recipient_email_address>
<xml_statement_no></xml_statement_no>
<statement_no></statement_no>
<invoice_no></invoice_no>
<sequential_statement_id></sequential_statement_id>
<event_data>
<event_no>1005</event_no>
<event_label>Password Reminder/Reset</event_label>
</event_data>
</apf2doc>
Note: This event fires when Aria has prepared a password reset notification. If your system manages its own authentication, you can use this event to initiate a parallel password reset flow. Subscribe to event 1017 to confirm the message was delivered.
Event 1006: Account Message Type “Contract Expiry/Renewal” Requires Sending
Aria sends this notification when a contract expiry or renewal notification is distilled and queued for delivery.
<?xml version="1.0" encoding="UTF-8"?>
<apf2doc>
<request>
<version>3.1</version>
<sender>A</sender>
<transaction_id>100000036</transaction_id>
<action>A</action>
<class>N</class>
<auth_key>CLIENTAUTH12345</auth_key>
</request>
<client_no>10001</client_no>
<acct_no>12345678</acct_no>
<client_acct_id>CLIENT-ACCT-001</client_acct_id>
<userid>jsmith</userid>
<senior_acct_no></senior_acct_no>
<master_plan_instance_no>98765</master_plan_instance_no>
<client_plan_instance_id>MPI-STANDARD-001</client_plan_instance_id>
<resp_level_cd>0</resp_level_cd>
<resp_plan_instance_no></resp_plan_instance_no>
<in_event_scope_ind>1</in_event_scope_ind>
<msg_id>20006</msg_id>
<msg_class>E</msg_class>
<msg_class_label>Contract Expiry/Renewal</msg_class_label>
<msg_creation_date>2026-06-15</msg_creation_date>
<msg_sent_date></msg_sent_date>
<msg_subject>Your Contract Is Expiring Soon</msg_subject>
<msg_recipient_email_address>customer@example.com</msg_recipient_email_address>
<xml_statement_no></xml_statement_no>
<statement_no></statement_no>
<invoice_no></invoice_no>
<sequential_statement_id></sequential_statement_id>
<event_data>
<event_no>1006</event_no>
<event_label>Contract Expiry/Renewal</event_label>
</event_data>
</apf2doc>
Note: Use this event to trigger a renewal workflow or to alert your sales team. The <master_plan_instance_no> field identifies the plan instance whose contract is expiring. Subscribe to event 1018 to confirm the message was delivered to your customer.
Event 1008: Account Message Type “Account Deactivation” Requires Sending
Aria sends this notification when an account deactivation notification is distilled and queued for delivery.
<?xml version="1.0" encoding="UTF-8"?>
<apf2doc>
<request>
<version>3.1</version>
<sender>A</sender>
<transaction_id>100000043</transaction_id>
<action>A</action>
<class>N</class>
<auth_key>CLIENTAUTH12345</auth_key>
</request>
<client_no>10001</client_no>
<acct_no>12345678</acct_no>
<client_acct_id>CLIENT-ACCT-001</client_acct_id>
<userid>jsmith</userid>
<senior_acct_no></senior_acct_no>
<master_plan_instance_no>98765</master_plan_instance_no>
<client_plan_instance_id>MPI-STANDARD-001</client_plan_instance_id>
<resp_level_cd>0</resp_level_cd>
<resp_plan_instance_no></resp_plan_instance_no>
<in_event_scope_ind>1</in_event_scope_ind>
<msg_id>20007</msg_id>
<msg_class>X</msg_class>
<msg_class_label>Account Deactivation</msg_class_label>
<msg_creation_date>2026-06-15</msg_creation_date>
<msg_sent_date></msg_sent_date>
<msg_subject>Your Account Has Been Deactivated</msg_subject>
<msg_recipient_email_address>customer@example.com</msg_recipient_email_address>
<xml_statement_no></xml_statement_no>
<statement_no></statement_no>
<invoice_no></invoice_no>
<sequential_statement_id></sequential_statement_id>
<event_data>
<event_no>1008</event_no>
<event_label>Account Deactivation</event_label>
</event_data>
</apf2doc>
Note: Do not revoke customer access until event 1020 fires, confirming the deactivation message was sent. Use this event to begin pre-deactivation cleanup tasks such as archiving records or logging the deactivation intent in your CRM.
Event 1009: Account Message Type “Account Welcome” Requires Sending
Aria sends this notification when an account welcome message is distilled and queued for delivery.
<?xml version="1.0" encoding="UTF-8"?>
<apf2doc>
<request>
<version>3.1</version>
<sender>A</sender>
<transaction_id>100000050</transaction_id>
<action>A</action>
<class>N</class>
<auth_key>CLIENTAUTH12345</auth_key>
</request>
<client_no>10001</client_no>
<acct_no>12345678</acct_no>
<client_acct_id>CLIENT-ACCT-001</client_acct_id>
<userid>jsmith</userid>
<senior_acct_no></senior_acct_no>
<master_plan_instance_no>98765</master_plan_instance_no>
<client_plan_instance_id>MPI-STANDARD-001</client_plan_instance_id>
<resp_level_cd>0</resp_level_cd>
<resp_plan_instance_no></resp_plan_instance_no>
<in_event_scope_ind>1</in_event_scope_ind>
<msg_id>20008</msg_id>
<msg_class>W</msg_class>
<msg_class_label>Account Welcome</msg_class_label>
<msg_creation_date>2026-06-15</msg_creation_date>
<msg_sent_date></msg_sent_date>
<msg_subject>Welcome to Our Service</msg_subject>
<msg_recipient_email_address>customer@example.com</msg_recipient_email_address>
<xml_statement_no></xml_statement_no>
<statement_no></statement_no>
<invoice_no></invoice_no>
<sequential_statement_id></sequential_statement_id>
<event_data>
<event_no>1009</event_no>
<event_label>Account Welcome</event_label>
</event_data>
</apf2doc>
Note: This event fires after a new account is created and Aria has prepared the welcome notification. Use it to trigger onboarding workflows such as provisioning initial resources or scheduling a welcome call. Subscribe to event 1022 to confirm the welcome message was delivered.
Event 1010: Message Type “Account Activation” Sent To Account Holder
Aria sends this notification when the account activation message is delivered to your customer.
<?xml version="1.0" encoding="UTF-8"?>
<apf2doc>
<request>
<version>3.1</version>
<sender>A</sender>
<transaction_id>100000057</transaction_id>
<action>M</action>
<class>N</class>
<auth_key>CLIENTAUTH12345</auth_key>
</request>
<client_no>10001</client_no>
<acct_no>12345678</acct_no>
<client_acct_id>CLIENT-ACCT-001</client_acct_id>
<userid>jsmith</userid>
<senior_acct_no></senior_acct_no>
<master_plan_instance_no>98765</master_plan_instance_no>
<client_plan_instance_id>MPI-STANDARD-001</client_plan_instance_id>
<resp_level_cd>0</resp_level_cd>
<resp_plan_instance_no></resp_plan_instance_no>
<in_event_scope_ind>1</in_event_scope_ind>
<msg_id>20009</msg_id>
<msg_class>A</msg_class>
<msg_class_label>Account Activation</msg_class_label>
<msg_creation_date>2026-06-15</msg_creation_date>
<msg_sent_date>2026-06-15</msg_sent_date>
<msg_subject>Activate Your Account</msg_subject>
<msg_recipient_email_address>customer@example.com</msg_recipient_email_address>
<xml_statement_no></xml_statement_no>
<statement_no></statement_no>
<invoice_no></invoice_no>
<sequential_statement_id></sequential_statement_id>
<event_data>
<event_no>1010</event_no>
<event_label>Account Activation</event_label>
</event_data>
</apf2doc>
Note: The <msg_sent_date> field confirms the date the message was delivered. Use this event as the signal to mark the activation flow complete in your CRM or provisioning system. The <msg_recipient_email_address> field identifies the address that received the message.
Event 1011: Message Type “Broadcast” Sent To Account Holder
Aria sends this notification when a broadcast message is delivered to your customer.
<?xml version="1.0" encoding="UTF-8"?>
<apf2doc>
<request>
<version>3.1</version>
<sender>A</sender>
<transaction_id>100000064</transaction_id>
<action>M</action>
<class>N</class>
<auth_key>CLIENTAUTH12345</auth_key>
</request>
<client_no>10001</client_no>
<acct_no>12345678</acct_no>
<client_acct_id>CLIENT-ACCT-001</client_acct_id>
<userid>jsmith</userid>
<senior_acct_no></senior_acct_no>
<master_plan_instance_no>98765</master_plan_instance_no>
<client_plan_instance_id>MPI-STANDARD-001</client_plan_instance_id>
<resp_level_cd>0</resp_level_cd>
<resp_plan_instance_no></resp_plan_instance_no>
<in_event_scope_ind>1</in_event_scope_ind>
<msg_id>20010</msg_id>
<msg_class>B</msg_class>
<msg_class_label>Broadcast</msg_class_label>
<msg_creation_date>2026-06-15</msg_creation_date>
<msg_sent_date>2026-06-15</msg_sent_date>
<msg_subject>Important Service Announcement</msg_subject>
<msg_recipient_email_address>customer@example.com</msg_recipient_email_address>
<xml_statement_no></xml_statement_no>
<statement_no></statement_no>
<invoice_no></invoice_no>
<sequential_statement_id></sequential_statement_id>
<event_data>
<event_no>1011</event_no>
<event_label>Broadcast</event_label>
</event_data>
</apf2doc>
Note: Broadcast messages are sent to all qualifying accounts. If your system maintains a communication log, record the <msg_id> to enable deduplication; Aria may retry delivery and refire this event. Use <msg_recipient_email_address> to confirm the correct recipient received the message.
Event 1012: Message Type “Credit Card Expiry” Sent To Account Holder
Aria sends this notification when the credit card expiry notification is delivered to your customer.
<?xml version="1.0" encoding="UTF-8"?>
<apf2doc>
<request>
<version>3.1</version>
<sender>A</sender>
<transaction_id>100000071</transaction_id>
<action>M</action>
<class>N</class>
<auth_key>CLIENTAUTH12345</auth_key>
</request>
<client_no>10001</client_no>
<acct_no>12345678</acct_no>
<client_acct_id>CLIENT-ACCT-001</client_acct_id>
<userid>jsmith</userid>
<senior_acct_no></senior_acct_no>
<master_plan_instance_no>98765</master_plan_instance_no>
<client_plan_instance_id>MPI-STANDARD-001</client_plan_instance_id>
<resp_level_cd>0</resp_level_cd>
<resp_plan_instance_no></resp_plan_instance_no>
<in_event_scope_ind>1</in_event_scope_ind>
<msg_id>20011</msg_id>
<msg_class>C</msg_class>
<msg_class_label>Credit Card Expiry</msg_class_label>
<msg_creation_date>2026-06-15</msg_creation_date>
<msg_sent_date>2026-06-15</msg_sent_date>
<msg_subject>Your Credit Card Is Expiring Soon</msg_subject>
<msg_recipient_email_address>customer@example.com</msg_recipient_email_address>
<xml_statement_no></xml_statement_no>
<statement_no></statement_no>
<invoice_no></invoice_no>
<sequential_statement_id></sequential_statement_id>
<event_data>
<event_no>1012</event_no>
<event_label>Credit Card Expiry</event_label>
</event_data>
</apf2doc>
Note: This event confirms the credit card expiry notice was delivered. If the customer does not update their payment method within your grace period, use the <acct_no> and <master_plan_instance_no> fields to locate the account and initiate a follow-up workflow.
Event 1013: Message Type “Dunning” Sent To Account Holder
Aria sends this notification when the dunning message is delivered to your customer.
<?xml version="1.0" encoding="UTF-8"?>
<apf2doc>
<request>
<version>3.1</version>
<sender>A</sender>
<transaction_id>100000078</transaction_id>
<action>M</action>
<class>N</class>
<auth_key>CLIENTAUTH12345</auth_key>
</request>
<client_no>10001</client_no>
<acct_no>12345678</acct_no>
<client_acct_id>CLIENT-ACCT-001</client_acct_id>
<userid>jsmith</userid>
<senior_acct_no></senior_acct_no>
<master_plan_instance_no>98765</master_plan_instance_no>
<client_plan_instance_id>MPI-STANDARD-001</client_plan_instance_id>
<resp_level_cd>0</resp_level_cd>
<resp_plan_instance_no></resp_plan_instance_no>
<in_event_scope_ind>1</in_event_scope_ind>
<msg_id>20012</msg_id>
<msg_class>D</msg_class>
<msg_class_label>Dunning</msg_class_label>
<msg_creation_date>2026-06-15</msg_creation_date>
<msg_sent_date>2026-06-15</msg_sent_date>
<msg_subject>Action Required: Outstanding Balance on Your Account</msg_subject>
<msg_recipient_email_address>customer@example.com</msg_recipient_email_address>
<xml_statement_no></xml_statement_no>
<statement_no></statement_no>
<invoice_no></invoice_no>
<sequential_statement_id></sequential_statement_id>
<event_data>
<event_no>1013</event_no>
<event_label>Dunning</event_label>
</event_data>
</apf2doc>
Note: Each dunning cycle generates a separate sent event. Use <msg_id> to distinguish individual dunning messages and to avoid applying duplicate account flags. Track dunning cycles by correlating this event with your collections workflow.
Event 1014: Message Type “Invoice/Statement” Sent To Account Holder
Aria sends this notification when the invoice or statement notification is delivered to your customer.
<?xml version="1.0" encoding="UTF-8"?>
<apf2doc>
<request>
<version>3.1</version>
<sender>A</sender>
<transaction_id>100000085</transaction_id>
<action>M</action>
<class>N</class>
<auth_key>CLIENTAUTH12345</auth_key>
</request>
<client_no>10001</client_no>
<acct_no>12345678</acct_no>
<client_acct_id>CLIENT-ACCT-001</client_acct_id>
<userid>jsmith</userid>
<senior_acct_no></senior_acct_no>
<master_plan_instance_no>98765</master_plan_instance_no>
<client_plan_instance_id>MPI-STANDARD-001</client_plan_instance_id>
<resp_level_cd>0</resp_level_cd>
<resp_plan_instance_no></resp_plan_instance_no>
<in_event_scope_ind>1</in_event_scope_ind>
<msg_id>20013</msg_id>
<msg_class>I</msg_class>
<msg_class_label>Invoice/Statement</msg_class_label>
<msg_creation_date>2026-06-15</msg_creation_date>
<msg_sent_date>2026-06-15</msg_sent_date>
<msg_subject>Your Invoice Is Ready</msg_subject>
<msg_recipient_email_address>customer@example.com</msg_recipient_email_address>
<xml_statement_no></xml_statement_no>
<statement_no>500013</statement_no>
<invoice_no>INV-2026-1013</invoice_no>
<sequential_statement_id>713</sequential_statement_id>
<event_data>
<event_no>1014</event_no>
<event_label>Invoice/Statement</event_label>
</event_data>
</apf2doc>
Note: Use the <invoice_no> and <statement_no> fields to correlate this delivery event with the billing document. If your system displays invoice delivery status, update the record when this event fires. The <msg_recipient_email_address> field confirms who received the notification.
Event 1015: Message Type “Account Comment/Note” Sent To Account Holder
Aria sends this notification when an account comment or note is delivered to your customer.
<?xml version="1.0" encoding="UTF-8"?>
<apf2doc>
<request>
<version>3.1</version>
<sender>A</sender>
<transaction_id>100000092</transaction_id>
<action>M</action>
<class>N</class>
<auth_key>CLIENTAUTH12345</auth_key>
</request>
<client_no>10001</client_no>
<acct_no>12345678</acct_no>
<client_acct_id>CLIENT-ACCT-001</client_acct_id>
<userid>jsmith</userid>
<senior_acct_no></senior_acct_no>
<master_plan_instance_no>98765</master_plan_instance_no>
<client_plan_instance_id>MPI-STANDARD-001</client_plan_instance_id>
<resp_level_cd>0</resp_level_cd>
<resp_plan_instance_no></resp_plan_instance_no>
<in_event_scope_ind>1</in_event_scope_ind>
<msg_id>20014</msg_id>
<msg_class>T</msg_class>
<msg_class_label>Account Comment/Note</msg_class_label>
<msg_creation_date>2026-06-15</msg_creation_date>
<msg_sent_date>2026-06-15</msg_sent_date>
<msg_subject>A Note Has Been Added to Your Account</msg_subject>
<msg_recipient_email_address>customer@example.com</msg_recipient_email_address>
<xml_statement_no></xml_statement_no>
<statement_no></statement_no>
<invoice_no></invoice_no>
<sequential_statement_id></sequential_statement_id>
<event_data>
<event_no>1015</event_no>
<event_label>Account Comment/Note</event_label>
</event_data>
</apf2doc>
Note: Use the <msg_subject> field to route the note to the appropriate team in your CRM. If your workflow logs outbound communications, record <msg_id> for deduplication.
Event 1016: Message Type “Other” Sent To Account Holder
Aria sends this notification when a message of type “Other” is delivered to your customer.
<?xml version="1.0" encoding="UTF-8"?>
<apf2doc>
<request>
<version>3.1</version>
<sender>A</sender>
<transaction_id>100000099</transaction_id>
<action>M</action>
<class>N</class>
<auth_key>CLIENTAUTH12345</auth_key>
</request>
<client_no>10001</client_no>
<acct_no>12345678</acct_no>
<client_acct_id>CLIENT-ACCT-001</client_acct_id>
<userid>jsmith</userid>
<senior_acct_no></senior_acct_no>
<master_plan_instance_no>98765</master_plan_instance_no>
<client_plan_instance_id>MPI-STANDARD-001</client_plan_instance_id>
<resp_level_cd>0</resp_level_cd>
<resp_plan_instance_no></resp_plan_instance_no>
<in_event_scope_ind>1</in_event_scope_ind>
<msg_id>20015</msg_id>
<msg_class>O</msg_class>
<msg_class_label>Other</msg_class_label>
<msg_creation_date>2026-06-15</msg_creation_date>
<msg_sent_date>2026-06-15</msg_sent_date>
<msg_subject>Message from Your Service Provider</msg_subject>
<msg_recipient_email_address>customer@example.com</msg_recipient_email_address>
<xml_statement_no></xml_statement_no>
<statement_no></statement_no>
<invoice_no></invoice_no>
<sequential_statement_id></sequential_statement_id>
<event_data>
<event_no>1016</event_no>
<event_label>Other</event_label>
</event_data>
</apf2doc>
Note: The “Other” message type is a catch-all for notifications that do not fit a standard category. Inspect <msg_subject> to determine the purpose of the message and route accordingly. Use <msg_id> to prevent duplicate processing if this event is replayed.
Event 1017: Message Type “Password Reminder/Reset” Sent To Account Holder
Aria sends this notification when the password reminder or reset notification is delivered to your customer.
<?xml version="1.0" encoding="UTF-8"?>
<apf2doc>
<request>
<version>3.1</version>
<sender>A</sender>
<transaction_id>100000106</transaction_id>
<action>M</action>
<class>N</class>
<auth_key>CLIENTAUTH12345</auth_key>
</request>
<client_no>10001</client_no>
<acct_no>12345678</acct_no>
<client_acct_id>CLIENT-ACCT-001</client_acct_id>
<userid>jsmith</userid>
<senior_acct_no></senior_acct_no>
<master_plan_instance_no>98765</master_plan_instance_no>
<client_plan_instance_id>MPI-STANDARD-001</client_plan_instance_id>
<resp_level_cd>0</resp_level_cd>
<resp_plan_instance_no></resp_plan_instance_no>
<in_event_scope_ind>1</in_event_scope_ind>
<msg_id>20016</msg_id>
<msg_class>P</msg_class>
<msg_class_label>Password Reminder/Reset</msg_class_label>
<msg_creation_date>2026-06-15</msg_creation_date>
<msg_sent_date>2026-06-15</msg_sent_date>
<msg_subject>Reset Your Password</msg_subject>
<msg_recipient_email_address>customer@example.com</msg_recipient_email_address>
<xml_statement_no></xml_statement_no>
<statement_no></statement_no>
<invoice_no></invoice_no>
<sequential_statement_id></sequential_statement_id>
<event_data>
<event_no>1017</event_no>
<event_label>Password Reminder/Reset</event_label>
</event_data>
</apf2doc>
Note: If your system issues its own password reset tokens, verify that the token has not already been used before acting on this event. Use <msg_sent_date> to enforce token expiry logic and <acct_no> to look up the customer record.
Event 1018: Message Type “Contract Expiry/Renewal” Sent To Account Holder
Aria sends this notification when the contract expiry or renewal notification is delivered to your customer.
<?xml version="1.0" encoding="UTF-8"?>
<apf2doc>
<request>
<version>3.1</version>
<sender>A</sender>
<transaction_id>100000113</transaction_id>
<action>M</action>
<class>N</class>
<auth_key>CLIENTAUTH12345</auth_key>
</request>
<client_no>10001</client_no>
<acct_no>12345678</acct_no>
<client_acct_id>CLIENT-ACCT-001</client_acct_id>
<userid>jsmith</userid>
<senior_acct_no></senior_acct_no>
<master_plan_instance_no>98765</master_plan_instance_no>
<client_plan_instance_id>MPI-STANDARD-001</client_plan_instance_id>
<resp_level_cd>0</resp_level_cd>
<resp_plan_instance_no></resp_plan_instance_no>
<in_event_scope_ind>1</in_event_scope_ind>
<msg_id>20017</msg_id>
<msg_class>E</msg_class>
<msg_class_label>Contract Expiry/Renewal</msg_class_label>
<msg_creation_date>2026-06-15</msg_creation_date>
<msg_sent_date>2026-06-15</msg_sent_date>
<msg_subject>Your Contract Is Expiring Soon</msg_subject>
<msg_recipient_email_address>customer@example.com</msg_recipient_email_address>
<xml_statement_no></xml_statement_no>
<statement_no></statement_no>
<invoice_no></invoice_no>
<sequential_statement_id></sequential_statement_id>
<event_data>
<event_no>1018</event_no>
<event_label>Contract Expiry/Renewal</event_label>
</event_data>
</apf2doc>
Note: Use <master_plan_instance_no> to identify the plan instance whose contract is expiring. If your CRM tracks renewal opportunities, create or update the opportunity record when this event fires. Subscribe to events 1069–1073 for advance contract-expiry notifications.
Event 1020: Message Type “Account Deactivation” Sent To Account Holder
Aria sends this notification when the account deactivation notification is delivered to your customer.
<?xml version="1.0" encoding="UTF-8"?>
<apf2doc>
<request>
<version>3.1</version>
<sender>A</sender>
<transaction_id>100000120</transaction_id>
<action>M</action>
<class>N</class>
<auth_key>CLIENTAUTH12345</auth_key>
</request>
<client_no>10001</client_no>
<acct_no>12345678</acct_no>
<client_acct_id>CLIENT-ACCT-001</client_acct_id>
<userid>jsmith</userid>
<senior_acct_no></senior_acct_no>
<master_plan_instance_no>98765</master_plan_instance_no>
<client_plan_instance_id>MPI-STANDARD-001</client_plan_instance_id>
<resp_level_cd>0</resp_level_cd>
<resp_plan_instance_no></resp_plan_instance_no>
<in_event_scope_ind>1</in_event_scope_ind>
<msg_id>20018</msg_id>
<msg_class>X</msg_class>
<msg_class_label>Account Deactivation</msg_class_label>
<msg_creation_date>2026-06-15</msg_creation_date>
<msg_sent_date>2026-06-15</msg_sent_date>
<msg_subject>Your Account Has Been Deactivated</msg_subject>
<msg_recipient_email_address>customer@example.com</msg_recipient_email_address>
<xml_statement_no></xml_statement_no>
<statement_no></statement_no>
<invoice_no></invoice_no>
<sequential_statement_id></sequential_statement_id>
<event_data>
<event_no>1020</event_no>
<event_label>Account Deactivation</event_label>
</event_data>
</apf2doc>
Note: This event confirms the deactivation message was delivered. After this event fires, it is safe to revoke customer access in downstream systems. Use <acct_no> and <client_acct_id> to locate the record and <msg_sent_date> to timestamp the deactivation confirmation.
Event 1021: Message Type “Unknown” Sent To Account Holder
Aria sends this notification when a message of unknown type is delivered to your customer.
<?xml version="1.0" encoding="UTF-8"?>
<apf2doc>
<request>
<version>3.1</version>
<sender>A</sender>
<transaction_id>100000127</transaction_id>
<action>M</action>
<class>N</class>
<auth_key>CLIENTAUTH12345</auth_key>
</request>
<client_no>10001</client_no>
<acct_no>12345678</acct_no>
<client_acct_id>CLIENT-ACCT-001</client_acct_id>
<userid>jsmith</userid>
<senior_acct_no></senior_acct_no>
<master_plan_instance_no>98765</master_plan_instance_no>
<client_plan_instance_id>MPI-STANDARD-001</client_plan_instance_id>
<resp_level_cd>0</resp_level_cd>
<resp_plan_instance_no></resp_plan_instance_no>
<in_event_scope_ind>1</in_event_scope_ind>
<msg_id>20019</msg_id>
<msg_class>U</msg_class>
<msg_class_label>Unknown</msg_class_label>
<msg_creation_date>2026-06-15</msg_creation_date>
<msg_sent_date>2026-06-15</msg_sent_date>
<msg_subject>Message Sent</msg_subject>
<msg_recipient_email_address>customer@example.com</msg_recipient_email_address>
<xml_statement_no></xml_statement_no>
<statement_no></statement_no>
<invoice_no></invoice_no>
<sequential_statement_id></sequential_statement_id>
<event_data>
<event_no>1021</event_no>
<event_label>Unknown</event_label>
</event_data>
</apf2doc>
Note: This event fires when a message with an unrecognized type is delivered. Log the <msg_class> and <msg_id> values for investigation. If your integration layer routes messages by type, route unknown messages to a default handler rather than discarding them.
Event 1022: Message Type “Account Welcome” Sent To Account Holder
Aria sends this notification when the account welcome message is delivered to your customer.
<?xml version="1.0" encoding="UTF-8"?>
<apf2doc>
<request>
<version>3.1</version>
<sender>A</sender>
<transaction_id>100000134</transaction_id>
<action>M</action>
<class>N</class>
<auth_key>CLIENTAUTH12345</auth_key>
</request>
<client_no>10001</client_no>
<acct_no>12345678</acct_no>
<client_acct_id>CLIENT-ACCT-001</client_acct_id>
<userid>jsmith</userid>
<senior_acct_no></senior_acct_no>
<master_plan_instance_no>98765</master_plan_instance_no>
<client_plan_instance_id>MPI-STANDARD-001</client_plan_instance_id>
<resp_level_cd>0</resp_level_cd>
<resp_plan_instance_no></resp_plan_instance_no>
<in_event_scope_ind>1</in_event_scope_ind>
<msg_id>20020</msg_id>
<msg_class>W</msg_class>
<msg_class_label>Account Welcome</msg_class_label>
<msg_creation_date>2026-06-15</msg_creation_date>
<msg_sent_date>2026-06-15</msg_sent_date>
<msg_subject>Welcome to Our Service</msg_subject>
<msg_recipient_email_address>customer@example.com</msg_recipient_email_address>
<xml_statement_no></xml_statement_no>
<statement_no></statement_no>
<invoice_no></invoice_no>
<sequential_statement_id></sequential_statement_id>
<event_data>
<event_no>1022</event_no>
<event_label>Account Welcome</event_label>
</event_data>
</apf2doc>
Note: This event confirms the welcome message was delivered to the new customer. Use it as the trigger to mark onboarding step one complete in your provisioning system. Correlate with event 1009 (the distillation event) using <msg_id> to track the full message lifecycle.
Event 1024: Message Type “ARC Resource Threshold Warning” Sent To Account Holder
Aria sends this notification when an ARC resource threshold warning is delivered to your customer.
<?xml version="1.0" encoding="UTF-8"?>
<apf2doc>
<request>
<version>3.1</version>
<sender>A</sender>
<transaction_id>100000141</transaction_id>
<action>M</action>
<class>N</class>
<auth_key>CLIENTAUTH12345</auth_key>
</request>
<client_no>10001</client_no>
<acct_no>12345678</acct_no>
<client_acct_id>CLIENT-ACCT-001</client_acct_id>
<userid>jsmith</userid>
<senior_acct_no></senior_acct_no>
<master_plan_instance_no>98765</master_plan_instance_no>
<client_plan_instance_id>MPI-STANDARD-001</client_plan_instance_id>
<resp_level_cd>0</resp_level_cd>
<resp_plan_instance_no></resp_plan_instance_no>
<in_event_scope_ind>1</in_event_scope_ind>
<msg_id>20021</msg_id>
<msg_class>G</msg_class>
<msg_class_label>ARC Resource Threshold Warning</msg_class_label>
<msg_creation_date>2026-06-15</msg_creation_date>
<msg_sent_date>2026-06-15</msg_sent_date>
<msg_subject>Resource Usage Threshold Warning</msg_subject>
<msg_recipient_email_address>customer@example.com</msg_recipient_email_address>
<xml_statement_no></xml_statement_no>
<statement_no></statement_no>
<invoice_no></invoice_no>
<sequential_statement_id></sequential_statement_id>
<event_data>
<event_no>1024</event_no>
<event_label>ARC Resource Threshold Warning</event_label>
</event_data>
</apf2doc>
Note: This event fires when a customer’s resource consumption approaches a configured threshold. Use <acct_no> and <master_plan_instance_no> to locate the account and review current usage. If your system enforces resource caps, use this event to pre-stage a throttling action.
Event 1025: Account Message Type “Broadcast” Requires Sending
Aria sends this notification when a broadcast message is distilled and queued for delivery.
<?xml version="1.0" encoding="UTF-8"?>
<apf2doc>
<request>
<version>3.1</version>
<sender>A</sender>
<transaction_id>100000148</transaction_id>
<action>A</action>
<class>N</class>
<auth_key>CLIENTAUTH12345</auth_key>
</request>
<client_no>10001</client_no>
<acct_no>12345678</acct_no>
<client_acct_id>CLIENT-ACCT-001</client_acct_id>
<userid>jsmith</userid>
<senior_acct_no></senior_acct_no>
<master_plan_instance_no>98765</master_plan_instance_no>
<client_plan_instance_id>MPI-STANDARD-001</client_plan_instance_id>
<resp_level_cd>0</resp_level_cd>
<resp_plan_instance_no></resp_plan_instance_no>
<in_event_scope_ind>1</in_event_scope_ind>
<msg_id>20022</msg_id>
<msg_class>B</msg_class>
<msg_class_label>Broadcast</msg_class_label>
<msg_creation_date>2026-06-15</msg_creation_date>
<msg_sent_date></msg_sent_date>
<msg_subject>Important Service Announcement</msg_subject>
<msg_recipient_email_address>customer@example.com</msg_recipient_email_address>
<xml_statement_no></xml_statement_no>
<statement_no></statement_no>
<invoice_no></invoice_no>
<sequential_statement_id></sequential_statement_id>
<event_data>
<event_no>1025</event_no>
<event_label>Broadcast</event_label>
</event_data>
</apf2doc>
Note: Broadcast messages are sent to all qualifying accounts at once. Because this event fires once per account, your integration may receive a high volume of events simultaneously during a broadcast campaign. Implement rate limiting and idempotency checks using <msg_id> and <transaction_id>.
Event 1026: Account Message Type “Electronic Collection Attempt” Requires Sending
Aria sends this notification when an electronic collection attempt notification is distilled and queued for delivery.
<?xml version="1.0" encoding="UTF-8"?>
<apf2doc>
<request>
<version>3.1</version>
<sender>A</sender>
<transaction_id>100000155</transaction_id>
<action>A</action>
<class>N</class>
<auth_key>CLIENTAUTH12345</auth_key>
</request>
<client_no>10001</client_no>
<acct_no>12345678</acct_no>
<client_acct_id>CLIENT-ACCT-001</client_acct_id>
<userid>jsmith</userid>
<senior_acct_no></senior_acct_no>
<master_plan_instance_no>98765</master_plan_instance_no>
<client_plan_instance_id>MPI-STANDARD-001</client_plan_instance_id>
<resp_level_cd>0</resp_level_cd>
<resp_plan_instance_no></resp_plan_instance_no>
<in_event_scope_ind>1</in_event_scope_ind>
<msg_id>20023</msg_id>
<msg_class>L</msg_class>
<msg_class_label>Electronic Collection Attempt</msg_class_label>
<msg_creation_date>2026-06-15</msg_creation_date>
<msg_sent_date></msg_sent_date>
<msg_subject>Payment Collection Attempt Initiated</msg_subject>
<msg_recipient_email_address>customer@example.com</msg_recipient_email_address>
<xml_statement_no></xml_statement_no>
<statement_no></statement_no>
<invoice_no></invoice_no>
<sequential_statement_id></sequential_statement_id>
<event_data>
<event_no>1026</event_no>
<event_label>Electronic Collection Attempt</event_label>
</event_data>
</apf2doc>
Note: This event fires when Aria has prepared a notification about an electronic payment collection attempt. Use it to flag the account in your payments system as having an in-progress collection. Subscribe to event 1035 to confirm the notification was delivered to your customer.
Event 1027: Account Message Type “Account Comment/Note” Requires Sending
Aria sends this notification when an account comment or note is distilled and queued for delivery.
<?xml version="1.0" encoding="UTF-8"?>
<apf2doc>
<request>
<version>3.1</version>
<sender>A</sender>
<transaction_id>100000162</transaction_id>
<action>A</action>
<class>N</class>
<auth_key>CLIENTAUTH12345</auth_key>
</request>
<client_no>10001</client_no>
<acct_no>12345678</acct_no>
<client_acct_id>CLIENT-ACCT-001</client_acct_id>
<userid>jsmith</userid>
<senior_acct_no></senior_acct_no>
<master_plan_instance_no>98765</master_plan_instance_no>
<client_plan_instance_id>MPI-STANDARD-001</client_plan_instance_id>
<resp_level_cd>0</resp_level_cd>
<resp_plan_instance_no></resp_plan_instance_no>
<in_event_scope_ind>1</in_event_scope_ind>
<msg_id>20024</msg_id>
<msg_class>T</msg_class>
<msg_class_label>Account Comment/Note</msg_class_label>
<msg_creation_date>2026-06-15</msg_creation_date>
<msg_sent_date></msg_sent_date>
<msg_subject>A Note Has Been Added to Your Account</msg_subject>
<msg_recipient_email_address>customer@example.com</msg_recipient_email_address>
<xml_statement_no></xml_statement_no>
<statement_no></statement_no>
<invoice_no></invoice_no>
<sequential_statement_id></sequential_statement_id>
<event_data>
<event_no>1027</event_no>
<event_label>Account Comment/Note</event_label>
</event_data>
</apf2doc>
Note: This event fires when Aria has prepared a comment or note for delivery to the customer. Use <msg_subject> to preview the note content and route the event to the appropriate team. Subscribe to event 1015 to confirm the note was delivered.
Event 1028: Account Message Type “Other” Requires Sending
Aria sends this notification when a message of type “Other” is distilled and queued for delivery.
<?xml version="1.0" encoding="UTF-8"?>
<apf2doc>
<request>
<version>3.1</version>
<sender>A</sender>
<transaction_id>100000169</transaction_id>
<action>A</action>
<class>N</class>
<auth_key>CLIENTAUTH12345</auth_key>
</request>
<client_no>10001</client_no>
<acct_no>12345678</acct_no>
<client_acct_id>CLIENT-ACCT-001</client_acct_id>
<userid>jsmith</userid>
<senior_acct_no></senior_acct_no>
<master_plan_instance_no>98765</master_plan_instance_no>
<client_plan_instance_id>MPI-STANDARD-001</client_plan_instance_id>
<resp_level_cd>0</resp_level_cd>
<resp_plan_instance_no></resp_plan_instance_no>
<in_event_scope_ind>1</in_event_scope_ind>
<msg_id>20025</msg_id>
<msg_class>O</msg_class>
<msg_class_label>Other</msg_class_label>
<msg_creation_date>2026-06-15</msg_creation_date>
<msg_sent_date></msg_sent_date>
<msg_subject>Message from Your Service Provider</msg_subject>
<msg_recipient_email_address>customer@example.com</msg_recipient_email_address>
<xml_statement_no></xml_statement_no>
<statement_no></statement_no>
<invoice_no></invoice_no>
<sequential_statement_id></sequential_statement_id>
<event_data>
<event_no>1028</event_no>
<event_label>Other</event_label>
</event_data>
</apf2doc>
Note: The “Other” message type covers notifications that do not map to a standard category. Inspect <msg_class> and <msg_subject> to determine appropriate routing. Subscribe to event 1016 to confirm delivery.
Event 1029: Account Message Type “Electronic Refund Processed” Requires Sending
Aria sends this notification when an electronic refund notification is distilled and queued for delivery.
<?xml version="1.0" encoding="UTF-8"?>
<apf2doc>
<request>
<version>3.1</version>
<sender>A</sender>
<transaction_id>100000176</transaction_id>
<action>A</action>
<class>N</class>
<auth_key>CLIENTAUTH12345</auth_key>
</request>
<client_no>10001</client_no>
<acct_no>12345678</acct_no>
<client_acct_id>CLIENT-ACCT-001</client_acct_id>
<userid>jsmith</userid>
<senior_acct_no></senior_acct_no>
<master_plan_instance_no>98765</master_plan_instance_no>
<client_plan_instance_id>MPI-STANDARD-001</client_plan_instance_id>
<resp_level_cd>0</resp_level_cd>
<resp_plan_instance_no></resp_plan_instance_no>
<in_event_scope_ind>1</in_event_scope_ind>
<msg_id>20026</msg_id>
<msg_class>R</msg_class>
<msg_class_label>Electronic Refund Processed</msg_class_label>
<msg_creation_date>2026-06-15</msg_creation_date>
<msg_sent_date></msg_sent_date>
<msg_subject>Your Refund Has Been Processed</msg_subject>
<msg_recipient_email_address>customer@example.com</msg_recipient_email_address>
<xml_statement_no></xml_statement_no>
<statement_no></statement_no>
<invoice_no></invoice_no>
<sequential_statement_id></sequential_statement_id>
<event_data>
<event_no>1029</event_no>
<event_label>Electronic Refund Processed</event_label>
</event_data>
</apf2doc>
Note: This event fires when Aria has prepared a refund notification. Use it to update the refund record in your payments system to “notification queued” status. Subscribe to event 1036 to confirm the notification was delivered to your customer.
Event 1030: Account Message Type “Supplemental Service Plan Change” Requires Sending
Aria sends this notification when a supplemental service plan change notification is distilled and queued for delivery.
<?xml version="1.0" encoding="UTF-8"?>
<apf2doc>
<request>
<version>3.1</version>
<sender>A</sender>
<transaction_id>100000183</transaction_id>
<action>A</action>
<class>N</class>
<auth_key>CLIENTAUTH12345</auth_key>
</request>
<client_no>10001</client_no>
<acct_no>12345678</acct_no>
<client_acct_id>CLIENT-ACCT-001</client_acct_id>
<userid>jsmith</userid>
<senior_acct_no></senior_acct_no>
<master_plan_instance_no>98765</master_plan_instance_no>
<client_plan_instance_id>MPI-STANDARD-001</client_plan_instance_id>
<resp_level_cd>0</resp_level_cd>
<resp_plan_instance_no></resp_plan_instance_no>
<in_event_scope_ind>1</in_event_scope_ind>
<msg_id>20027</msg_id>
<msg_class>S</msg_class>
<msg_class_label>Supplemental Service Plan Change</msg_class_label>
<msg_creation_date>2026-06-15</msg_creation_date>
<msg_sent_date></msg_sent_date>
<msg_subject>Your Service Plan Has Changed</msg_subject>
<msg_recipient_email_address>customer@example.com</msg_recipient_email_address>
<xml_statement_no></xml_statement_no>
<statement_no></statement_no>
<invoice_no></invoice_no>
<sequential_statement_id></sequential_statement_id>
<event_data>
<event_no>1030</event_no>
<event_label>Supplemental Service Plan Change</event_label>
</event_data>
</apf2doc>
Note: This event fires when Aria has prepared a notification about a change to a supplemental service plan. Use <master_plan_instance_no> to identify the affected plan instance and begin pre-delivery service updates if needed. Subscribe to event 1037 to confirm delivery.
Event 1031: Account Message Type “MTD Usage Threshold Over” Requires Sending
Aria sends this notification when a month-to-date usage threshold over notification is distilled and queued for delivery.
<?xml version="1.0" encoding="UTF-8"?>
<apf2doc>
<request>
<version>3.1</version>
<sender>A</sender>
<transaction_id>100000190</transaction_id>
<action>A</action>
<class>N</class>
<auth_key>CLIENTAUTH12345</auth_key>
</request>
<client_no>10001</client_no>
<acct_no>12345678</acct_no>
<client_acct_id>CLIENT-ACCT-001</client_acct_id>
<userid>jsmith</userid>
<senior_acct_no></senior_acct_no>
<master_plan_instance_no>98765</master_plan_instance_no>
<client_plan_instance_id>MPI-STANDARD-001</client_plan_instance_id>
<resp_level_cd>0</resp_level_cd>
<resp_plan_instance_no></resp_plan_instance_no>
<in_event_scope_ind>1</in_event_scope_ind>
<msg_id>20028</msg_id>
<msg_class>M</msg_class>
<msg_class_label>MTD Usage Threshold Over</msg_class_label>
<msg_creation_date>2026-06-15</msg_creation_date>
<msg_sent_date></msg_sent_date>
<msg_subject>Month-to-Date Usage Threshold Exceeded</msg_subject>
<msg_recipient_email_address>customer@example.com</msg_recipient_email_address>
<xml_statement_no></xml_statement_no>
<statement_no></statement_no>
<invoice_no></invoice_no>
<sequential_statement_id></sequential_statement_id>
<event_data>
<event_no>1031</event_no>
<event_label>MTD Usage Threshold Over</event_label>
</event_data>
</apf2doc>
Note: This event fires when month-to-date usage has crossed a configured over-threshold. Use it to trigger a usage alert in your operations dashboard before the message reaches the customer. Subscribe to event 1038 to confirm the customer notification was delivered.
Event 1032: Account Message Type “MTD Usage Threshold Under” Requires Sending
Aria sends this notification when a month-to-date usage threshold under notification is distilled and queued for delivery.
<?xml version="1.0" encoding="UTF-8"?>
<apf2doc>
<request>
<version>3.1</version>
<sender>A</sender>
<transaction_id>100000197</transaction_id>
<action>A</action>
<class>N</class>
<auth_key>CLIENTAUTH12345</auth_key>
</request>
<client_no>10001</client_no>
<acct_no>12345678</acct_no>
<client_acct_id>CLIENT-ACCT-001</client_acct_id>
<userid>jsmith</userid>
<senior_acct_no></senior_acct_no>
<master_plan_instance_no>98765</master_plan_instance_no>
<client_plan_instance_id>MPI-STANDARD-001</client_plan_instance_id>
<resp_level_cd>0</resp_level_cd>
<resp_plan_instance_no></resp_plan_instance_no>
<in_event_scope_ind>1</in_event_scope_ind>
<msg_id>20029</msg_id>
<msg_class>V</msg_class>
<msg_class_label>MTD Usage Threshold Under</msg_class_label>
<msg_creation_date>2026-06-15</msg_creation_date>
<msg_sent_date></msg_sent_date>
<msg_subject>Month-to-Date Usage Below Threshold</msg_subject>
<msg_recipient_email_address>customer@example.com</msg_recipient_email_address>
<xml_statement_no></xml_statement_no>
<statement_no></statement_no>
<invoice_no></invoice_no>
<sequential_statement_id></sequential_statement_id>
<event_data>
<event_no>1032</event_no>
<event_label>MTD Usage Threshold Under</event_label>
</event_data>
</apf2doc>
Note: This event fires when month-to-date usage has dropped below a configured threshold after previously exceeding it. Use it to clear any usage alerts you raised when event 1031 fired. Subscribe to event 1039 to confirm the customer notification was delivered.
Event 1033: Account Message Type “PTD Usage Threshold Over” Requires Sending
Aria sends this notification when a period-to-date usage threshold over notification is distilled and queued for delivery.
<?xml version="1.0" encoding="UTF-8"?>
<apf2doc>
<request>
<version>3.1</version>
<sender>A</sender>
<transaction_id>100000204</transaction_id>
<action>A</action>
<class>N</class>
<auth_key>CLIENTAUTH12345</auth_key>
</request>
<client_no>10001</client_no>
<acct_no>12345678</acct_no>
<client_acct_id>CLIENT-ACCT-001</client_acct_id>
<userid>jsmith</userid>
<senior_acct_no></senior_acct_no>
<master_plan_instance_no>98765</master_plan_instance_no>
<client_plan_instance_id>MPI-STANDARD-001</client_plan_instance_id>
<resp_level_cd>0</resp_level_cd>
<resp_plan_instance_no></resp_plan_instance_no>
<in_event_scope_ind>1</in_event_scope_ind>
<msg_id>20030</msg_id>
<msg_class>Q</msg_class>
<msg_class_label>PTD Usage Threshold Over</msg_class_label>
<msg_creation_date>2026-06-15</msg_creation_date>
<msg_sent_date></msg_sent_date>
<msg_subject>Period-to-Date Usage Threshold Exceeded</msg_subject>
<msg_recipient_email_address>customer@example.com</msg_recipient_email_address>
<xml_statement_no></xml_statement_no>
<statement_no></statement_no>
<invoice_no></invoice_no>
<sequential_statement_id></sequential_statement_id>
<event_data>
<event_no>1033</event_no>
<event_label>PTD Usage Threshold Over</event_label>
</event_data>
</apf2doc>
Note: PTD thresholds measure usage for the full billing period. Use <acct_no> and <master_plan_instance_no> to locate the account and update your usage monitoring dashboard. Subscribe to event 1040 to confirm customer delivery.
Event 1034: Account Message Type “PTD Usage Threshold Under” Requires Sending
Aria sends this notification when a period-to-date usage threshold under notification is distilled and queued for delivery.
<?xml version="1.0" encoding="UTF-8"?>
<apf2doc>
<request>
<version>3.1</version>
<sender>A</sender>
<transaction_id>100000211</transaction_id>
<action>A</action>
<class>N</class>
<auth_key>CLIENTAUTH12345</auth_key>
</request>
<client_no>10001</client_no>
<acct_no>12345678</acct_no>
<client_acct_id>CLIENT-ACCT-001</client_acct_id>
<userid>jsmith</userid>
<senior_acct_no></senior_acct_no>
<master_plan_instance_no>98765</master_plan_instance_no>
<client_plan_instance_id>MPI-STANDARD-001</client_plan_instance_id>
<resp_level_cd>0</resp_level_cd>
<resp_plan_instance_no></resp_plan_instance_no>
<in_event_scope_ind>1</in_event_scope_ind>
<msg_id>20031</msg_id>
<msg_class>K</msg_class>
<msg_class_label>PTD Usage Threshold Under</msg_class_label>
<msg_creation_date>2026-06-15</msg_creation_date>
<msg_sent_date></msg_sent_date>
<msg_subject>Period-to-Date Usage Below Threshold</msg_subject>
<msg_recipient_email_address>customer@example.com</msg_recipient_email_address>
<xml_statement_no></xml_statement_no>
<statement_no></statement_no>
<invoice_no></invoice_no>
<sequential_statement_id></sequential_statement_id>
<event_data>
<event_no>1034</event_no>
<event_label>PTD Usage Threshold Under</event_label>
</event_data>
</apf2doc>
Note: This event fires when period-to-date usage has fallen below a configured threshold. Use it to clear any PTD alerts that were raised when event 1033 fired. Subscribe to event 1041 to confirm customer delivery.
Event 1035: Message Type “Electronic Collection Attempt” Sent To Account Holder
Aria sends this notification when the electronic collection attempt notification is delivered to your customer.
<?xml version="1.0" encoding="UTF-8"?>
<apf2doc>
<request>
<version>3.1</version>
<sender>A</sender>
<transaction_id>100000218</transaction_id>
<action>M</action>
<class>N</class>
<auth_key>CLIENTAUTH12345</auth_key>
</request>
<client_no>10001</client_no>
<acct_no>12345678</acct_no>
<client_acct_id>CLIENT-ACCT-001</client_acct_id>
<userid>jsmith</userid>
<senior_acct_no></senior_acct_no>
<master_plan_instance_no>98765</master_plan_instance_no>
<client_plan_instance_id>MPI-STANDARD-001</client_plan_instance_id>
<resp_level_cd>0</resp_level_cd>
<resp_plan_instance_no></resp_plan_instance_no>
<in_event_scope_ind>1</in_event_scope_ind>
<msg_id>20032</msg_id>
<msg_class>L</msg_class>
<msg_class_label>Electronic Collection Attempt</msg_class_label>
<msg_creation_date>2026-06-15</msg_creation_date>
<msg_sent_date>2026-06-15</msg_sent_date>
<msg_subject>Payment Collection Attempt Initiated</msg_subject>
<msg_recipient_email_address>customer@example.com</msg_recipient_email_address>
<xml_statement_no></xml_statement_no>
<statement_no></statement_no>
<invoice_no></invoice_no>
<sequential_statement_id></sequential_statement_id>
<event_data>
<event_no>1035</event_no>
<event_label>Electronic Collection Attempt</event_label>
</event_data>
</apf2doc>
Note: This event confirms the collection attempt notification was delivered. Update your payments log to reflect the notification delivery timestamp from <msg_sent_date>. If the collection attempt later fails, you may receive a dunning event (1003/1013) for the same account.
Event 1036: Message Type “Electronic Refund Processed” Sent To Account Holder
Aria sends this notification when the electronic refund notification is delivered to your customer.
<?xml version="1.0" encoding="UTF-8"?>
<apf2doc>
<request>
<version>3.1</version>
<sender>A</sender>
<transaction_id>100000225</transaction_id>
<action>M</action>
<class>N</class>
<auth_key>CLIENTAUTH12345</auth_key>
</request>
<client_no>10001</client_no>
<acct_no>12345678</acct_no>
<client_acct_id>CLIENT-ACCT-001</client_acct_id>
<userid>jsmith</userid>
<senior_acct_no></senior_acct_no>
<master_plan_instance_no>98765</master_plan_instance_no>
<client_plan_instance_id>MPI-STANDARD-001</client_plan_instance_id>
<resp_level_cd>0</resp_level_cd>
<resp_plan_instance_no></resp_plan_instance_no>
<in_event_scope_ind>1</in_event_scope_ind>
<msg_id>20033</msg_id>
<msg_class>R</msg_class>
<msg_class_label>Electronic Refund Processed</msg_class_label>
<msg_creation_date>2026-06-15</msg_creation_date>
<msg_sent_date>2026-06-15</msg_sent_date>
<msg_subject>Your Refund Has Been Processed</msg_subject>
<msg_recipient_email_address>customer@example.com</msg_recipient_email_address>
<xml_statement_no></xml_statement_no>
<statement_no></statement_no>
<invoice_no></invoice_no>
<sequential_statement_id></sequential_statement_id>
<event_data>
<event_no>1036</event_no>
<event_label>Electronic Refund Processed</event_label>
</event_data>
</apf2doc>
Note: This event confirms the refund notification was delivered. Update the refund record in your payments system with the delivery timestamp from <msg_sent_date>. Use <msg_id> to correlate this event with the corresponding distillation event (1029).
Event 1037: Message Type “Supplemental Service Plan Change” Sent To Account Holder
Aria sends this notification when the supplemental service plan change notification is delivered to your customer.
<?xml version="1.0" encoding="UTF-8"?>
<apf2doc>
<request>
<version>3.1</version>
<sender>A</sender>
<transaction_id>100000232</transaction_id>
<action>M</action>
<class>N</class>
<auth_key>CLIENTAUTH12345</auth_key>
</request>
<client_no>10001</client_no>
<acct_no>12345678</acct_no>
<client_acct_id>CLIENT-ACCT-001</client_acct_id>
<userid>jsmith</userid>
<senior_acct_no></senior_acct_no>
<master_plan_instance_no>98765</master_plan_instance_no>
<client_plan_instance_id>MPI-STANDARD-001</client_plan_instance_id>
<resp_level_cd>0</resp_level_cd>
<resp_plan_instance_no></resp_plan_instance_no>
<in_event_scope_ind>1</in_event_scope_ind>
<msg_id>20034</msg_id>
<msg_class>S</msg_class>
<msg_class_label>Supplemental Service Plan Change</msg_class_label>
<msg_creation_date>2026-06-15</msg_creation_date>
<msg_sent_date>2026-06-15</msg_sent_date>
<msg_subject>Your Service Plan Has Changed</msg_subject>
<msg_recipient_email_address>customer@example.com</msg_recipient_email_address>
<xml_statement_no></xml_statement_no>
<statement_no></statement_no>
<invoice_no></invoice_no>
<sequential_statement_id></sequential_statement_id>
<event_data>
<event_no>1037</event_no>
<event_label>Supplemental Service Plan Change</event_label>
</event_data>
</apf2doc>
Note: This event confirms the plan change notification was delivered. Use <master_plan_instance_no> to identify the affected plan instance and finalize any service updates that were pre-staged when event 1030 fired.
Event 1038: Message Type “MTD Usage Threshold Over” Sent To Account Holder
Aria sends this notification when the month-to-date usage threshold over notification is delivered to your customer.
<?xml version="1.0" encoding="UTF-8"?>
<apf2doc>
<request>
<version>3.1</version>
<sender>A</sender>
<transaction_id>100000239</transaction_id>
<action>M</action>
<class>N</class>
<auth_key>CLIENTAUTH12345</auth_key>
</request>
<client_no>10001</client_no>
<acct_no>12345678</acct_no>
<client_acct_id>CLIENT-ACCT-001</client_acct_id>
<userid>jsmith</userid>
<senior_acct_no></senior_acct_no>
<master_plan_instance_no>98765</master_plan_instance_no>
<client_plan_instance_id>MPI-STANDARD-001</client_plan_instance_id>
<resp_level_cd>0</resp_level_cd>
<resp_plan_instance_no></resp_plan_instance_no>
<in_event_scope_ind>1</in_event_scope_ind>
<msg_id>20035</msg_id>
<msg_class>M</msg_class>
<msg_class_label>MTD Usage Threshold Over</msg_class_label>
<msg_creation_date>2026-06-15</msg_creation_date>
<msg_sent_date>2026-06-15</msg_sent_date>
<msg_subject>Month-to-Date Usage Threshold Exceeded</msg_subject>
<msg_recipient_email_address>customer@example.com</msg_recipient_email_address>
<xml_statement_no></xml_statement_no>
<statement_no></statement_no>
<invoice_no></invoice_no>
<sequential_statement_id></sequential_statement_id>
<event_data>
<event_no>1038</event_no>
<event_label>MTD Usage Threshold Over</event_label>
</event_data>
</apf2doc>
Note: Use <msg_sent_date> to timestamp the alert in your usage monitoring system. If you need to throttle the customer’s service, do so only after this event confirms the customer was notified.
Event 1039: Message Type “MTD Usage Threshold Under” Sent To Account Holder
Aria sends this notification when the month-to-date usage threshold under notification is delivered to your customer.
<?xml version="1.0" encoding="UTF-8"?>
<apf2doc>
<request>
<version>3.1</version>
<sender>A</sender>
<transaction_id>100000246</transaction_id>
<action>M</action>
<class>N</class>
<auth_key>CLIENTAUTH12345</auth_key>
</request>
<client_no>10001</client_no>
<acct_no>12345678</acct_no>
<client_acct_id>CLIENT-ACCT-001</client_acct_id>
<userid>jsmith</userid>
<senior_acct_no></senior_acct_no>
<master_plan_instance_no>98765</master_plan_instance_no>
<client_plan_instance_id>MPI-STANDARD-001</client_plan_instance_id>
<resp_level_cd>0</resp_level_cd>
<resp_plan_instance_no></resp_plan_instance_no>
<in_event_scope_ind>1</in_event_scope_ind>
<msg_id>20036</msg_id>
<msg_class>V</msg_class>
<msg_class_label>MTD Usage Threshold Under</msg_class_label>
<msg_creation_date>2026-06-15</msg_creation_date>
<msg_sent_date>2026-06-15</msg_sent_date>
<msg_subject>Month-to-Date Usage Below Threshold</msg_subject>
<msg_recipient_email_address>customer@example.com</msg_recipient_email_address>
<xml_statement_no></xml_statement_no>
<statement_no></statement_no>
<invoice_no></invoice_no>
<sequential_statement_id></sequential_statement_id>
<event_data>
<event_no>1039</event_no>
<event_label>MTD Usage Threshold Under</event_label>
</event_data>
</apf2doc>
Note: Use it to clear any active MTD threshold alerts in your monitoring dashboard. Correlate with event 1038 using <acct_no> and <master_plan_instance_no> to close the alert lifecycle.
Event 1040: Message Type “PTD Usage Threshold Over” Sent To Account Holder
Aria sends this notification when the period-to-date usage threshold over notification is delivered to your customer.
<?xml version="1.0" encoding="UTF-8"?>
<apf2doc>
<request>
<version>3.1</version>
<sender>A</sender>
<transaction_id>100000253</transaction_id>
<action>M</action>
<class>N</class>
<auth_key>CLIENTAUTH12345</auth_key>
</request>
<client_no>10001</client_no>
<acct_no>12345678</acct_no>
<client_acct_id>CLIENT-ACCT-001</client_acct_id>
<userid>jsmith</userid>
<senior_acct_no></senior_acct_no>
<master_plan_instance_no>98765</master_plan_instance_no>
<client_plan_instance_id>MPI-STANDARD-001</client_plan_instance_id>
<resp_level_cd>0</resp_level_cd>
<resp_plan_instance_no></resp_plan_instance_no>
<in_event_scope_ind>1</in_event_scope_ind>
<msg_id>20037</msg_id>
<msg_class>Q</msg_class>
<msg_class_label>PTD Usage Threshold Over</msg_class_label>
<msg_creation_date>2026-06-15</msg_creation_date>
<msg_sent_date>2026-06-15</msg_sent_date>
<msg_subject>Period-to-Date Usage Threshold Exceeded</msg_subject>
<msg_recipient_email_address>customer@example.com</msg_recipient_email_address>
<xml_statement_no></xml_statement_no>
<statement_no></statement_no>
<invoice_no></invoice_no>
<sequential_statement_id></sequential_statement_id>
<event_data>
<event_no>1040</event_no>
<event_label>PTD Usage Threshold Over</event_label>
</event_data>
</apf2doc>
Note: Update your usage monitoring dashboard with the <msg_sent_date> value. Correlate with the distillation event (1033) using <msg_id> to track the full notification lifecycle.
Event 1041: Message Type “PTD Usage Threshold Under” Sent To Account Holder
Aria sends this notification when the period-to-date usage threshold under notification is delivered to your customer.
<?xml version="1.0" encoding="UTF-8"?>
<apf2doc>
<request>
<version>3.1</version>
<sender>A</sender>
<transaction_id>100000260</transaction_id>
<action>M</action>
<class>N</class>
<auth_key>CLIENTAUTH12345</auth_key>
</request>
<client_no>10001</client_no>
<acct_no>12345678</acct_no>
<client_acct_id>CLIENT-ACCT-001</client_acct_id>
<userid>jsmith</userid>
<senior_acct_no></senior_acct_no>
<master_plan_instance_no>98765</master_plan_instance_no>
<client_plan_instance_id>MPI-STANDARD-001</client_plan_instance_id>
<resp_level_cd>0</resp_level_cd>
<resp_plan_instance_no></resp_plan_instance_no>
<in_event_scope_ind>1</in_event_scope_ind>
<msg_id>20038</msg_id>
<msg_class>K</msg_class>
<msg_class_label>PTD Usage Threshold Under</msg_class_label>
<msg_creation_date>2026-06-15</msg_creation_date>
<msg_sent_date>2026-06-15</msg_sent_date>
<msg_subject>Period-to-Date Usage Below Threshold</msg_subject>
<msg_recipient_email_address>customer@example.com</msg_recipient_email_address>
<xml_statement_no></xml_statement_no>
<statement_no></statement_no>
<invoice_no></invoice_no>
<sequential_statement_id></sequential_statement_id>
<event_data>
<event_no>1041</event_no>
<event_label>PTD Usage Threshold Under</event_label>
</event_data>
</apf2doc>
Note: Use it to resolve any PTD threshold alerts raised by event 1040. Use <acct_no> and <master_plan_instance_no> to locate and update the account record.
Event 1042: Account Message Type “XML Statement” Requires Sending
Aria sends this notification when an XML statement notification is distilled and queued for delivery.
<?xml version="1.0" encoding="UTF-8"?>
<apf2doc>
<request>
<version>3.1</version>
<sender>A</sender>
<transaction_id>100000267</transaction_id>
<action>A</action>
<class>N</class>
<auth_key>CLIENTAUTH12345</auth_key>
</request>
<client_no>10001</client_no>
<acct_no>12345678</acct_no>
<client_acct_id>CLIENT-ACCT-001</client_acct_id>
<userid>jsmith</userid>
<senior_acct_no></senior_acct_no>
<master_plan_instance_no>98765</master_plan_instance_no>
<client_plan_instance_id>MPI-STANDARD-001</client_plan_instance_id>
<resp_level_cd>0</resp_level_cd>
<resp_plan_instance_no></resp_plan_instance_no>
<in_event_scope_ind>1</in_event_scope_ind>
<msg_id>20039</msg_id>
<msg_class>I</msg_class>
<msg_class_label>XML Statement</msg_class_label>
<msg_creation_date>2026-06-15</msg_creation_date>
<msg_sent_date></msg_sent_date>
<msg_subject>Your XML Statement Is Ready</msg_subject>
<msg_recipient_email_address>customer@example.com</msg_recipient_email_address>
<xml_statement_no>800039</xml_statement_no>
<statement_no>500039</statement_no>
<invoice_no></invoice_no>
<sequential_statement_id>739</sequential_statement_id>
<event_data>
<event_no>1042</event_no>
<event_label>XML Statement</event_label>
</event_data>
</apf2doc>
Note: The <xml_statement_no> field identifies the XML-formatted statement document. Use this event to trigger retrieval of the XML statement via the Aria API before the notification reaches the customer. Subscribe to the paired sent event to confirm delivery.
Event 1043: Credit Note Message Distilled
Aria sends this notification when a credit note message is distilled in Aria.
<?xml version="1.0" encoding="UTF-8"?>
<apf2doc>
<request>
<version>3.1</version>
<sender>A</sender>
<transaction_id>100000274</transaction_id>
<action>A</action>
<class>N</class>
<auth_key>CLIENTAUTH12345</auth_key>
</request>
<client_no>10001</client_no>
<acct_no>12345678</acct_no>
<client_acct_id>CLIENT-ACCT-001</client_acct_id>
<userid>jsmith</userid>
<senior_acct_no></senior_acct_no>
<master_plan_instance_no>98765</master_plan_instance_no>
<client_plan_instance_id>MPI-STANDARD-001</client_plan_instance_id>
<resp_level_cd>0</resp_level_cd>
<resp_plan_instance_no></resp_plan_instance_no>
<in_event_scope_ind>1</in_event_scope_ind>
<msg_id>20040</msg_id>
<msg_class>N</msg_class>
<msg_class_label>Credit Note</msg_class_label>
<msg_creation_date>2026-06-15</msg_creation_date>
<msg_sent_date></msg_sent_date>
<msg_subject>A Credit Has Been Applied to Your Account</msg_subject>
<msg_recipient_email_address>customer@example.com</msg_recipient_email_address>
<xml_statement_no></xml_statement_no>
<statement_no></statement_no>
<invoice_no></invoice_no>
<sequential_statement_id></sequential_statement_id>
<event_data>
<event_no>1043</event_no>
<event_label>Credit Note</event_label>
</event_data>
</apf2doc>
Note: Use <msg_id> as the idempotency key to avoid processing the same credit note twice. Subscribe to event 1044 to confirm the credit note message was delivered to your customer.
Event 1044: Credit Note Message Sent
Aria sends this notification when the credit note message is delivered to your customer.
<?xml version="1.0" encoding="UTF-8"?>
<apf2doc>
<request>
<version>3.1</version>
<sender>A</sender>
<transaction_id>100000281</transaction_id>
<action>M</action>
<class>N</class>
<auth_key>CLIENTAUTH12345</auth_key>
</request>
<client_no>10001</client_no>
<acct_no>12345678</acct_no>
<client_acct_id>CLIENT-ACCT-001</client_acct_id>
<userid>jsmith</userid>
<senior_acct_no></senior_acct_no>
<master_plan_instance_no>98765</master_plan_instance_no>
<client_plan_instance_id>MPI-STANDARD-001</client_plan_instance_id>
<resp_level_cd>0</resp_level_cd>
<resp_plan_instance_no></resp_plan_instance_no>
<in_event_scope_ind>1</in_event_scope_ind>
<msg_id>20041</msg_id>
<msg_class>N</msg_class>
<msg_class_label>Credit Note</msg_class_label>
<msg_creation_date>2026-06-15</msg_creation_date>
<msg_sent_date>2026-06-15</msg_sent_date>
<msg_subject>A Credit Has Been Applied to Your Account</msg_subject>
<msg_recipient_email_address>customer@example.com</msg_recipient_email_address>
<xml_statement_no></xml_statement_no>
<statement_no></statement_no>
<invoice_no></invoice_no>
<sequential_statement_id></sequential_statement_id>
<event_data>
<event_no>1044</event_no>
<event_label>Credit Note</event_label>
</event_data>
</apf2doc>
Note: This event confirms the credit note notification was delivered. Correlate with event 1043 using <msg_id> to close the credit note notification lifecycle. Use <msg_sent_date> to timestamp the delivery in your financial records.
Event 1045: Account Message Type “Payment Method Removed” Requires Sending
Aria sends this notification when a payment method removed notification is distilled and queued for delivery.
<?xml version="1.0" encoding="UTF-8"?>
<apf2doc>
<request>
<version>3.1</version>
<sender>A</sender>
<transaction_id>100000288</transaction_id>
<action>A</action>
<class>N</class>
<auth_key>CLIENTAUTH12345</auth_key>
</request>
<client_no>10001</client_no>
<acct_no>12345678</acct_no>
<client_acct_id>CLIENT-ACCT-001</client_acct_id>
<userid>jsmith</userid>
<senior_acct_no></senior_acct_no>
<master_plan_instance_no>98765</master_plan_instance_no>
<client_plan_instance_id>MPI-STANDARD-001</client_plan_instance_id>
<resp_level_cd>0</resp_level_cd>
<resp_plan_instance_no></resp_plan_instance_no>
<in_event_scope_ind>1</in_event_scope_ind>
<msg_id>20042</msg_id>
<msg_class>Y</msg_class>
<msg_class_label>Payment Method Removed</msg_class_label>
<msg_creation_date>2026-06-15</msg_creation_date>
<msg_sent_date></msg_sent_date>
<msg_subject>A Payment Method Has Been Removed from Your Account</msg_subject>
<msg_recipient_email_address>customer@example.com</msg_recipient_email_address>
<xml_statement_no></xml_statement_no>
<statement_no></statement_no>
<invoice_no></invoice_no>
<sequential_statement_id></sequential_statement_id>
<event_data>
<event_no>1045</event_no>
<event_label>Payment Method Removed</event_label>
</event_data>
</apf2doc>
Note: This event fires when a payment method has been removed and Aria has prepared the customer notification. Use <acct_no> to check whether the customer still has a valid default payment method on file. Subscribe to event 1046 to confirm delivery.
Event 1046: Message Type “Payment Method Removed” Sent To Account Holder
Aria sends this notification when the payment method removed notification is delivered to your customer.
<?xml version="1.0" encoding="UTF-8"?>
<apf2doc>
<request>
<version>3.1</version>
<sender>A</sender>
<transaction_id>100000295</transaction_id>
<action>M</action>
<class>N</class>
<auth_key>CLIENTAUTH12345</auth_key>
</request>
<client_no>10001</client_no>
<acct_no>12345678</acct_no>
<client_acct_id>CLIENT-ACCT-001</client_acct_id>
<userid>jsmith</userid>
<senior_acct_no></senior_acct_no>
<master_plan_instance_no>98765</master_plan_instance_no>
<client_plan_instance_id>MPI-STANDARD-001</client_plan_instance_id>
<resp_level_cd>0</resp_level_cd>
<resp_plan_instance_no></resp_plan_instance_no>
<in_event_scope_ind>1</in_event_scope_ind>
<msg_id>20043</msg_id>
<msg_class>Y</msg_class>
<msg_class_label>Payment Method Removed</msg_class_label>
<msg_creation_date>2026-06-15</msg_creation_date>
<msg_sent_date>2026-06-15</msg_sent_date>
<msg_subject>A Payment Method Has Been Removed from Your Account</msg_subject>
<msg_recipient_email_address>customer@example.com</msg_recipient_email_address>
<xml_statement_no></xml_statement_no>
<statement_no></statement_no>
<invoice_no></invoice_no>
<sequential_statement_id></sequential_statement_id>
<event_data>
<event_no>1046</event_no>
<event_label>Payment Method Removed</event_label>
</event_data>
</apf2doc>
Note: This event confirms the payment method removal notice was delivered. If the removed payment method was the customer’s only one, use <acct_no> to flag the account for follow-up. Use <msg_sent_date> to timestamp the notification in your audit log.
Event 1047: Account Message Type “MTD Unit Usage Threshold Over” Requires Sending
Aria sends this notification when a month-to-date unit usage threshold over notification is distilled and queued for delivery.
<?xml version="1.0" encoding="UTF-8"?>
<apf2doc>
<request>
<version>3.1</version>
<sender>A</sender>
<transaction_id>100000302</transaction_id>
<action>A</action>
<class>N</class>
<auth_key>CLIENTAUTH12345</auth_key>
</request>
<client_no>10001</client_no>
<acct_no>12345678</acct_no>
<client_acct_id>CLIENT-ACCT-001</client_acct_id>
<userid>jsmith</userid>
<senior_acct_no></senior_acct_no>
<master_plan_instance_no>98765</master_plan_instance_no>
<client_plan_instance_id>MPI-STANDARD-001</client_plan_instance_id>
<resp_level_cd>0</resp_level_cd>
<resp_plan_instance_no></resp_plan_instance_no>
<in_event_scope_ind>1</in_event_scope_ind>
<msg_id>20044</msg_id>
<msg_class>H</msg_class>
<msg_class_label>MTD Unit Usage Threshold Over</msg_class_label>
<msg_creation_date>2026-06-15</msg_creation_date>
<msg_sent_date></msg_sent_date>
<msg_subject>Month-to-Date Unit Usage Threshold Exceeded</msg_subject>
<msg_recipient_email_address>customer@example.com</msg_recipient_email_address>
<xml_statement_no></xml_statement_no>
<statement_no></statement_no>
<invoice_no></invoice_no>
<sequential_statement_id></sequential_statement_id>
<event_data>
<event_no>1047</event_no>
<event_label>MTD Unit Usage Threshold Over</event_label>
</event_data>
</apf2doc>
Note: Unit usage thresholds track discrete unit counts rather than monetary amounts. Use this event to trigger a unit-level alert in your operations dashboard. Subscribe to event 1051 to confirm the customer notification was delivered.
Event 1048: Account Message Type “MTD Unit Usage Threshold Under” Requires Sending
Aria sends this notification when a month-to-date unit usage threshold under notification is distilled and queued for delivery.
<?xml version="1.0" encoding="UTF-8"?>
<apf2doc>
<request>
<version>3.1</version>
<sender>A</sender>
<transaction_id>100000309</transaction_id>
<action>A</action>
<class>N</class>
<auth_key>CLIENTAUTH12345</auth_key>
</request>
<client_no>10001</client_no>
<acct_no>12345678</acct_no>
<client_acct_id>CLIENT-ACCT-001</client_acct_id>
<userid>jsmith</userid>
<senior_acct_no></senior_acct_no>
<master_plan_instance_no>98765</master_plan_instance_no>
<client_plan_instance_id>MPI-STANDARD-001</client_plan_instance_id>
<resp_level_cd>0</resp_level_cd>
<resp_plan_instance_no></resp_plan_instance_no>
<in_event_scope_ind>1</in_event_scope_ind>
<msg_id>20045</msg_id>
<msg_class>J</msg_class>
<msg_class_label>MTD Unit Usage Threshold Under</msg_class_label>
<msg_creation_date>2026-06-15</msg_creation_date>
<msg_sent_date></msg_sent_date>
<msg_subject>Month-to-Date Unit Usage Below Threshold</msg_subject>
<msg_recipient_email_address>customer@example.com</msg_recipient_email_address>
<xml_statement_no></xml_statement_no>
<statement_no></statement_no>
<invoice_no></invoice_no>
<sequential_statement_id></sequential_statement_id>
<event_data>
<event_no>1048</event_no>
<event_label>MTD Unit Usage Threshold Under</event_label>
</event_data>
</apf2doc>
Note: This event fires when month-to-date unit usage has dropped below a configured threshold after previously exceeding it. Use it to clear the unit alert raised by event 1047. Subscribe to event 1052 to confirm delivery.
Event 1049: Account Message Type “PTD Unit Usage Threshold Over” Requires Sending
Aria sends this notification when a period-to-date unit usage threshold over notification is distilled and queued for delivery.
<?xml version="1.0" encoding="UTF-8"?>
<apf2doc>
<request>
<version>3.1</version>
<sender>A</sender>
<transaction_id>100000316</transaction_id>
<action>A</action>
<class>N</class>
<auth_key>CLIENTAUTH12345</auth_key>
</request>
<client_no>10001</client_no>
<acct_no>12345678</acct_no>
<client_acct_id>CLIENT-ACCT-001</client_acct_id>
<userid>jsmith</userid>
<senior_acct_no></senior_acct_no>
<master_plan_instance_no>98765</master_plan_instance_no>
<client_plan_instance_id>MPI-STANDARD-001</client_plan_instance_id>
<resp_level_cd>0</resp_level_cd>
<resp_plan_instance_no></resp_plan_instance_no>
<in_event_scope_ind>1</in_event_scope_ind>
<msg_id>20046</msg_id>
<msg_class>F</msg_class>
<msg_class_label>PTD Unit Usage Threshold Over</msg_class_label>
<msg_creation_date>2026-06-15</msg_creation_date>
<msg_sent_date></msg_sent_date>
<msg_subject>Period-to-Date Unit Usage Threshold Exceeded</msg_subject>
<msg_recipient_email_address>customer@example.com</msg_recipient_email_address>
<xml_statement_no></xml_statement_no>
<statement_no></statement_no>
<invoice_no></invoice_no>
<sequential_statement_id></sequential_statement_id>
<event_data>
<event_no>1049</event_no>
<event_label>PTD Unit Usage Threshold Over</event_label>
</event_data>
</apf2doc>
Note: PTD unit usage thresholds apply to the full billing period. Use <acct_no> and <master_plan_instance_no> to locate the account and update your unit-usage monitoring dashboard. Subscribe to event 1053 to confirm delivery.
Event 1050: Account Message Type “PTD Unit Usage Threshold Under” Requires Sending
Aria sends this notification when a period-to-date unit usage threshold under notification is distilled and queued for delivery.
<?xml version="1.0" encoding="UTF-8"?>
<apf2doc>
<request>
<version>3.1</version>
<sender>A</sender>
<transaction_id>100000323</transaction_id>
<action>A</action>
<class>N</class>
<auth_key>CLIENTAUTH12345</auth_key>
</request>
<client_no>10001</client_no>
<acct_no>12345678</acct_no>
<client_acct_id>CLIENT-ACCT-001</client_acct_id>
<userid>jsmith</userid>
<senior_acct_no></senior_acct_no>
<master_plan_instance_no>98765</master_plan_instance_no>
<client_plan_instance_id>MPI-STANDARD-001</client_plan_instance_id>
<resp_level_cd>0</resp_level_cd>
<resp_plan_instance_no></resp_plan_instance_no>
<in_event_scope_ind>1</in_event_scope_ind>
<msg_id>20047</msg_id>
<msg_class>Z</msg_class>
<msg_class_label>PTD Unit Usage Threshold Under</msg_class_label>
<msg_creation_date>2026-06-15</msg_creation_date>
<msg_sent_date></msg_sent_date>
<msg_subject>Period-to-Date Unit Usage Below Threshold</msg_subject>
<msg_recipient_email_address>customer@example.com</msg_recipient_email_address>
<xml_statement_no></xml_statement_no>
<statement_no></statement_no>
<invoice_no></invoice_no>
<sequential_statement_id></sequential_statement_id>
<event_data>
<event_no>1050</event_no>
<event_label>PTD Unit Usage Threshold Under</event_label>
</event_data>
</apf2doc>
Note: This event fires when PTD unit usage has dropped below a configured threshold. Use it to clear any PTD unit-usage alerts raised by event 1049. Subscribe to event 1054 to confirm delivery to your customer.
Event 1051: Message Type “MTD Unit Usage Threshold Over” Sent To Account Holder
Aria sends this notification when the month-to-date unit usage threshold over notification is delivered to your customer.
<?xml version="1.0" encoding="UTF-8"?>
<apf2doc>
<request>
<version>3.1</version>
<sender>A</sender>
<transaction_id>100000330</transaction_id>
<action>M</action>
<class>N</class>
<auth_key>CLIENTAUTH12345</auth_key>
</request>
<client_no>10001</client_no>
<acct_no>12345678</acct_no>
<client_acct_id>CLIENT-ACCT-001</client_acct_id>
<userid>jsmith</userid>
<senior_acct_no></senior_acct_no>
<master_plan_instance_no>98765</master_plan_instance_no>
<client_plan_instance_id>MPI-STANDARD-001</client_plan_instance_id>
<resp_level_cd>0</resp_level_cd>
<resp_plan_instance_no></resp_plan_instance_no>
<in_event_scope_ind>1</in_event_scope_ind>
<msg_id>20048</msg_id>
<msg_class>H</msg_class>
<msg_class_label>MTD Unit Usage Threshold Over</msg_class_label>
<msg_creation_date>2026-06-15</msg_creation_date>
<msg_sent_date>2026-06-15</msg_sent_date>
<msg_subject>Month-to-Date Unit Usage Threshold Exceeded</msg_subject>
<msg_recipient_email_address>customer@example.com</msg_recipient_email_address>
<xml_statement_no></xml_statement_no>
<statement_no></statement_no>
<invoice_no></invoice_no>
<sequential_statement_id></sequential_statement_id>
<event_data>
<event_no>1051</event_no>
<event_label>MTD Unit Usage Threshold Over</event_label>
</event_data>
</apf2doc>
Note: Use <msg_sent_date> to timestamp the alert in your monitoring system. Correlate with event 1047 using <msg_id> to close the notification lifecycle.
Event 1052: Message Type “MTD Unit Usage Threshold Under” Sent To Account Holder
Aria sends this notification when the month-to-date unit usage threshold under notification is delivered to your customer.
<?xml version="1.0" encoding="UTF-8"?>
<apf2doc>
<request>
<version>3.1</version>
<sender>A</sender>
<transaction_id>100000337</transaction_id>
<action>M</action>
<class>N</class>
<auth_key>CLIENTAUTH12345</auth_key>
</request>
<client_no>10001</client_no>
<acct_no>12345678</acct_no>
<client_acct_id>CLIENT-ACCT-001</client_acct_id>
<userid>jsmith</userid>
<senior_acct_no></senior_acct_no>
<master_plan_instance_no>98765</master_plan_instance_no>
<client_plan_instance_id>MPI-STANDARD-001</client_plan_instance_id>
<resp_level_cd>0</resp_level_cd>
<resp_plan_instance_no></resp_plan_instance_no>
<in_event_scope_ind>1</in_event_scope_ind>
<msg_id>20049</msg_id>
<msg_class>J</msg_class>
<msg_class_label>MTD Unit Usage Threshold Under</msg_class_label>
<msg_creation_date>2026-06-15</msg_creation_date>
<msg_sent_date>2026-06-15</msg_sent_date>
<msg_subject>Month-to-Date Unit Usage Below Threshold</msg_subject>
<msg_recipient_email_address>customer@example.com</msg_recipient_email_address>
<xml_statement_no></xml_statement_no>
<statement_no></statement_no>
<invoice_no></invoice_no>
<sequential_statement_id></sequential_statement_id>
<event_data>
<event_no>1052</event_no>
<event_label>MTD Unit Usage Threshold Under</event_label>
</event_data>
</apf2doc>
Note: Use it to clear any active MTD unit-usage alerts in your monitoring dashboard. Correlate with event 1051 using <acct_no> and <master_plan_instance_no> to close the alert lifecycle.
Event 1053: Message Type “PTD Unit Usage Threshold Over” Sent To Account Holder
Aria sends this notification when the period-to-date unit usage threshold over notification is delivered to your customer.
<?xml version="1.0" encoding="UTF-8"?>
<apf2doc>
<request>
<version>3.1</version>
<sender>A</sender>
<transaction_id>100000344</transaction_id>
<action>M</action>
<class>N</class>
<auth_key>CLIENTAUTH12345</auth_key>
</request>
<client_no>10001</client_no>
<acct_no>12345678</acct_no>
<client_acct_id>CLIENT-ACCT-001</client_acct_id>
<userid>jsmith</userid>
<senior_acct_no></senior_acct_no>
<master_plan_instance_no>98765</master_plan_instance_no>
<client_plan_instance_id>MPI-STANDARD-001</client_plan_instance_id>
<resp_level_cd>0</resp_level_cd>
<resp_plan_instance_no></resp_plan_instance_no>
<in_event_scope_ind>1</in_event_scope_ind>
<msg_id>20050</msg_id>
<msg_class>F</msg_class>
<msg_class_label>PTD Unit Usage Threshold Over</msg_class_label>
<msg_creation_date>2026-06-15</msg_creation_date>
<msg_sent_date>2026-06-15</msg_sent_date>
<msg_subject>Period-to-Date Unit Usage Threshold Exceeded</msg_subject>
<msg_recipient_email_address>customer@example.com</msg_recipient_email_address>
<xml_statement_no></xml_statement_no>
<statement_no></statement_no>
<invoice_no></invoice_no>
<sequential_statement_id></sequential_statement_id>
<event_data>
<event_no>1053</event_no>
<event_label>PTD Unit Usage Threshold Over</event_label>
</event_data>
</apf2doc>
Note: Update your monitoring system with <msg_sent_date>. Correlate with distillation event 1049 using <msg_id> to track the full notification lifecycle.
Event 1054: Message Type “PTD Unit Usage Threshold Under” Sent To Account Holder
Aria sends this notification when the period-to-date unit usage threshold under notification is delivered to your customer.
<?xml version="1.0" encoding="UTF-8"?>
<apf2doc>
<request>
<version>3.1</version>
<sender>A</sender>
<transaction_id>100000351</transaction_id>
<action>M</action>
<class>N</class>
<auth_key>CLIENTAUTH12345</auth_key>
</request>
<client_no>10001</client_no>
<acct_no>12345678</acct_no>
<client_acct_id>CLIENT-ACCT-001</client_acct_id>
<userid>jsmith</userid>
<senior_acct_no></senior_acct_no>
<master_plan_instance_no>98765</master_plan_instance_no>
<client_plan_instance_id>MPI-STANDARD-001</client_plan_instance_id>
<resp_level_cd>0</resp_level_cd>
<resp_plan_instance_no></resp_plan_instance_no>
<in_event_scope_ind>1</in_event_scope_ind>
<msg_id>20051</msg_id>
<msg_class>Z</msg_class>
<msg_class_label>PTD Unit Usage Threshold Under</msg_class_label>
<msg_creation_date>2026-06-15</msg_creation_date>
<msg_sent_date>2026-06-15</msg_sent_date>
<msg_subject>Period-to-Date Unit Usage Below Threshold</msg_subject>
<msg_recipient_email_address>customer@example.com</msg_recipient_email_address>
<xml_statement_no></xml_statement_no>
<statement_no></statement_no>
<invoice_no></invoice_no>
<sequential_statement_id></sequential_statement_id>
<event_data>
<event_no>1054</event_no>
<event_label>PTD Unit Usage Threshold Under</event_label>
</event_data>
</apf2doc>
Note: Use it to resolve any PTD unit-usage alerts raised by event 1053. Use <acct_no> and <master_plan_instance_no> to locate and update the account record.
Event 1055: Account Message Type “Master Plan Instance Deprovisioned” Requires Sending
Aria sends this notification when a master plan instance deprovisioned notification is distilled and queued for delivery.
<?xml version="1.0" encoding="UTF-8"?>
<apf2doc>
<request>
<version>3.1</version>
<sender>A</sender>
<transaction_id>100000358</transaction_id>
<action>A</action>
<class>N</class>
<auth_key>CLIENTAUTH12345</auth_key>
</request>
<client_no>10001</client_no>
<acct_no>12345678</acct_no>
<client_acct_id>CLIENT-ACCT-001</client_acct_id>
<userid>jsmith</userid>
<senior_acct_no></senior_acct_no>
<master_plan_instance_no>98765</master_plan_instance_no>
<client_plan_instance_id>MPI-STANDARD-001</client_plan_instance_id>
<resp_level_cd>0</resp_level_cd>
<resp_plan_instance_no></resp_plan_instance_no>
<in_event_scope_ind>1</in_event_scope_ind>
<msg_id>20052</msg_id>
<msg_class>X</msg_class>
<msg_class_label>Master Plan Instance Deprovisioned</msg_class_label>
<msg_creation_date>2026-06-15</msg_creation_date>
<msg_sent_date></msg_sent_date>
<msg_subject>Your Service Plan Has Been Deprovisioned</msg_subject>
<msg_recipient_email_address>customer@example.com</msg_recipient_email_address>
<xml_statement_no></xml_statement_no>
<statement_no></statement_no>
<invoice_no></invoice_no>
<sequential_statement_id></sequential_statement_id>
<event_data>
<event_no>1055</event_no>
<event_label>Master Plan Instance Deprovisioned</event_label>
</event_data>
</apf2doc>
Note: Begin pre-deprovisioning cleanup (such as archiving usage data or revoking access tokens) when this event fires, but do not complete deprovisioning until event 1056 confirms the customer was notified.
Event 1056: Message Type “Master Plan Instance Deprovisioned” Sent to Account Holder
Aria sends this notification when the master plan instance deprovisioned notification is delivered to your customer.
<?xml version="1.0" encoding="UTF-8"?>
<apf2doc>
<request>
<version>3.1</version>
<sender>A</sender>
<transaction_id>100000365</transaction_id>
<action>M</action>
<class>N</class>
<auth_key>CLIENTAUTH12345</auth_key>
</request>
<client_no>10001</client_no>
<acct_no>12345678</acct_no>
<client_acct_id>CLIENT-ACCT-001</client_acct_id>
<userid>jsmith</userid>
<senior_acct_no></senior_acct_no>
<master_plan_instance_no>98765</master_plan_instance_no>
<client_plan_instance_id>MPI-STANDARD-001</client_plan_instance_id>
<resp_level_cd>0</resp_level_cd>
<resp_plan_instance_no></resp_plan_instance_no>
<in_event_scope_ind>1</in_event_scope_ind>
<msg_id>20053</msg_id>
<msg_class>X</msg_class>
<msg_class_label>Master Plan Instance Deprovisioned</msg_class_label>
<msg_creation_date>2026-06-15</msg_creation_date>
<msg_sent_date>2026-06-15</msg_sent_date>
<msg_subject>Your Service Plan Has Been Deprovisioned</msg_subject>
<msg_recipient_email_address>customer@example.com</msg_recipient_email_address>
<xml_statement_no></xml_statement_no>
<statement_no></statement_no>
<invoice_no></invoice_no>
<sequential_statement_id></sequential_statement_id>
<event_data>
<event_no>1056</event_no>
<event_label>Master Plan Instance Deprovisioned</event_label>
</event_data>
</apf2doc>
Note: After this event fires, complete any remaining deprovisioning steps such as revoking access and archiving account data. Use <master_plan_instance_no> to identify the deprovisioned plan instance.
Event 1057: Account Message Type “Contract End: Terminate Service and Billing” Requires Sending
Aria sends this notification when a contract-end termination notification is distilled and queued for delivery.
<?xml version="1.0" encoding="UTF-8"?>
<apf2doc>
<request>
<version>3.1</version>
<sender>A</sender>
<transaction_id>100000372</transaction_id>
<action>A</action>
<class>N</class>
<auth_key>CLIENTAUTH12345</auth_key>
</request>
<client_no>10001</client_no>
<acct_no>12345678</acct_no>
<client_acct_id>CLIENT-ACCT-001</client_acct_id>
<userid>jsmith</userid>
<senior_acct_no></senior_acct_no>
<master_plan_instance_no>98765</master_plan_instance_no>
<client_plan_instance_id>MPI-STANDARD-001</client_plan_instance_id>
<resp_level_cd>0</resp_level_cd>
<resp_plan_instance_no></resp_plan_instance_no>
<in_event_scope_ind>1</in_event_scope_ind>
<msg_id>20054</msg_id>
<msg_class>E</msg_class>
<msg_class_label>Contract End: Terminate Service and Billing</msg_class_label>
<msg_creation_date>2026-06-15</msg_creation_date>
<msg_sent_date></msg_sent_date>
<msg_subject>Your Contract Has Ended: Service and Billing Will Terminate</msg_subject>
<msg_recipient_email_address>customer@example.com</msg_recipient_email_address>
<xml_statement_no></xml_statement_no>
<statement_no></statement_no>
<invoice_no></invoice_no>
<sequential_statement_id></sequential_statement_id>
<event_data>
<event_no>1057</event_no>
<event_label>Contract End: Terminate Service and Billing</event_label>
</event_data>
</apf2doc>
Note: Begin service termination pre-work when this event fires, but do not terminate service until event 1062 confirms the customer was notified.
Event 1058: Account Message Type “Contract End: Terminate Service and Billing (Proration)” Requires Sending
Aria sends this notification when a contract-end termination with proration notification is distilled and queued for delivery.
<?xml version="1.0" encoding="UTF-8"?>
<apf2doc>
<request>
<version>3.1</version>
<sender>A</sender>
<transaction_id>100000379</transaction_id>
<action>A</action>
<class>N</class>
<auth_key>CLIENTAUTH12345</auth_key>
</request>
<client_no>10001</client_no>
<acct_no>12345678</acct_no>
<client_acct_id>CLIENT-ACCT-001</client_acct_id>
<userid>jsmith</userid>
<senior_acct_no></senior_acct_no>
<master_plan_instance_no>98765</master_plan_instance_no>
<client_plan_instance_id>MPI-STANDARD-001</client_plan_instance_id>
<resp_level_cd>0</resp_level_cd>
<resp_plan_instance_no></resp_plan_instance_no>
<in_event_scope_ind>1</in_event_scope_ind>
<msg_id>20055</msg_id>
<msg_class>E</msg_class>
<msg_class_label>Contract End: Terminate Service and Billing (Proration)</msg_class_label>
<msg_creation_date>2026-06-15</msg_creation_date>
<msg_sent_date></msg_sent_date>
<msg_subject>Your Contract Has Ended: Service and Billing Will Terminate with Proration</msg_subject>
<msg_recipient_email_address>customer@example.com</msg_recipient_email_address>
<xml_statement_no></xml_statement_no>
<statement_no></statement_no>
<invoice_no></invoice_no>
<sequential_statement_id></sequential_statement_id>
<event_data>
<event_no>1058</event_no>
<event_label>Contract End: Terminate Service and Billing (Proration)</event_label>
</event_data>
</apf2doc>
Note: The proration variant indicates that a partial-period charge has been calculated for the final billing cycle. Ensure your billing system has processed the prorated charge before terminating service. Subscribe to event 1063 to confirm the customer notification was delivered.
Event 1059: Account Message Type “Contract End: Continue Service” Requires Sending
Aria sends this notification when a contract-end continue-service notification is distilled and queued for delivery.
<?xml version="1.0" encoding="UTF-8"?>
<apf2doc>
<request>
<version>3.1</version>
<sender>A</sender>
<transaction_id>100000386</transaction_id>
<action>A</action>
<class>N</class>
<auth_key>CLIENTAUTH12345</auth_key>
</request>
<client_no>10001</client_no>
<acct_no>12345678</acct_no>
<client_acct_id>CLIENT-ACCT-001</client_acct_id>
<userid>jsmith</userid>
<senior_acct_no></senior_acct_no>
<master_plan_instance_no>98765</master_plan_instance_no>
<client_plan_instance_id>MPI-STANDARD-001</client_plan_instance_id>
<resp_level_cd>0</resp_level_cd>
<resp_plan_instance_no></resp_plan_instance_no>
<in_event_scope_ind>1</in_event_scope_ind>
<msg_id>20056</msg_id>
<msg_class>E</msg_class>
<msg_class_label>Contract End: Continue Service</msg_class_label>
<msg_creation_date>2026-06-15</msg_creation_date>
<msg_sent_date></msg_sent_date>
<msg_subject>Your Contract Has Ended: Service Will Continue</msg_subject>
<msg_recipient_email_address>customer@example.com</msg_recipient_email_address>
<xml_statement_no></xml_statement_no>
<statement_no></statement_no>
<invoice_no></invoice_no>
<sequential_statement_id></sequential_statement_id>
<event_data>
<event_no>1059</event_no>
<event_label>Contract End: Continue Service</event_label>
</event_data>
</apf2doc>
Note: Use <master_plan_instance_no> to locate the plan instance and confirm it transitions correctly to a month-to-month or other ongoing arrangement. Subscribe to event 1064 to confirm customer delivery.
Event 1060: Account Message Type “Contract End: Renew Automatically” Requires Sending
Aria sends this notification when a contract auto-renewal notification is distilled and queued for delivery.
<?xml version="1.0" encoding="UTF-8"?>
<apf2doc>
<request>
<version>3.1</version>
<sender>A</sender>
<transaction_id>100000393</transaction_id>
<action>A</action>
<class>N</class>
<auth_key>CLIENTAUTH12345</auth_key>
</request>
<client_no>10001</client_no>
<acct_no>12345678</acct_no>
<client_acct_id>CLIENT-ACCT-001</client_acct_id>
<userid>jsmith</userid>
<senior_acct_no></senior_acct_no>
<master_plan_instance_no>98765</master_plan_instance_no>
<client_plan_instance_id>MPI-STANDARD-001</client_plan_instance_id>
<resp_level_cd>0</resp_level_cd>
<resp_plan_instance_no></resp_plan_instance_no>
<in_event_scope_ind>1</in_event_scope_ind>
<msg_id>20057</msg_id>
<msg_class>E</msg_class>
<msg_class_label>Contract End: Renew Automatically</msg_class_label>
<msg_creation_date>2026-06-15</msg_creation_date>
<msg_sent_date></msg_sent_date>
<msg_subject>Your Contract Has Been Renewed Automatically</msg_subject>
<msg_recipient_email_address>customer@example.com</msg_recipient_email_address>
<xml_statement_no></xml_statement_no>
<statement_no></statement_no>
<invoice_no></invoice_no>
<sequential_statement_id></sequential_statement_id>
<event_data>
<event_no>1060</event_no>
<event_label>Contract End: Renew Automatically</event_label>
</event_data>
</apf2doc>
Note: Use it to trigger any renewal-related tasks in your CRM, such as updating contract dates or notifying the account manager. Subscribe to event 1065 to confirm customer delivery.
Event 1061: Account Message Type “Contract End: Rollover” Requires Sending
Aria sends this notification when a contract-end rollover notification is distilled and queued for delivery.
<?xml version="1.0" encoding="UTF-8"?>
<apf2doc>
<request>
<version>3.1</version>
<sender>A</sender>
<transaction_id>100000400</transaction_id>
<action>A</action>
<class>N</class>
<auth_key>CLIENTAUTH12345</auth_key>
</request>
<client_no>10001</client_no>
<acct_no>12345678</acct_no>
<client_acct_id>CLIENT-ACCT-001</client_acct_id>
<userid>jsmith</userid>
<senior_acct_no></senior_acct_no>
<master_plan_instance_no>98765</master_plan_instance_no>
<client_plan_instance_id>MPI-STANDARD-001</client_plan_instance_id>
<resp_level_cd>0</resp_level_cd>
<resp_plan_instance_no></resp_plan_instance_no>
<in_event_scope_ind>1</in_event_scope_ind>
<msg_id>20058</msg_id>
<msg_class>E</msg_class>
<msg_class_label>Contract End: Rollover</msg_class_label>
<msg_creation_date>2026-06-15</msg_creation_date>
<msg_sent_date></msg_sent_date>
<msg_subject>Your Contract Has Rolled Over</msg_subject>
<msg_recipient_email_address>customer@example.com</msg_recipient_email_address>
<xml_statement_no></xml_statement_no>
<statement_no></statement_no>
<invoice_no></invoice_no>
<sequential_statement_id></sequential_statement_id>
<event_data>
<event_no>1061</event_no>
<event_label>Contract End: Rollover</event_label>
</event_data>
</apf2doc>
Note: A rollover means the customer has transitioned to a new contract term without interruption. Update the contract record in your CRM with the new term dates when this event fires. Subscribe to event 1066 to confirm customer delivery.
Event 1062: Message Type “Contract End: Terminate Service and Billing” Sent to Account Holder
Aria sends this notification when the contract-end termination notification is delivered to your customer.
<?xml version="1.0" encoding="UTF-8"?>
<apf2doc>
<request>
<version>3.1</version>
<sender>A</sender>
<transaction_id>100000407</transaction_id>
<action>M</action>
<class>N</class>
<auth_key>CLIENTAUTH12345</auth_key>
</request>
<client_no>10001</client_no>
<acct_no>12345678</acct_no>
<client_acct_id>CLIENT-ACCT-001</client_acct_id>
<userid>jsmith</userid>
<senior_acct_no></senior_acct_no>
<master_plan_instance_no>98765</master_plan_instance_no>
<client_plan_instance_id>MPI-STANDARD-001</client_plan_instance_id>
<resp_level_cd>0</resp_level_cd>
<resp_plan_instance_no></resp_plan_instance_no>
<in_event_scope_ind>1</in_event_scope_ind>
<msg_id>20059</msg_id>
<msg_class>E</msg_class>
<msg_class_label>Contract End: Terminate Service and Billing</msg_class_label>
<msg_creation_date>2026-06-15</msg_creation_date>
<msg_sent_date>2026-06-15</msg_sent_date>
<msg_subject>Your Contract Has Ended: Service and Billing Will Terminate</msg_subject>
<msg_recipient_email_address>customer@example.com</msg_recipient_email_address>
<xml_statement_no></xml_statement_no>
<statement_no></statement_no>
<invoice_no></invoice_no>
<sequential_statement_id></sequential_statement_id>
<event_data>
<event_no>1062</event_no>
<event_label>Contract End: Terminate Service and Billing</event_label>
</event_data>
</apf2doc>
Note: After this event fires, it is safe to terminate service and stop billing in your downstream systems. Use <master_plan_instance_no> to identify the plan instance being terminated.
Event 1063: Message Type “Contract End: Terminate Service and Billing (Proration)” Sent to Account Holder
Aria sends this notification when the contract-end termination with proration notification is delivered to your customer.
<?xml version="1.0" encoding="UTF-8"?>
<apf2doc>
<request>
<version>3.1</version>
<sender>A</sender>
<transaction_id>100000414</transaction_id>
<action>M</action>
<class>N</class>
<auth_key>CLIENTAUTH12345</auth_key>
</request>
<client_no>10001</client_no>
<acct_no>12345678</acct_no>
<client_acct_id>CLIENT-ACCT-001</client_acct_id>
<userid>jsmith</userid>
<senior_acct_no></senior_acct_no>
<master_plan_instance_no>98765</master_plan_instance_no>
<client_plan_instance_id>MPI-STANDARD-001</client_plan_instance_id>
<resp_level_cd>0</resp_level_cd>
<resp_plan_instance_no></resp_plan_instance_no>
<in_event_scope_ind>1</in_event_scope_ind>
<msg_id>20060</msg_id>
<msg_class>E</msg_class>
<msg_class_label>Contract End: Terminate Service and Billing (Proration)</msg_class_label>
<msg_creation_date>2026-06-15</msg_creation_date>
<msg_sent_date>2026-06-15</msg_sent_date>
<msg_subject>Your Contract Has Ended: Service and Billing Will Terminate with Proration</msg_subject>
<msg_recipient_email_address>customer@example.com</msg_recipient_email_address>
<xml_statement_no></xml_statement_no>
<statement_no></statement_no>
<invoice_no></invoice_no>
<sequential_statement_id></sequential_statement_id>
<event_data>
<event_no>1063</event_no>
<event_label>Contract End: Terminate Service and Billing (Proration)</event_label>
</event_data>
</apf2doc>
Note: Verify that the prorated charge from event 1058 has been posted to the account before closing the billing record. Use <master_plan_instance_no> to locate the affected plan instance.
Event 1064: Message Type “Contract End: Continue Service” Sent to Account Holder
Aria sends this notification when the contract-end continue-service notification is delivered to your customer.
<?xml version="1.0" encoding="UTF-8"?>
<apf2doc>
<request>
<version>3.1</version>
<sender>A</sender>
<transaction_id>100000421</transaction_id>
<action>M</action>
<class>N</class>
<auth_key>CLIENTAUTH12345</auth_key>
</request>
<client_no>10001</client_no>
<acct_no>12345678</acct_no>
<client_acct_id>CLIENT-ACCT-001</client_acct_id>
<userid>jsmith</userid>
<senior_acct_no></senior_acct_no>
<master_plan_instance_no>98765</master_plan_instance_no>
<client_plan_instance_id>MPI-STANDARD-001</client_plan_instance_id>
<resp_level_cd>0</resp_level_cd>
<resp_plan_instance_no></resp_plan_instance_no>
<in_event_scope_ind>1</in_event_scope_ind>
<msg_id>20061</msg_id>
<msg_class>E</msg_class>
<msg_class_label>Contract End: Continue Service</msg_class_label>
<msg_creation_date>2026-06-15</msg_creation_date>
<msg_sent_date>2026-06-15</msg_sent_date>
<msg_subject>Your Contract Has Ended: Service Will Continue</msg_subject>
<msg_recipient_email_address>customer@example.com</msg_recipient_email_address>
<xml_statement_no></xml_statement_no>
<statement_no></statement_no>
<invoice_no></invoice_no>
<sequential_statement_id></sequential_statement_id>
<event_data>
<event_no>1064</event_no>
<event_label>Contract End: Continue Service</event_label>
</event_data>
</apf2doc>
Note: Update the contract status in your CRM to reflect that the customer is now on an ongoing arrangement. Correlate with event 1059 using <msg_id> to close the notification lifecycle.
Event 1065: Message Type “Contract End: Renew Automatically” Sent to Account Holder
Aria sends this notification when the contract auto-renewal notification is delivered to your customer.
<?xml version="1.0" encoding="UTF-8"?>
<apf2doc>
<request>
<version>3.1</version>
<sender>A</sender>
<transaction_id>100000428</transaction_id>
<action>M</action>
<class>N</class>
<auth_key>CLIENTAUTH12345</auth_key>
</request>
<client_no>10001</client_no>
<acct_no>12345678</acct_no>
<client_acct_id>CLIENT-ACCT-001</client_acct_id>
<userid>jsmith</userid>
<senior_acct_no></senior_acct_no>
<master_plan_instance_no>98765</master_plan_instance_no>
<client_plan_instance_id>MPI-STANDARD-001</client_plan_instance_id>
<resp_level_cd>0</resp_level_cd>
<resp_plan_instance_no></resp_plan_instance_no>
<in_event_scope_ind>1</in_event_scope_ind>
<msg_id>20062</msg_id>
<msg_class>E</msg_class>
<msg_class_label>Contract End: Renew Automatically</msg_class_label>
<msg_creation_date>2026-06-15</msg_creation_date>
<msg_sent_date>2026-06-15</msg_sent_date>
<msg_subject>Your Contract Has Been Renewed Automatically</msg_subject>
<msg_recipient_email_address>customer@example.com</msg_recipient_email_address>
<xml_statement_no></xml_statement_no>
<statement_no></statement_no>
<invoice_no></invoice_no>
<sequential_statement_id></sequential_statement_id>
<event_data>
<event_no>1065</event_no>
<event_label>Contract End: Renew Automatically</event_label>
</event_data>
</apf2doc>
Note: Update contract dates and renewal terms in your CRM after this event fires. Use <master_plan_instance_no> to identify the renewed plan instance.
Event 1066: Message Type “Contract End: Rollover” Sent to Account Holder
Aria sends this notification when the contract rollover notification is delivered to your customer.
<?xml version="1.0" encoding="UTF-8"?>
<apf2doc>
<request>
<version>3.1</version>
<sender>A</sender>
<transaction_id>100000435</transaction_id>
<action>M</action>
<class>N</class>
<auth_key>CLIENTAUTH12345</auth_key>
</request>
<client_no>10001</client_no>
<acct_no>12345678</acct_no>
<client_acct_id>CLIENT-ACCT-001</client_acct_id>
<userid>jsmith</userid>
<senior_acct_no></senior_acct_no>
<master_plan_instance_no>98765</master_plan_instance_no>
<client_plan_instance_id>MPI-STANDARD-001</client_plan_instance_id>
<resp_level_cd>0</resp_level_cd>
<resp_plan_instance_no></resp_plan_instance_no>
<in_event_scope_ind>1</in_event_scope_ind>
<msg_id>20063</msg_id>
<msg_class>E</msg_class>
<msg_class_label>Contract End: Rollover</msg_class_label>
<msg_creation_date>2026-06-15</msg_creation_date>
<msg_sent_date>2026-06-15</msg_sent_date>
<msg_subject>Your Contract Has Rolled Over</msg_subject>
<msg_recipient_email_address>customer@example.com</msg_recipient_email_address>
<xml_statement_no></xml_statement_no>
<statement_no></statement_no>
<invoice_no></invoice_no>
<sequential_statement_id></sequential_statement_id>
<event_data>
<event_no>1066</event_no>
<event_label>Contract End: Rollover</event_label>
</event_data>
</apf2doc>
Note: Update the contract record in your CRM with the new term details. Correlate with event 1061 using <msg_id> to close the notification lifecycle.
Event 1067: Account Message Type “Credit Card Update Required” Requires Sending
Aria sends this notification when a credit card update required notification is distilled and queued for delivery.
<?xml version="1.0" encoding="UTF-8"?>
<apf2doc>
<request>
<version>3.1</version>
<sender>A</sender>
<transaction_id>100000442</transaction_id>
<action>A</action>
<class>N</class>
<auth_key>CLIENTAUTH12345</auth_key>
</request>
<client_no>10001</client_no>
<acct_no>12345678</acct_no>
<client_acct_id>CLIENT-ACCT-001</client_acct_id>
<userid>jsmith</userid>
<senior_acct_no></senior_acct_no>
<master_plan_instance_no>98765</master_plan_instance_no>
<client_plan_instance_id>MPI-STANDARD-001</client_plan_instance_id>
<resp_level_cd>0</resp_level_cd>
<resp_plan_instance_no></resp_plan_instance_no>
<in_event_scope_ind>1</in_event_scope_ind>
<msg_id>20064</msg_id>
<msg_class>C</msg_class>
<msg_class_label>Credit Card Update Required</msg_class_label>
<msg_creation_date>2026-06-15</msg_creation_date>
<msg_sent_date></msg_sent_date>
<msg_subject>Please Update Your Credit Card Information</msg_subject>
<msg_recipient_email_address>customer@example.com</msg_recipient_email_address>
<xml_statement_no></xml_statement_no>
<statement_no></statement_no>
<invoice_no></invoice_no>
<sequential_statement_id></sequential_statement_id>
<event_data>
<event_no>1067</event_no>
<event_label>Credit Card Update Required</event_label>
</event_data>
</apf2doc>
Note: This event fires when a customer’s credit card requires updating (for example, the card has been declined or the details are invalid). Use <acct_no> to flag the account in your billing system as needing a payment method update. Subscribe to event 1068 to confirm delivery.
Event 1068: Message Type “Credit Card Update Required” Sent to Account Holder
Aria sends this notification when the credit card update required notification is delivered to your customer.
<?xml version="1.0" encoding="UTF-8"?>
<apf2doc>
<request>
<version>3.1</version>
<sender>A</sender>
<transaction_id>100000449</transaction_id>
<action>M</action>
<class>N</class>
<auth_key>CLIENTAUTH12345</auth_key>
</request>
<client_no>10001</client_no>
<acct_no>12345678</acct_no>
<client_acct_id>CLIENT-ACCT-001</client_acct_id>
<userid>jsmith</userid>
<senior_acct_no></senior_acct_no>
<master_plan_instance_no>98765</master_plan_instance_no>
<client_plan_instance_id>MPI-STANDARD-001</client_plan_instance_id>
<resp_level_cd>0</resp_level_cd>
<resp_plan_instance_no></resp_plan_instance_no>
<in_event_scope_ind>1</in_event_scope_ind>
<msg_id>20065</msg_id>
<msg_class>C</msg_class>
<msg_class_label>Credit Card Update Required</msg_class_label>
<msg_creation_date>2026-06-15</msg_creation_date>
<msg_sent_date>2026-06-15</msg_sent_date>
<msg_subject>Please Update Your Credit Card Information</msg_subject>
<msg_recipient_email_address>customer@example.com</msg_recipient_email_address>
<xml_statement_no></xml_statement_no>
<statement_no></statement_no>
<invoice_no></invoice_no>
<sequential_statement_id></sequential_statement_id>
<event_data>
<event_no>1068</event_no>
<event_label>Credit Card Update Required</event_label>
</event_data>
</apf2doc>
Note: If the customer does not respond within your defined grace period, use <acct_no> to initiate a follow-up communication or account restriction. Use <msg_sent_date> to start the grace period clock.
Event 1069: Account Message Type “Contract Expiry – Continue Existing Service without Contract” Advance Notification Requires Sending
Aria sends this notification when an advance notification is distilled indicating the contract will expire and service will continue without a new contract.
<?xml version="1.0" encoding="UTF-8"?>
<apf2doc>
<request>
<version>3.1</version>
<sender>A</sender>
<transaction_id>100000456</transaction_id>
<action>A</action>
<class>N</class>
<auth_key>CLIENTAUTH12345</auth_key>
</request>
<client_no>10001</client_no>
<acct_no>12345678</acct_no>
<client_acct_id>CLIENT-ACCT-001</client_acct_id>
<userid>jsmith</userid>
<senior_acct_no></senior_acct_no>
<master_plan_instance_no>98765</master_plan_instance_no>
<client_plan_instance_id>MPI-STANDARD-001</client_plan_instance_id>
<resp_level_cd>0</resp_level_cd>
<resp_plan_instance_no></resp_plan_instance_no>
<in_event_scope_ind>1</in_event_scope_ind>
<msg_id>20066</msg_id>
<msg_class>E</msg_class>
<msg_class_label>Contract Expiry - Continue Existing Service without Contract Advance Notification</msg_class_label>
<msg_creation_date>2026-06-15</msg_creation_date>
<msg_sent_date></msg_sent_date>
<msg_subject>Advance Notice: Your Contract Is Expiring and Service Will Continue</msg_subject>
<msg_recipient_email_address>customer@example.com</msg_recipient_email_address>
<xml_statement_no></xml_statement_no>
<statement_no></statement_no>
<invoice_no></invoice_no>
<sequential_statement_id></sequential_statement_id>
<event_data>
<event_no>1069</event_no>
<event_label>Contract Expiry - Continue Existing Service without Contract Advance Notification</event_label>
</event_data>
</apf2doc>
Note: Advance notifications fire before contract expiry, giving customers time to act. Use this event to alert your account management team that the contract is expiring and the customer will shift to service without a contract. Subscribe to event 1074 to confirm the advance notice was delivered.
Event 1070: Account Message Type “Contract Expiry – Rollover Automatically” Advance Notification Requires Sending
Aria sends this notification when an advance notification is distilled indicating the contract will roll over automatically.
<?xml version="1.0" encoding="UTF-8"?>
<apf2doc>
<request>
<version>3.1</version>
<sender>A</sender>
<transaction_id>100000463</transaction_id>
<action>A</action>
<class>N</class>
<auth_key>CLIENTAUTH12345</auth_key>
</request>
<client_no>10001</client_no>
<acct_no>12345678</acct_no>
<client_acct_id>CLIENT-ACCT-001</client_acct_id>
<userid>jsmith</userid>
<senior_acct_no></senior_acct_no>
<master_plan_instance_no>98765</master_plan_instance_no>
<client_plan_instance_id>MPI-STANDARD-001</client_plan_instance_id>
<resp_level_cd>0</resp_level_cd>
<resp_plan_instance_no></resp_plan_instance_no>
<in_event_scope_ind>1</in_event_scope_ind>
<msg_id>20067</msg_id>
<msg_class>E</msg_class>
<msg_class_label>Contract Expiry - Rollover Automatically Advance Notification</msg_class_label>
<msg_creation_date>2026-06-15</msg_creation_date>
<msg_sent_date></msg_sent_date>
<msg_subject>Advance Notice: Your Contract Will Roll Over Automatically</msg_subject>
<msg_recipient_email_address>customer@example.com</msg_recipient_email_address>
<xml_statement_no></xml_statement_no>
<statement_no></statement_no>
<invoice_no></invoice_no>
<sequential_statement_id></sequential_statement_id>
<event_data>
<event_no>1070</event_no>
<event_label>Contract Expiry - Rollover Automatically Advance Notification</event_label>
</event_data>
</apf2doc>
Note: Use this event to notify your account management team that an automatic rollover is scheduled. If your CRM tracks contract renewals, create a pending renewal record when this event fires. Subscribe to event 1075 to confirm customer delivery of the advance notice.
Event 1071: Account Message Type “Contract Expiry – Terminate Service and Billing (Proration)” Advance Notification Requires Sending
Aria sends this notification when an advance notification is distilled indicating the contract will expire and service will terminate with proration.
<?xml version="1.0" encoding="UTF-8"?>
<apf2doc>
<request>
<version>3.1</version>
<sender>A</sender>
<transaction_id>100000470</transaction_id>
<action>A</action>
<class>N</class>
<auth_key>CLIENTAUTH12345</auth_key>
</request>
<client_no>10001</client_no>
<acct_no>12345678</acct_no>
<client_acct_id>CLIENT-ACCT-001</client_acct_id>
<userid>jsmith</userid>
<senior_acct_no></senior_acct_no>
<master_plan_instance_no>98765</master_plan_instance_no>
<client_plan_instance_id>MPI-STANDARD-001</client_plan_instance_id>
<resp_level_cd>0</resp_level_cd>
<resp_plan_instance_no></resp_plan_instance_no>
<in_event_scope_ind>1</in_event_scope_ind>
<msg_id>20068</msg_id>
<msg_class>E</msg_class>
<msg_class_label>Contract Expiry - Terminate Service and Billing (Proration) Advance Notification</msg_class_label>
<msg_creation_date>2026-06-15</msg_creation_date>
<msg_sent_date></msg_sent_date>
<msg_subject>Advance Notice: Your Contract Will Expire and Service Will Terminate with Proration</msg_subject>
<msg_recipient_email_address>customer@example.com</msg_recipient_email_address>
<xml_statement_no></xml_statement_no>
<statement_no></statement_no>
<invoice_no></invoice_no>
<sequential_statement_id></sequential_statement_id>
<event_data>
<event_no>1071</event_no>
<event_label>Contract Expiry - Terminate Service and Billing (Proration) Advance Notification</event_label>
</event_data>
</apf2doc>
Note: Ensure your billing system is configured to calculate the prorated final charge. Subscribe to event 1076 to confirm the advance notice was delivered.
Event 1072: Account Message Type “Contract Expiry – Terminate Service and Billing” Advance Notification Requires Sending
Aria sends this notification when an advance notification is distilled indicating the contract will expire and service will terminate.
<?xml version="1.0" encoding="UTF-8"?>
<apf2doc>
<request>
<version>3.1</version>
<sender>A</sender>
<transaction_id>100000477</transaction_id>
<action>A</action>
<class>N</class>
<auth_key>CLIENTAUTH12345</auth_key>
</request>
<client_no>10001</client_no>
<acct_no>12345678</acct_no>
<client_acct_id>CLIENT-ACCT-001</client_acct_id>
<userid>jsmith</userid>
<senior_acct_no></senior_acct_no>
<master_plan_instance_no>98765</master_plan_instance_no>
<client_plan_instance_id>MPI-STANDARD-001</client_plan_instance_id>
<resp_level_cd>0</resp_level_cd>
<resp_plan_instance_no></resp_plan_instance_no>
<in_event_scope_ind>1</in_event_scope_ind>
<msg_id>20069</msg_id>
<msg_class>E</msg_class>
<msg_class_label>Contract Expiry - Terminate Service and Billing Advance Notification</msg_class_label>
<msg_creation_date>2026-06-15</msg_creation_date>
<msg_sent_date></msg_sent_date>
<msg_subject>Advance Notice: Your Contract Will Expire and Service Will Terminate</msg_subject>
<msg_recipient_email_address>customer@example.com</msg_recipient_email_address>
<xml_statement_no></xml_statement_no>
<statement_no></statement_no>
<invoice_no></invoice_no>
<sequential_statement_id></sequential_statement_id>
<event_data>
<event_no>1072</event_no>
<event_label>Contract Expiry - Terminate Service and Billing Advance Notification</event_label>
</event_data>
</apf2doc>
Note: Use this event to begin pre-termination workflows such as notifying the account team or preparing an offboarding plan. Do not terminate service until the advance notice period has elapsed and the contract has actually expired. Subscribe to event 1077 to confirm delivery.
Event 1073: Account Message Type “Contract Renewal – Renew Automatically” Advance Notification Requires Sending
Aria sends this notification when an advance notification is distilled indicating the contract will renew automatically.
<?xml version="1.0" encoding="UTF-8"?>
<apf2doc>
<request>
<version>3.1</version>
<sender>A</sender>
<transaction_id>100000484</transaction_id>
<action>A</action>
<class>N</class>
<auth_key>CLIENTAUTH12345</auth_key>
</request>
<client_no>10001</client_no>
<acct_no>12345678</acct_no>
<client_acct_id>CLIENT-ACCT-001</client_acct_id>
<userid>jsmith</userid>
<senior_acct_no></senior_acct_no>
<master_plan_instance_no>98765</master_plan_instance_no>
<client_plan_instance_id>MPI-STANDARD-001</client_plan_instance_id>
<resp_level_cd>0</resp_level_cd>
<resp_plan_instance_no></resp_plan_instance_no>
<in_event_scope_ind>1</in_event_scope_ind>
<msg_id>20070</msg_id>
<msg_class>E</msg_class>
<msg_class_label>Contract Renewal - Renew Automatically Advance Notification</msg_class_label>
<msg_creation_date>2026-06-15</msg_creation_date>
<msg_sent_date></msg_sent_date>
<msg_subject>Advance Notice: Your Contract Will Renew Automatically</msg_subject>
<msg_recipient_email_address>customer@example.com</msg_recipient_email_address>
<xml_statement_no></xml_statement_no>
<statement_no></statement_no>
<invoice_no></invoice_no>
<sequential_statement_id></sequential_statement_id>
<event_data>
<event_no>1073</event_no>
<event_label>Contract Renewal - Renew Automatically Advance Notification</event_label>
</event_data>
</apf2doc>
Note: Use this event to prepare your CRM for the upcoming renewal, such as pre-staging the new contract dates or alerting the account manager. Subscribe to event 1078 to confirm the advance notice was delivered to the customer.
Event 1074: Message Type “Contract Expiry – Continue Existing Service without Contract” Advance Notification Sent to Account Holder
Aria sends this notification when the advance contract expiry notice is delivered to your customer, indicating service will continue without a new contract.
<?xml version="1.0" encoding="UTF-8"?>
<apf2doc>
<request>
<version>3.1</version>
<sender>A</sender>
<transaction_id>100000491</transaction_id>
<action>M</action>
<class>N</class>
<auth_key>CLIENTAUTH12345</auth_key>
</request>
<client_no>10001</client_no>
<acct_no>12345678</acct_no>
<client_acct_id>CLIENT-ACCT-001</client_acct_id>
<userid>jsmith</userid>
<senior_acct_no></senior_acct_no>
<master_plan_instance_no>98765</master_plan_instance_no>
<client_plan_instance_id>MPI-STANDARD-001</client_plan_instance_id>
<resp_level_cd>0</resp_level_cd>
<resp_plan_instance_no></resp_plan_instance_no>
<in_event_scope_ind>1</in_event_scope_ind>
<msg_id>20071</msg_id>
<msg_class>E</msg_class>
<msg_class_label>Contract Expiry - Continue Existing Service without Contract Advance Notification</msg_class_label>
<msg_creation_date>2026-06-15</msg_creation_date>
<msg_sent_date>2026-06-15</msg_sent_date>
<msg_subject>Advance Notice: Your Contract Is Expiring and Service Will Continue</msg_subject>
<msg_recipient_email_address>customer@example.com</msg_recipient_email_address>
<xml_statement_no></xml_statement_no>
<statement_no></statement_no>
<invoice_no></invoice_no>
<sequential_statement_id></sequential_statement_id>
<event_data>
<event_no>1074</event_no>
<event_label>Contract Expiry - Continue Existing Service without Contract Advance Notification</event_label>
</event_data>
</apf2doc>
Note: Use <msg_sent_date> to calculate the remaining time before the contract expires and determine your window for proactive outreach. Correlate with event 1069 using <msg_id>.
Event 1075: Message Type “Contract Expiry – Rollover Automatically” Advance Notification Sent to Account Holder
Aria sends this notification when the advance rollover notice is delivered to your customer.
<?xml version="1.0" encoding="UTF-8"?>
<apf2doc>
<request>
<version>3.1</version>
<sender>A</sender>
<transaction_id>100000498</transaction_id>
<action>M</action>
<class>N</class>
<auth_key>CLIENTAUTH12345</auth_key>
</request>
<client_no>10001</client_no>
<acct_no>12345678</acct_no>
<client_acct_id>CLIENT-ACCT-001</client_acct_id>
<userid>jsmith</userid>
<senior_acct_no></senior_acct_no>
<master_plan_instance_no>98765</master_plan_instance_no>
<client_plan_instance_id>MPI-STANDARD-001</client_plan_instance_id>
<resp_level_cd>0</resp_level_cd>
<resp_plan_instance_no></resp_plan_instance_no>
<in_event_scope_ind>1</in_event_scope_ind>
<msg_id>20072</msg_id>
<msg_class>E</msg_class>
<msg_class_label>Contract Expiry - Rollover Automatically Advance Notification</msg_class_label>
<msg_creation_date>2026-06-15</msg_creation_date>
<msg_sent_date>2026-06-15</msg_sent_date>
<msg_subject>Advance Notice: Your Contract Will Roll Over Automatically</msg_subject>
<msg_recipient_email_address>customer@example.com</msg_recipient_email_address>
<xml_statement_no></xml_statement_no>
<statement_no></statement_no>
<invoice_no></invoice_no>
<sequential_statement_id></sequential_statement_id>
<event_data>
<event_no>1075</event_no>
<event_label>Contract Expiry - Rollover Automatically Advance Notification</event_label>
</event_data>
</apf2doc>
Note: Update the pending renewal record in your CRM to reflect that the customer has been notified. Correlate with event 1070 using <msg_id> to close the advance-notification lifecycle.
Event 1076: Message Type “Contract Expiry – Terminate Service and Billing (Proration)” Advance Notification Sent to Account Holder
Aria sends this notification when the advance proration termination notice is delivered to your customer.
<?xml version="1.0" encoding="UTF-8"?>
<apf2doc>
<request>
<version>3.1</version>
<sender>A</sender>
<transaction_id>100000505</transaction_id>
<action>M</action>
<class>N</class>
<auth_key>CLIENTAUTH12345</auth_key>
</request>
<client_no>10001</client_no>
<acct_no>12345678</acct_no>
<client_acct_id>CLIENT-ACCT-001</client_acct_id>
<userid>jsmith</userid>
<senior_acct_no></senior_acct_no>
<master_plan_instance_no>98765</master_plan_instance_no>
<client_plan_instance_id>MPI-STANDARD-001</client_plan_instance_id>
<resp_level_cd>0</resp_level_cd>
<resp_plan_instance_no></resp_plan_instance_no>
<in_event_scope_ind>1</in_event_scope_ind>
<msg_id>20073</msg_id>
<msg_class>E</msg_class>
<msg_class_label>Contract Expiry - Terminate Service and Billing (Proration) Advance Notification</msg_class_label>
<msg_creation_date>2026-06-15</msg_creation_date>
<msg_sent_date>2026-06-15</msg_sent_date>
<msg_subject>Advance Notice: Your Contract Will Expire and Service Will Terminate with Proration</msg_subject>
<msg_recipient_email_address>customer@example.com</msg_recipient_email_address>
<xml_statement_no></xml_statement_no>
<statement_no></statement_no>
<invoice_no></invoice_no>
<sequential_statement_id></sequential_statement_id>
<event_data>
<event_no>1076</event_no>
<event_label>Contract Expiry - Terminate Service and Billing (Proration) Advance Notification</event_label>
</event_data>
</apf2doc>
Note: Begin final proration calculations and ensure your billing system is ready to post the prorated charge at contract end. Correlate with event 1071 using <msg_id>.
Event 1077: Message Type “Contract Expiry – Terminate Service and Billing” Advance Notification Sent to Account Holder
Aria sends this notification when the advance termination notice is delivered to your customer.
<?xml version="1.0" encoding="UTF-8"?>
<apf2doc>
<request>
<version>3.1</version>
<sender>A</sender>
<transaction_id>100000512</transaction_id>
<action>M</action>
<class>N</class>
<auth_key>CLIENTAUTH12345</auth_key>
</request>
<client_no>10001</client_no>
<acct_no>12345678</acct_no>
<client_acct_id>CLIENT-ACCT-001</client_acct_id>
<userid>jsmith</userid>
<senior_acct_no></senior_acct_no>
<master_plan_instance_no>98765</master_plan_instance_no>
<client_plan_instance_id>MPI-STANDARD-001</client_plan_instance_id>
<resp_level_cd>0</resp_level_cd>
<resp_plan_instance_no></resp_plan_instance_no>
<in_event_scope_ind>1</in_event_scope_ind>
<msg_id>20074</msg_id>
<msg_class>E</msg_class>
<msg_class_label>Contract Expiry - Terminate Service and Billing Advance Notification</msg_class_label>
<msg_creation_date>2026-06-15</msg_creation_date>
<msg_sent_date>2026-06-15</msg_sent_date>
<msg_subject>Advance Notice: Your Contract Will Expire and Service Will Terminate</msg_subject>
<msg_recipient_email_address>customer@example.com</msg_recipient_email_address>
<xml_statement_no></xml_statement_no>
<statement_no></statement_no>
<invoice_no></invoice_no>
<sequential_statement_id></sequential_statement_id>
<event_data>
<event_no>1077</event_no>
<event_label>Contract Expiry - Terminate Service and Billing Advance Notification</event_label>
</event_data>
</apf2doc>
Note: Use <msg_sent_date> as the start of the advance-notice period to schedule termination workflows. Do not terminate service until the advance period has elapsed and contract expiry has occurred. Correlate with event 1072 using <msg_id>.
Event 1078: Message Type “Contract Renewal – Renew Automatically” Advance Notification Sent to Account Holder
Aria sends this notification when the advance auto-renewal notice is delivered to your customer.
<?xml version="1.0" encoding="UTF-8"?>
<apf2doc>
<request>
<version>3.1</version>
<sender>A</sender>
<transaction_id>100000519</transaction_id>
<action>M</action>
<class>N</class>
<auth_key>CLIENTAUTH12345</auth_key>
</request>
<client_no>10001</client_no>
<acct_no>12345678</acct_no>
<client_acct_id>CLIENT-ACCT-001</client_acct_id>
<userid>jsmith</userid>
<senior_acct_no></senior_acct_no>
<master_plan_instance_no>98765</master_plan_instance_no>
<client_plan_instance_id>MPI-STANDARD-001</client_plan_instance_id>
<resp_level_cd>0</resp_level_cd>
<resp_plan_instance_no></resp_plan_instance_no>
<in_event_scope_ind>1</in_event_scope_ind>
<msg_id>20075</msg_id>
<msg_class>E</msg_class>
<msg_class_label>Contract Renewal - Renew Automatically Advance Notification</msg_class_label>
<msg_creation_date>2026-06-15</msg_creation_date>
<msg_sent_date>2026-06-15</msg_sent_date>
<msg_subject>Advance Notice: Your Contract Will Renew Automatically</msg_subject>
<msg_recipient_email_address>customer@example.com</msg_recipient_email_address>
<xml_statement_no></xml_statement_no>
<statement_no></statement_no>
<invoice_no></invoice_no>
<sequential_statement_id></sequential_statement_id>
<event_data>
<event_no>1078</event_no>
<event_label>Contract Renewal - Renew Automatically Advance Notification</event_label>
</event_data>
</apf2doc>
Note: Use <msg_sent_date> to determine the notification date and schedule renewal processing to occur on the contract renewal date. Correlate with event 1073 using <msg_id> to close the advance-notification lifecycle.
General Notes for System Integrators
The <version> element is fixed at 3.1 for payloads in this event class. Do not use this value to version-gate your integration logic; use the <class> and <event_no> fields instead to route incoming payloads.
The <sender> element is always A (Aria) for outbound event notifications. Aria does not currently support inbound provisioning requests from clients for this class, so you can treat sender=A as a fixed constant when building your receiver.
The <action> element identifies the type of operation that triggered the notification. Use A (add) for events in which a message has been distilled and queued, and M (modify) for events in which a message has been sent. Because this class does not represent a persistent object being added, modified, or deleted in the traditional sense, there is no <object_action> element in payloads for this class.
The <class> value for all payloads in this class is N, identifying the payload as an Account and Master Plan Instances Notification event. Use this field as the first routing key in your integration layer to direct payloads to your notification handler. Within that handler, use <event_no> inside <event_data> to select the specific handling logic for each event.
The <acct_no> field is the immutable Aria-assigned account identifier. Always use this field as the primary key when looking up account records in your downstream systems. The <client_acct_id> field is a client-defined identifier and may change over the life of the account. Do not rely on <client_acct_id> as a stable primary key.
The <master_plan_instance_no> field identifies the specific master plan instance associated with the event. The <client_plan_instance_id> is the client-assigned identifier for that plan instance and is mutable. Use <master_plan_instance_no> as the stable reference when routing events to service or billing handlers that are scoped to a plan instance.
Use the <transaction_id> field as an idempotency key to detect and discard duplicate deliveries. Aria may redeliver a payload if the initial delivery attempt did not receive a successful acknowledgment. Store processed <transaction_id> values and reject duplicates before applying any side effects.
Always validate the <auth_key> value against the key configured in your Aria account before processing any payload. Discard payloads that present an unrecognized or mismatched authentication key. This validation step prevents unauthorized or malformed payloads from triggering unintended actions in your downstream systems.
The <msg_id> field is the Aria-assigned unique identifier for the message. Use it to correlate a distillation event (for example, event 1001) with its corresponding sent event (for example, event 1010) and to track the full lifecycle of a customer notification. The <msg_class> and <msg_class_label> fields identify the category of the message; see the Account Message Types legend in the Aria API documentation for a complete list of valid <msg_class> values.
For events that involve invoice or statement documents, the <invoice_no>, <statement_no>, <xml_statement_no>, and <sequential_statement_id> fields identify the associated billing document. These fields are empty for non-billing events. When present, use them to correlate the notification with the correct billing record in your financial system.
The <msg_sent_date> field is empty for distillation events (those with <action>A</action>) and is populated for sent events (those with <action>M</action>). Use this field to timestamp delivery confirmation in your communication logs and to enforce grace periods or escalation timers tied to message delivery.