Retry and troubleshoot
Find failed submissions, correct their cause, and resume processing.
Search for NTMP Sync Errors to view records whose status is Failed. Read Error Code and Error Message, and inspect the related lines before retrying.
Retry a failed submission
- Identify and correct the cause using the table below.
- Select the failed record and choose Retry. Its header returns to Pending.
- Allow the job to run, or choose Process Now to process the company's pending queue.
- Return to NTMP GL Sync and confirm the result.
Retry All re-queues every Failed record in the company. The current action does not honor page filters or a selected subset. Use individual Retry actions when only some failures are ready to be submitted again.
Common problems
| Message or symptom | What to check |
|---|---|
Please set SERVER_URL on the NTMP Settings page. | Enter the base URL issued by HA Consultancy in NTMP Settings. |
Could not reach the NTMP server at ... | Check the URL, outgoing HttpClient permission, and server availability. Inspect the job queue error and restart it after recovery. |
BAD_RESPONSE or an unexpected server response | Verify the server URL, tenant identifier, and API key. An authentication failure may return text instead of the expected response format. Contact support if the connection values are correct. |
| Unauthorized or a facility credential error | Have HA Consultancy confirm whether the organization API key or the facility credentials need attention. To replace facility credentials, resume onboarding and go back to Facility Credentials. |
| Missing facility credentials | Complete the credentials step for the correct license, then retrieve accounts and complete mapping again. |
| NTMP account was not pulled | Retrieve the facility's chart of accounts before setting the mapping. |
| Inactive or non-LEDGER account | Choose an active NTMP ledger account. For a rejected batch already in the queue, contact support about correcting its saved lines. |
| Posting blocked for an unmapped account | Map every account used together in the transaction, then post again. |
| Unbalanced batch | Contact support with the sync Entry No. and transaction details. |
| Records remain Pending | Check that the NTMP job exists, is not on hold, and has no unresolved error. See job queue administration. |
| No row appears after posting | Confirm the facility is Mapped - Complete, the transaction touches mapped accounts, and it was posted after activation. Older entries are not backfilled automatically. |
What a retry preserves
Retrying preserves the stored account numbers, amounts, document references, ledger identifiers, and submission mode. Updating G/L account mappings or DEFAULT_MODE does not rebuild an existing queued batch.
If the saved batch itself needs correction, contact HA Consultancy with the affected Entry No. Avoid repeatedly retrying unchanged data that NTMP has rejected.
Share useful support details
Include the facility code, sync Entry No., transaction number, mode, error code and message, approximate failure time, and any job queue error. Do not include API keys or facility secrets. See contact support.