Troubleshooting Remote Payment Services

This section provides solutions to commonly troublesome topics related to Remote Payment Services. For more detailed and specific topics, visit our Knowledge Base.

Having trouble with payment numbers in Remote Payment Services?

Mekorma recommends using different number series if there are multiple users. When a user finishes and posts one batch, there may be issues with the number series if they start capturing a second batch before the last batch has been posted. This ultimately requires them to manually update the starting payment number.

If you are having issues with duplicate payment numbers, see Renumbering Payment Numbers.

Receiving an API error when enrolling Remote Payment Services?

If you are receiving errors related to the API while enrolling Remote Payment Services, navigate to Extension Management > Remote Payment Services > Extension Settings (click the app name to open the settings). Verify that Allow HttpClient Requests is turned on.

Having trouble reviewing errors?

To help minimize errors when using Remote Payment Services, enable Data Check in the General Ledger Setup page. This feature activates the Journal Check FactBox, which makes errors and solutions more visible to users.

My remote batches are on the RPS Vendor Ledger Entry Utility List.

The RPS Vendor Ledger Entry Utility List displays vendor ledger entry table information specific to Mekorma Remote Payment Services. This tool helps determine whether an invoice with issues was included in a remote payment batch.

If you’re unsure how to interpret the data on this page or need help resolving an error, please contact Mekorma Support.

My remote batch is stuck in processing.

If a remote batch is stuck, review the details in RPS Batch List. This will show where your batch is getting stuck and why. With assistance from Mekorma Support, batches can be overridden and manually moved along the remote payment process.