Post B2B Invoice Interface

Push B2B invoice - Once the B2B invoice is generated by the client’s ERP using the Sales order posting, The same invoice needs to be pushed to Omni. The below API can be used to push the B2B invoice to Increff.
URLs -
Prod - http://assure-proxy.increff.com/ajio-vms/b2bInvoice/posting
Staging - http://staging-oltp.increff.com/ajio-vms/b2bInvoice/posting

Headers

authUsername:

authPassword:

Method

POST

Payload

invoiceUrl/invoicePdf - one of the fields is mandatory

{
"invoiceNumber": "9200006652",
"invoiceDate": "2020-10-16T20:22:28.000+05:30",
"forwardPurchaseOrder": "4042640641",

"isPartialInvoice": true,

"invoiceLineEntries": [
{
"channelSkuCode": "460491724004",
"quantity": 1
},

{
"channelSkuCode": "460491724006",
"quantity": 2
},

{
"channelSkuCode": "460491724008",
"quantity": 1
}
],

"qrCode": "String",

"irnNumber": "String",

"invoicePdf": "Base 64 encoded byte stream",
"invoiceURL": "Invoice PDF public URL"
}

Response

Http Status Code: 200 [Success]

Payload Details

Parameter Name	Data Type	Description	Mandatory
invoiceNumber	String	Invoice number on Invoice Document	yes
invoiceDate	ZonedDateTime	Invoice date and time with zone information	yes
forwardPurchaseOrder	String	Purchase Order Number	yes
qrCode	String	QR Code	yes
irnNumber	String	IRN number	yes
isPartialInvoice	Boolean	If ERP has created partial invoice for complete order then it will be true	yes
invoiceLineEntries	List	This is required only in case there can be multiple invoices against one PO.	no
channelSkuCode	String	This will be the SKU code sent during Ajio order posting.	no
quantity	Integer	Sku quantity that is invoiced	no
invoicePdf	String	Base 64 encoded byte stream	Any one of these is mandatory.
invoiceURL	String	Invoice PDF public URL	Any one of these is mandatory.