Search Results for

    Show / Hide Table of Contents

    Bulk Payments (aka Batch Payments)

    Name Type Path
    GetBatchPayments GET /api/BatchPayment
    Get batch payments with a search filter
    GetBatchPayment GET /api/BatchPayment/{idOrCode}
    Get a batch payment by id or by document number.
    CreateBatchPayment POST /BatchPayment/{idOrCode}/allocations
    Add allocations to the batch payment
    AddBatchPaymentAllocations POST /api/BatchPayment/{idOrCode}/allocations
    Add allocations to the batch payment
    UpdateBatchPayment PATCH /api/BatchPayment/{batchPaymentId}
    Update a batch payment
    ReplaceBatchPaymentAllocations PUT /api/BatchPayment/{idOrCode}/allocations
    Replaces all allocations in the batch payment
    DeleteBatchPaymentAllocation DELETE /api/BatchPayment/{idOrCode}/allocations/{allocationId}
    Delete an allocation in the batch payment

    Further Bulk payment information:

    • Creating
    • Updating
    • Abandoning
    • Submitting
    • Amending
    • Processing
    • Posting
    • Unposting
    • Adding allocations
    • Updating all allocations
    • Removing allocations

    POST /api/batchpayment

    {
    	"bankAccountId": "MITGBP",
    	"description": "API 3",
    	"allocations": [
    		{
    			"docId": "PIN1",
    			"allocAmountCurrency": 100
    		},
    		{
    			"DocId": "PIN2",
    			"AllocAmountCurrency": 200
    		}
    	]
    }
    

    This creates a new Bulk Payment for the specified bank account, allocating the specified invoices and amounts for payment.

    Reference: POST /api/BatchPayment

    Updateable fields of the Bulk payment can be updated by patching:

    PATCH /api/batchpayment/(id)

    {
    	"Description": "API 123",
    	"BankRef": "Payment 123"
    }
    

    Reference: PATCH /api/BatchPayment/(id)

    Bulk payments can be abandoned if they are in a draft state.

    POST /api/batchpayment/{batchPaymentRef}/abandon
    

    Bulk payments can be submitted if they are in a draft state.

    POST /api/batchpayment/{batchPaymentRef}/submit
    

    The submission is an asynchronous process, and a response of 200 OK means it has been queued for processing.

    As the document goes for validation and authorisation, its status will change.

    Bulk payments that are in an approved or processed state can be set back to a draft state for amending.

    POST /api/batchpayment/{batchPaymentRef}/amend
    

    Bulk payments can be processed if they are in an approved state.

    POST /api/batchpayment/{batchPaymentRef}/process
    

    Bulk payments can be posted if they are in an processed state.

    POST /api/batchpayment/{batchPaymentRef}/post
    

    Bulk payments can be unposted if they are in an posted state.

    POST /api/batchpayment/{batchPaymentRef}/unpost
    

    Additional allocations can be added via:

    POST /api/batchpayment/(io)/allocations

    [
    	{
    		"DocId": "PIN3",
    		"AllocAmountCurrency": 300
    	}
    ]
    

    Note: If a previous allocation exists on PIN3, the allocated amount will be updated to 300.

    All allocations can be replaced (discarding any current allocations):

    PUT /api/batchpayment/(batchPaymentId)/allocations

    [
    	{
    		"DocId": "PIN3",
    		"AllocAmountCurrency": 300
    	}
    ]
    

    An allocation can be deleted by its ID:

    DELETE /api/batchpayment/{batchPaymentId}/allocations/{allocationId}


    Updated September 2025

    In this article
    Back to top Generated by DocFX