What XARA does, and what stays yours
XARA does a client’s whole month, up to the pack. Signing off, sending, paying and a handful of other decisions stay with your firm and your client, and XARA’s code enforces that.
XARA does a client’s whole month, from coding the first transaction to building the pack your client reads. The calls that belong to people stay with people. That split is written into its code, so it’s the same on every client, every day.
XARA
The month’s bookkeeping
- Codes or matches every bank and card line
- Enters and codes every bill
- Reads statements, checks and receipts
- Reconciles each account to $0.00
- Posts month-end entries and accruals
- Prepares the financials
- Files the reports and updates Karbon
- Drafts the questions for your client
Your firm
The calls only you can make
- Answers the few questions XARA asks
- Sends what goes to a client or vendor
- Gives the word on an earlier month
- Decides who has access
Your client
Its own money
- Releases every payment in BILL
- Approves the bills it pays
The work is XARA’s
XARA works in QuickBooks, Xero, BILL and the rest of your firm’s software on the same screens a bookkeeper uses, under its own login, and keeps working on a month for as many days as it takes, through the bookkeeping, month-end entries, balance sheet checks and the pack. Nobody at your firm operates it or fills in a form. It logs each change before making it and reads it back afterwards, so a line is posted once and a bill is entered once.
The calls that stay with people
| The call | Who makes it |
|---|---|
| Signing off a client’s month | Your preparer, reviewer and second reviewer, one after another. |
| Posting month-end entries | Your preparer, by pressing Post these entries, unless your firm has told XARA to post that client’s entries on its own. |
| Sending the pack | XARA builds it and files the final. A person at your firm sends it. |
| Paying | Your client’s payer releases every payment in BILL. In the books, XARA enters what was paid. |
| Anything sent to a client or vendor | XARA drafts it. A person at your firm reads it and sends it. |
| Approving a bill | The people who approve bills at your client and your firm. |
| Where a vendor is paid | A vendor’s bank details and AutoPay stay as your client set them. |
| Who has access | Your firm adds XARA as a user and can remove it at any time. XARA adds nobody. |
| An earlier month | XARA posts in a closed month only on your word. |
| A reconciliation that won’t tie | XARA tells you the difference. An adjustment to force it is yours alone. |
AutoPay, in that list, is BILL’s setting for paying a vendor automatically.
The right client, every time
Before XARA changes anything, its computer reads the company named on the page. It works in a client’s books only while the software shows that client. On any other page it looks and does nothing more.
Held in code
These are checks in XARA’s code, and they hold whatever anyone types to it. Its computer reads every button before pressing it, once in its own software and again inside the page itself.
Here’s the foot of BILL’s Enter a bill page on Cottonwood Creek Mechanical LLC, our test company. Create & next saves the bill and opens the next one, and that’s the button XARA presses. Review & pay, beside it, is the payer’s.

XARA’s role in BILL would let it approve a bill. Its own code keeps approving with your people regardless, so the line holds on its own and owes nothing to a permission setting.
When it needs you
XARA asks one clear question and keeps working on everything else. The line in question waits in the client’s holding account until someone answers, and the question reaches you in the chat, the console and your email. If XARA can’t back up an entry, it adds it to the month’s open items, and your preparer gets them all at once.
What does Cottonwood Creek need from me?
Next, see how you can check all of it in Watching and replaying.