[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"detail-sidebar-cat-1-en-105":3,"doc-seo-236159-105":53,"doc-detail-236159-en":126},{"code":4,"msg":5,"data":6},0,"success",[7,14,19,24,29,34,39,44,49],{"id":8,"doc_module":9,"doc_module_name":10,"category_name":11,"show_sort_weight":12,"slug":13},11,1,"Template","Presentations",90,"presentations",{"id":15,"doc_module":9,"doc_module_name":10,"category_name":16,"show_sort_weight":17,"slug":18},12,"Resumes",80,"resumes",{"id":20,"doc_module":9,"doc_module_name":10,"category_name":21,"show_sort_weight":22,"slug":23},14,"Invoices",70,"invoices",{"id":25,"doc_module":9,"doc_module_name":10,"category_name":26,"show_sort_weight":27,"slug":28},15,"Posters",60,"posters",{"id":30,"doc_module":9,"doc_module_name":10,"category_name":31,"show_sort_weight":32,"slug":33},16,"Social Media",50,"social-media",{"id":35,"doc_module":9,"doc_module_name":10,"category_name":36,"show_sort_weight":37,"slug":38},17,"Forms",40,"forms",{"id":40,"doc_module":9,"doc_module_name":10,"category_name":41,"show_sort_weight":42,"slug":43},18,"Letters",30,"letters",{"id":45,"doc_module":9,"doc_module_name":10,"category_name":46,"show_sort_weight":47,"slug":48},21,"Paper Templates",5,"papers-templates",{"id":50,"doc_module":9,"doc_module_name":10,"category_name":51,"show_sort_weight":4,"slug":52},158,"General","general-158",{"code":4,"msg":54,"data":55},"ok",{"site_id":56,"language":57,"slug":58,"title":59,"keywords":60,"description":61,"schema_data":62,"social_meta":119,"head_meta":121,"extra_data":123,"updated_unix":125},105,"en","phoenix-pharma-zugferd-incoming-invoice-implementation-supplement-version-12","Phoenix Pharma ZUGFeRD - Incoming invoice implementation supplement - Version 1.2","","Implementation supplement for incoming invoices under the ZUGFeRD standard, specifying Phoenix Pharma’s required use of an extended profile only. Defines mandatory and conditional field behaviors for issuer, buyer, seller and payment term structures, including supported date format rules, GlobalID schemeID mappings (BGA/GLN, BFA/UID), and item identification using GTIN or PZN with strict scheme codes. Covers coded allowance/charge constraints, credit note negative quantities/amounts, mandatory payment terms, and includes relevant code lists and example file references.",{"@graph":63,"@context":118},[64,80,101],{"@type":65,"itemListElement":66},"BreadcrumbList",[67,71,74,77],{"item":68,"name":69,"@type":70,"position":9},"https://docshare.wps.com","Home","ListItem",{"item":72,"name":10,"@type":70,"position":73},"https://docshare.wps.com/template/",2,{"item":75,"name":21,"@type":70,"position":76},"https://docshare.wps.com/template/invoices/",3,{"item":78,"name":59,"@type":70,"position":79},"https://docshare.wps.com/template/phoenix-pharma-zugferd-incoming-invoice-implementation-supplement-version-12/236159/",4,{"url":78,"name":59,"@type":81,"image":82,"author":87,"headline":59,"publisher":90,"fileFormat":93,"inLanguage":57,"description":61,"dateModified":94,"datePublished":95,"encodingFormat":93,"isAccessibleForFree":96,"interactionStatistic":97},"DigitalDocument",{"url":83,"@type":84,"width":85,"height":86},"https://docshare.wps.com/thumbnails/phoenix-pharma-zugferd-incoming-invoice-implementation-supplement-version-12/236159.png","ImageObject",442,249,{"name":88,"@type":89},"Sarah ","Person",{"url":68,"name":91,"@type":92},"DocShare","Organization","application/pdf","2026-10-16","2026-09-11",true,{"@type":98,"interactionType":99,"userInteractionCount":79},"InteractionCounter",{"@type":100},"ViewAction",{"@type":102,"mainEntity":103},"FAQPage",[104,110,114],{"name":105,"@type":106,"acceptedAnswer":107},"Which ZUGFeRD profile is supported by Phoenix Pharma for incoming invoices?","Question",{"text":108,"@type":109},"Only the extended profile is supported. Fields not described in this supplement must follow the official ZUGFeRD guideline.","Answer",{"name":111,"@type":106,"acceptedAnswer":112},"What date formats are allowed for date-type fields?",{"text":113,"@type":109},"The only supported format where an attribute format is specified is format 102 (CCYYMMDD). Otherwise, date fields without the format attribute must use CCYY-MM-DD.",{"name":115,"@type":106,"acceptedAnswer":116},"How should buyer and seller identifiers be represented using GlobalID and schemeID?",{"text":117,"@type":109},"For the buyer, schemeID should be BGA when using a BGA number, or 0088 when using a GLN; GlobalID must match the schemeID. For the seller, schemeID should be BFA for a BFA number, or UID when using USt-IdNr; GlobalID must correspond to the chosen schemeID.","https://schema.org",{"og:url":78,"og:type":120,"og:title":59,"og:site_name":91,"og:description":61},"article",{"robots":122,"canonical":78},"index,follow",{"doc_id":124,"site_id":56},236159,1789103351,{"code":4,"msg":5,"data":127},{"doc_id":124,"user_id":128,"nickname":88,"user_avatar":129,"doc_module":9,"category_id":20,"category_name":21,"doc_title":59,"doc_description":61,"doc_content":130,"file_id":131,"file_url":132,"file_type":133,"file_size":134,"view_count":79,"is_deleted":4,"is_public":9,"is_downloadable":9,"audit_status":9,"page_count":79,"language":135,"language_code":57,"site_id":56,"html_lang":57,"table_of_contents":136,"faqs":137,"seo_title":138,"seo_description":61,"update_tm":125,"read_time":73},962085320529,"https://ap-avatar.wpscdn.com/davatar_9964176cb1d06d4a9deccf72a44ae3dc","Phoenix Pharma  \nZUGFeRD  \nIncoming invoice implementation supplement to official ZUGFeRD guideline  \nVersion: 1.2  \nIssue date: 12.08.2020  \nAuthor: COMARCH EDI  \n1. Fields used by Phoenix Pharma  \nFollowing table contains a list of fields that are used in non-standard way for incoming invoices in ZUGFeRD v1 .0 format. Invoice issuer should follow the standard ZUGFeRD guideline for fields not described in this document. Only extended profile of ZUGFeRD is supported.  \n\n| Element path | Usage requirement | Remarks |\n| --- | --- | --- |\n| CrossIndustryDocument +SpecifiedExchangedDocumentContext ++GuidelineSpecifiedDocumentContextParameter | R | Only extended profile is supported.\u003Cbr>urn:ferd:CrossIndustryDocument:invoice:1p0: extended |\n| CrossIndustryDocument +SpecifiedExchangedDocumentContext ++BusinessProcessSpecifiedDocumentContext Parameter\u003Cbr>+++ID | R | 380 = INVOICE\u003Cbr>381 = CREDIT NOTE |\n| CrossIndustryDocument +SpecifiedSupplyChainTradeTransaction ++ApplicableSupplyChainTradeAgreement +++SellerTradeParty\u003Cbr>++++ID | R | For direct suppliers (eg. suppliers which selling products to Phoenix Pharma) -BFA code.\u003Cbr>For indirect/cost suppliers (eg. suppliers which provides services to Phoenix Pharma) -USt-IdNr |\n| CrossIndustryDocument +SpecifiedSupplyChainTradeTransaction ++ApplicableSupplyChainTradeAgreement +++BuyerTradeParty\u003Cbr>++++ID | R | For direct suppliers (eg. suppliers which selling products to Phoenix Pharma) -\"76539419\"\u003Cbr>For indirect/cost suppliers (eg. suppliers which provides services to Phoenix Pharma) - \"9991032040045\" |\n| CrossIndustryDocument\u003Cbr>+HeaderExchangedDocument\u003Cbr>++IssueDateTime\u003Cbr>+++DateTimeString\u003Cbr>@format = \"102\" | R | The only supported date format is 102 – CCYYMMDD.\u003Cbr>This rule applies to all date-type fields where attribute format can be specified. Date fields without “format” attribute should contain date in CCYY-MM-DD format. |\n| CrossIndustryDocument +SpecifiedSupplyChainTradeTransaction ++ApplicableSupplyChainTradeAgreement +++BuyerTradeParty\u003Cbr>++++GlobalID\u003Cbr>@attribute schemeID | R | If buyer is identified by BGA number, schemeID should contain “BGA”.\u003Cbr>If buyer is identified by GLN, schemeID should contain “0088”.\u003Cbr>The value in GlobalID should correspond to schemeID value. |\n| CrossIndustryDocument +SpecifiedSupplyChainTradeTransaction ++ApplicableSupplyChainTradeAgreement +++SellerTradeParty\u003Cbr>++++GlobalID\u003Cbr>@attribute schemeID | R | If supplier is identified by BFA number, schemeID should contain “BFA”. If supplier is identified by USt-IdNr then “UID” should be used in schemeID.\u003Cbr>The value in GlobalID should correspond to schemeID value. |\n| CrossIndustryDocument\u003Cbr>+SupplyChainTradeTransaction | C1 | The only codes that are possible to use are: DAY = day |\n\n\n| ++ApplicableHeaderTradeSettlement +++SpecifiedTradePaymentTerms ++++ApplicableTradePaymentDiscountTerms +++++BasisPeriodMeasure\u003Cbr>@unitCode |  | WEE = week.\u003Cbr>Additionally, only one ApplicableTradePaymentDiscountTerms should be used per\u003Cbr>SpecifiedTradePaymentTerms. |\n| --- | --- | --- |\n| CrossIndustryDocument\u003Cbr>+SupplyChainTradeTransaction ++ApplicableHeaderTradeSettlement +++SpecifiedTradePaymentTerms ++++ApplicableTradePaymentPenaltyTerms +++++BasisPeriodMeasure\u003Cbr>@unitCode | C1 | The only codes that are possible to use are: DAY = day\u003Cbr>WEE = week\u003Cbr>Additionally, only one ApplicableTradePaymentPenaltyTerms should be used per\u003Cbr>SpecifiedTradePaymentTerms. |\n| rsm:CrossIndustryDocument\u003Cbr>+rsm:SpecifiedSupplyChainTradeTransaction ++ram:IncludedSupplyChainTradeLineItem +++ram:SpecifiedTradeProduct\u003Cbr>++++ram:GlobalID | R | Item should be identified with GTIN or PZN Number (Pharmazentralnummer) .\u003Cbr>Scheme ID:\u003Cbr>0088 = EAN\u003Cbr>MF = Pharmazentralnummer |\n\nTo specify allowance/surcharge it is necessary to use coded information, free text-information is not supported.  \nCredit notes should contain negative quantity and monetary amounts.  \n1) It is necessary to state at least 1 payment terms.  \n2. Code list","cbCaigs5ghA8DdSd","https://ap.wps.com/l/cbCaigs5ghA8DdSd","pdf",207462,"English","# 1. Fields used by Phoenix Pharma\n## Extended profile support and mandatory parameters\n## Date and GlobalID schemeID rules\n## Payment terms: discount and penalty basis units\n## Line item product identification (GTIN/PZN)\n## Allowance/surcharge and credit note requirements\n# 2. Code lists\n## Business process context codes\n## Document type codes\n## Referenced document code list\n## Allowance/charge reason code list\n## Period unit of measure codes\n## Item global ID scheme ID codes\n# 3. Example files","[{\"question\":\"Which ZUGFeRD profile is supported by Phoenix Pharma for incoming invoices?\",\"answer\":\"Only the extended profile is supported. Fields not described in this supplement must follow the official ZUGFeRD guideline.\"},{\"question\":\"What date formats are allowed for date-type fields?\",\"answer\":\"The only supported format where an attribute format is specified is format 102 (CCYYMMDD). Otherwise, date fields without the format attribute must use CCYY-MM-DD.\"},{\"question\":\"How should buyer and seller identifiers be represented using GlobalID and schemeID?\",\"answer\":\"For the buyer, schemeID should be BGA when using a BGA number, or 0088 when using a GLN; GlobalID must match the schemeID. For the seller, schemeID should be BFA for a BFA number, or UID when using USt-IdNr; GlobalID must correspond to the chosen schemeID.\"}]","Phoenix Pharma ZUGFeRD - Incoming invoice implementation supplement - Version 1.2 | PDF"]