Skip to content

ERP: Post Documents posts the documents in one table to the ERP systems set up in the Posting Register. The step names no system: each document goes to the system its entity is routed to (see Set Up ERP Systems). Every document it sends, holds or stops is recorded in the Posting Register.

Whether anything is sent depends on the run’s posting mode and on the system’s own mode. A document posted in Simulate is checked and recorded as Would post, and nothing is sent to the ERP. The step has no Validate Only setting of its own.

For how to shape the table, run in Simulate and then Live, and work with the run afterward, see Post Documents to ERP Systems.

The General tab has three sections and a More ▸ link.

  • 1 · The table — the Table to post. One row per line; rows with the same entity and doc_number are one document. The documents are frozen when a run starts.
  • 2 · Column matches — how each column of your table was matched to a document field: Matched by name, Matched by an alternative name or You chose this. For a column the step cannot recognize, choose what it is used as.
  • 3 · The first document, as its system will receive it — a preview of the first document, its system and its lines, or the reason it cannot be built yet.

More ▸ opens four settings:

  • Hold for a person — hold a document for approval when The amount is above an amount, It was posted from a file, It is a reversal, credit or correction, It is flagged as unusual, or Always. With nothing ticked, nothing is held here; a hold here only adds to what a system already holds.
  • Who is told — Whoever started the run or A list of people…, alerted when something needs attention.
  • Rounding account and limit — Add a rounding line to an unbalanced document, with its Account and Limit. Unticked, there is no rounding.
  • When a posted document comes back changed — ask (the default: the document goes under Needs attention with two choices), or correct (reverse it and post the new version, for a step that re-runs every period).

A source table that isn’t there, or has no columns or no rows, isn’t an error: the step finishes with a warning and posts nothing.