The short version
You have audited financial statements that tie out cleanly, a report you can submit by your deadline, and a request list that felt predictable instead of endless.
We’ll start by locking down the PBC request list and timeline so you know exactly what we’ll ask for and when. You’ll end up with audited financials you can hand over with confidence, and an audit that keeps moving even when support is missing. Next is a short planning call to confirm timing and key contacts.
We run audits in a way that keeps your close files usable instead of turning into a scavenger hunt. We send the PBC list early, tie it to a due-date calendar, and tell you which items drive the most testing. If something is missing, we label it, offer options, and keep fieldwork moving while you track it down.
About us
We’re a two-person audit team that focuses on financial statement audit work for organizations that do not have time to learn auditing while also closing the books. Elena Morales leads each engagement and signs the report. Gavin Brooks runs day-to-day fieldwork and keeps the PBC list, questions, and open items in one place you can track.
People pick us when they want an audit that stays organized and says the quiet part out loud. We flag the high-effort areas early, so you can line up support before we arrive. We also keep our questions tied to a test and a purpose, so you are not guessing why we are asking. When an item is missing, we give you practical paths forward instead of a stalled audit.
Who you will work with
You’ll work with the same two people from planning through report release, so questions get answered by the person doing the work.
Team
Elena Morales, Engagement partner. Elena is the engagement partner. She sets audit strategy, reviews key areas, clears final notes, and signs the report.
Gavin Brooks, Audit manager. Gavin is the audit manager. He runs fieldwork, keeps the PBC list moving, and tells you what we need next and what can wait.
Selected work
These are a few recent financial statement audit and assurance engagements that show the kinds of deadlines, records, and stakeholders we’re used to working with.
Portfolio
Contractor audit closeout. Year-end books were closed, but schedules were inconsistent across jobs and cost codes. We rebuilt the PBC list around the job-cost system, tested a targeted sample, and issued on time for the bank renewal.
Nonprofit grant audit. The grantor needed audited financials plus support for major program expenses. We planned around the submission date, tested the largest vendors first, and cleared questions while the finance team kept month-end moving.
First-time reviewed statements. A new board requested assurance, but the close package was still evolving. We ran a readiness pass, fixed the highest-risk gaps, then completed the engagement without a late-cycle scramble.
“They told us what they needed early, and nothing surprised us in fieldwork.”
Controller, a mid-sized contractor
How we work
On one recent contractor engagement, the close file existed but the support lived in too many places, and the bank deadline was fixed. We started with a readiness pass, rebuilt the PBC list around the general ledger and job-cost reports, and assigned an owner and due date to each item. During fieldwork we tested revenue and costs using a focused sample tied to the biggest projects, so the team was not pulling support for low-risk items. The audit report was released 10 days before the bank package was due, and we reduced the open-item list from 64 items at kickoff to 6 items by the end of the second fieldwork day.
1. PBC list and timing Week 1 We send the initial PBC request list and a simple timeline with due dates. You tell us who owns each area, and we adjust the list to match how your close files are actually organized. We also call out the items that drive the most testing, so you can start there. 2. Risk and planning Week 2 We set materiality, plan the high-risk areas, and confirm the sampling approach so there are no surprises during fieldwork. We ask a short set of questions about revenue, cash, debt, and any unusual transactions, and we confirm your reporting deadline and review dates. 3. Fieldwork and testing Weeks 3-4 We perform walkthroughs, select samples, and test balances and disclosures. We keep an open-items list that shows what is pending, who is working on it, and what we can do next while an item is being located. We schedule short daily check-ins while we are actively testing. 4. Wrap and report release Week 5 We clear partner review notes, tie out the draft report to the final numbers, and confirm management’s review points. If a late item affects the financials, we show you exactly what it changes and what else it touches. Once everything ties out, we release the final report package.
What it costs
These fees cover the five-week timeline shown above and the standard audit steps for each option. We’ll confirm the final fee once we’ve seen your year-end trial balance and PBC readiness.
Priced items
Getting started
Everything below is what you’ll have in hand at the end of the engagement, plus the working structure we use to keep the audit predictable.
1. A PBC request list tailored to your close file and systems 2. An agreed audit timeline with due dates and points of contact 3. Planning decisions: materiality, key risks, and the testing approach we’ll use in the financial statement audit filework set-up (GAAS) and audit fieldwork completion and documentation (GAAS) and audit manager-driven sampling and testwork schedules and partner review notes cleared and final audit report tie-out and release package includes audited financial statements and independent auditor’s report
Signature
Fee summary
Payment
To book the work, you’ll pay 30% of the price when you sign. The remaining 70% is due when the engagement is complete. Each invoice is payable within 14 days of its date.
What we need from you. We’ll send the PBC list and a due-date plan in Week 1. You’ll get the smoothest fieldwork week when items are uploaded by those dates and one point person answers follow-ups within one business day.
Schedule and availability. We’ll hold Weeks 1 through 5 once the booking payment is in and we have your main deadline. If your board or bank date moves, tell us as soon as you know so we can adjust the fieldwork window.
Changes in scope. If the records or reporting needs change after planning, we’ll spell out what changed, what extra work it adds, and the fee impact before we do the extra work. Nothing rolls in silently.
Missing support
If a requested item can’t be produced, we’ll ask for an alternate support option first. If there isn’t one, we’ll explain the audit impact in plain terms, including any report wording or timing risk.
Access for fieldwork. For Weeks 3 and 4, we’ll need access to your general ledger detail, support schedules, and the people who can explain unusual items. We’ll keep questions in one running list so you can batch replies.
Workpapers and final reports. You’ll receive the final issued report at the end of Week 5 once review notes are cleared and the tie-out is complete. Our workpapers stay with us; you’ll keep your records and the support you provide.
