auth.030.001.01

Q: How do I validate a auth.030 message?

Run askiso validate message.xml . The schema is found from the document's own namespace, so you do not name it. Validation needs that schema installed. To check the business rules without one, run askiso lint instead.

What auth.030.001.01 is

auth.030.001.01 is an ISO 20022 message definition. Its business area is Regulatory Reporting (auth), and auth.030 is the definition it versions.

AskISO does not copy the specification. The Registration Authority publishes the message definition report and the schema, free of charge. The links below go straight there.

This is one of 3 published versions of auth.030, and it is not the newest. The current version is auth.030.001.03. That does not make this page obsolete: a counterparty running an older integration may still send you exactly this version, and you will need to read it.

Versions of auth.030

The standard publishes 3 versions of this definition. A newer version does not automatically replace an older one. The scheme or market infrastructure you send to decides which version you should be using.

Where to get the schema

auth.030.001.01 is published in 2 message sets. Download from the Registration Authority, then import:

askiso catalog fetch auth.030

Message set	Version	Download
Financial Instruments and Transactions Regulatory Reporting (Trade Repository Reporting)	v02	iso20022.org
Financial Instruments and Transactions Regulatory Reporting (Trade Repository Reporting)	v01	iso20022.org

What AskISO does with auth.030.001.01

askiso info auth.030.001.01                    # metadata and schema paths
askiso validate message.xml                    # full XSD validation, needs the schema
askiso lint message.xml                        # business rules, needs no schema
askiso generate auth.030.001.01 --from-schema  # walks the schema

Questions

What business area does auth.030.001.01 belong to?

Regulatory Reporting (auth).

How do I validate a auth.030 message?

Run askiso validate message.xml. The schema is found from the document's own namespace, so you do not name it. Validation needs that schema installed. To check the business rules without one, run askiso lint instead.

Does AskISO include the auth.030.001.01 schema?

No. AskISO ships no ISO 20022 specification content at all. You download the message set from the Registration Authority, then import it with askiso catalog add. The binary carries only an index: what exists, and where to find it.

Which version of auth.030 should I send?

The scheme or market infrastructure you send to decides that, not the standard. There are 3 published versions. Run askiso diff <from> <to> to see every structural difference between two of them, marked as breaking or compatible.

Check a auth.030 message — paste one and see every finding, with the rule and the path behind it
All Regulatory Reporting messages — the rest of the Regulatory Reporting area, and every other ISO 20022 message
Documentation — installing AskISO, and every command it offers

AskISO generates this page from its built-in index of the standard. The source of truth for ISO 20022 is iso20022.org.