Resolve import suspense rows before calculating payouts

The import suspense queue keeps row-level import issues visible after the import job finishes. Use it to fix missing mappings, review warnings, and reprocess affected rows without uploading the same file again.

Start Free Try Sample Data

Details

What to know

When an issue appears

Allocora writes suspense issues when an import row or import artifact needs review before a period can be trusted for calculation.

Blockers include missing product mappings, invalid amounts or dates, unsupported currency, template mismatches, unavailable stored files, and plan-limit rows.
Warnings include duplicate external IDs and suspicious amount spikes that should be reviewed before closing a period.
Queue filters include source, import, selected template, status, severity, issue type, period, and search terms.
Revenue Sources shows open suspense counts per source, and calculation readiness links back to the queue when the selected scope has unresolved items.

How reprocessing works

Reprocessing is scoped to the affected row or mapping issue and preserves accepted revenue facts.

For missing product mappings, map or ignore the external identifier first, then reprocess to queue product-mapping backfill for affected revenue rows.
For template or mapping review, use Review import to open the source import history with the affected import selected.
For row issues, Allocora reads the stored import artifact, applies corrected row values entered in the review modal when provided, and checks the source external ID before creating any new revenue row.
If a revenue row with the same source external ID already exists, the issue is marked resolved instead of duplicating revenue.

Audit and readiness

Every terminal action is recorded for later review, and unresolved blockers affect calculation readiness.

Resolve means the issue was reviewed and closed without creating a new revenue row; a resolution note records the decision.
Exclude means the row should not participate in the current import outcome; a resolution note records why.
Reprocessed means Allocora either queued product backfill or created a new immutable revenue row from the stored artifact.
Open blockers prevent the selected source and period from being calculation-ready; open warnings appear as non-blocking readiness warnings.

Reference Tables

Fields and checks

Common suspense issue types

Use this table to choose the next action.

Issue type	Severity	Next action
Missing product mapping	Blocker	Map or ignore the external product identifier, then reprocess.
Invalid amount or date	Blocker	Correct the row values in the reprocess modal or fix the source data/mapping before reprocessing.
Unsupported currency	Blocker	Use rows that match the workspace default currency or split the data into the right workspace.
Template mismatch	Blocker	Review the selected import template and column mapping, then import again when needed.
Duplicate external ID	Warning	Confirm whether the existing accepted revenue row is correct, then resolve or exclude.
Suspicious spike	Warning	Review the row amount and resolve if valid, or exclude and import a correction separately.

Troubleshooting

If this does not work

Reprocess says the product identifier still needs mapping.

Open Products > Mappings, map or ignore the exact external identifier for the same source, then return to Import Suspense and reprocess.

Reprocess says the stored import file is unavailable.

The original artifact cannot be read. Upload a corrected file as a new import or restore the stored artifact before retrying.

A calculation remains not ready after a mapping was fixed.

Return to Import Suspense and reprocess or resolve the open blocker for the selected source and period.

Feedback

Was this page helpful?

Send a note if a step is unclear, missing, or out of date.

Email Support

Apply this in a workspace

Start free, use sample data, then replace examples with your own revenue rows when the workflow is clear.

Start Free Browse Docs