Skip to main content

Map Columns Without Errors

The last step in `Document Matching` is where Blast Audit writes results back into Excel. Clean column mapping prevents avoidable errors like duplicate outputs, overwritten inputs, or a run that produces nothing. You may still see `Copilot

Written by William Karkegi
Updated over 2 weeks ago

The last step in Document Matching is where Blast Audit writes results back into Excel. Clean column mapping prevents avoidable errors like duplicate outputs, overwritten inputs, or a run that produces nothing. You may still see Copilot Audit in a few older labels.

Who this is for

  • Users finishing a Document Matching setup

  • Anyone seeing mapping errors before a run starts

  • Teams building reusable matching templates

Before you begin

  • Finish step 1 and step 2 in Document Matching

  • Confirm First row includes headers is correct for your selected range

  • Know which columns are inputs and which columns should receive results

How to do it

  1. Open step 3, Finalize your document match.

  2. Review each row under Input Columns.

  3. For every field you want Blast Audit to return, choose a destination under Output Columns or Output to.

  4. Keep output columns separate from your input columns. If needed, add empty columns in Excel first and select them as outputs.

  5. Make sure at least one output column is mapped before you click Run Matching.

  6. If you use headers, confirm the header row really contains column names and not data values.

  7. If a required field should control acceptance, mark it as Required only after the output mapping is already correct.

Expected result

  • Every output goes to a unique destination column

  • Input columns stay untouched

  • Output columns sit where your team expects to review them

  • The selected range leaves enough room to the right for output columns

  • The run starts without validation errors

Avoid this

  • Mapping an output back into the same column as the input. Blast Audit blocks this with Output column cannot be the same as an input column.

  • Reusing the same output column for multiple results. You will see This column is already assigned to another output.

  • Forgetting to map any output at all. You will see Select at least one output column before running.

  • Selecting a range too far to the right in Excel. The add-in can block the run if the worksheet has no room to create the output columns.

  • Treating a data row as the header row, then wondering why the mapping feels misaligned

If it still doesn't work

  • Go back to step 1 and re-check First row includes headers

  • Move your Excel selection left if you run out of output space

  • If you are applying a template and see a header mismatch, read "Save and Reuse Matching Templates"

  • If the error still is not obvious, use "Fix Engine and Mapping Errors"

Practice with sample files

  • Search for Practice Matching with Sample Documents in this collection.

  • Use the attached PDFs and CSVs there to test this workflow before you use live client files.

Read next

  • Run First Document Matching

  • Save and Reuse Matching Templates

  • Use Advanced Matching Options

  • Fix Engine and Mapping Errors

  • Practice Matching with Sample Documents

Did this answer your question?