Skip to content

Derive a missing consignee without storing or emitting it #59

Description

@jbagsik

Part of

Field fidelity and validation of parsed e-invoices — restoring facts the parser reads but the model cannot hold, and making the readiness figure agree with the conformance verdict.

What to build

Where the document names no consignee, the buyer address stands in for display and validation and is marked as derived. It is not stored and not emitted, so the structured document never asserts a delivery address the readable copy does not show. Only with this in place may the field become required.

Acceptance criteria

  • A missing consignee is derived from the buyer address for display and validation
  • The derived value is visibly marked as derived
  • The derived value is not written to the stored delivery field
  • The delivery group is omitted from the generated artifact when the consignee was derived
  • The delivery address field is raised to required priority

Blocked by

Metadata

Metadata

Assignees

No one assigned

    Labels

    ready-for-agentSpec is ready for an agent to implement

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions