A transaction is missing

Applies to: Admins, data owners, and Finance users
Prerequisites: A safe source identifier and the expected refresh period

Problem

A record exists in the approved source but cannot be found in Perslace for the expected period.

Likely causes

• The source and Perslace use different dates or time zones.
• The sync has not completed.
• The source query or connection has an issue.
• Mapping failed.
• The identifier is duplicated or invalid.
• A filter excludes the record.

Checks to perform

1. Verify the record in the source and note a safe identifier.
2. Align the source and Perslace date ranges and time zones.
3. Confirm that the connection is Active and note Last Sync.
4. Inspect Sync History.
5. Clear table filters.
6. Compare the record identifiers with the approved source sample.

Required-field rules remain unverified.

Resolution steps

1. Wait until the configured refresh window has elapsed.
2. Correct an authorised source or mapping issue, if found.
3. Run Manual Sync only with approval.
4. Verify the known record.
5. Verify the total for the complete period.

When to contact support

Contact Support if the source record remains absent after a successful sync with correct filters and mapping, or if repeated syncs fail.

Information to include

• Workspace and source type.
• Safe record ID.
• Source timestamp and time zone.
• Expected period.
• Last successful sync.
• Sanitised page path and error message.
• Sanitised screenshot.

Remove query strings, tokens, and invitation links. Never include credentials.

Last updated: August 2026