Control and evidence. Global Office: Sync

Nothing reaches the books without somebody saying so

Every automated route into Global Office: Sync ends at the same place: a screen with the document beside the numbers1, and three answers. Accept it, correct it, or decline it. A document scanned on a phone, a folder of many, a batch sent in by a client on a no-login link: all of them stop there.

A financial field is never filled in by guessing. A line it couldn't read is marked and left blank. A plausible wrong number is worse than an empty box, because nobody checks a box that's already full.
An amount it can't read is refused, not rounded. "About 400", or an empty box, doesn't become 400.
Anything needing a second look says why in words. Not a colored dot you have to learn the meaning of.
A bill is never marked paid by the machine. A payment is recorded as its own expense, so a bill can be part paid, paid two different ways, or taken back. Only a person settles one.
A proposed match is only ever a proposal. Every bank charge matched to a receipt comes with its reason in a sentence, and nothing counts as covered until a person agrees.
Declining is a first-class answer. A document sent in by a client can be declined with a reason the client never sees, and the decision is kept.

The Audit Trail

Your name is on it

Every field the scanner proposed and every one you corrected is kept side by side, for as long as the account exists, with the source document attached. When a client asks how a number got there, or an examiner does, you can show them the whole chain from photograph to ledger.

Every entry says which account made it as well as the IP address. "I do not know who changed that" isn't an answer you should ever have to give a client, and in Global Office: Sync it's not an answer you can be forced into.

The trail can't be edited from anywhere in Sync, including by the person who built it.

An entry can't be altered or removed after the fact, and the database refuses it rather than the app simply not offering a way. That's the difference between a promise and a design.

The Audit Trail on a full screen: a table of 625 changes by name, client, table and the address each was made from, with one row selected and its record open in a panel on the right

That record panel read closely: audit trail record number 5AC8F22F, the expense ledger row 3640 for Marek Home Services edited at 17:17:18 on 09/10/2026 from address 65.187.122.62, and underneath it the payment method marked Changed, with a previous value of Check and changed to Credit Card

And the document stays attached to the record. Photograph to ledger to the entry in your accounting software: one chain, with the picture on the end of it. The photograph isn't a thumbnail that gets thrown away once the fields are read, and it travels out to QuickBooks, Xero or FreshBooks attached to the transaction rather than being left behind in Global Office: Sync.

The part nobody wants to think about

When something goes wrong, your record is never the thing that gets lost

Silence is the fault that costs the most, because a record that quietly went nowhere is one you find out about from an auditor rather than from your app. So every way Global Office: Sync can fail has somewhere for your record to wait.

A document the reader couldn't make sense of is held, not dropped. It goes to the Triage Room and waits there for you to finish it by hand. It's never guessed at, and it never silently disappears.
A scan that can't reach the reader tells you so in words. You get a blank form to fill in yourself and a sentence saying what happened, because a dead signal and a receipt that genuinely had nothing on it must never look the same.
Your photograph is kept on the phone until it lands. Bad coverage isn't your fault and it's not a reason to lose the only copy of a receipt. It waits with the typed record and both go together when there's a signal.
Nothing is filed pointing at a picture that's not there. The picture has to arrive and hand back a real address before the record commits. If it can't, neither is written and the pair stays queued together.
If the books can't be written to, the record is buffered rather than lost. It's put aside outside the database and filed automatically once the books answer again, and it's only cleared from the buffer after the write has actually committed.
It won't fill in a financial field by guessing. A line it couldn't read is marked and left blank. A plausible wrong number is worse than an empty box.

What none of that covers, said here rather than discovered later. If the whole system is down, nothing is running to catch anything, and no product can honestly claim otherwise. What's covered is the far more common case: everything running, and the books briefly unreachable.

The fine print shouldn't be fine print at all

Here's what Global Office: Sync won't do, and why…
up front instead of buried in the terms.

Sync won't file anything without you. It proposes and you approve. There's no setting that turns that off, and there's no plan for one.
Sync isn't an accounting system and doesn't want to be. No general ledger, no trial balance, no financial statements. It feeds the software you already have.
Sync isn't a bank feed. It works from documents, not from transactions. If you connect a bank, it's used for one thing: finding the charges with no paper behind them. It's read only, it never moves money, it never sees your bank password, and it keeps only the last four digits of an account number.
Sync won't email anything that opens your books. Not a link, not an archive. A finished archive waits inside the app for somebody signed in to collect, and deletes itself after three days.
Sync doesn't track how you use it. It keeps no record of which screens you open or what device you use. A sign-in is kept only while it's live, and within an hour of it ending it becomes part of an anonymous daily count. The Audit Trail does record when each change was made and the IP address it came from, because that's its job.
Sync doesn't reach back into QuickBooks and quietly change an entry it already sent. A correction is made once, in the accounting software, by the person whose books they are.
Sync doesn't file taxes and it doesn't give tax advice. It prepares the records a tax preparer needs.
Sync doesn't do payroll and has no employee records. It's built for a business whose helpers are paid as subcontractors.
One client can't be read from another. In Global Office: Sync that rule is enforced by the server rather than by the screen, so it holds even if the screen has a bug in it.
United States only, on purpose. US tax documents, the IRS mileage rate, the categories a US tax return uses, 1099 thresholds. There's no VAT or GST handling.

This isn't the privacy policy. Everything above is a product decision, written here because a buyer shouldn't have to discover it later. What happens to your information is in the privacy policy.

Side by side needs a wide screen: a computer, or a tablet turned sideways. On a phone the same screen shows one half at a time, with a Document tab and a Details tab to switch between the photograph and what was read from it. Back

Sync proposes. The human approves

Nothing reaches the books without somebody saying so

Your name is on it

When something goes wrong, your record is never the thing that gets lost

The fine print shouldn't be fine print at all