/quickbooks/invoices · Payments → /quickbooks/payments
Organisations that keep their statutory books in QuickBooks Online do not have to re-key
anything: the QuickBooks screens list the invoices and payments Nyumba Zetu has raised, in the shape
QuickBooks expects, and push the ones you select.
QuickBooks is enabled per branch rather than self-serve. The menu entry and both grids only appear
for branches on the QuickBooks subscriber list — ask support to enable it for yours. Everything
below assumes it is already connected.
What syncs, and in which direction
The sync is one-way: Nyumba Zetu → QuickBooks.
Nyumba Zetu stays the system of record for money. QuickBooks holds the accounting mirror, and the
platform keeps a crosswalk of every pushed object — the QuickBooks id plus its sync token — so a
re-sync updates the existing QuickBooks record instead of creating a duplicate.
The Invoices tab
The grid deliberately mirrors QuickBooks’ own invoice import layout, which is why several column headers carry an asterisk — those are the fields QuickBooks treats as required:
Because the layout matches the import template, exporting the grid gives you a file you can load
into QuickBooks manually if you ever need to work offline. See Reports for export
mechanics.
The Payments tab
The same treatment for receipts: each row is a payment recorded here, with its own Synced flag. Sync payments after their invoices — a payment cannot be applied in QuickBooks until the invoice it settles is there.Syncing
1
Filter to what has not synced
Sort or filter on Synced = False. That is the backlog; everything else is already in
QuickBooks.
2
Select the rows
Tick the invoices or payments you want to push. Selection is per grid — invoices and payments
are pushed separately.
3
Run “Sync with QuickBooks”
The bulk action asks for confirmation, then pushes each selected row and marks it synced.
4
Re-read the Synced column
Refresh the grid. Anything still
False did not go through — see below.When a row will not sync
Re-running the sync on an already-synced row is safe: the crosswalk makes it an update, not a
duplicate.
Good practice
- Sync on a rhythm — end of day or end of week — rather than ad hoc. A predictable backlog is easier to read than a grid where nobody knows what was last pushed.
- Reconcile monthly. Compare the financial statements here against the equivalent QuickBooks report before you close the period. They should agree to the cent; a gap means something failed to sync and nobody looked.
- Fix data here, not there. Correcting the invoice in Nyumba Zetu and re-syncing keeps both sides consistent. Editing the copy in QuickBooks leaves the platform believing the wrong figure is filed.
- Do not use QuickBooks as the arrears source. Balances, allocations and collections all read the platform ledger — see Invoices and payments.