BIWizz Bridge

It finds your SAGA companies by itself

You do not tell it where to look and you do not type file paths. On first run it reads the SAGA installation on the machine and shows you every company it found, with its name and tax ID, exactly as they appear in SAGA.

• It proposes which SAGA company matches which BIWizz company, by tax ID
• A proposal stays a proposal: you confirm the link once, by hand
• Companies blocked in SAGA, ones in the legacy format, and ones living on another machine are labelled as such rather than hidden

Intelligent syncing, not a blind hourly copy

A SAGA database can be hundreds of megabytes. Copying and sending it again when nothing has changed burns hours of disk and bandwidth — on the same machine you are trying to work on.

• Before anything else, Bridge checks whether the database changed — it reads a few bytes, not the whole file
• It reads the database's own transaction counter rather than the file date: the date moves even when nothing was recorded, the counter does not
• If nothing changed, nothing is copied and nothing is sent. A check costs milliseconds
• When SAGA is open and holding the database locked, Bridge reads a shadow copy of the disk — it never touches SAGA’s files and never attaches to its database

The same with three companies and with three hundred

A practice with hundreds of clients is the normal case, not the exception. Bridge walks every company on every run, but only does real work for the ones that actually changed.

• One shadow copy per volume for the whole run, not one per company
• Companies that are not linked yet cost nothing — there is no point reading a database you have nowhere to put
• The tray shows how many companies were checked, how many were sent, and what is waiting on you

When several accountants share one company

This is where data actually gets lost. SAGA's own advice for working from two places is to back up on one machine and restore on the other — the baton passes from one to the next. That works, as long as it only ever moves one way.

• Bridge records which machine it took the baton from each time, and BIWizz shows you the whole chain
• If two accountants start from the same backup and both carry on, neither copy contains the other. Bridge recognises that and flags it
• It never picks a winner on its own. Picking one means silently discarding somebody’s work — which is exactly what happens when you go by "whoever uploaded last"
• What counts is what was recorded, not the clock on the machine. Clocks in different offices disagree, and a file’s date survives being copied

It updates itself

Updates arrive automatically and are cryptographically signed — Bridge only installs what we signed. Nobody has to walk round the office to move everyone to a new version.

From install to first sync

1. 1

   Install the app on the machine where you keep your books in SAGA.

2. 2

   It shows you an eight-character code. Type it into BIWizz and pick which companies it may sync.

3. 3

   Confirm which SAGA company matches which BIWizz company. Everything after that runs on its own.

Want to see it on your own data?

We will walk you through how a SAGA database gets into BIWizz and what you can do with it afterwards.