Interface "PEPPOL30 Validation"

PEPPOL · Microsoft.Peppol · BC29-30 · source at ea08af5e · facts from BC29

Procedures

• ValidateDocument(RecordVariant: Variant)
• ValidateDocumentLines(RecordVariant: Variant): Validates all sales document lines for PEPPOL compliance. Checks line-specific requirements for electronic document transmission.
• ValidateDocumentLine(RecordVariant: Variant): Validates an individual sales document line for PEPPOL compliance. Checks unit of measure codes, descriptions, tax categories, and other line-specific requirements.
• ValidateLineTypeAndDescription(RecordVariant: Variant): Boolean: Checks if a line has the required type and description for PEPPOL electronic documents. Validates that the line type and description meet PEPPOL requirements.
• ValidatePostedDocument(RecordVariant: Variant): Validates a posted sales credit memo for PEPPOL compliance. Performs validation checks on the credit memo header and related data.

Ask your agent

Procedure bodies are not stored here (D10). For a procedure body or the calls of one procedure, ask bc-code-atlas (external, by Stefan Maron, MIT; default corpus w1-28), which the bc-observatory plugin connects: bcatlas_resolve_node(object_type: "interface", object_name: "PEPPOL30 Validation"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.