Skip to main content
All use cases
ERP + fiscalOperations

Every transaction, written to the right ERP.

The agent writes each money event to the correct ERP per country and entity, currency-converted, fiscal-attached, and counterparty-matched. The accounting team stops keying and starts reviewing.

BeforeManual entry, month-end reconciliation
AfterWritten on settle, zero manual entries
Zero
manual reconciliation entries
Try it in the Sandbox
Zero
Manual entries
Reconciliation happens on settle
Per entity
Right ERP
Omie, Bling or Tiny by country
Fiscal-attached
On every entry
NF-e bound to the transaction (homologation)
Sealed
Every write
Hash-chained to the mandate
What the agent does

One transaction, one ERP entry.

The agent pays the payable, converts the currency, matches the counterparty, writes the entry to the right ERP, attaches the fiscal document, and seals it to the mandate. Nothing gets keyed by hand.

  • Writes to the right ERP per country and entity
  • Currency-converted and counterparty-matched
  • Fiscal document attached to every entry
  • Each write sealed to the mandate that allowed it
Entry · AP-771
ERP · mandate
Agent
Payable AP-771. Paying and writing to Omie.
via codespar_pay · Pix rail
Paid. Entry written, fiscal doc attached.
EntryAP-771
ERPOmie
AmountR$ 3.480,00
Receiptrcpt_EB
Reconciled. No manual entry needed.
paid · written · sealedrcpt_EB01
The pain

The conversation is the easy part.

Every transaction gets keyed into an ERP by hand, then reconciled at month end across countries and entities.

Key each transaction into the ERP

The agent writes the entry on settle

Pick the right entity and country by hand

The agent routes to the correct ERP automatically

Attach the fiscal doc after the fact

The fiscal document is attached to every entry

Reconcile across systems at month end

Each write is a sealed, matched entry

How the agent does it

The ERP writes itself, under a mandate.

The agent pays, converts, matches, and writes each transaction to the right ERP per country and entity, with the fiscal document attached. NF-e runs in homologation; Pix carries the money leg. Every write seals to the mandate.

01
Transaction
Ledger

Money event settles

02
Convert
FX

Currency for the entity

03
Match
Matcher

Counterparty and account

04
Write
Omie / Bling

Entry to the right ERP

05
Attach
codespar_invoice

Fiscal doc, then seal

Fiscal rail
Architecture

On each settled transaction the agent converts currency, matches the counterparty, and writes the entry to the right ERP per country and entity via the Omie, Bling or Tiny connector, with codespar_invoice attaching the fiscal document. Every write is hash-sealed to the mandate.

In code

A few lines. The whole loop.

erp-bridge.ts
const session = await codespar.sessions.create();

// write each transaction to the right ERP, fiscal-attached
const res = await session.execute("codespar_pay", {
  payable: "AP-771",
  erp: "omie", // routed by country and entity
  attachFiscalDoc: true,
});

await session.verificationStatus(res.toolCallId);
Zero · sealedreceipt · rcp_erp-br
Featured tools
codespar_pay

Pays the payable on the local rail, inside the mandate.

codespar_invoice

Attaches the fiscal document to the ERP entry.

Audit ledger

Hash-seals every ERP write to the mandate that allowed it.

See the meta-tool reference

Ship it this afternoon.

Open the sandbox, point a session at your providers, and run the whole loop against real rails in minutes — not the quarter it takes to build it by hand.

Multi-country ERP bridge — CodeSpar | CodeSpar