Find help with the work that fills your week.

Zeno matches each line to the real names and accounts in the file and flags what needs a decision.

The table shows every line, its coding, and the reason anything is held back. Nothing is written yet.

Take out the posting you are not sure of, a name you do not want created, or a row of a cleanup, and put it back later. The rest of the batch carries on.

Every batch in progress across every client, and whose move it is, without opening a company file.

A batch blocked on names you have not set up yet gets them created together, then re-checked. The same step loads a chart of accounts, a class list or any other list QuickBooks lets you add to, from a spreadsheet.

A chart of accounts, a class list, a season of new customers and jobs, items and terms can be prepared together as one table, where QuickBooks supports adding them. Every name is checked against the file, near-duplicates are called out by name, and parents are created before what refers to them.

Which columns it has, a few sample rows, and which columns read as dates and amounts. Nothing is read in yet.

Say which column is the date, the amount, the payee and the bank, and every row is read for you. A date that could be day-first or month-first is asked about, not guessed. The column choices go on the review page, so a wrong one is caught before anything posts.

Review the new names and transactions from an IIF file before posting. Reversal is available for supported entries, subject to the transaction and the current books.

Your answer is recorded with your name, the time, and your own words, whether you gave it in chat or on the review screen.

Once the link is in front of you, the chat waits for your decision. Approve or reject on the page and it carries on from there. Nobody has to go back and say so.

A batch you refuse shows as rejected instead of sitting there looking untouched, and it cannot be posted until somebody looks again.

Posting is a separate action from preparing. A clean batch is not permission.

Reverse supported entries from a posting run in the same company file. The result says what was removed, already gone or refused; special records have limits.

Every batch this workstation has put into QuickBooks, newest first.

QuickBooks' own result for every entry, including the ones it refused and why.

Trace any transaction back to the batch, the person who approved it, and the document behind it.

From a folder of PDFs, a spreadsheet, or a statement, coded and ready to read.

Charges and credits both, split across accounts, jobs, and classes.

Several accounts, jobs, or classes on one check, without opening the form each time.

It sits against the vendor and comes off the next payment run.

Every open bill and every credit sitting against them, in one list, so a payment run applies the credits instead of missing them.

Picks up the terms discount and any credit on file rather than paying the gross. One vendor or the whole run as a batch, paid by check or by card.

Nothing posts and no balance moves until the goods or the bill arrive.

Stock goes up and the cost sits in a liability. It does not become payable until the bill comes. A day of deliveries against many orders is one batch.

Stops a part-delivered purchase order following you around, without pretending it was billed.

The liability payment, recorded the way QuickBooks expects rather than as a plain check, for one agency or every agency due this period as a batch.

One at a time or the entire monthly billing, prepared together and read once.

The charges gather on each account and one statement covers the period. A whole rent roll is one batch you read once.

No invoice, no open balance, straight to undeposited funds or the bank.

Nothing posts. Each estimate is there to become an invoice when the work is done, and a hundred of them out of the estimating system arrive as one batch.

The order stays open in the invoicing window until it is filled. An order desk export lands as one batch.

Three of the five shipped and the other two are not coming. This is how you say so.

One check settling four invoices, allocated the way you would allocate it.

Held on account for the next invoice, or refunded.

Returns a customer's credit to the card rather than cutting a check, one at a time or the processor's whole refund file as a batch.

Every unpaid invoice, straight out of the company file.

Everything taken in but not yet banked, ready to be grouped onto a deposit.

The receipts that went in on one paying-in slip become one deposit, so the reconciliation matches.

Between operating and payroll, or to the money market and back.

Marks the lines cleared. The reconciliation itself is still yours to finish in QuickBooks.

The lookup you would otherwise do by scrolling a register with a date range guessed at.

Once per bank or card account, naming the QuickBooks account its lines belong in. A bank must go to a bank account and a card to a card account, and moving one that already posts somewhere asks first.

Name each card by its last four digits and give it a default account, so the office manager’s charges arrive suggested to office supplies unless a rule says otherwise.

Every card on each card account, its holder, its default account, and how many of its charges are still waiting.

How many lines still need a decision, per account, without opening anything.

Shows which column was read as the date, the amount and the payee. Check those choices before importing the transactions.

Reads the .qfx, .ofx, .qbo or CSV you downloaded. Lines already imported are recognised, so re-importing a month to pick up its last few days does not double it.

Zeno checks the file for the check or deposit a line might already be, before you post it a second time.

When no single transaction matches a bank line: the ones that add up to it, the other half of a transfer, or a search of the register for the check that cleared late or went in for the wrong amount.

It leaves the queue without posting, and the transaction it matched is recorded beside it.

What the rules already coded, what they suggested, and what still needs you. Sort by oldest first or narrow the list to one card.

Your decisions are recorded against the lines, or a line is linked to what is already in the file. Teach one as a rule and next month it is answered before you look.

A transfer you will enter from the other side, or a line that is not this company. It leaves the queue but is remembered, so the next import does not offer it again.

Review the proposed entries together before posting. Supported entries can be reversed later, subject to the transaction and the current books. The two sides of a transfer become one entry, and a line already in the register is held back rather than posted twice.

One sign-in for the whole practice, shared by every workstation working from the same journal.

You get a link to open in a browser, on any device. Your banking credentials go to the bank and never reach the workstation or us.

See which bank connections stopped working and when, so a disconnected account does not look like a quiet month.

You pay per account, so leave off the savings account nobody codes. Each one you keep is pointed at the QuickBooks account its lines belong in, checked to be the right kind, and moving one later asks first.

New lines stop arriving while it is paused; where the account posts and what is already waiting stay put. Resume it and the relay reads the paused stretch again, so the gap is filled in.

Connect mid-year without doubling the months you already keyed, or reach back as far as the bank allows (up to two years) for books that start earlier. The date can be moved later; nothing already in your queue is doubled.

Straight into the same queue a downloaded statement fills, coded by the same rules. Nothing posts without the usual approval.

What the bank says each account holds, next to the QuickBooks balance for each account on the feed, with the difference explained: transactions not yet in QuickBooks, entries waiting for approval and amounts the feed cannot account for.

The bank login is removed and billing for it stops. Anything already in your queue stays exactly as it is.

Accruals, depreciation, and allocations: the entries that look the same every month.

Quantity or value, against the account you use for shrinkage.

Sites for each yard, van or shop, and transfers that move what exists without touching the P&L. A rebalancing across sites is one batch. Needs QuickBooks Advanced Inventory.

A price level is a percentage off everything or a list of items priced specially, attached to the customers who get it.

A unit-of-measure set with its conversions. Check the ratios first because QuickBooks offers no way to correct one.

A billing rate level for the same service item, attached to the person whose time it is.

Add the currencies a multicurrency file needs and keep their codes right.

Quantity on hand per warehouse, not the total across all locations. This prevents promising a customer stock that is 200 miles away.

The bill of materials every build reads. Changing it shows you which parts would stop being consumed.

Components come off the shelf, finished units go on, one build or a production run as one batch. A build the stock will not cover is refused, or recorded as pending until it is if you ask for that.

The build that could not run for want of stock, completed once the stock is there.

Trips against a vehicle, for the deduction or the client rebill. A mileage log arrives as a spreadsheet and posts as one batch.

Add the truck a trip is logged against, or fix the one that was misspelled.

A to-do with a date, about the customer, vendor or employee it concerns, on the QuickBooks To Do List where the next bookkeeper sees it. Corrected or marked done from here too.

A prospect with its locations and contact people, not a customer until someone converts it in QuickBooks. Read, added and corrected from here.

A class code with its rate per $100 of payroll and the date each rate took effect, and the next rate added when the insurer announces it.

Set up special accounts and items such as Undeposited Funds, Opening Balance Equity, Retained Earnings, received-not-billed and finance charges so QuickBooks uses them for their intended purpose.

Corrects the entry in place rather than deleting it, so an invoice already built from it keeps its link.

Worked time, by employee or subcontractor, one entry or the whole timesheet import as a batch. Billable hours reach the next invoice.

Run from QuickBooks, so the numbers are QuickBooks' own. No menu hunting for the right variant.

QuickBooks opens one file at a time. This does not, so a practice-wide question takes one answer.

Built on your PC, refreshed when you say, so questions never wait on a file being open.

What it holds, when it was last refreshed, and how much older history the file has that it does not, before you rely on an answer from it.

Legal name, address, and fiscal year: the header facts a filing asks for.

Every budget set up in the file for a fiscal year, with the annual figure on each row. Budgets are still written in QuickBooks.

Change supported coding, dates, classes or lines. A cleanup plan can apply a header patch or a line recode across a selection, with live changes checked again before applying.

It stays in the register at zero, which is what an auditor expects to find.

Gone rather than voided. Zeno will say which one you are asking for.

Prepare a header patch, line recode, void or delete against a selection. Supported list records can also be corrected or deleted through a cleanup plan. Review each row and its warnings; snapshots preserve the record, not an automatic undo. Back up the file before destructive cleanup.

Removes a list record nothing references, after a preview, from any list QuickBooks lets go of. Anything with history is refused.

HOME DEPOT, Home Depot, and Home Depot #4 become one name with all the history.

Names, addresses, terms, or the job it hangs under.

Including the 1099 settings you find wrong every January.

The other name lists, which are easy to get wrong and awkward to fix by hand.

A chart tidy-up, with a warning about what it re-labels on reports already printed.

Rename it or move it under a different parent.

Fix the account an item points at and re-code what was already posted through it.

Change the members of a bundle you bill as one line.

Including jobs under an existing customer.

With the 1099 setting done at the point of creation.

For someone the file pays who is neither a customer nor a vendor.

In the right type and under the right parent.

For departments, properties, funds, or however you cut the P&L.

Service, inventory, non-inventory, or the other item types.

One line on the invoice, several items behind it.

The lines that change what an invoice adds up to, including the tax rate and the agency it is owed to. Rates and memberships can be corrected later.

Who the sale is credited to, and the codes that record why something was not taxed.

2% 10 net 30 and the rest.

The small profile lists that reports get grouped by.

Balance, terms, and the jobs beneath it.

What is owed and how they are set up.

The whole chart, or the part of it you are coding against.

To check what you are allowed to code to before you code to it.

With the accounts each item posts to.

Names, status and hire dates, inactive included. The list leaves out social security numbers and pay.

The small lists postings are coded against, with the exact spellings QuickBooks will accept.

See what custom fields the file defines, and write the route number or PO reference onto the record.

The fixed asset list records what was bought, when it was bought, its serial number, and when it was sold so the depreciation schedule stops. It posts nothing.

Define a field and which records carry it. Removing one shows you first how much history goes with it.

Review 1099 box mappings and P&L accounts that no tax line will report before preparing returns from incomplete reports.

Map the account a subcontractor was paid from onto the right box, so their 1099 is not short. Shows you first what would stop being reported.

See each agency and the tax items behind its total, in the same structure used to file a return.

The correction you make this month is the coding it proposes next month. Match on the payee, the memo or an amount range, and code the lines already waiting as well.

See exactly which waiting bank lines it would catch, and how often it would have matched over the last two years. Nothing is saved.

Everything it has been taught for this client.

Changes nothing already posted.

For the line you are unsure about: the rule that covers it, or how the file has coded that payee before.

Why this client splits rent across two classes, and what the owner wants seen separately.

Everything recorded, including what is still waiting on you.

Nothing it worked out on its own is used until you have agreed with it.

For when the client changes how they want it done.

Two years of the books read into notes and coding rules for you to confirm, plus the questions worth asking the client first.

The month-end checklist, with the client-specific parts left as blanks.

This client's, the ones that apply to everybody, and the checks built into Zeno.

The same checklist, with the right accounts and names already in it. The built-in check-up reads the books itself and lists what to raise: stale invoices, Undeposited Funds that never cleared, lines parked in Ask My Accountant.

A draft nobody has read cannot be run.

When the process changes.

The note you would have written on a legal pad, kept with the client.

What was done on this client last month, for the review or the invoice.

Without QuickBooks needing to be open.

Picks up its real name and path rather than asking you to type them.

For the ones on a server or a mapped drive.

And which of them are set up and current.

Removes the name only. The company file is untouched.

A close, a sales tax filing, a review, with how often it comes round and when each period is due.

What runs for each client and how often, and which PCs have been asking for work, so a machine nobody opened stands out.

Attach a procedure you have approved, or the built-in check-up, and each period is prepared for you to review. A draft nobody has read is refused.

No new periods open. Anything still open stays until someone closes it.

Every period that has come due, across every client, with the procedure for each.

Claimed for two hours, so two people sharing the practice never prepare the same batch.

The batches made, nothing to do, or what got in the way, written to the work log. The period stays open until you approve the work.

Once a month is marked done, Zeno refuses anything dated inside it until you reopen it: new plans, direct postings, corrections, voids and reversals. The one exception is a batch already approved before you closed the month, which can still be applied, so plan it again if it should wait. QuickBooks' own closing date is left alone.

Off the list until the date you choose. Nothing is closed or locked.

One code from the console, once per journal. Registered company files become client books on the firm subscription.

Which files are registered, whether posting is entitled, and when that was last confirmed.

The local journal, rules, and history stay exactly as they are.

The whole thing, in order, with the next step always named.

Close it and come back tomorrow without starting again.

Which files are finished, which are waiting, and on what.

One real question answered end to end, proving the whole chain works.

With the reason kept, so you know why when you come back.

Reads your setup, batches, rules, and notes and suggests the useful next thing.

Checks the whole chain and names the first broken link and its fix, instead of you guessing.

Licence, whether writing is switched on, and where the history is kept.

Asked at the moment you ask it, not from a cached answer.

Verifies the download. Running the installer is still your decision.

A roadblock or a request, sent from the chat you hit it in. Your build, machine and licence go with it so nobody has to ask; you see the whole message before it sends.