🔗 Accounting Bridge

Accounting Bridge connects TSync's Accounting to the software your accountant already uses, so the two stay in sync without anyone re-typing entries. It can send your journal entries out to the external system and bring entries in from it, on a schedule.

It works with three worlds:

  • SAGA C — via an XML drop-folder (and, optionally, read-only from a Firebird .fdb file).
  • 1C Enterprise 8.3+ — via OData (a live web connection) or EnterpriseData XML files.
  • SAF-T D406 — the Romanian ANAF standard file, generated for manual upload to SPV.

Requires the Accounting module. Accounting Bridge reads its entries from TSync Accounting (the general ledger), so that module must be installed. Romanian e-Factura / e-Transport are not handled here — they are left to the RO ANAF module if you have it.

Where to find it

Install the module from Config Center → Module Management. Once active, a Accounting Bridge item appears in the sidebar with these pages:

Page What it's for
Targets The external systems you exchange with (one row per connection).
SAGA C Run and review the SAGA exchange.
1C Run and review the 1C exchange.
SAF-T D406 Generate the ANAF SAF-T file for a period.
Account mappings Match a TSync account code to the code used in the other system.
Partner mappings Match a customer/supplier/employee to the other system's code.
Item mappings Match a product/nomenclature item to the other system's code.
Export log Every run (out and in), with its status and result.

Setting up an exchange

  1. Add a target. On Targets → New, give it a name and pick a driver (see the table below). Fill in what that driver needs — a drop-folder path, or a web address plus a username and password.
  2. Add the mappings. So both sides speak the same language, match your accounts, partners and items to the codes used in the external system. An entry with no mapping falls back to its raw code.
  3. Turn on the direction(s) you want. Enable outbound (send) and/or inbound (receive). From then on the exchange runs automatically with the scheduled task — nothing is sent until you enable it.
  4. Check the Export log. Each run records whether it succeeded, the file it wrote or read, and a short summary. A failure on one target never blocks the others.

Available drivers

Driver System Direction How it connects
SAGA C — XML SAGA C both ways Writes an OUT folder, reads an IN folder
SAGA — SQL (Firebird) SAGA C receive only Reads the .fdb file directly (needs the Firebird driver)
1C OData 1C 8.3+ both ways Live web connection (secure login)
1C EnterpriseData XML 1C both ways Universal XML drop-folder
SAF-T D406 RO ANAF send only Generates an unsigned XML file for manual SPV upload
Custom REST your own both ways A placeholder for a bespoke integration

No double-posting (idempotency)

The bridge is built so a run can be repeated safely:

  • Outbound — each journal batch carries a fixed id; once sent, it is stamped so it is never sent twice.
  • Inbound — each incoming document is matched by its unique id; if it is already in your ledger, it is skipped (or updated, when the external file marks it as a change or a cancellation).
  • Processed drop-folder files are moved to an archive folder automatically when one is configured.

About the SAF-T D406 file

The SAF-T page produces the ANAF D406 XML for a chosen period — the header, the chart of accounts, and every journal entry in range grouped into journals. A few things to know:

  • The file is not digitally signed here — you submit it to SPV manually (or sign it through the RO ANAF module / DUKIntegrator).
  • Opening and closing balances are placeholders; the exact figures come from your accountant's period-close work.

Security

  • Passwords and API tokens for a target are encrypted before they are stored.
  • Drop-folders must live outside the public web folder.
  • 1C OData connects over a secure (TLS) login; certificate checking can be tightened from the target's advanced settings when you are not on a trusted local network.

Who can use it

Access is controlled by role permissions (set under Setup → Roles):

Permission Allows
View See targets and the log.
Configure targets Create targets and mappings.
Send data Run an outbound export.
Import data Run an inbound import.
Administer Delete targets and manage the encryption key.