Map fields to your ERP
It is set up on the ERP step itself, inside the workflow — not on the Integrations page. Ten minutes checking this now saves a long clean-up later.
- A walkthrough video, then why a mapping mistake repeats on every record
- The eight steps, and the three things you can do with each row
- The line-item groups, which are the ones to watch
- When unmapped is fine, and when it is not
01 · Video
Feature walkthrough
02 · Why
Why check what it guessed?
Merchaint guesses the mapping for you, and it is good at the obvious ones — DocNumber to Invoice Number, TxnDate to Invoice Date. But a guess is still a guess, and a mapping mistake repeats on every record that syncs afterwards.
03 · How
Check and fix a mapping
- Open the Pull or Push step. Scroll to
FIELD MAPPINGS. - Wait for Analyzing fields… to finish. You will get a summary like Mapped 8 of 14 fields.
- Read the list. Each row is an accounting-system field, an arrow, and the Merchaint column.
- Press
Editto change anything. - For each row, either send it → column and choose the column, or choose = value and type a fixed value.
- Choose — skip — for fields you do not want.
- Open the line item groups at the bottom and map those too.
- Press
Save Mapping.
04 · Expected result
The summary line reads Mapped n of n fields with nothing important left unmapped, and the line-item groups no longer say 0 of 7.
05 · Troubleshooting and notes
The edit view shows real sample values from your ERP
Next to each field and its type — for example DocNumber STRING inv-123456. That is the fastest way to tell what a cryptic ERP field name actually holds. Use it.
The confidence score is a number next to each row
100 means Merchaint is sure. Lower numbers are worth checking.
Unmapped is not always wrong
Fields like PrivateNote or GlobalTaxCalculation are often fine to skip. Read the unmapped list rather than trying to empty it.
"= value" is useful for constants
Always the same department code, or a fixed account.
Re-analyse after you change the module
Add a column and the mapping does not know about it; press the refresh button next to Edit.
Cancel really cancels
Nothing is saved until you press Save Mapping.
06 · FAQ
Common questions
No. Mapping for a workflow is done here, on the step. The Integrations page has its own mapping, for its own sync configurations — see Checking integration health.
No. They are separate, on separate steps, and they do not have to agree — though usually they should.
It saves this mapping for the scheduled sync configurations in the Integrations area. You do not need it for a workflow — the step’s own mapping is enough. The screen says so too.
The list comes from what your accounting system exposes for that entity type. If something is missing, check you have chosen the right Entity Type.