Skip to content

Set Up ERP Systems for Posting

A system is one ERP connection in one environment. The Post Documents step, a post from a file and every other way of posting (see Post Documents to ERP Systems) send each document to a system, and the system decides how the document is built, checked and sent. Every ERP connection you can see shows up as a system on its own — five SAP connections are five systems, cloud and on-premise side by side — and the same connection in a sandbox and a production environment is two systems, each with its own settings.

You set systems up once per environment. Every project in that environment shares the grid of which entity posts where and each system’s settings. Only Go live is per project.

Open the Posting Register and choose Systems under Settings in the rail. The header has:

  • An environment picker: the environment whose systems are listed.
  • A project picker, starting at No project. Choose a project to see whether each system is Live in it and to go live.
  • Actions, with Go live in this project… (shown to a project architect), Copy to another environment… (shown to a workspace administrator), Suggest which entity posts where… and History of changes.

The page shows two cards: Systems · environment and Which entity posts where. With no ERP connection in the environment, the page says No systems to post to: add a connection to an ERP system in Connections and it appears here.

Each system is one row: its name, its ERP type and a set of pills.

Pill What it says
Cloud A cloud system.
On-premise · agent online An on-premise system whose agent has been in contact within the last five minutes.
On-premise · agent offline since time / On-premise · agent not connected The agent is not online, or no agent serves this environment.
Can post The system can be posted to.
Not checked An on-premise system whose agent is not online.
Live / Simulate Shown only with a project chosen: whether this system posts for real in that project.
Retired The system takes no new postings. Shown in place of Live or Simulate.

A row can also carry two buttons:

  • Reconnect — shown when an on-premise system’s agent is not online. It opens the connection so you can sign in again.
  • Go live › — shown to a project architect, with a project chosen, on a system that is not Retired, can post and is still in Simulate. See Go Live.

Open a row with the toggle at its left. It shows three things and a row of links.

What is left is the checklist of what stands between the system and posting, each item with who does it. An item that is done is ticked and marked done.

Item Who Done when
Service account and its permissions IT Always done for now; nothing to set up.
Agent installed and online (on-premise only) IT The agent is online.
An entity posts to this system Workspace administrator A row of Which Entity Posts Where names this system.
Go live Project architect The system is Live in the chosen project.

What it can do is one line, such as “Takes journals, customer invoices · reverses journals · answers in the call”. It lists the document types the system takes, the ones it can reverse, and whether its answer comes back answers in the call or answers later. The full list for each system is below, under What Each System Can Do.

Copy of its lists shows how old the system’s copy of its accounts, companies and periods is, with Refresh now and View the copy. See The Copy of a System’s Lists.

The links under them are For IT, Settings…, Mark as Retired (or Bring back from Retired) and History, which opens History of Changes for this system alone.

Every setting has a starting value, and most projects never change one.

Setting Where Who changes it Starting value
Which entity posts where Systems, once per environment A workspace administrator No rows. With no rows, the only system that is not Retired listed on Systems takes every entity.
Retired A system’s row A workspace administrator Not retired
Simulate or Live Go live, per system, per project The project’s architect Simulate
Values needed every time A system’s Settings A workspace administrator None
Code matches (including the entity match) A system’s Settings A workspace administrator None
The customer’s own function (SAP on-premise) A system’s Settings A workspace administrator None, or the function a converted step brings
Hold rules Hold rules, per system A register administrator (erp.register.admin) Nothing is held
Hold for a person The step, under More ▸ The step’s builder Nothing is held
Who is told The step, under More ▸ The step’s builder Whoever started the run
Rounding account and limit The step, under More ▸ The step’s builder No rounding
When a posted document comes back changed The step, under More ▸ The step’s builder Ask (the starting value). It goes under Needs attention with two choices.

The four step settings are described with the step on Post Documents to ERP Systems; a step’s hold is described below.

Choose Settings… on an opened row. The dialog, Settings: system, is editable only by a workspace administrator; anyone else sees Only a workspace administrator can change these. Save replaces the system’s whole settings, and each change is recorded in History of Changes.

Values needed every time are values added to every document sent to this system, as Value and Set to pairs. A system reads the ones it needs by name, and a document’s own column of the same meaning wins over the system’s value:

System Value Used for
Sage Intacct gl_journal_id The journal a journal entry posts to, when the document has no journal_type.
Sage 100 bank_code The bank account a payment is drawn on, when the document has no bank_code.

Code matches say where a code here is another code in the system: a Dimension, Our code and Code in the system. Use the dimension entity for an entity whose company in the system has another code, and account for an account. The checks look a code up in the system’s lists through its match, or as written when it has none, and an entity match also lets the grid suggest this system for that entity.

The customer’s own function appears only for SAP on-premise. Name the function for each Document type. Settings names the function only: each function’s field match — which SAP field takes which column — is kept on the system as it is, and a function that a converted SAP posting step brought keeps the field match the step had. See SAP On-Premise.

The second card is the grid of which entity posts to which system, from which date, set once per environment and shared by every project in it. Each row is an entity, →, a system and an optional From (YYYY-MM-DD).

  1. Choose Add a row, type the entity and choose a system from Choose a system. Only systems that are not Retired are offered.
  2. Leave From (YYYY-MM-DD) blank for “from the beginning”, or give the date the entity starts posting to that system. To move an entity to another system mid-year, keep its first row and add a second row for the new system from the date it moves, for example 2026-07-01.
  3. Choose Save. A date that is not in that form is refused with A date reads like 2026-07-01.

Editing the grid needs a workspace administrator; anyone else sees it read-only. An entity already saved can’t be renamed: remove its row with the cross at the end and add another. Entities that documents have named but no row names yet are listed with no system chosen; with none at all, the card says No entities yet. They are the ones found in the tables you post. Add a row to name one.

A document posts through the systems of its project’s environment.

  • Its system is the entity’s latest row whose From date is on or before the document’s posting date (today, when it has none).
  • When the environment’s grid has no rows at all, and only one system that is not Retired is listed on Systems, that system takes every document.
  • A document whose entity no row covers on that date is not posted, and says there is no system for its entity.
  • A document whose row names a Retired system is not posted, and says the system is retired.

For an entity no row names yet, the grid suggests a system when exactly one system in the environment that is not Retired names that entity — through an entity code match or in its own copy of its company list. The row shows Suggested and stays read-only until you choose Accept; only accepted rows are saved.

Suggest which entity posts where… in Actions is Weave’s suggestion from the Data Foundation: with a project chosen, it fills in each entity the project’s Foundation loaded with the connection it loaded it from. Nothing is calculated by a model and nothing is saved: the rows are filled in, a message says how many, and you read each and choose Save. With nothing loaded, it says Nothing to suggest yet.

  • A row whose system is Retired is shown read-only with Retired. Saving the grid keeps it.
  • A row whose system you can’t see is shown read-only with Not in this list. Saving the grid removes it, so Save first asks you to confirm in Save routing.

Nothing posts for real until someone goes live on purpose. Go live is per system and per project: in one project some systems can be Live while others are still in Simulate. A project that is new, copied or trialed starts in Simulate on every system until someone goes live in it.

  1. Choose the project in the header’s project picker.
  2. Choose Go live › on a system’s row, or Go live in this project… in Actions for every system that can post and is not Live yet. Without a project chosen you are told Choose a project to go live in.
  3. The Go live dialog first checks what would change, without changing anything, and shows it:
    • These become Live: the systems that will post for real.
    • The project’s posting mode changes to Live, so every Live system posts for real. — shown when the project itself is not yet in Live mode.
    • Already Live: the systems that already are.
    • system cannot go Live: with the reason: the system is Retired, the project is locked, you don’t have write access to that connection, or it is not a system you can post to.
  4. Choose Go live. It is enabled only when at least one system would become Live.

Going live writes the project’s authorization for those systems in that environment, and sets the project’s posting mode to Live where it was not. Each system that goes live is recorded in History of Changes. Go live is never copied to another environment or project.

Go live needs the project’s architect, on a project that is not locked, with your own write access to each connection. The same check applies through the REST API (POST /erp/go-live) and through the MCP tool erp_go_live, which also refuses a delegated AI token: a person goes live, never an agent acting for one. Both only report what would change unless dry_run is set to false.

Choose Mark as Retired on an opened row and confirm with Retire: the system stops being offered for posting until it is brought back. Its rows in the grid are kept, and documents routed to it are not posted. Bring back from Retired reverses it. Both need a workspace administrator and are recorded in History of Changes.

For IT opens For IT: system, what the product does in this system so it can be allowed and audited:

  • Signs in as — the account the connection signs in with.
  • Batch size — the batch size the system’s settings set, or Not set.
  • Agent and Agent version — for an on-premise system.
  • What we call — each function or service the product calls by name, with when it was last used. For SAP on-premise these are the functions set in Settings. Before anything has been posted or tested, it says Nothing yet. It is listed once this system has been posted to or tested.

When the sign-in has expired, the dialog says so and offers Reconnect.

Set a sandbox up once and copy it to production rather than typing it again. Choose Copy to another environment… in Actions (a workspace administrator only).

  1. Choose the environment under Copy to.
  2. Every system of this environment is listed and ticked when the same connection is a system in the other environment; one that is not is shown as system (not in this environment) and can’t be ticked.
  3. Choose Copy and confirm.

For each ticked system, the copy replaces that system’s settings, code matches and SAP functions in the other environment with these, and adds the rows of the grid that name it and that the other environment lacks (the same entity from the same date). Rows already there are left as they are. The result says how many rows of the grid and how many systems’ settings were copied. Go live is not copied: every project in the other environment stays in Simulate until someone goes live there.

The checks compare documents with the system’s own Accounts, Companies and Periods. PlaidCloud keeps a copy of each, read from the system itself:

  • At the start of every Live run on a Live system, from the system, with up to 60 seconds for the whole read. Only that run’s read can stop a document.
  • On Refresh now, on an opened row. Refreshing contacts your ERP system as posting does, so it needs a workspace administrator and your own write access to that connection. It reports how many accounts, companies and periods it read, and how long the read took. A refreshed copy is for viewing: it does not feed a check.

Each list shows its age on the row — such as “Accounts read 3 hours ago”, “Periods partial, read 2 days ago” or “Companies not read yet” — or that it could not be read and why. A copy that was cut short or came back empty does not replace the one before it.

View the copy opens Copy of the lists, one list at a time (Accounts, Companies or Periods), with Code, Name, Blocked, Status in the system, From and To. It shows up to the first 5,000 rows. Tax codes, customers and suppliers are not copied; they are left to the system.

A Simulate run reads nothing from the system, so in Simulate these checks don’t run and the system decides when you go live.

At the start of a Live run on a Live system, each document is checked against the lists that run read. A check whose list could not be read, came back partial or empty, or did not finish in time is not checked — never passed, never a stop — and the system decides. The run page shows which checks ran on each document.

  • Period open. The document’s period is found by its period code, or else by the periods its posting date falls in. It is stopped only when every period holding it is closed for posting in the system — an adjustment period that overlaps its month keeps the date open. A period whose status the system reports in words PlaidCloud does not know is not checked.
  • The entity is a company. When the company list was read, the document’s entity — through its entity code match if it has one, or else as written — must be one of the system’s companies.
  • The accounts exist. When the account list was read, every line’s account — through its account code match if it has one, or else as written — must be in the system and not blocked for posting. Numeric codes match whatever their leading zeros, so 6100 finds 0000006100.

A stopped document is Not posted with the reason, such as “Line 3: account 6100 is not in system”. Which lists each ERP system offers is in the table below.

Nothing is held until a rule says so. A document a rule holds waits as Needs approval for a person to approve it in Approvals; everything else that passes its checks is sent without one. Choose Hold rules under Settings in the rail.

The list has Name, Applies to, Hold when, Approved by and By. With no rules it says Nothing is held. Anyone with erp.register.view can read the rules; adding, editing and deleting need a register administrator (erp.register.admin), who sees New rule, Edit and Delete in the toolbar. Deleting a rule stops it holding anything new; documents already waiting stay waiting until someone decides. Every change is recorded in History of Changes.

New rule opens New hold rule:

  1. Name the rule, for example “Journals over 250,000”.
  2. Choose the system under Applies to. The systems of every environment you can see are offered.
  3. Tick what holds a document under Hold when. All that are ticked must hold; with nothing ticked, nothing is held.
    • The amount is over a figure, in the entity’s own currency: the document’s size is its debits plus positive local amounts, or its transaction amounts when the table gives no local ones.
    • It was posted from a file.
    • It is a reversal, credit or correction — tick any of the three.
    • It is flagged as unusual — see Flagged as Unusual.
    • Always, for example during close — holds every document on the system; it turns the other conditions off.
  4. Choose who approves under Approved by: The register’s approvers, or Named people — tick the people and, optionally, the entities they approve for, separated by commas (blank is every entity).
  5. Choose Save. It is enabled once the rule has a name, a system, at least one condition, an amount that is a number and, for named people, at least one person.

A held document holds every other document of its set, so a set is approved and posts as one.

An approver needs erp.register.approve and their own grant on the document’s connection. When the rule names people, only those people approve — and only for the entities it lists, if it lists any. Nobody approves a document they sent: neither the person who started the run nor the person whose Post these sent it.

An approval given while the document was sent in Simulate does not count for a Live send: when the same document is later sent Live, it is held again for a new decision.

If your workspace requires separation of duties for postings, a reversal, credit or correction that it covers is also held for a second person, even with no rule.

A Post Documents step can hold more than its systems do, under More ▸ → Hold for a person. Its conditions are The amount is above, It was posted from a file, It is a reversal, credit or correction, It is flagged as unusual and Always, combined the same way; with nothing ticked, nothing more is held. A step’s hold only adds to the system’s rules — it can’t release what a system rule holds — and its documents are approved by the register’s approvers. Named approvers are set on a system rule.

Changing a step’s hold through the REST API (PUT /erp/steps/{step_id}/holds) or the MCP tool erp_hold_upsert needs analyze.step.write and the project’s Architect or Manager role on a project that is not locked.

A document is flagged as unusual when, compared with what its entity posted before:

  • its amount is more than ten times larger or smaller than the last posting of the same reference;
  • it uses an account, customer, supplier or trading partner its entity has not used in its last 500 documents; or
  • its posting date is outside its period.

Each flag records the sentence that says why, such as “The posting date 2026-08-02 is outside the period 2026-07.” The flag is computed from the entity’s earlier documents; no AI model is called. An entity with no earlier documents is never flagged.

Every system below can run in Simulate, which builds and checks each document and sends nothing. A document of a type its system does not take is Not posted; it is not turned into another type.

System Where Takes Reverses Answer Lists for the checks
NetSuite Cloud Journals, customer invoices Journals In the call Accounts, subsidiaries, posting periods
Sage Intacct Cloud Journals, customer invoices Journals In the call Accounts, entities, reporting periods
QuickBooks Cloud Journals, customer invoices, supplier invoices, credit memos Journals, customer invoices In the call Accounts, the company, months closed up to the books’ close date
Xero Cloud Journals, customer invoices, supplier invoices, credit memos Journals, customer invoices In the call Accounts, the organization, months closed up to the lock date
Acumatica Cloud Journals, customer invoices, supplier invoices, payments, credit memos Journals Later Accounts, branches, financial periods
Business Central Cloud Journals Journals In the call Companies, accounts, accounting periods
Dynamics 365 F&O Cloud Journals Journals Later Main accounts, legal entities, fiscal periods
Oracle Fusion Cloud Journals Journals Later Ledgers, account combinations, accounting periods
S/4HANA Cloud Cloud Journals Journals Later Company codes, G/L accounts — no periods, so Period open is not checked
Workday Cloud Journals Journals Later Companies, ledger accounts, fiscal periods
SAP (on-premise) On-premise Journals, customer invoices, supplier invoices, through the customer’s function — Later, from the agent’s report None read; the system decides
Sage 100 On-premise Journals, payments — Later, from the agent None read; the agent checks period and open invoices in a Live run

An answer in the call comes back as the document is sent. An answer later arrives after the send, and the document is Waiting until it does; a document whose answer never settles is Unconfirmed, which you settle from the Posting Register.

SAP on-premise posts through the agent, by calling the customer’s own function for each document type — set under The customer’s own function. A document whose type has no function, or whose function’s field match holds no field for the document’s reference, is Not posted. Converting an existing SAP posting step brings its function and field match to the system, when the system has no function for that document type yet; see Post Documents to ERP Systems.

  • Simulate builds the same request and stops before the agent: nothing reaches SAP.
  • Live hands the documents to the agent serving the system’s environment. The agent writes SAP’s answers to a report in the project’s default document account (under /erp_posting/sap), and each document stays Waiting until that report is read. A project with no default document account can’t post to SAP Live, and its documents are Not posted with that reason.
  • When the agent is offline, nothing is sent: the documents are Not posted, saying the agent was offline, and can be retried once it is back. When the agent does not take the documents within about 18 seconds, they are taken back unsent and Not posted in the same way.
  • A document SAP’s report leaves undecided is Unconfirmed. Settle it from the Posting Register.

Sage 100 is on-premise and has no network API: documents reach it through the agent, which runs Sage’s Business Object Interface.

  • One company per connection. The connection names the Sage company and its currency. A document for another company, or with a line in another currency, is not sent.
  • Journals post as GL journal entries. A journal’s reference is its description in Sage, so it can be at most 30 characters.
  • Payments post as AP manual checks for payments made outside Sage: one supplier per payment, the reference as the check number (at most 7 characters), a bank_code (from the document or the system’s values needed every time), and each line naming the invoice it pays with a positive amount.
  • In a Live run, the agent asks Sage first: a journal dated in a period Sage has closed is stopped, and so is a payment for an invoice Sage does not hold open.
  • After the send, a document is Posted only when Sage’s posted tables show it. A document entered in a Sage batch but not yet updated stays Waiting; a background sweep asks the agent again, at most once an hour, and one still waiting after seven days becomes Unconfirmed.

Every change to a system is recorded with who made it and when: System settings, Retired, SAP function, Code match, Which entity posts where, Hold rule, Go live and List copy (each read of a system’s lists). Choose History of changes under Settings in the rail or in the Actions menu, or History on a system’s row for that system alone. The list has When, By, What, System, Which, From and To.

You see the changes to systems you hold a grant on; a Go live only for projects you can reach, and a step’s hold only in projects you can reach.

Every rule below is checked by the server, the same for the app, the REST API and the MCP tools, unless its row says otherwise.

To You need
See Systems, a system’s settings, the grid and its copy of the lists analyze.connection.read, and only the connections you can see
Change settings, retire a system, save the grid, copy to another environment A workspace administrator
Refresh a system’s lists A workspace administrator on the Systems page, or analyze.connection.read through the REST API and the MCP tool erp_system_lists; either way, your own write access to that connection
Go live The project’s architect on a project that is not locked, with your own write access to each connection; a person, never a delegated AI token
Read hold rules erp.register.view
Add, change or delete a system’s hold rule A register administrator (erp.register.admin)
Change a step’s own hold analyze.step.write, and the project’s Architect or Manager role on a project that is not locked
Approve a held document erp.register.approve and your own grant on the document’s connection; named in the rule when it names people; never your own send