Consolidated billing error (BudgetOrderError.INVALID_BILLING_ACCOUNT) in the new library

[spatariu]

Hello,

We are migrating the Adwords library from the old library to the new one and we have an issue adding consolidated billing to a managed client. Everything seems the same,
the request objects are identical as data, but differ a bit as structure. I am pasting the request SOAP object made by the new PHP library (the sensitive data is hidden since
this is a public channel):

<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns1="https://adwords.google.com/api/adwords/cm/v201802" xmlns:ns2="https://adwords.google.com/api/adwords/billing/v201802">
SOAP-ENV:Header
ns2:RequestHeader
ns1:clientCustomerIdxxxx</ns1:clientCustomerId>
ns1:developerTokenxxxx</ns1:developerToken>
ns1:userAgentRankingcoach Adwords (AwApi-PHP, googleads-php-lib/33.1.0, PHP/5.5.9-1ubuntu4.22)</ns1:userAgent>
ns1:validateOnlyfalse</ns1:validateOnly>
ns1:partialFailurefalse</ns1:partialFailure>
</ns2:RequestHeader>
</SOAP-ENV:Header>
SOAP-ENV:Body
ns2:mutate
ns2:operations
ns1:operatorADD</ns1:operator>
ns2:operand
ns2:billingAccountIdxxxx</ns2:billingAccountId>
ns2:billingAccountNamexxxx</ns2:billingAccountName>
ns2:poNumberxxxx</ns2:poNumber>
ns2:budgetOrderNamexxxx</ns2:budgetOrderName>
ns2:primaryBillingIdxxxx</ns2:primaryBillingId>
ns2:spendingLimit
ns1:microAmount500000000</ns1:microAmount>
</ns2:spendingLimit>
ns2:startDateTime20180326 202251 Europe/Berlin</ns2:startDateTime>
ns2:endDateTime20200110 000000 Europe/Berlin</ns2:endDateTime>
</ns2:operand>
</ns2:operations>
</ns2:mutate>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>

The response:

Array
(
[status] => error
[msg] => Google\AdsApi\AdWords\v201802\billing\BudgetOrderService Error
[0] => Array
(
[masg] => BudgetOrderError.INVALID_BILLING_ACCOUNT
[field_path] => operations[0].operand
)

)

Could you please give us some ideas what is wrong here?

[fiboknacky]

Hi @spatariu

I believe this would be because of some API version updates, not the client library itself.
Could you please ask the experts on AdWords API forum instead?
Please state your previous API version and current API version you're using.

Best,
Knack

[spatariu]

We tried the same call with the new library on the version v201705 and it doesn't work, but the calls from the old library with v201705 work so I am not sure it's an api version issue.

[fiboknacky]

Could you please attach the SOAP logs for both old and new client library requests to adwordsapiadvisor+thanetpra@google.com?

Thanks.

[spatariu]

Since there are sensitive details (login data) and big amounts of money involved I cannot send you the requests in a more specific format than above. If it helps you I can give you the customerId for tracking at the most. We have a master mcc white labeled by google which manages thousands of accounts.

[fiboknacky]

Hi @spatariu

If you can't provide more details, I'm afraid it's really hard to debug.
The above email is on the google domain and I belong to the official AdWords API support team, so please rest assured that this will be fine.

At the very least, if you're not comfortable sending everything, could you send the request ID instead for both cases instead?

Best,
Knack

[spatariu]

I can provide you the request id that we need to debug '00056853731ba4980a814e0ace0b2aab' from v201802. Thank you!

[fiboknacky]

Could you provide request ID of old lib that you say it works too, please?

[spatariu]

Yes, sorry for the delay, this is the same call from the old library v201705 which works, id: '00056861cdbfe1300ac11ec2230ac0b9'.

Thanks,
Claudiu

[fiboknacky]

Hello Claudiu,

The only apparent difference I can find is the budgetOrderName, which shouldn't be a factor to fail your request.
I'll contact billing team to see what happen.

Best,
Knack

[spatariu]

Hi Knack,

Great, thank you, we only hope that the old library will still work until the billing team comes with a resolution. We are forced to use it until further hints.

Regards,
Claudiu