Manual E-bill 499.41

More documents

Recommendations

Info

Parameter Definition userID Unique ID number of the bill recipient, corresponds to the EBillAccountID, numeric, 17 digits familyName Private customer: Last name, alphanumeric, max. 35 digits Business customer: Company name (first part), alphanumeric, max. 30 digits givenName Private customer: First name, alphanumeric, max. 35 digits Business customer: Company name (second part), alphanumeric, max. 90 digits lang 2-digit, alphanumeric language code de = German fr = French it = Italian en = English The following is an example of this type of URL: https:/ /w ww.yourcompany.ch/register.asp?userID=41100000001211282& familyName=Muster&givenName=Max&lang=de The URL is transmitted as base64 encoded. The following is an example: https:/ /w ww.yourcompany.ch/register.asp?userID=NDExMDAwMDAwMDE yMTEyODI=&familyName=TXVzdGVy&givenName=TWF4&lang=ZGU= If the bill recipient is registered to receive digitally signed bills and the biller supplies digitally signed bills, an additional attribute (vat=true) is provided with the URL. The following is an example of this type of URL with the additional attribute vat=true: https:/ /w ww.yourcompany.ch/register.asp?userID=41100000001211282& familyName=Muster&givenName=Max&lang=de&vat=true Manual E-bill Version October 2010 30/64
8. Bill presentment module If the bill presentment module is used (see section 4.3.1) there are two possible options: • The biller creates a PDF file for each bill from the bill detail data and transmits these to PostFinance (see section 8.1). • PostFinance creates a PDF for each submitted bill data using a standard style sheet (see section 8.2). There is always a 1:1 relationship between the bill data and the bill details. To show the same bill detail for several bills, the static bill detail must be used (see section 4.3.4). 8.1 Delivery of bill details by the biller The biller can design the layout of the PDF files as he wishes. In accordance with the security requirements of e-finance, they may not contain any hyperlinks except a secure link (URL in the format https:/ /w ww.yourcompany. ch/...) to a bill enclosure located on the biller’s own platform. Furthermore, no active elements, e. g. Java Script, ActiveX or other links may be contained in them. To ensure optimum performance for the bill recipient, PostFinance recommends that the individual PDF files should not exceed 50 KB. The maximum size is 150 KB in order to avoid transmission problems. PDF files are assigned to the bill data via the BillerID and the TransactionID which together form a unique bill identifier. Thus the naming convention for PDF files is as follows: _.PDF Because PostFinance cannot check whether the details in the bill data correspond to those of the PDF file, it is the biller’s responsibility to ensure the correctness of the PDF file and to adhere to this naming convention. The PDF files may be delivered separately or they may be integrated as a referenced object as a Base64 string with MimeType=x-application/ pdfappendix into the “Appendix” element in the yellowbill invoice. If the PDF files are delivered separately, the order in which they are delivered makes no difference. Ideally, however, all bills and their corresponding PDF files should be delivered on the same day. For further details concerning data delivery, please refer to section 11. 8.2 Generating bill details via PostFinance The bill details in the yellowbill system are created exclusively by means of a standard style sheet. They contain the information required by law (incl. the addresses of the biller and bill recipient, VAT number of the biller, bill items, summary for each VAT set, etc.) but do not include the biller’s logo. It is not possible to make individual adjustments to the style sheet. Manual E-bill Version October 2010 31/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: 7.3 Registration and cancellation v
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 and 48: Comments: • For a registration
Page 49 and 50: Combination options for the amount
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

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?