Manual E-bill 499.41

More documents

Recommendations

Info

12.5 Bill data 12.5.1 yellowbill Invoice (input) yellowbill Invoice is the standard format for structured bill data and describes both the syntax and structure of electronic bills (XML files). The format is based on the swissDIGIN standard (see section 12.5.7). The main elements when sending the XML file are the “Header” and the “Body” (see diagram below). The “Header” contains mainly internal yellowbill system control data. The main contents are defined in the “Body”. Graphical representation of XML yellowbill Invoice • The “Body” consists of the elements “DeliveryInfo”, “Bill”, “Payment- Data”, “BillPresentment” and “Appendix”. • The elements “DeliveryInfo” and “BillPresentment” contain specific key data for the yellowbill system such as the unique number of the biller (BillerID) or control data for bill presentment. • The main bill content is in the “Bill” element. This element in turn is divided – similar to a paper bill – into the elements “Header” (address data of bill recipient and issuer), “LineItems” (bill line items as on a paper bill) and “Summary” (summary per VAT rate). IMPORTANT: For processing unsigned bills, the element “Bill” can be omitted. • The “PaymentData” element contains the ISR data (ISR elements) and the unique bill recipient’s subscriber number for e-bill (EBillAccountID). The “PaymentType” field indicates whether it is a bill (“ESR”), credit (“CREDIT”) or a bill detail for Debit Direct payments (“DD”). The “Instalment” element can be used to define instalments. Manual E-bill Version October 2010 48/64
Combination options for the amount (positive or negative) and the payment method in the “PaymentData” part from yellowbill invoice and the implications for the status shown to the invoice recipient: TotalAmount PaymentType Positive ESR Open Status in e-finance Positive DD For information Positive CREDIT Not possible, displays ➡ error code 17 Positive OTHER For information Negative or zero ESR For information Negative or zero DD For information Negative or zero CREDIT For information Negative or zero OTHER For information The biller can attach any information in the “Appendix”. For instance, the bill detail can be integrated directly into the appendix as a PDF (see section 8.1). The XML data in yellowbill Invoice format must be supplied in the UTF-8 character set (w ww.utf-8.com). The naming convention of the bill data is: _.XML One XML file is generated for each bill/credit note. The maximum file size is 2 MB. The biller must check the contents of the bill data before uploading them. A conformity check against the schema can be performed at any time at the following web page: http:/ /tools.decisionsoft.com/schemaValidate For a detailed description of the yellowbill Invoice schema see the Annex to this document. Manual E-bill Version October 2010 49/64
Page 1 and 2: 499.41 en (pf.ch) 10.2010 PF Manual
Page 3 and 4: Contents 1. Service description 6 1
Page 5 and 6: 12. Data formats 43 12.1 BillerID a
Page 7 and 8: The main purpose of e-bill is the f
Page 9 and 10: The following tax-related points mu
Page 11 and 12: Billers can ask PostFinance to forw
Page 13 and 14: 2. Registration processes for bille
Page 15 and 16: 2.4 Service for delivering data to
Page 17 and 18: 3.3.1 Registering via e-finance The
Page 19 and 20: When the bill recipient calls up th
Page 21 and 22: 4.7 Searching for bills Billers can
Page 23 and 24: 5. PostFinance processes 5.1 Receip
Page 25 and 26: 6. Bill recipient processes 6.1 Pro
Page 27 and 28: 7. Registration and cancellation Bi
Page 29 and 30: 7.3 Registration and cancellation v
Page 31 and 32: 8. Bill presentment module If the b
Page 33 and 34: The error codes below provide an ov
Page 35 and 36: 10. ISR subscription at PostFinance
Page 37 and 38: Channel E-finance online view yello
Page 39 and 40: The following web services are avai
Page 41 and 42: The following folders are used for
Page 43 and 44: 12. Data formats 12.1 BillerID and
Page 45 and 46: 12.2.1 User data Name Description P
Page 47: Comments: • For a registration
Page 51 and 52: 12.5.4 Other input or output format
Page 53 and 54: 13.2 Processes relating to bill pro
Page 55 and 56: 13.2.8 Booking and confirming the p
Page 57 and 58: Annex • Service Level Agreement (
Page 59 and 60: E-bill help desk PostFinance has ta
Page 61 and 62: Example of PDFOnly billing Electron
Page 63 and 64: Abbreviations / Terms Description E

Manual E-bill 499.41

Create successful ePaper yourself

Delete template?

Save as template?