Rank: Advanced Member
Groups: Registered
Joined: 2/28/2018(UTC) Posts: 67  Location: Pennsylvani mostly Was thanked: 9 time(s) in 9 post(s)
|
paymentTypeId - you're right. That is not coming over. reference - in my test, that was coming over, but I remember fixing that at some point so you might need a newer version receiptNumber - There isn't a receipt number in the DTO for A/R Payments - I think that's from the A/P side Also, our forum wasn't sending out notifications for new posts. This appears to be fixed now. That's why it took us so long to respond. I used BusinessSample to test but had to open up new periods to get it to accept 2025 dates. Here are the various DTOs and response bodies (I've included this so I can refresh my memory on Monday): Code:
{
"companyId": 2147470000,
"customerId": 2147469989,
"date": "2-14-2025",
"paymentTypeId": 2147469999,
"reference": "12346",
"bankAccountId": 2147470000,
"invoices": [
{
"invoiceId": 2147469394,
"amount": 100
}
]
}
Response body:
{
"id": 2147469308,
"batchId": 2147469658,
"companyId": 2147470000,
"customerId": 2147469989,
"date": "02-14-2025",
"paymentTypeId": null,
"reference": "012346",
"bankAccountId": 2147470000,
"amount": 100
}
Result of GET (ARPayment) ID=(2147469308)
{
"id": 2147469308,
"batchId": 2147469658,
"companyId": 2147470000,
"customerId": 2147469989,
"date": "02-14-2025",
"paymentTypeId": null,
"reference": "012346",
"bankAccountId": 2147470000,
"amount": 100
}
|
