Error during the push payment to Sage 300. The payment type is 'Receipt'.

Hello Team,

I try to push a payment with the 'Receipt' status.
But I receive an error message: "value": "The request parameters are invalid. Fail to save value to (Applied Receipts/Adjustments) for fields (Customer Number, Document Number, Payment Number, Cust. Receipt Amount) with values (SAGE 300 T1,  104 BATCH, 1, 822.8)"

Could you help me what is the reason for the issue?

Here an example of the request:

{
"BatchRecordType": "CA",
"BatchNumber": 74,
"BatchDate": "2021-07-09T00:00:00Z",
"Description": "receipt",
"BankCode": "CCB",
"DefaultBankCurrency": "CAD",
"ReceiptsAdjustments": [
{
"BatchType": "CA",
"BatchNumber": 74,
"EntryNumber": 1,
"CustomerNumber": "SAGE 300 T1",
"ReceiptDateAdjustmentDate": "2021-07-09T00:00:00Z",
"EntryDescription": "1",
"EntryReference": "",
"BankReceiptAmount": 33,
"CustomerReceiptAmount": 33,
"ReceiptTransactionType": "Receipt",
"PaymentType": "Check",
"AppliedReceiptsAdjustments": [
{
"BatchType": "CA",
"BatchNumber": 74,
"EntryNumber": 1,
"LineNumber": 20,
"CustomerNumber": "SAGE 300 T1",
"DocumentNumber": "74-INVOICE",
"PaymentNumber": 1,
"CustomerReceiptAmount": 33,
"ReceiptTransactionType": "Receipt",
"UpdateOperation": "Unspecified"
}
],
"UpdateOperation": "Unspecified"
}
],
"UpdateOperation": "Unspecified"
}

*********************************

Parents
  • 0

    Hi there,

    Thanks for sharing these details — it's always valuable to see real-world examples of integration behavior like this. While this post is a few years old, we’re still seeing interest in Sage 300 integration and payment API workflows, especially around push payment types like "RECEIPT."

    Loudspeaker If anyone in the community has come across this error more recently or found a resolution/workaround, please feel free to share your insight below. Contributions like these help strengthen our knowledge base and support other users facing similar issues.

    Thanks again for starting this discussion!

    —Erzsi

Reply
  • 0

    Hi there,

    Thanks for sharing these details — it's always valuable to see real-world examples of integration behavior like this. While this post is a few years old, we’re still seeing interest in Sage 300 integration and payment API workflows, especially around push payment types like "RECEIPT."

    Loudspeaker If anyone in the community has come across this error more recently or found a resolution/workaround, please feel free to share your insight below. Contributions like these help strengthen our knowledge base and support other users facing similar issues.

    Thanks again for starting this discussion!

    —Erzsi

Children