UpdateRecurringOrderTemplatesAvtaleGiro
Inputs (Array[] UpdateRecurringOrderTemplateAvtaleGiro to update)
Name | Type | Description | Mandatory | Available from version |
---|---|---|---|---|
BrickId | Guid | This is the unique id of the RecurringOrderTemplateAvtaleGiro that should be updated | ||
BusinessDate | DateTime | A date that sends to the bank when the due date is when the bank is suppose to charge money from the TransferReceiver. | ||
SendDate | DateTime | Date for when first time to trigger the Order Template. After it trigger it will add additional months to next SendDate depending which PaymentPeriod is selected. Date when creating a TransferOrder that will be sending a notification to the bank with the BusinessDate as due date when to charge the money from the TransferReceiver. | ||
CashAmount | decimal | Amount in NOK for the order (maximum two decimal places are allowed). | ||
TransferReceiverId | Guid | The TransferReceiver(Admission) for the order | ||
Comment | string | Comment on the order | ||
StatusKey | string | The status on the RecurringOrderTemplate. Can be updated to "Active" or "InActive". The associated TransferReceiver must have an active mandate in order to set the status to "Active". | ||
AllocationProfileId | Guid | The allocation profile for the recurring order template. Note: A recurring order can have either an allocation profile or an instrument, not both. Updating a template with an allocation profile will clear any existing instrument. | ||
InstrumentId | Guid | The instrument for the recurring order template. Note: A recurring order can have either an instrument or an allocation profile, not both. Updating a template with an instrument will clear any existing allocation profile. |
Response rows
Name | Type | Description | Available from version |
---|---|---|---|
Entities | Array | All RecurringOrderTemplateAvtaleGiro in the request is returned along with each RecurringOrderTemplateAvtaleGiros BrickId, and array of Errors per RecurringOrderTemplateAvtaleGiro |
Code examples
XML request example
Content-Type: text/xml; charset=utf-8
<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:tns="http://tempuri.org/" xmlns:s1="http://microsoft.com/wsdl/types/" xmlns:tm="http://microsoft.com/wsdl/mime/textMatching/">
<soap:Body>
<UpdateRecurringOrderTemplatesAvtaleGiro xmlns="http://tempuri.org/">
<req>
<Credentials>
<UserName>{{username}}</UserName>
<Password>{{password}}</Password>
</Credentials>
<identify>{{identify}}</identify>
<Entities>
<UpdateRecurringOrderTemplateAvtaleGiro>
<BrickId>7d7c48f1-413c-4338-9579-000000000000</BrickId>
<CashAmount>999</CashAmount>
<Comment>New Comment</Comment>
<StatusKey>Active</StatusKey>
<BusinessDate>2024-01-01</BusinessDate>
<SendDate>2024-01-01</SendDate>
<InstrumentId>b74d445e-e37e-4553-b242-000000000000</InstrumentId>
</UpdateRecurringOrderTemplateAvtaleGiro>
</Entities>
<Fields>
<CashAmount>true</CashAmount>
<TransferReceiverId>true</TransferReceiverId>
<Comment>true</Comment>
<StatusKey>true</StatusKey>
<BusinessDate>true</BusinessDate>
<SendDate>true</SendDate>
<InstrumentId>true</InstrumentId>
<TransferReceiver>true</TransferReceiver>
</Fields>
</req>
</UpdateRecurringOrderTemplatesAvtaleGiro>
</soap:Body>
</soap:Envelope>
Blog Posts
Related pages
Terms of License
Change Policy
© 2009 - 2024 Huddlestock Technologies AB All rights reserved