RCM & insurance

Stage, dry-run and publish insurance setup imports

Use register templates and row-level reports while preserving draft and activation boundaries.

Current source · source reviewed · 6 min read

Before you begin

RCM import permission.
Correct register template and sanitized source data with its owner.

1. Discover the register and template

Use the import workspace/register catalog to select the supported register and obtain its current template. Availability can depend on deployment features.

2. Stage the upload

Upload the file to create a batch with source provenance. Headers are matched by name and executable spreadsheet content is refused.

3. Inspect the dry run and issue export

Review resolved references, duplicates, unsupported enum values and row/column issues. Use the issues.csv export for remediation without exposing private values publicly.

4. Publish as drafts

After fixing errors, publish the batch through the supported operation. Imported records remain drafts; review, source verification, maker-checker and activation remain separate.

5. Reconcile the result

Compare created drafts with the register snapshot and use the supported rollback capability where permitted. Do not treat rollback as erasing activated or historically used configuration.

Safe spreadsheet handling

Formulas and external links are rejected rather than executed. Preserve original unsupported strings for review instead of coercing them into valid-looking values.

Dependency order

Organizations, roles, agreements, contracts, policies/classes, tariffs and integration rows have dependencies. Resolve prerequisite identifiers before publication.

Troubleshooting

An upload is refused

Read the capped size/row limits or executable-content finding, correct the source file and stage a new reviewed batch.

Source evidence

References are pinned to the private MANSOQ source repository. Repository access is required to open these links.