# Update the status of reimbursement invoices

Debugging Tools

Interface should be called on the server side, not in the front end (Weixin Mini Program, web pages, APP, etc.) directly called, specific reference interface call guide

Invoice bx update invoice status

Reimbursement enterprises and reimbursement service providers can use this interface to lock, unlock and reimburse an invoice. The business implications of each operation and its performance on the client side are as follows:

Locking: The locking operation should be performed when the electronic invoice enters the enterprise's reimbursement process. After the locking operation is performed, the electronic envoice will still exist in the user card package, but it cannot be repeated to submit reimbursement.

Unlocking: When the electronic invoice cannot complete the reimbursement process for various reasons, the unlocking operation should be performed. After the locking operation is performed, the electronic invoice is restored to a state that can be submitted.

Reimbursement: When reimbursement of electronic invoices is completed, the reimbursement operation should be performed using this interface. After performing the reimbursement operation, the electronic invoice is removed from the user's card packet, and the user can view the write-off information of the electronic envelope in the card packet message. Note that reimbursement is irreversible and developers are advised to call it with caution.

# 1. How to call

# HTTPS calls

POST https://api.weixin.qq.com/card/invoice/reimburse/updateinvoicestatus?access_token=ACCESS_TOKEN

# Cloud Calls

• This interface does not support cloud calls

# Third party invocation

• This interface supports Third Party Platform generation business call.

• The permission set to which this interface belongs is: 26

• When a service provider is authorized by one of the permissions set, it can call on behalf of the merchant by using authorizer_access_token , which can be viewed in the third-party call documentation.

# 2. Request parameters

# Query parametersQuery String parameters

# Request BodyRequest Payload

nothing

# 3. Return Parameters

# Response Payload

# 4. Note

There are no special considerations for this interface

# 5. Code examples

Example Requests

{
    "card_id": "pjZ8Yt5crPbAouhFqFf6JFgZv4Lc",
    "encrypt_code": "fbdt/fWy1VitQwhbKtSjNeR3BJyfpeJXfZjjGsdCXiM=",
    "reimburse_status": "INVOICE_REIMBURSE_INIT"
}

Return an example

{
    "errcode": 0,
    "errmsg": "ok"
}

# 6. Error code

The following is a list of error codes for this interface, other error codes can refer to General error codes

# 7. Scope of application