Send to SMD Validation & Configuration

Purpose of XML Configuration

Send to SMD generates an XML file that is consumed directly by an external system (e.g. billing, finance, or operational platforms).

The XML format is strictly governed to ensure:

• Compatibility with the external system
• Accurate financial and operational processing
• No downstream transformation or manual intervention

Each agency’s XML configuration is defined during implementation and reflects that agency’s specific system requirements.

Scope of Configuration

XML configuration controls how campaign data is represented when exported.

This includes:

• Field mappings between Advvy and the external system
• Required vs optional data elements
• Structural grouping of campaign activity
• Agency-specific identifiers, codes, and classifications
• Enforcement of external system schema rules

Once configured, this structure applies consistently to all Send to SMD exports for the agency.

What Admins Can Configure

Admins (with implementation support) can define or adjust:

• Mapping of Advvy fields to XML elements
• Mandatory field requirements
• Validation rules tied to the export
• Handling of agency-specific commercial logic
• Identifier and reference code usage

All changes require:

• Alignment with the external system owner
• Testing using real campaign data
• Validation against downstream ingestion rules

What Cannot Be Configured at Runtime

The following cannot be changed by end users or adjusted per campaign:

• XML schema structure
• Required fields enforced by the external system
• Validation logic tied to financial compliance
• Grouping logic for exported activity
• XML format per individual export

Any change to these requires a formal configuration update and revalidation.

Relationship Between Validation and XML Output

Pre-validation exists to protect the integrity of the XML output.

Validation ensures:

• All required XML fields can be populated
• Data types and values meet schema constraints
• Financial values are compliant and interpretable
• Exported activity will not be rejected downstream

If validation fails:

• The XML file is not generated
• The campaign queue item is marked as errored
• Users must correct campaign data before retrying

Filtering and Partial Exports

Users may filter which campaign activity is included in a Send to SMD action.

Admins should note:

• Only filtered activity is validated and exported
• XML rules apply equally to full and partial exports
• Partial exports increase the importance of consistent structural rules

Validation logic is applied only to included activity, not the entire campaign.

Governance and Risk Considerations

Poorly aligned XML configuration can result in:

• Rejected files downstream
• Manual rework in finance or billing systems
• Inconsistent reconciliation outcomes
• User frustration and repeated export failures

Overly strict validation may block legitimate scenarios.
 Overly permissive validation increases operational and financial risk.

Admin Best Practices

• Align XML requirements with finance and system owners before configuration
• Avoid agency-specific exceptions unless strictly required
• Test changes using real-world campaign scenarios
• Document assumptions and constraints clearly
• Escalate structural edge cases rather than bypassing validation

Summary

XML configuration defines how campaign data leaves Advvy.
 It is deliberately rigid, centrally governed, and enforced through validation to protect downstream systems.

Admins are responsible for ensuring configuration reflects real operational requirements while maintaining data integrity.