Struct Invoice 

pub struct Invoice {

    pub customization_id: Identifier,
    pub profile_id: String,
    pub id: Identifier,
    pub issue_date: Date,
    pub due_date: Option<Date>,
    pub invoice_type_code: Code,
    pub note: Option<String>,
    pub tax_point_date: Option<Date>,
    pub document_currency_code: Code,
    pub tax_currency_code: Option<Code>,
    pub accounting_cost: Option<String>,
    pub buyer_reference: Option<String>,
    pub invoice_period: Option<InvoicePeriod>,
    pub order_reference: Option<OrderReference>,
    pub billing_reference: Option<Vec<BillingReference>>,
    pub despatch_document_reference: Option<DespatchDocumentReference>,
    pub receipt_document_reference: Option<ReceiptDocumentReference>,
    pub originator_document_reference: Option<OriginatorDocumentReference>,
    pub contract_document_reference: Option<ContractDocumentReference>,
    pub project_reference: Option<ProjectReference>,
    pub payment_means: Option<Vec<PaymentMeans>>,
    pub payment_terms: Option<PaymentTerms>,
    pub invoice_line: Vec<InvoiceLine>,
}

Peppol Bis Invoice 3.0

Fields

customization_id: Identifier

Specification Identifier An identification of the specification containing the total set of rules regarding semantic content, cardinalities and business rules to which the data contained in the instance document conforms.

profile_id: String

Business Process Type Identifies the business process context in which the transaction appears, to enable the Buyer to process the Invoice in an appropriate way.

id: Identifier

Invoice Number A unique identification of the Invoice. The sequential number required in Article 226(2) of the directive 2006/112/EC [2], to uniquely identify the Invoice within the business context, time-frame, operating systems and records of the Seller. No identification scheme is to be used.

issue_date: Date

Invoice Issue Date The date when the Invoice was issued. Format “YYYY-MM-DD”

due_date: Option<Date>

Payment Due Date The date when the payment is due.Format “YYYY-MM-DD”. In case the Amount due for payment (BT-115) is positive, either the Payment due date (BT-9) or the Payment terms (BT-20) shall be present.

invoice_type_code: Code

Invoice Type Code A code specifying the functional type of the Invoice.

note: Option<String>

Invoice Note A textual note that gives unstructured information that is relevant to the Invoice as a whole.Such as the reason for any correction or assignment note in case the invoice has been factored.

tax_point_date: Option<Date>

Value Added Tax Point Date The date when the VAT becomes accountable for the Seller and for the Buyer in so far as that date can be determined and differs from the date of issue of the invoice, according to the VAT directive.This element is required if the Value added tax point date is different from the Invoice issue date.

document_currency_code: Code

Invoice Currency Code The currency in which all Invoice amounts are given, except for the Total VAT amount in accounting currency. Only one currency shall be used in the Invoice, except for the VAT accounting currency code (BT-6) and the invoice total VAT amount in accounting currency (BT-111).

tax_currency_code: Option<Code>

Vat Accounting Currency Code The currency used for VAT accounting and reporting purposes as accepted or required in the country of the Seller. Shall be used in combination with the Invoice total VAT amount in accounting currency (BT-111), when the VAT accounting currency code differs from the Invoice currency code.

accounting_cost: Option<String>

Buyer Accounting Reference A textual value that specifies where to book the relevant data into the Buyer’s financial accounts.

buyer_reference: Option<String>

Buyer Reference An identifier assigned by the Buyer used for internal routing purposes. An invoice must have buyer reference or purchase order reference (BT-13).

invoice_period: Option<InvoicePeriod>

Delivery Or Invoice Period A group of business terms providing information on the invoice period. Also called delivery period. If the group is used, the invoiceing period start date and/or end date must be used.

order_reference: Option<OrderReference>

Order And Sales Order Reference

billing_reference: Option<Vec<BillingReference>>

Preceding Invoice Reference A group of business terms providing information on one or more preceding Invoices.

despatch_document_reference: Option<DespatchDocumentReference>

Despatch Advice Reference

receipt_document_reference: Option<ReceiptDocumentReference>

Receipt Advice Reference

originator_document_reference: Option<OriginatorDocumentReference>

Tender Or Lot Reference

contract_document_reference: Option<ContractDocumentReference>

Contract Reference

project_reference: Option<ProjectReference>

Project Reference

payment_means: Option<Vec<PaymentMeans>>

Payment Instructions A group of business terms providing information about the payment.

payment_terms: Option<PaymentTerms>

Payment Terms

invoice_line: Vec<InvoiceLine>

Invoice Line A group of business terms providing information on individual Invoice lines.

Trait Implementations

impl Clone for Invoice

fn clone(&self) -> Invoice

Returns a duplicate of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl Debug for Invoice

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl<'de> Deserialize<'de> for Invoice

fn deserialize<__D>(__deserializer: __D) -> Result<Self, __D::Error>

where __D: Deserializer<'de>,

Deserialize this value from the given Serde deserializer.

impl Serialize for Invoice

fn serialize<__S>(&self, __serializer: __S) -> Result<__S::Ok, __S::Error>

where __S: Serializer,

Serialize this value into the given Serde serializer.