An outside bookkeeper usually needs a reliable way to see or receive sales, payment, refund and settlement records for the month—not the ability to change menus, payment settings or staff accounts. The right arrangement may be a restricted, time-limited login, or it may be reports exported by a restaurant manager. Choose the method that supplies the records needed for reconciliation without giving away unnecessary control.
Start by naming one person at the restaurant to own access. That person agrees on the close schedule with the bookkeeper, checks what the software can actually restrict, and removes access when the work is done. The owner may take that role, or a trusted manager may handle the monthly process.
Decide what the bookkeeper needs to reconcile
Ask the bookkeeper to describe the reconciliation before choosing permissions. Typically, the job is to compare recorded sales and adjustments with payment activity and the amounts deposited by payment providers. A sales total alone may not explain the difference between transactions recorded on a busy weekend and money that reaches the bank later.
Agree on the reporting period and the records needed for each payment channel. The bookkeeper may ask for sales by payment method, refunds and voids, payment processor statements, deposits and details of unusual adjustments. They may also need an order-level record to investigate a mismatch. Ask which fields are essential and whether a summary is enough for routine work.
Keep the measures distinct. Sales are transactions recorded by the restaurant; deposits are transfers into a bank account. A processor statement may show fees or timing differences that help explain why the figures differ. Whether a particular report presents those details is a question for the vendor and the payment provider.
Service conditions can change the access decision. A bookkeeper working once a month may be well served by a manager’s export. Someone resolving exceptions throughout the month may need a more direct way to retrieve records. Multiple locations, separate payment accounts or a short close deadline can increase the work of assembling reports. Ask whether the bookkeeper needs each location separately and who can supply records from systems outside the restaurant platform.
Build a monthly-close access worksheet
Use the worksheet below to agree on the minimum handoff. The records and decisions in it are hypothetical; they illustrate a single restaurant with one outside bookkeeper. They do not describe Fleksa’s export or permission options.
| Close task | Record or access needed | Owner | Restriction or check |
|---|---|---|---|
| Prepare monthly sales | Sales by date and payment method, plus refunds and voids | Manager | Confirm the period and whether adjustments appear in the report |
| Match payment activity | Processor statements and deposit records | Owner | Provide separately if they are not in the restaurant software |
| Investigate a difference | Relevant transaction details or a manager-supplied extract | Bookkeeper requests; manager supplies | Limit the request to the period and records needed |
| Close access | Expiry date or confirmation that shared files are no longer needed | Owner | Check access after the deadline and record the result |
For this restaurant, suppose the bookkeeper needs reports for the previous calendar month by the fifth business day. The manager prepares the sales records, and the owner supplies processor and deposit records from the relevant accounts. The bookkeeper flags any difference and asks the manager for specific transactions rather than receiving broad access to every operational screen.
The owner’s decision is to start with manager-supplied files. The bookkeeper works only at month-end, and the manager can provide the agreed records on time. If repeated follow-up requests make that handoff too slow, the owner can revisit a restricted login after checking exactly what it permits.
Before adopting the worksheet, ask for a sample sales report and compare its fields with the bookkeeper’s checklist. Ask which file formats are available, whether the date range can be selected, and whether an export includes transaction details as well as totals. Do not assume that a screen view can also be downloaded.
Compare the access approaches
Manager-supplied reports. A restaurant employee retrieves the agreed records and sends them through a method both parties have approved. This gives the restaurant a clear review point and avoids an outside login. It also takes staff time every month, especially when the bookkeeper needs follow-up details. Ask how the recipient will receive files securely and how long each party needs to retain them.
Restricted outside-user login. If the vendor supports an appropriate role, the bookkeeper may be able to retrieve needed records without waiting for a manager. The benefit depends on the actual boundaries: can the user view the right reports, export the required data, and do neither more nor less than the job requires? A reports-only label is not enough; inspect the individual actions. Also ask whether access can expire automatically or must be removed manually.
Shared account access. Avoid giving an outside bookkeeper a manager’s credentials. Sharing makes it harder to tell who performed an action and complicates removal when the engagement ends. If the only practical login has broad operational powers, use a manager-supplied handoff while looking for a better arrangement.
Compare the approaches on staff effort, guest impact and cost together. A manager export puts work on the restaurant but can happen outside service. A direct login may reduce requests to staff, but an overly broad account could allow changes that disrupt ordering or reservations. Ask whether an additional user, location, report or export carries a charge, and obtain a written quote for the exact setup. Quoted subscription or access charges are not the whole operating cost: include staff preparation time and any separate processor or accounting-tool charges in your comparison.
For Fleksa, consult the plans page for current pricing; pricing details were checked in November 2026. Confirm the price and availability of any particular setup before relying on it. The relevant choice is the total operational quote and workload for the records you need, not simply the lowest listed plan price.
Test expiry and restrictions before choosing
Write down the expected result before testing. For a restricted login, the minimum pass is that the bookkeeper can reach the agreed records during the access window, cannot change operational settings, and cannot sign in after access has been removed or has expired. Treat a missing export or a broader-than-agreed setting as a failure for that proposed setup, even if the user can see the sales totals.
Ask the vendor for a safe demonstration or test environment. Use a test account and simulated records where available. A practice check must not trigger a real payment, guest message or courier dispatch, and it must not change live menus, payment settings or service controls.
- Check the permitted work. During the access window, have the test user open the agreed report and, if required, attempt a sample export. Record the date range, fields and file format. Pass only if the bookkeeper can obtain the agreed information.
- Check the boundary. Attempt to open or initiate a change to an operational setting in the test environment, such as a menu or payment configuration. The expected result is that the action is unavailable or denied. Record the screen or denial message without submitting a live change.
- Check the end of access. Set an expiry if supported, or have the owner remove the test user at the agreed time. Afterward, attempt to sign in again. Pass only if access is denied. Record who removed it, when, and what happened on the later attempt.
- Check the fallback. If the user cannot get an essential record without broader powers, have the manager retrieve that record instead. Confirm the handoff can meet the close deadline.
Save a short access record with the role, approved reports, start and end dates, test results and the person responsible for removal. Review the vendor’s permissions with those requirements in hand, but verify the specific actions in the proposed account. Also ask what happens to previously downloaded files: ending a login does not itself retrieve a copy already shared with the bookkeeper.
If there is no safe test environment, ask the vendor to demonstrate the controls without changing live operations. A live service pilot is a separate decision: schedule it only after the access boundary is acceptable, give staff a fallback for the close, and monitor ordinary work without creating artificial guest transactions.
Set the handoff and review date
Put the arrangement in writing: who prepares each record, where it goes, when it is due, how exceptions are requested and who confirms access removal. For a file-based process, agree on a secure transfer method and a contact for a missing or incorrect report. For a login, agree on the access window and a manual removal owner even if automatic expiry is offered.
After the first close, ask the manager and bookkeeper what caused delays. A repeated request for the same detail may justify adding a field to the regular handoff. A request to alter settings is a reason to keep that action with authorized restaurant staff, not to expand the bookkeeper’s role by default. Consult a qualified adviser when contract, legal or tax treatment needs interpretation.
Compare this workflow with your current process, then ask Fleksa to demonstrate the applicable reporting and access controls for your restaurant management software setup.
Frequently asked questions
Does an outside bookkeeper need a restaurant software login?
Not always. If a manager can provide complete records on time and handle follow-up requests, a file-based handoff may be sufficient. Consider a restricted login when the work requires direct access and the available controls meet your requirements.
Which reports should a bookkeeper receive?
Agree on the list with the bookkeeper. It may include sales by period and payment method, refunds and voids, processor statements and deposit records, plus transaction details needed to resolve differences.
What if the software cannot automatically expire access?
Assign an owner to remove the user at a documented deadline and attempt a sign-in afterward to confirm removal. If that process or the available restrictions are not acceptable, use manager-supplied records instead.
