Has anybody successfully created a Customer Payment and applied it to an Invoice with the SuiteTalk REST API? We have been struggling for months on this (our best guess is a busted Beta record?). Any help would be greatly appreciated.

what do your attempts look like

Thanks for the quick reply @battk! The request is:

PUT: https://{redacted}.<http://suitetalk.api.netsuite.com/services/rest/record/v1/customerpayment/eid:edc6916a-d59e-4f58-8eba-7313a526447c|suitetalk.api.netsuite.com/services/rest/record/v1/customerpayment/eid:edc6916a-d59e-4f58-8eba-7313a526447c>

Body:

{
  "account": {
    "id": "217"
  },
  "apply": {
    "items": [
      {
        "amount": 57,
        "applyDate": "2020-11-14T03:58:19.668Z",
        "apply": true,
        "doc": {
          "id": "508405"
        },
        "type": "CustInvc"
      }
    ]
  },
  "createdDate": "2020-11-14T03:58:19.668Z",
  "customer": {
    "id": "51557"
  },
  "memo": "card 4242",
  "payment": 57,
  "tranDate": "2020-11-14T03:58:19.668Z"
}

that doesnt really look like an attempt that could succeed

I'm fairly new to this, would you mind explaining more? What key would need to be matched? I'm making a very similar call via the SOAP api and it's working as expected.

i dont think you can call yourself new to something if you have been doing this for months

In the netsuite world, I think a few months is fairly new! But either way, I'd really appreciate your help if you think you know a solution.

We have tried to follow the documentation as best we can, and from what we can tell, we are following the request as it's expected here: https://system.netsuite.com/help/helpcenter/en_US/APIs/REST_API_Browser/record/v1/2021.1/index.html#/definitions/customerPayment-applyElement

they dont actually document which is the key

😂

ive yet to see a key that is a ns resource object

ok so if we rule that out, the only other options would really be

line

(which we've tried),

type

(which we've tried) or the ref's

i wouldnt go with doing everything at once

just attempted one each, same error

have you tried the invoice transform?

I have not, I'm actually unsure what that is

where did you find the format for the apply list?

from that article? something seems off about the 'items' list but I'm digging around too, I need to be able to accomplish this same thing

It looks like it would make sense if you compare the same working request in SOAP:

<tranCust:applyList>
                    <tranCust:apply>
                        <tranCust:apply>true</tranCust:apply>
                        <tranCust:doc>578479</tranCust:doc>
                        <tranCust:applyDate>2020-12-03T02:50:22.000-08:00</tranCust:applyDate>
                        <tranCust:amount>565.83</tranCust:amount>
                    </tranCust:apply>
                </tranCust:applyList>

no 'items' array in the SOAP

id go for the transform from invoice to customer payment

yeah, very good idea, seeing some info in Answer Id: 91284

its similar, though not in execution, to soap's initialize operation

Gregg, have you tried simplifying as much as possible? maybe closer to

{
  "customer": {
    "id": "51557"
  },
  "memo": "card 4242",
  "payment": 5,
  "apply": {
    "items": [
      {
        "line": 0,
        "amount": 5,
        "apply": true,
        "doc": {
          "id": "508405"
        }
      }
    ]
  }
}

You absolutely can set created dates in NetSuite, we do this frequently with no problems. As far as simplifying the request, yes, we have tried every combination of payloads over the past few months. Item lists work fine in many other record types, just not in Customer Payments for whatever reason.

my testing so far suggests thats it is messed up

I've tried several combinations with the line number included....

so it basically only works when there is one invoice to apply

what do you mean 1 invoice to apply?

if there is only 1 line in the apply sublist

That worked for you?! Can you please share your request body?

the second example you shared

again, customer with only 1 open invoice

oh only 1 open invoice on the customer side, I see

so that there is only 1 line on the apply sublist

the transform doesn't work well for our usecase

what about it doesnt work

we have many thousands of invoices and payments that are frequently updated from a backend service source of truth. We absolutely have to use the

UPSERT

operation with `eid`'s

probably best to live with soap unless you plan on keeping track of which customer payments have been created

unfortunately that's been our plan and what's in production since summer