
Unlike Bpay, there is no agreement yet between financial institutions surrounding the reversal of mistaken payments using internet banking.
However, the clearing houses are drafting amendments to the Bulk Electronic Clearing System, the self-regulatory framework that governs transactions between 46 banks, buildings societies and credit unions.
Most mistaken payments are resolved without fuss but some are not. At times the unintended recipients refuse to repay their unexpected windfall, spend the money before they can repay it or are simply not aware that they have received funds by mistake.
Ben Slade, a principal with law firm Maurice Blackburn, says under common law there is a legal requirement to return funds received that were not intended for you, although this can be defeated by bankruptcy.
The current protocols dealing with reversal of funds due to mistaken payments differ between financial institutions. Some will return funds automatically while others will not even tell a payer who has received the mistaken payment because they consider it a breach of a customer's privacy.
"If the recipient refuses to allow the institution to disclose their identity their hands are tied," Hamilton says. "In essence [a refund] requires the co-operation of the recipient and they are entitled as a matter of privacy not to have their details disclosed."
The amendments will not be finalised until mid-year but Hamilton says the intention is to standardise the procedures for a recall of mistaken payments. The aim is to amend existing rules "so they oblige participants to follow a structured process for resolving these mistaken payments.
"But we don't want to create a system which allows people to stop a payment made over the internet because they have buyer's remorse."
Slade agrees changing the conditions to give authorisation on this matter to financial institutions is far from straightforward: "The problem is there will always be circumstances where there is a dispute about whether it really was a genuine mistake."
Mistaken payments are also among a number of issues to be investigated in a review of the electronic funds transfer code of conduct. The review is expected to be completed next month.
BILL PAYMENTS
Mistaken payments are also possible through the bill payment system, Bpay, if someone enters the wrong customer reference number or amount. The difference is there are measures in place to address them.
"The most common mistake is where people add an extra zero to the amount they intended to pay," says Andrew Arnott, the general manager of Bpay.
Bpay has an error corrections scheme, which - as long as there has been a genuine mistake - allows a reversal of the funds without the involvement of the payee. "Overpayments and other mistakes will always occur because of human error but a measure of a sophisticated payments system is the ability to rectify them," he says.
How to retrieve funds - or return them
The process for retrieving funds sent to the wrong account begins with you.
Once you have told your bank, it will trace the funds. But that's where the process can hit a snag. At present the recipient has to act to authorise a reversal. They may be legally obliged to do so but what if they don't?
To find out who has your money, says Ben Slade, a principal with law firm Maurice Blackburn, you could make a claim against the bank to give you the details, called an application for preliminary discovery, "but to do so would cost thousands of dollars".
Once you know who has the funds you can make a common-law claim for "money had and received".
"This is such an expensive process that the amount transferred would have to be very large to make it worthwhile," he says.
The Australian Payments Clearing Association's intended changes would oblige financial institutions to reverse the funds in the case of genuine mistakes. Those institutions would then have to make sure that the terms and conditions on deposit accounts explained the institution was authorised to reverse genuine mistaken payments.
"The changes would bind the institutions to comply with the process, not the customer. But once the customer signs off on the terms and conditions they won't have to," says the association's Chris Hamilton.
"It's really a fairness thing. People may think, 'Whacko, the bank has given me money.' But it's usually not the bank's money; it belongs to another customer. With the exception of banks making accounting mistakes, a credit results from a debit somewhere else."
send photos, videos & tip-offs to 0424 SMS SMH (+61 424 767 764), or us.
Did you know you could pay less than $1 a day for a subscription to the Herald? Subscribe today.Ah... ok.  That makes more sense.  I think I still disagree slightly just because I think that if stronger talent shows below academy then academy will start grabbing new players instead of just sitting on old talent (see again 2 already from radiance into academy in like a year or 2).  Hai probably wouldn't have as much sway on an academy team to 'gamble' on newer talent like he does on his own org at radiance.  Higher ups in investing groups and especially from traditional sports backers might just wanna see success and see academy as 'back up lcs players' instead of a talent farm.  Like I wouldn't be surprised if part of the reason you see old players in'retirement home academy' is the org wanting to have a backup... and former lcs player who is below average but not getting better is a safer sub if needed in a pinch than 18 year old solo queue mechanical god hot shot who could be the next Jensen but needs to  time to learn macro, communication, etc.   That lcs vet is more likely to pull a win if he needs to come in for a week due to illness, injury, etc.  So esp if you're a mid tier team that needs every win for playoffs it's a much "smarter" bet to have academy be vets who can sub in if need be, whereas a team who is consistently top (see c9) can gamble and develop someone in academy like they did with blaber a year or 2 ago, knowing that if he does have to come in even if he goes 0-2 in a week playoffs are still fairly secure<filename>azps-3.8.0/Az.CosmosDB/Az.CosmosDB.md
---
Module Name: Az.CosmosDB
Module Guid: 91832aaa-dc11-4583-8239-bce5fd531604
Download Help Link: {{ https://docs.microsoft.com/en-us/powershell/module/az.cosmosdb }}
Help Version: {{ 1.0.0 }}
Locale: en-US
content_git_url: https://github.com/Azure/azure-powershell/blob/master/src/CosmosDB/CosmosDB/help/Az.CosmosDB.md
original_content_git_url: https://github.com/Azure/azure-powershell/blob/master/src/CosmosDB/CosmosDB/help/Az.CosmosDB.md
---

# Az.CosmosDB Module
## Description
The topics in this section document the Azure PowerShell cmdlets for Azure CosmosDB in the Azure Resource Manager (ARM) framework. The cmdlets exist in the Microsoft.Azure.Commands.CosmosDB namespace.

## Az.CosmosDB Cmdlets
### [Get-AzCosmosDBSqlContainer](Get-AzCosmosDBSqlContainer.md)
Gets the CosmosDB Sql Container.

### [Get-AzCosmosDBSqlContainerThroughput](Get-AzCosmosDBSqlContainerThroughput.md)
Gets the throughput settings corresponding to a CosmosDB Sql Container.

### [Get-AzCosmosDBSqlDatabase](Get-AzCosmosDBSqlDatabase.md)
Gets the CosmosDB Sql Database.

### [Get-AzCosmosDBSqlDatabaseThroughput](Get-AzCosmosDBSqlDatabaseThroughput.md)
Gets the throughput settings corresponding to a CosmosDB Sql Database.

### [Get-AzCosmosDBSqlStoredProcedure](Get-AzCosmosDBSqlStoredProcedure.md)
Gets the CosmosDB Sql StoredProcedure.

### [Get-AzCosmosDBSqlTrigger](Get-AzCosmosDBSqlTrigger.md)
Gets the CosmosDB Sql Trigger.

### [Get-AzCosmosDBSqlUserDefinedFunction](Get-AzCosmosDBSqlUserDefinedFunction.md)
Gets the CosmosDB Sql User Defined Function.

### [New-AzCosmosDBSqlConflictResolutionPolicy](New-AzCosmosDBSqlConflictResolutionPolicy.md)
Creates a new CosmosDB Sql ConflictResolutionPolicy object.

### [New-AzCosmosDBSqlIndexingPolicy](New-AzCosmosDBSqlIndexingPolicy.md)
Creates a new CosmosDB Sql IndexingPolicy object.

### [New-AzCosmosDBSqlUniqueKey](New-AzCosmosDBSqlUniqueKey.md)
Creates a new CosmosDB Sql UniqueKey object.

### [New-AzCosmosDBSqlUniqueKeyPolicy](New-AzCosmosDBSqlUniqueKeyPolicy.md)
Creates a new CosmosDB Sql UniqueKeyPolicy object.

### [Remove-AzCosmosDBSqlContainer](Remove-AzCosmosDBSqlContainer.md)
Deletes