Who this page is for
This page describes how remote accounting and audit-support work is organised once you have a file in front of you. It is written for freelance accountants and CPAs who work on files that belong to another firm, and for accountants qualified elsewhere who work on US files.
Labels used across this section: US rule means a requirement from a US body (the AICPA, the IRS, the FTC). Country-neutral means practice that holds wherever you sit. Check your own regulator means your home licensing body or tax authority may have its own rule, and you should read it there. This page is general information, not legal or tax advice.
What the work is
Remote work for a firm usually falls into a handful of task types.
- Bookkeeping cleanup: coding, correcting and catching up a client's books before anyone prepares statements from them.
- Reconciliations: bank, credit card and sub-ledger to control account.
- Month-end close support: accruals, prepaids, schedules and a close checklist.
- Audit file preparation: building schedules, tying them to the trial balance, referencing evidence, and writing the procedure and result for each area.
- Review and compilation file preparation: the work behind a review or compilation under the AICPA's SSARS, which has different documentation than an audit.
- Tie-out and workpaper review: checking that statements, notes and schedules agree, and that each workpaper stands on its own.
- Confirmations handling: tracking requests and replies and following up exceptions.
You prepare, check and document. The firm's engagement partner or report signer decides what the firm concludes and signs. Under the AICPA's quality management standard for audits, the engagement partner takes responsibility for the direction and supervision of the engagement team and the review of its work (AU-C 220.29), and reviews documentation of significant matters and judgments (AU-C 220.31). Your work feeds that review. It does not replace it.
How a file moves
A typical file has six stages, whatever the work type.
- Intake. The firm offers a file with a scope: which entity, which period, which areas, which deliverable, when the next review point is.
- Start checks. Before you open client data you decide whether you can take the file: independence, conflicts, competence for the task, and the confidentiality terms you will work under. The per-file start checklist in this section lists the questions.
- Set-up. You read the prior-year file if there is one, the scope note, and any instructions on indexing and referencing. You note questions before you start, not at the end.
- Work. You perform each procedure, record it as you go, and keep a running list of open items.
- Review cycle. A reviewer reads your work and sends notes. You clear each one with evidence and a short reply, and the reviewer decides when it is cleared.
- Close. Open items are resolved or handed over in writing, the file is complete and indexed, and your access ends according to the agreement.
The point of writing it out this way is that every stage leaves a trace. A remote contributor has no hallway conversation to fall back on, so what is not written down did not happen.
What a working day looks like
Hours and tools vary by person, so this section describes order of work, not a schedule.
Start with messages and review notes from the previous day, because a note that blocks someone else's work comes first. Then take the next piece of work on the open-items list. Finish one procedure fully, including the reference to evidence, before starting the next. Write each workpaper while the detail is fresh: the standard for audit documentation says it should be prepared on a timely basis (AU-C 230.07) and the explanatory material adds that documentation prepared when the work is performed or shortly after is likely to be more accurate (AU-C 230.A3). End the day with a short status line to your point of contact: what is done, what is blocked, what you need.
The rules that shape how you work
Documentation (US rule)
For an audit, AU-C 230 requires documentation sufficient for an experienced auditor with no previous connection to the audit to understand the nature, timing and extent of procedures performed, the results and evidence obtained, and significant findings, conclusions and judgments (AU-C 230.08). It must also record the identifying characteristics of items tested, who performed the work and when it was completed, and who reviewed it and the date and extent of the review (AU-C 230.09). The final audit file is assembled no later than 60 days after the report release date (AU-C 230.16) and is retained for at least five years from that date (AU-C 230.17).
For SSARS engagements the documentation minimums differ. A compilation file includes the engagement letter or other written agreement, a copy of the financial statements and a copy of the report (AR-C 80.40). A preparation engagement has similar minimums (AR-C 70.22). A review file must let an experienced accountant with no connection to the review understand the procedures, the evidence obtained, and significant matters (AR-C 90.137).
Confidentiality (US rule)
AU-C 230.19 requires the auditor to adopt reasonable procedures to maintain the confidentiality of client information. As a contributor you meet that requirement in practice by working only where the firm says you may, keeping client data out of personal accounts and devices, and not sharing it with anyone the firm has not cleared.
Ethics and independence (US rule)
The auditor must comply with relevant ethical requirements (AU-C 200.16). The AICPA's explanatory text describes independence as covering both fact and appearance and points to the Code's Conceptual Framework for Independence (ET 1.210.010). The independence rules for an audit are set at the engagement level, so they apply to the file you are touching and not only to you as a person. In SSARS work, a compilation requires the accountant to determine whether they are independent (AR-C 80.07) and a review requires independence, with withdrawal if it is impaired (AR-C 90.10). A preparation engagement does not require an independence determination (AR-C 70.03). Run the per-file independence check before each file, even when you have worked for the firm before.
Tax return information (US rule)
If a file contains tax return information, section 7216 of the Internal Revenue Code and its regulations can restrict how it is used and disclosed by tax return preparers. The regulation at 26 CFR 301.7216-3 requires consent that is knowing and voluntary, in writing, signed and dated, naming the parties and purpose, and it cannot be obtained retroactively. It also provides that, for Form 1040 series filers, a US-based preparer generally cannot obtain consent to disclose a Social Security number to a preparer located outside the United States unless an adequate data protection safeguard is in place. Whether the rule reaches your task depends on whether you are assisting in preparing returns. Raise the question with the firm at intake, not after you have opened the data.
Data security (US rule)
The IRS tells tax professionals that federal law gives the FTC authority to set data safeguard regulations, including for professional tax return preparers, and that the FTC Safeguards Rule requires a written security plan (Publication 4557). The rule itself lists the elements, among them access controls, encryption of customer information in transit and at rest, multi-factor authentication, secure disposal, monitoring, training, oversight of service providers and an incident response plan (16 CFR 314.4). A firm may treat a freelancer as a service provider under its own program. Read what the firm's agreement asks of you, and follow Publication 4557's basics regardless: anti-malware on all devices, strong unique passwords with a password manager, multi-factor authentication, encrypted files and drives, backups kept off the network, no public wireless for client work, and a secure VPN for remote access to a firm network.
Tools
You will need a way to receive files, a way to record work, a way to talk, and a way to track your own time and open items. The firm often dictates the first two. The tools page in this section covers what to look for and what to avoid, without naming products.
Communication
Three habits carry most of the weight: say what you did and did not do, ask early with the specific item and what you already checked, and put every decision in writing. The communication page covers templates for each. AU-C 230 also asks for documentation of discussions of significant findings with management and others, including when and with whom (AU-C 230.11), so a short written record of a call is part of the work.
Common mistakes
- Starting without a scope note, then discovering halfway that the area was out of scope.
- Reconciling to the wrong source: the client's list rather than the third-party statement.
- Leaving a tick mark unexplained, so the reviewer cannot tell what it means.
- Clearing a review note with "done" and no reference to the evidence.
- Saving a client file to a personal folder "just for today".
- Treating a difference you cannot explain as immaterial without telling the reviewer.
When a file stalls
Files stall for ordinary reasons: a client document is late, a question has no owner, a reviewer is away. Handle a stall the same way each time. Write down what is blocked and since when, name who can unblock it, state what you will do in the meantime, and give a date on which you will raise it again. Move to another part of the file only if the scope allows it and the firm knows. Do not fill a gap with an estimate and present it as support. A short, dated entry in the workspace beats a long message sent late, and it gives the reviewer a clear trail if the timetable moves.
FAQ
Do I need a licence to do this work?
It depends on the task and the state. Preparing schedules and checking tie-outs under a licensed person's supervision is treated differently from signing a report. The state board of accountancy is the source, and the licensure pages in this section explain how to read the board's rules. If you work from another country, check your own regulator as well.
Does the firm or the freelancer own the workpapers?
The agreement and the professional standards answer this, and the contracts pages explain what to look for. Do not copy a file out of the firm's workspace unless the agreement says you may.
Who signs the report?
The firm. A contributor prepares or checks work; the person who signs is responsible for the engagement. Describe your role accurately, as "prepared", "tied out" or "reviewed", and never imply you signed or issued anything.
What changes between audit and SSARS files?
The assurance level and the documentation. An audit rests on sufficient appropriate evidence; a review rests mainly on analytical procedures and inquiries (AR-C 90.04); a compilation does not require verifying management's information (AR-C 80.02). Check which engagement type each file is before you decide how much support to attach.
Sources
- AICPA, AU-C Section 230, Audit Documentation (AU-C sections, currently effective): https://www.aicpa-cima.com/resources/download/aicpa-statements-on-auditing-standards-currently-effective
- AICPA, AU-C Section 220, Quality Management for an Engagement Conducted in Accordance With GAAS (same download): https://www.aicpa-cima.com/resources/download/aicpa-statements-on-auditing-standards-currently-effective
- AICPA, SSARS AR-C sections 70, 80 and 90 (currently effective): https://www.aicpa-cima.com/resources/download/aicpa-ssarss-currently-effective
- IRS, Publication 4557, Safeguarding Taxpayer Data (Rev. 6-2024): https://www.irs.gov/pub/irs-pdf/p4557.pdf
- eCFR, 16 CFR 314.4, Elements (FTC Safeguards Rule): https://www.ecfr.gov/current/title-16/part-314/section-314.4
- eCFR, 26 CFR 301.7216-3, Disclosure or use permitted only with the taxpayer's consent: https://www.ecfr.gov/current/title-26/part-301/section-301.7216-3