Integrations and automation

Review imported automation documents and fix exceptions

Open the imported document detail when automation did not land cleanly and fix the real exception instead of ignoring it.

4 min read · Updated Mar 18, 2026 · Managers and bookkeepers reviewing automation output

Use document review when automation gets close but not all the way there.

The goal is to fix the real issue so the same exception does not keep coming back.

Quick facts

Start here

  • Document exceptions are best handled while the source material is still fresh.
  • Repeated exceptions often point to a missing rule or weak source data.
  • Do not treat exception work as noise. It is how the automation gets better.

Step 1: Open the document and identify the real blocker

  • Use the automation queue to open the document detail view.
  • Decide whether the issue is missing data, wrong mapping, or a rule that needs tightening.
Use the automation queue to isolate the document that failed and decide whether the blocker is data, mapping, or rule logic.

Step 2: Fix the cause and test the result

  • Correct the source, mapping, or rule depending on what failed.
  • Then review the next similar document to confirm the exception is actually gone.
If the same exception keeps returning, tighten the rule or mapping so the next matching document lands cleanly.