The invoice's id. \nGenerated by Billberry. Not from the ``.\n"}, 'type': {'type': 'string', 'example': 'debit', 'description': "The invoice's type — credit or debit. \nFor example, from the Estonian e-invoice format's `` `` element.\n", 'enum': ['debit', 'credit']}, 'registryCode': {'type': 'string', 'example': '16122596', 'description': "The organization the invoice belongs to. \nMatches either `senderRegistryCode` if it's a sent invoice and `receiverRegistryCode` if it was received.\n"}, 'senderRegistryCode': {'type': 'string', 'example': '16122596', 'description': "The invoice sender/seller's registry code. \nFrom `` ``.\n"}, 'senderName': {'type': 'string', 'example': 'Example Company OÜ', 'nullable': True, 'description': "The invoice sender/seller's name. \nFrom `` `` ``\n"}, 'receiverRegistryCode': {'type': 'string', 'example': '16122596', 'description': "The invoice receiver/buyer's registry code. \nFrom `` ``.\n"}, 'receiverName': {'type': 'string', 'example': 'Example Company OÜ', 'nullable': True, 'description': "The invoice receiver/buyer's name. \nFrom `` `` ``\n"}, 'number': {'type': 'string', 'example': 'INV123', 'description': "The invoice's number as set by the sender. \nFrom `` ``.\n"}, 'date': {'type': 'string', 'format': 'date', 'description': 'The date of the invoice as set by the sender. \nFrom `` ``.\n', 'example': '2020-06-18'}, 'dueDate': {'type': 'string', 'format': 'date', 'nullable': True, 'example': '2020-06-25', 'description': 'The due date of the invoice. \nFrom `` `` ``.\n'}, 'receivedAt': {'type': 'string', 'nullable': True, 'format': 'date-time', 'example': '2020-06-18T13:37:42.666Z', 'description': 'Time when the invoice was received.'}, 'receivedFromOperator': {'nullable': True, 'example': 'billberry', 'description': "The operator who sent the invoice to Billberry.\n\nNote that the operator list may change with time as operators enter and exit the market. A single operator's identifier will remain static however and won't be re-used.\n\nIf you want to show the operator in a human-readable way to your app users, you may want a list of operator brand names, websites etc. Let us know and we'll add an API endpoint for that.\n", 'anyOf': [{'type': 'string', 'enum': ['billberry', 'earveldaja', 'finbite', 'telema', 'unifiedpost', 'peppol']}, {'type': 'string'}]}, 'receivedFileId': {'type': 'string', 'nullable': True, 'deprecated': True, 'example': 'EMK_2021_153500000', 'description': 'The received `` ``. \nAlso set for invoices uploaded to Billberry for sending. May help with tracing invoices if problems occur.\n\nOnly applicable to invoices received in the Estonian e-arve format.\n'}, 'receivedExternalId': {'type': 'string', 'nullable': True, 'example': '2221337', 'description': 'The invoice id from an external operator. \nSome operators, like [E-arveldaja](https://e-arveldaja.rik.ee), assign invoices an id of their own. \nMay help with tracing invoices if problems occur.\n'}, 'sentAt': {'type': 'string', 'nullable': True, 'format': 'date-time', 'example': '2020-06-18T13:37:42.666Z', 'description': 'Time when the invoice was sent.'}, 'sentToOperator': {'nullable': True, 'example': 'billberry', 'anyOf': 'ref_8', 'description': "The operator to whom the invoice was sent to.\n\nNote that the operator list may change with time as operators enter and exit the market. A single operator's identifier will remain static however and won't be re-used.\n\nIf you want to show the operator in a human-readable way to your app users, you may want a list of operator brand names, websites etc. Let us know and we'll add an API endpoint for that.\n"}, 'sentFileId': {'type': 'string', 'nullable': True, 'example': '42', 'description': 'The sent `` `` element. \nGenerated by Billberry and usually identical to the invoice id. \nMay help with tracing invoices if problems occur.\n'}, 'sentExternalId': {'type': 'string', 'nullable': True, 'example': '2221337', 'description': 'The invoice id from an external operator. \nSome operators, like [E-arveldaja](https://e-arveldaja.rik.ee), assign invoices an id of their own. \nMay help with tracing invoices if problems occur.\n'}, 'delivery': {'anyOf': [{'type': 'null'}, {'$ref': '#/components/schemas/InvoiceDeliveryV1'}], 'description': 'For now, present if you just sent the invoice.\n'}, 'fileType': {'nullable': True, 'example': 'application/vnd.billberry.earve+xml; v=1.2', 'description': "The MIME type of the e-invoice file.\n\nNote that the MIME type of the e-invoice files may have metadata attributes not listed here. For example, the Estonian e-arve may include a version — `application/vnd.billberry.earve+xml; v=1.2`. The UBL invoice may include the values of `` and `` to help you identify the customization (e.g. compatibility with EN 16931 or with PEPPOL's BIS 3.0).\n", 'anyOf': [{'type': 'string', 'enum': ['application/vnd.billberry.earve+xml', 'application/vnd.billberry.finvoice+xml', 'application/vnd.billberry.teapps+xml', 'application/vnd.billberry.ubl-invoice+xml', 'application/vnd.billberry.ubl-credit-note+xml']}, {'type': 'string'}]}, 'pdfSize': {'type': 'integer', 'example': 128, 'minimum': 0, 'description': "The size in bytes of the secondary accompanying PDF that one Estonian e-invoice operator (namely [E-arveldaja](https://e-arveldaja.rik.ee)) sends. That is, not via the ``'s `` tag, but through a proprietary channel.\n\nAs of Feb 23, 2023 **Billberry reattaches this externally sent PDF** to the e-invoice as an `` element, making this path redundant. While it is theoretically possible for E-arveldaja to both send an attachment and a secondary PDF, it's unlikely and in our view not worth handling. Most other operators tend not to accept invoices with non-PDF attachments anyways, making them rare.\n\nIf the size is non-zero, you can request the PDF via `/invoices/{invoiceId}.pdf`.\n\nNote that there might still be an attachment in the invoice, which you can get by downloading the original XML from `/invoices/{invoiceId}.xml` and extracting ``.\n"}}} is not valid under any of the given schemas