Fully digitized electronic invoices, referred to as all-electric invoices, refer to: Relying on the trusted identity system and electronic invoice service platform, with the basic characteristics of removing media, removing format, labeling, elementalization, credit granting system, and code assignment system, covering the whole The brand-new invoices of fields, all links, and all elements have the same legal effect as paper invoices.
The era of all-electric invoices has come, do you still fill in manually, copy and paste the invoice title, check the product information, product model, invoiced amount, and then calculate the tax-free amount and tax amount, often tossing for a long time for the difference of 1 cent, for four Integrate five into one and burn out, and finally have to send the successfully issued PDF invoice format file to the consumer. We understand the distress of financial students, because we have experienced it. Now share the realized automatic invoicing and the method of interface invoicing.
The tool for automatic invoicing is shown in the figure below:
The features of the all-electric automatic invoicing tool are as follows:
1) Support multiple sales-side invoicing companies to issue invoices at the same time;
2) Support all types of invoices: all-electric special tickets, all-electric general 3) Automatic invoicing
can be completed without manual intervention;
4) Support API invoicing mode, calling the all-electric invoicing interface API can be integrated into existing systems;
5) Support Aerospace, Baiwang, ukey Simultaneous and parallel invoicing with all electric invoices;
6) Supports merging and splitting, automatic processing of discounts, automatic filling of remarks, automatic write-back, and adjustment of amount difference data.
Docking instructions for the all-electric invoice billing interface
Request URL: fpkj...com/kpgl/fpkj
Request method: POST
interface request header type ContentType: application/x-www-form-urlencoded;charset=UTF-8
Parameter format: DATA
Return parameter format: JSON
request parameter format : token=&data=[base64 of invoice message json]&spid=seller enterprise id
Invoice message json, as follows:
[
{ "XTLSH": "Document No.", "KHMC": "Customer Name", "KHSH": "Tax ID", "KHDZ": "Address", "KHKHYHZH": "Customer Bank account number", "FPZL": "Invoice Type", "BZ": "Remarks", "KPR": "Biller", "SKR": "Payee", "FHR": "Reviewer", " YFPHM": "Hong Chong's original invoice number", "KHYJ": "Customer email", "KHSJ": "Customer mobile phone number", "ITEM":[ { "CPMC": "Product Name 1", "CPXH": "Product Model", "CPDW": "Product Unit", "SL": "Tax Rate", "CPSL": "Quantity",
"BHSJE": "Tax Excluded Amount",
"SE": "Tax Amount",
"FLBM": "Classification Code",
"XSYH": "Tax Rate Preferential",
"LSLBZ": "Zero Tax Rate Mark",
"YHSM" : "Special Offer",
"KCJE": "0"
},
{ "CPMC": "Product Name 2", "CPXH": "Product Model", "CPDW": "Product Unit", "SL": "Tax Rate ", "CPSL": "Quantity", "BHSJE": "Tax Excluded Amount", "SE": "Tax Amount", "FLBM": "Classification Code", "XSYH": "Tax Rate Preference", "LSLBZ": "Zero Tax Rate Mark", "YHSM": "Preference Description" ,
"KCJE": "0"
}
]
}
]
Return parameter message example:
{ "Reulst": "1", "Message": "", "SucessList": [ { "KPJG": "1", "KPRQ": "20230307", "KPFK": "Issue Success", "URL": "/SHKJ/57650286251271074003.pdf", "FPHM": "23442000000019681253", "JQBH": "", "FPDM": "", "SKM": "", "PDFXX": " PDF generated successfully", "XTLSH": "0900883436", "EWM": "01,32, ,23442000000019681253,1200.00,20230307, ,4E73,", "JYM": "57650286251271074003" } ], "ErrList": [ {
"XTLSH": "",
"ErrMsg": ""
}
]
}
Note:
When Result=0, it means that the data must be abnormal or the process is abnormal. At this time, you need to pay attention to the value of Message.
When Result=1, it does not necessarily mean that the invoicing is successful. When the offline invoicing or the tax disk is not online, it may mean that the receipt is successful. If it is batch invoicing, you need to pay attention to the value of ErrList. At this time, it may be partially successful and partially copies were unsuccessful.
The only situation that can determine successful invoicing: SucessList list and the invoice number is not empty,
if Result=1 and the invoice number returned in the SucessList list is empty, you need to obtain the invoicing status by asynchronously obtaining the invoicing result.