merchaint · help
Contact supportOpen Merchaint

Push records to your ERP

Workspace admin3 min readUpdated 3 Sep 2026
In this article

An invoice arrives, gets read, gets matched, gets approved — and then somebody has to key it into the accounting system. This step is that somebody.

  • A walkthrough video, then three triggers that make a safe push
  • The six steps, and the three data sources
  • Why line items are never mapped for you, and what that breaks
  • How to test with one record before widening

01 · Video

Feature walkthrough

Video · pushing an approved invoice · 2:30

02 · Why

Why do we have this?

This is the end of the line. An invoice arrives, gets read, gets matched, gets approved — and then somebody has to key it into the accounting system. This step is that somebody.

03 · Use cases

Use case 1
Push once approved

Trigger on On Approval Resolved, so only approved invoices go.

Use case 2
Push when a match succeeds

Trigger on On Match Status Changed, to → Matched.

Use case 3
Push on a schedule

Everything that is ready, once a night.

04 · How

Build a Push

  1. Create a workflow with a trigger that only fires on records that should really go. An approval or a match status is safer than "record updated".
  2. Press ADD STEP and choose Push to ERP.
  3. Choose the Connection and the Entity Type.
  4. Choose the Data Source: Trigger Data (the record that started this), Previous Node Output, or Custom Module.
  5. Choose the Source Module.
  6. Open FIELD MAPPINGS and check every field, including the line items. See Map fields to your ERP.

05 · Expected result

The record appears in your accounting system as the entity type you chose. The record in Merchaint shows its sync status, which you can check from the module grid.

06 · Troubleshooting and notes

Fields marked with an asterisk are required by the accounting system

Not by Merchaint. Leave one of those unmapped and the push will be refused.

Choose a careful trigger

"Record Updated" will push the same invoice every time anyone touches it. Approval or match status is usually what you actually mean.

Use "Only run once per record"

On the push step, so a record cannot be sent twice.

Test with one record

Add a trigger condition that matches a single invoice, run it, and go and look in your accounting system before widening it.

07 · FAQ

Common questions

What if the supplier does not exist in the ERP?

The push is held or fails, because it cannot resolve the reference. Pull your suppliers in first so both sides agree on who is who — see Pull records from your ERP.

Does pushing create a duplicate if I push twice?

Merchaint tracks what it has already sent and updates rather than duplicating. Even so, use "Only run once per record".

Can I push several records at once?

Point the step at a Custom Module rather than the trigger record.

Where do I see whether it worked?

The record's sync status in the module grid, and the run in the workflow's logs.